About 3, idk what’s going on with my system, but sometimes after a big yay update, the kde login fails (something about the plasma environment failing to boot or idk I have not debugged it correctly yet), then after a reboot systemd-boot fails to load it and the efi entry dissapears. I’m forced to arch-chroot and reinstall the bootctl. After doing so, sometimes I have to do it again and other times it logs correctly.
Again, not debugged it correctly but it’s not like I did any kind of weird change to any config, just installed some flatpaks, some steam games, and lutris for League, which in the end is basically wine, and a yay update provoking this behaviour is pretty bad.
I’ve had this happen. I never did figure it out, personally. I distro hopped a bit and eventually ended up back on Arch and it didn’t happen again, so I guess it was a bugged install?
Yeah, I’ve taken the routine of logging into tty3 before kde to pipe the journal tal output into a file to debug only the error if it happens. Yeah I know I can fine tune then output to get only the last execution and so on and I have done it, but it was not that clear and this happened after a work day and I wanted to fuck off and chill so the next time it happens I’ll be more through.
About 3, idk what’s going on with my system, but sometimes after a big yay update, the kde login fails (something about the plasma environment failing to boot or idk I have not debugged it correctly yet), then after a reboot systemd-boot fails to load it and the efi entry dissapears. I’m forced to arch-chroot and reinstall the bootctl. After doing so, sometimes I have to do it again and other times it logs correctly.
Again, not debugged it correctly but it’s not like I did any kind of weird change to any config, just installed some flatpaks, some steam games, and lutris for League, which in the end is basically wine, and a yay update provoking this behaviour is pretty bad.
I’ve had this happen. I never did figure it out, personally. I distro hopped a bit and eventually ended up back on Arch and it didn’t happen again, so I guess it was a bugged install?
Journalctl might be a great friend here.
Yeah, I’ve taken the routine of logging into tty3 before kde to pipe the journal tal output into a file to debug only the error if it happens. Yeah I know I can fine tune then output to get only the last execution and so on and I have done it, but it was not that clear and this happened after a work day and I wanted to fuck off and chill so the next time it happens I’ll be more through.
Just Linux stuff xD
Yeah, I feel that man. Hopefully it doesn’t happen again though.