archwiki
opi
Our great sponsors
archwiki | opi | |
---|---|---|
268 | 51 | |
141 | 221 | |
2.1% | 3.6% | |
7.2 | 8.8 | |
17 days ago | 3 months ago | |
PHP | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
archwiki
-
Get People Interested in Contributing to Your Open Project
Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.
-
Archlinux wiki
Since we also modified the MediaWiki Sourcecode you can find our fork here: https://github.com/archlinux/archwiki
What would you expect to find in that repo? The underlying software for wiki.archlinux.org is mediawiki and that is not based on git.
-
Hyprland 0.29.* causing trouble after a few days of working fine (on archbtw)
-------------------------------------------- Hyprland Crash Report -------------------------------------------- I tried so hard, and got so far... Hyprland received signal 11 (Segmentation fault) Version: 0a78f6031c8fcc6773f136fccde3d560aaac239d Tag: v0.29.0 System info: System name: Linux Node name: nah Release: 6.4.12-arch1-1 Version: #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) os-release: NAME="Arch Linux" PRETTY_NAME="Arch Linux" ID=arch BUILD_ID=rolling ANSI_COLOR="38;2;23;147;209" HOME_URL="https://archlinux.org/" DOCUMENTATION_URL="https://wiki.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/" LOGO=archlinux-logo Backtrace: #0 | Hyprland(_Z12getBacktracev+0x62) [0x55644d617522] ?? ??:0 #1 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x42c) [0x55644d5f203c] ?? ??:0 #2 | Hyprland(_Z25handleUnrecoverableSignali+0x47) [0x55644d5893d7] ?? ??:0 #3 | /usr/lib/libc.so.6(+0x3e710) [0x7f350243e710] ?? ??:0 #4 | /usr/lib/libwlroots.so.12032(+0x516a2) [0x7f35030676a2] ?? ??:0 #5 | /usr/lib/libwlroots.so.12032(+0x4f659) [0x7f3503065659] ?? ??:0 #6 | /usr/lib/libwlroots.so.12032(+0x54d55) [0x7f350306ad55] ?? ??:0 #7 | /usr/lib/libwlroots.so.12032(+0x5689e) [0x7f350306c89e] ?? ??:0 #8 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f3502fcd01e] ?? ??:0 #9 | /usr/lib/libseat.so.1(+0x30ca) [0x7f3502a870ca] ?? ??:0 #10 | /usr/lib/libsystemd.so.0(+0x2a675) [0x7f350315c675] ?? ??:0 #11 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #12 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #13 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #14 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #15 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #16 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #17 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #18 | /usr/lib/libsystemd.so.0(+0x2a56d) [0x7f350315c56d] ?? ??:0 #19 | /usr/lib/libsystemd.so.0(+0x2a59b) [0x7f350315c59b] ?? ??:0 #20 | /usr/lib/libsystemd.so.0(+0x2a50b) [0x7f350315c50b] ?? ??:0 #21 | /usr/lib/libsystemd.so.0(+0x2a70f) [0x7f350315c70f] ?? ??:0 #22 | /usr/lib/libsystemd.so.0(+0x48268) [0x7f350317a268] ?? ??:0 #23 | /usr/lib/libsystemd.so.0(+0x4fce7) [0x7f3503181ce7] ?? ??:0 #24 | /usr/lib/libseat.so.1(+0x36de) [0x7f3502a876de] ?? ??:0 #25 | /usr/lib/libwlroots.so.12032(+0x4d127) [0x7f3503063127] ?? ??:0 #26 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xa2) [0x7f3502fceae2] ?? ??:0 #27 | /usr/lib/libwayland-server.so.0(wl_display_run+0x27) [0x7f3502fcf2d7] ?? ??:0 #28 | Hyprland(main+0x8d9) [0x55644d577dd9] ?? ??:0 #29 | /usr/lib/libc.so.6(+0x27cd0) [0x7f3502427cd0] ?? ??:0 #30 | /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f3502427d8a] ?? ??:0 #31 | Hyprland(_start+0x25) [0x55644d586735] ?? ??:0 Log tail: [LOG] Callback 5564501935d0 -> 5564501935c8, Keyboard removed. [LOG] Destroyed keyboard 5564501934d0 [LOG] Callback 55644fd2f938 -> 55644fd2f930, Keyboard removed. [LOG] Callback 55644fd2f800 -> 55644fd2f7f8, Keyboard removed. [LOG] Callback 55644fd2f868 -> 55644fd2f860, Keyboard removed. [LOG] Callback 55644fd2f8d0 -> 55644fd2f8c8, Keyboard removed. [LOG] Destroyed keyboard 55644fd2f7d0 [LOG] Callback 556450074a38 -> 556450074a30, Keyboard removed. [LOG] Callback 556450074900 -> 5564500748f8, Keyboard removed. [LOG] Callback 556450074968 -> 556450074960, Keyboard removed. [LOG] Callback 5564500749d0 -> 5564500749c8, Keyboard removed. [LOG] Destroyed keyboard 5564500748d0 [LOG] Callback 5564500874f8 -> 5564500874f0, Mouse removed. [LOG] Callback 5564501cc9d8 -> 5564501cc9d0, Keyboard removed. [LOG] Callback 5564501cc8a0 -> 5564501cc898, Keyboard removed. [LOG] Callback 5564501cc908 -> 5564501cc900, Keyboard removed. [LOG] Callback 5564501cc970 -> 5564501cc968, Keyboard removed. [LOG] Destroyed keyboard 5564501cc870 [LOG] Callback 55644fcf59e8 -> 55644fcf59e0, Mouse removed. [LOG] Callback 5564500bf3f8 -> 5564500bf3f0, Keyboard removed. [LOG] Callback 5564500bf2c0 -> 5564500bf2b8, Keyboard removed. [LOG] Callback 5564500bf328 -> 5564500bf320, Keyboard removed. [LOG] Callback 5564500bf390 -> 5564500bf388, Keyboard removed. [LOG] Destroyed keyboard 5564500bf290 [LOG] Callback 55644f3bc2b8 -> 55644f3bc2b0, Mouse removed. [LOG] Callback 55645003b3a8 -> 55645003b3a0, Keyboard removed. [LOG] Callback 55645003b270 -> 55645003b268, Keyboard removed. [LOG] Callback 55645003b2d8 -> 55645003b2d0, Keyboard removed. [LOG] Callback 55645003b340 -> 55645003b338, Keyboard removed. [LOG] Destroyed keyboard 55645003b240 [LOG] Callback 55644ff5f058 -> 55644ff5f050, Mouse removed. [LOG] Callback 5564500e9108 -> 5564500e9100, Keyboard removed. [LOG] Callback 5564500e8fd0 -> 5564500e8fc8, Keyboard removed. [LOG] Callback 5564500e9038 -> 5564500e9030, Keyboard removed. [LOG] Callback 5564500e90a0 -> 5564500e9098, Keyboard removed. [LOG] Destroyed keyboard 5564500e8fa0 [LOG] Callback 556450206068 -> 556450206060, Keyboard removed. [LOG] Callback 556450205f30 -> 556450205f28, Keyboard removed. [LOG] Callback 556450205f98 -> 556450205f90, Keyboard removed. [LOG] Callback 556450206000 -> 556450205ff8, Keyboard removed. [LOG] Destroyed keyboard 556450205f00 [LOG] Callback 556450067b70 -> 556450067b68, SwitchDevice removed. [LOG] Callback 556450067b08 -> 556450067b00, SwitchDevice removed. [LOG] Callback 55644fe495e8 -> 55644fe495e0, Tablet removed. [LOG] Callback 55644fe49580 -> 55644fe49578, Tablet removed. [LOG] Callback 55644fe49518 -> 55644fe49510, Tablet removed. [LOG] Callback 55644fe494b0 -> 55644fe494a8, Tablet removed. [LOG] Callback 55644fe49448 -> 55644fe49440, Tablet removed. [LOG] Removed a tablet [LOG] Session got activated!
-
Windows 11 has made the “clean Windows install” an oxymoron
> spend hours on google to fix some crap
That's the Windows way. It's a bad fit for Linux, because there is no one true obsessively-backwards-compatible Linux.
The good news is we don't need it: Linux isn't a black box, so we don't need to guess or study its behavior. We can look it up instead. The goal here is to construct understanding from documentation, as opposed to deconstructing behavior from testing.
Some great starting points to get your bearings are:
- https://wiki.gentoo.org/wiki/Main_Page
- man pages
- hyprland crashing on launch
- debian is a good os if you don't value your time
-
Notetaking when solving issues and learning stuff
Yes, but... the advantage of the pure log method is you have a full record of what you've done. Depends on what you want. But definitely would be a waste of time trying to create a fully-organized personal wiki. Use ArchWiki instead.
- Fedora Docs (?)
-
Endeavour with Mulvad.
Me personally, I've found the EndeavourOS community to be very friendly and helpfull, the forums on the official site, as well as this Subreddit are great places to get help, when you're stuck, but also try the archwiki first - https://wiki.archlinux.org/ as Endeavour is Arch based this can be an invaluable resource.
opi
-
Do you guys have installed codec trough zypper or opi?
This is incorrect. It also installs a set list of packages.
You can see exactly what opi codecs does and what it installs here https://github.com/openSUSE/opi/blob/master/opi/plugins/packman.py
You can use opi codecs or opi pacman which will install all the codecs and stuff at once. This is the github that explains how to install individual items through opi if you prefer to limit what opi installs.
-
Following Fedora and openSUSE, Manjaro moves further away from Arch Linux by not enabling Mesa's patent-loaded codecs
Yeah I'm pretty sure it's using Packman https://github.com/openSUSE/opi
-
Something better than Arch?
Not sure how well it works since I'm not using it myself but you might check out opi. It is similar to AUR helper in the sense that it combines the different places to install panels from.
- what is opi, OBS and packman
-
Yast like tool for other distros?
You can use opi to install packages from OBS quite easily. Or use Yast and the ymp files you can download.
-
Just try it, it's glorious
The amazing tooling: - YaST, the best configuration tool out there. I think its fair to say that nothing comes close to the number of things you can configure with Yast. - Open Build Service (OBS), a tool that automatically builds binaries for software and sets up repositories to add to your favorite package manager. Supports every major linux distro but intergrates especially well with the openSUSE software store, and OPI (openSUSE equivelant to something like paru or yay) to be like the AUR but (imo) better. - openQA, Automated testing for any package or operating system, making sure that even on leading edge software, you're still stable. - snapper, out of the box btrfs snapshots that make sure you can (almost) always boot into a useable system, even after a bumpy update.
-
Arch vs openSUSE Tumbleweed: Pros & Cons?
It's important to note that just like the AUR has AUR helpers, the Opensuse build system also has helpers. Opi is a helper for the OBS.
-
OpenSUSE noob
OPI is useful for installing things that are difficult to find or aren't in the main repos.
What are some alternatives?
linux-tkg - linux-tkg custom kernels
flathub - Pull requests for new applications to be added
openSUSE-release-tools - Tools to aid in staging and release work for openSUSE/SUSE
dnfdragora - dnfdragora is a dnf frontend based on libyui abstraction
com.discordapp.Discord
web - ALG Website Source Code
slickstack - Lightning-fast WordPress on Nginx
tumbleweed-cli - Command line interface for interacting with Tumbleweed snapshots.
archweb - Arch Linux website code
scanmem - memory scanner for Linux
PhotoPrism - AI-Powered Photos App for the Decentralized Web 🌈💎✨
morph - NixOS deployment tool