this post was submitted on 19 Jan 2025
911 points (98.8% liked)

linuxmemes

22294 readers
699 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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 sudo in 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.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • Β 

    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 remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] spicytuna62 76 points 2 weeks ago* (last edited 2 weeks ago) (14 children)

    Windows: You got a kernel panic from an update just once this week? I went through two BSODs today!

    Mac: It'd happen more often if I actually had software! You get everything!

    Arch: While getting updates can cause crashes sometimes, new stuff is fun.

    Debian: You guys are getting updates?

    [–] Hiro8811 20 points 2 weeks ago (10 children)

    What? I never had an update break my system on Arch, even with nvidia proprietary drivers.

    [–] HatFullOfSky 6 points 2 weeks ago (1 children)

    I've had two instances in the past year on Purple Arch (Endeavor) where a kernel update "broke" my system. In both cases, the system still booted fine though, so not all definitions of "broken"may apply.

    The first time there was a bug with the kernel drivers for my wireless card which caused a component of Network Manager to lag out the entire UI to the point it was basically unresponsive trying to find a connection, but never did.

    The second time, it was a bug with the Vulkan drivers that caused all my games to crash within 60 seconds of starting up. Games are the main thing I use my PC for, so my system was effectively "broken", even though everything else was fine.

    I am of course not discrediting your fortune - I merely wanted to share

    [–] [email protected] 2 points 2 weeks ago (2 children)

    Yea, that is not your system broken, but just an package update that was faulty, and probably fixed with an update a few hours later, isn’t it?

    And you were able to role back such packages with yay/pacman, I suppose?

    [–] HatFullOfSky 2 points 2 weeks ago

    Yeah, kernel rollback fixed things no problem

    [–] [email protected] 1 points 2 weeks ago

    Is this how people can claim that Arch is stable, they just redefine breaking to exclude anything that might actually happen?

    load more comments (8 replies)
    load more comments (11 replies)