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.
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.
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.
Oohhh, I'm stealing this - I've managed to fool a few people with 'the sunspots BS', maybe I'll get a dreamcatcher tattood on my lower back if they don't fall for it...
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)
19 Comments
blotz@lemmy.world · 38 pts · 2y
Ah! the classic "Turn it off and on again (but for real this time)". Works every time.
SaltyIceteaMaker@iusearchlinux.fyi · 21 pts · 2y
Works every time 72% of the time
hellfire103@lemmy.ca · 30 pts · 2y
Yesterday, I spent half an hour trying to figure out why SDDM wasn't seeing
/usr/share/wayland-sessions/sway.desktopbefore 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 pts · 2y
How do you even manage to install a graphical sessions without installing anything that depends on a font
hellfire103@lemmy.ca · 9 pts · 2y
% sudo xbps-install -Su sddm sway wayland% sudo ln -s /etc/sv/sddm /var/service% sudo sv up sddmillegalargumentexc@lemmy.world · 1 pts · 2y
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)
loaExMachina@sh.itjust.works · 20 pts · 2y
agent_flounder@lemmy.world · 10 pts · 2y
How could Linux do this to you??
(Totally never happened to me /s)
prof@infosec.pub · 5 pts · 2y
Classic!
Magister@lemmy.world · 13 pts · 2y
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.pub · 2 pts · 2y
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 pts · 2y
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.pub · 4 pts · 2y
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.
agent_flounder@lemmy.world · 4 pts · 2y
I think it was sunspots.
Viking_Hippie@lemmy.world · 7 pts · 2y
Solar flares and the moon ascending in Venus for sure.
IsoSpandy@lemm.ee · 7 pts · 2y
Maybe OPs Chakra flow was unstable when operating the machine
flambonkscious@sh.itjust.works · 4 pts · 2y
Oohhh, I'm stealing this - I've managed to fool a few people with 'the sunspots BS', maybe I'll get a dreamcatcher tattood on my lower back if they don't fall for it...
DumbAceDragon@sh.itjust.works · 9 pts · 2y
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)
onlinepersona@programming.dev · 5 pts · 2y
What's with the cat face?
Edit: Oh, it's the user's profile picture.
CC BY-NC-SA 4.0
prof@infosec.pub · 4 pts · 2y
It's my cat, I am the user 😄