this post was submitted on 04 Jan 2025
870 points (97.3% liked)
linuxmemes
21736 readers
1295 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I use Arch BTW.
Today the liquidctl integration of cooler control died, making all my fans go into a safe profile which makes a lot more noise than normal. Imagine having to listen to that for an hour trying to get it working again. I did get it working luckily, somehow the coolercontrol-liqctld python module didn't register properly. Once I got the module registered everything was working, for now....
yea this is probably the most annoying issue i've had on Arch. every time there's a new version of Python, you'll need to reinstall some python packages, usually the AUR stuff.
https://wiki.archlinux.org/title/Python#Module_not_found_after_Python_version_update
Not gonna lie, I'm glad I've moved from Arch to Tumbleweed. Media codecs are handled worse somehow, but I haven't had to deal with crap like this ever since…
You have to add the source with the non free codec packages:
https://en.opensuse.org/SDB:Installing_codecs_from_Packman_repositories
I tried that already, didn't really help. That repo is currently deactivated on my machine, I think I had some (more) annoying problem with it (don't remember all the details), but after spending quite a few hours on this problem, I essentially gave up trying to fix it. Right now, video playback works well enough that I don't want to deal with it anymore.
And, honestly, I haven't had a Linux installation where everything related to multimedia and graphics drivers just worked flawlessly. Ubuntu, Debian, Arch and Suse all had different issues. Switching from Nvidia to AMD didn't help, either. Sometimes the flaws were minor and easy to ignore, but it has never ever worked as well as it does on Windows.
hmmm, did you try switching(vendor change) all system packages to pacman? (an option in the yast software installation module when you select the repository)
Best job with auto driver configuration (etc.) on most machines did endeavourOS for me. Just make sure to choose the correct vulcan / mesa packages while installing steam
I generally install steam as one of the first apps on most machines in order to get all the GPU dependencies sorted.
Is it that hard to roll back an update?
No, but depending on what's wrong that might not be the best thing to do. If the new version is broken, rolling back to a previous working version might fix it. But when the update broke something, it might not fix it and could even make it worse. I'd rather figure out what went wrong and how to fix it, it's a good skill to have. And if the new version does turn out to be broken, it's good to have dug into it so you can make a proper bug report.
I think I would rather just use something stable.
Luckily there is a distro for anyone. There's plenty of super stable distros out there. But if you want the cutting edge, stability will be comprised. And the cutting edge is pretty cool at the moment, so for me it's worth the issue once and again.
I use Fedora and it seems to provide a pretty good middle ground. I know some like to fix broken systems but for me I want something more recent without breakage. (I actually use Fedora Silverblue so I can easily roll back changes)