• blotz@lemmy.world
    38·
    2 years ago

    Ah! the classic “Turn it off and on again (but for real this time)”. Works every time.

  • Hellfire103@lemmy.caEnglish
    30·
    2 years ago

    Yesterday, I spent half an hour trying to figure out why SDDM wasn’t seeing /usr/share/wayland-sessions/sway.desktop before I realised that the reason it wasn’t showing up in the menu was because I hadn’t installed any fonts; so it was there, but it was invisible.

    • TurboWafflz@lemmy.world
      5·
      2 years ago

      How do you even manage to install a graphical sessions without installing anything that depends on a font

      • Hellfire103@lemmy.caEnglish
        9·
        2 years ago

        % sudo xbps-install -Su sddm sway wayland

        % sudo ln -s /etc/sv/sddm /var/service

        % sudo sv up sddm

        “Hey, why aren’t there any sessions?”

        • illegal.argument@lemmy.worldEnglish
          1·
          2 years ago

          i’ve faced this issue so much and i still haven’t found a solution for it other than to have my dm and de in my xinitrc

          is there actually a seamless fix (or is the xinitrc the seamless way lmao)

  • Magister@lemmy.world
    13·
    2 years ago

    Do you have fastboot enabled in your BIOS? Because it can screw up FW not being uploaded/transferred in devices like network cards

    • prof@infosec.pubOP
      2·
      2 years ago

      I did check the bios settings but couldn’t really find anything that would directly affect a pcie card.

      Most power management stuff that could cause issues is turned off. Fast boot itself was also off.

  • IsoSpandy@lemm.ee
    12·
    2 years ago

    I can totally relate to you. Everytime we touch the software and even the slightest bit changes, the pitchforks are ready. I even read the entire forum post and man it is awesome.

    Anyways glad you got it fixed

    • prof@infosec.pubOP
      4·
      2 years ago

      Thanks! It’s really funny. Especially since KDE updated to version 6 and caused a lot of issues for other users - so it had to be the a software issue of course!

      I’m still not entirely convinced, that it wasn’t a software issue that caused the device to misbehave.

  • DumbAceDragon@sh.itjust.worksEnglish
    9·
    2 years ago

    This actually happened to me not too long ago. Things would randomly just crash. Turns out it was because my RAM had bad sectors in it.

    On linux I’d just restart whatever crashed and it usually went along fine for another 30 minutes. Worst that happened was btrfs would make my drive readonly until a reboot because it knew some shit was up.

    On windows it bluescreened several times before corrupting the hard drive (was thankfully able to recover it lol)