Hmmm… 🤔

    • normalexit@lemmy.world
      link
      fedilink
      arrow-up
      29
      ·
      2 months ago

      Well I updated my computer and my audio stopped working; to the logs! Lol I love Linux, but find myself asking “what now?” much more frequently with it…

      With windows it is more like “wtf is this new ad on my start menu?” Or “how can I opt out of all these features no one ever asked for?”

      • renzev@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        2 months ago

        One time an update broke audio, and I spent like 15 minutes digging around in pipewire logs and weird config parameters before I realized that I was literally just muted lol. Pulseaudio has irrevocably conditioned me to assume that whenever there is no audio, it must be some obscure bizzare weird issue instead of something simple

        • MonkeMischief@lemmy.today
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          This is definitely a thing!!

          We’re using Linux so we just assume it’s some highly technical issue right off the bat lol. This has caught me a few times. 😂

    • renzev@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 months ago

      btrfs subvolume snapshot / /snapshots/backup1 lol

      Won’t save you from a bricked bootloader tho haha

      • MonkeMischief@lemmy.today
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 months ago

        Once I manually deleted a snapshot folder because I didn’t see it listed, and thought it was “orphaned” and just taking up space. :D

        “SUDO THAT SUCKER!!” 👉

        OS says “Okie dokie boss.”

        Suddenly none of my commands are working.

        Turns out I deleted the currently mounted active snapshot . Safe to say it was reinstall time.

        Don’t go manually touching system files, folks. 😂

  • bob_lemon@feddit.org
    link
    fedilink
    arrow-up
    48
    arrow-down
    4
    ·
    2 months ago

    Other cures include literally just restarting your PC once a month so it can install updates.

    • Zorsith@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      13
      ·
      2 months ago

      Or disabling the stupid power settings that mean a shutdown isn’t a shutdown, and turning your computer off when not in use

      • DannyBoy@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        15
        ·
        2 months ago

        It’s hilarious that so many issues in Windows can be fixed with a restart but then they made it not actually restart when turned off and on again.

        • Gestrid@lemmy.ca
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 months ago

          My understanding (unless they’ve changed it) was that a restart is a restart because software (either the OS or 3rd party software or both) may need the computer restarted to finish installing or updating stuff.

          I’d heard that a shutdown wasn’t actually a shutdown, though.

    • twinnie@feddit.uk
      link
      fedilink
      arrow-up
      8
      arrow-down
      2
      ·
      2 months ago

      I mean, I use Linux but I’ve used a lot of Windows in the past. I don’t find either of them particularly more stable than the other. I had blue screens a few years ago on my laptop and that turned out to be faulty RAM. I haven’t had a Windows-caused BSOD in years. And all this talk of Windows suddenly starting an update while I’m using it, I’ve literally never had that happen.

    • TrickDacy@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      6
      ·
      2 months ago

      It’s windows. You’ll not have a choice in restarting at least once every couple of days.

  • Shard@lemmy.world
    link
    fedilink
    arrow-up
    31
    arrow-down
    2
    ·
    2 months ago

    Linux Syndrome:

    When nobody asked but somehow the solution is Linux.

    • renzev@lemmy.world
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      1
      ·
      2 months ago

      If you browse linux communities long enough, you eventually start seeing openbsd users who condescendingly speak about linux the same way some linux users speak about windows lol. It’s turtles all the way down!

      • Honytawk@lemmy.zip
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        2 months ago

        But this isn’t a linux community though, it is a meme community.

        The linuxmemes are on a different community.

  • PugJesus@lemmy.world
    link
    fedilink
    English
    arrow-up
    31
    arrow-down
    3
    ·
    2 months ago

    I haven’t seen a blue screen in years.

    Yes, Linux Preachers, I am a Windows user.

  • Sotuanduso@lemm.ee
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    5
    ·
    2 months ago

    Linux machines don’t crash unexpectedly, because if they do, it’s your fault for configuring it wrong and you should have expected it.

    • dch82@lemmy.zip
      link
      fedilink
      arrow-up
      19
      arrow-down
      2
      ·
      2 months ago

      Windows machines don’t crash unexpectedly because it’s Microsoft and you should have expected it.

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      2 months ago

      Or you just decided to update all your packages like a madman whilst not running on a Debian based distro

      • Ephera@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        Bruh, if a package update breaks something, I just roll back the BTRFS snapshot.

  • ooterness@lemmy.world
    link
    fedilink
    English
    arrow-up
    26
    ·
    2 months ago

    I saw that happen once in a big presentation.

    There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.

    I was only in the audience and I still have nightmares.

    • feddylemmy@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      2 months ago

      shutdown.exe -a should take care of situations like that. It’s not an excuse for taking away your options on the UI though.

      • ooterness@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 months ago

        Does that require admin access? It wasn’t their machine, it was one the school provided for the auditorium.

        • feddylemmy@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          2 months ago

          By default a normal user can abort the shutdown. They could also configure group policy to prevent shutdown permissions which also prevents aborting a shutdown.

          The GPO is Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Shut down the system.

      • Honytawk@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2 months ago

        What about all those update skippers that start complaining to Microsoft when their system breaks because they don’t understand that updates are crucial for a good running system?

        I get why Microsoft forces it now on the Home editions.

    • halcyoncmdr@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      2 months ago

      Greyed out options like that almost always mean the person has been hitting cancel or delay for several warnings already.

    • Matriks404@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      2 months ago

      I don’t want to be that guy, because I still hate Windows, but… most people who have these problems just didn’t set up updates properly. Well, that, or they never restart their computer.

    • Laser@feddit.org
      link
      fedilink
      arrow-up
      9
      ·
      2 months ago

      Blue screens were much more common back in the day, I guess nowadays they’re equally stable. Windows current issues are the deliberate choices Microsoft makes

    • EddoWagt@feddit.nl
      link
      fedilink
      arrow-up
      8
      ·
      2 months ago

      I currently have a memory or CPU issues (I have not investigated), which causes my windows install to lag out for a second, but my Linux install just completely crashes the entire system

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      I have crashed Linux before. On a Raspberry Pi. I was fucking around with some electronics on a breadboard, hooking them up to the GPIO pins while the thing is running like a dunce, and a male jumper wire connected to Vcc got away from me and dragged across the circuit board near the SoC.

      It came back up after I power cycled the board. I’ve otherwise never actually crashed Linux. I’ve crashed software running on Linux, sure, but I’ve never seen a kernel panic in 10 years of penguin flavored computing.

    • I Cast Fist@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      For a while, Linux Mint was significantly less stable than Windows 10 on my previous laptop. Worse, sometimes the system crash would freeze *everything, where it wouldn’t even let me do the CTRL ALT F1 to get a basic shell, so the only solution was a full power off/on

      • MonkeMischief@lemmy.today
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        That is painful. It’ll work SO WELL on a bunch of systems but sometimes someone has a particular config that’ll throw monkey-wrenches all over. It always feels like the most rotten luck being on the other end of that huh? :(

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    26
    arrow-down
    7
    ·
    2 months ago

    Windows user here. I don’t have a fear of BSODs.

    On the other hand, I have “Linux users are elitist jerks” syndrome, which stops me from switching to Linux, due to a fear of Linux users might be elitist jerks. This can be only cured by massive improvements to the Linux community, and a debugger that has an actual GUI for Linux (no, I don’t care about whatever cute little script you’ve written for GDB for a semi-automated testsuite for command line utility that converts one obscure format into another).

    • MonkeMischief@lemmy.today
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      2 months ago

      “Linux users are elitist jerks”

      Elitist jerks are elitist jerks. Ever talked to a stuck-up Windows I.T admin? The constant scoffing is unreal.

      What about people rich (or financially goofy) enough to obsess with Apple products?

      I think most community people regardless of OS just wanna be helpful and enthusiastic. (I like the word “enthusiast” haha) You’ll always find elitists around topics that involve learning skills and mastery.

      I dunno, I’m just happy sometimes people care here when I enthusiastically ramble to them about all their Linux-y choices they can solve problems with lol. We’re not all like that.

      Jerks just stick out more. Don’t let them tint your opinion of an entire community. I managed to even enjoy ranked League of Legends for a short while because I didn’t assume everyone was out to attack my ego with theirs.

      Hope you have an awesome one and let us know if we can help you with anything. :)

  • renzev@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 months ago

    I’m a Linux user, and I have “X11 decides to lock up the entire system irrecoverably for no reason” syndrome. Should probably look into wayland…

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      X does fall over sometimes. Since I’ve been on Fedora KDE running Wayland, I’ve had a couple “you’re now in recovery mode” moments as well.

  • ObsidianZed@lemmy.world
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    2 months ago

    Since when did the Blue Screen concept change from being an actual error screen to simply the Windows update screen?

    I’m guessing shortly after Windows began implementing aforementioned update screen?

    This is the first I’ve heard it referred to as the Blue Screen.

    For reference: https://wikipedia.org/wiki/Blue_screen_of_death

  • Kaity@leminal.space
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    2 months ago

    Unfortunately as a linux user you may get stuck-on-post syndrome but there are widely available immunizations and treatments available.

    • TheEmpireStrikesDak@thelemmy.club
      link
      fedilink
      arrow-up
      4
      ·
      2 months ago

      I’ve had a black screen of death on Mint. All I was trying to do was crop a video on kdenlive. It black screened on me and somehow even messed up the boot menu so that my Mint was showing up as just Ubuntu. I went straight back to Shotcut after that. I really wanted to switch from Windows to Linux, but so far, Linux, or at least Mint, really hates me. Up till recently, I was still using Mint for my music storage, but it has trouble even moving files onto my phone now. I’ve pretty much given up.

      • far_university190@feddit.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 months ago

        if want to diagnose black screen, can use sudo journalctl -S "TIME" to see journal since TIME (“X min ago”, timestamp, etc.). may have message on error.

        can try syncthing to move file to/from phone

  • Blaster M@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    2 months ago

    99 percent of the time I’ve had to deal with a bsod in Windows, it was a bad driver (Intel controllerless Wi-Fi, for one) or a software issue (Malwarebytes Premium or Kaspersky + insert networking app here). Sometimes it’s a hardware problem (stupid ASUS laptops with builtin RAM), and rarely, a bad disk clone (gotta do that bcdboot)

  • _____@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    I’ve used Windows since the late 90s and I’ve had infinite blue screen loops before. probably a hardware issue but it’s not like this fear is irrational.

    • Gormadt@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      Seemingly once a year my windows machine goes into an infinite loop of bluescreens. It’s because of my wireless/bluetooth card everytime.

      Windows will update the driver during one of it’s bug updates, fail, then I have to go into safe mode and install the correct driver. Then it’s business as usual.

      Windows doesn’t seem to care that I told it to never update my drivers, it’ll still do it once a year.

      • Gestrid@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        For me, it’s not that Windows updates my drivers during a big update. It’s simply that Windows broke the driver while installing a big update.

        I’ve had it happen where my Wi-Fi driver broke so it could only connect to an unprotected network. So I’d simply setup my phone as a hotspot and download the Wi-Fi driver from the manufacturer’s website and reinstall it. That’d immediately fix the issue. Though, actually, that issue hasn’t occured in years. The last time it happened, I think, was in the early years of Windows 10.