linuxmemes

20880 readers

7 users here now

I use Arch btw

Sister communities:

LemmyMemes: Memes
LemmyShitpost: Anything and everything goes.
RISA: Star Trek memes and shitposts

Community rules

Follow the site-wide rules and code of conduct
Be civil
Post Linux-related content
No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago

MODERATORS

[email protected]

212

Matt Parker's take on Linux (lemmy.world)

submitted 3 months ago by [email protected] to c/[email protected]

42 comments fedilink hide all child comments

Clip from Stand-up Maths video https://youtu.be/pgyI8aPctaI?t=75

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 3 months ago (2 children)

updates that don't require a restart

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.

[–] [email protected] 10 points 3 months ago* (last edited 3 months ago)

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.

[–] [email protected] 4 points 3 months ago

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