this post was submitted on 11 Aug 2024
211 points (83.7% liked)
linuxmemes
21603 readers
725 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, 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'm a huge Linux fan but that wasn't my experience. My experience was apps getting borked by attempting to load the updated versions of libs and communicating with a half-updated system where they don't understand each other. For example with KDE I often had the experience that after updating packages, even the shutdown and similar buttons don't work in the start menu. They were doing nothing, and when I looked at system logs, I have seen some failure with starting that confirmation overlay with the countdown. But similar experience with Firefox too.
Somehow it does not happen on my laptop, even though I use the same distro and still KDE. But on the desktop it was predictably happening, and the worst part was that I was still new with how a desktop works (technically) on Linux so I could not even troubleshoot it, while the system was actively falling apart. By the way, I still don't know what the fuck was happening, or how would I diag it.
Upvoted because your experience is valid, but I will say that mercifully so far, I haven't had this issue personally. Instead, rather, my Windows 10 installation is basically broken because MS pushed an update that requires it to enlarge the recovery partition, but because there's another OS past the recovery partition, it can't. So whenever I use it now, I need to wait for it to try updating itself, recognize that it failed, and then undo the updates and boot again (the entire process takes 10+ minutes). I only use this partition for emergencies where something critical absolutely won't work on Linux, but it's still hilarious to me that this happened shortly after I abandoned ship.
Part of it will be because an uodate needs a restart of an app, a service or reboot(kernel) to actually update. People think the update finishing means everything is now running new code in memory, but it will hold old code till it is allowed to use the new stuff. Not sure on a deb system but with zypper ps -s it tells you exactly which packages are not running latest updated packages and need to be "released" before it can