Today my installation of the Sway edition of EndeavourOS stopped showing anything after login. I was able to use the display manager just fine, but after that my monitor reported that there was no signal. I can still use EndeavourOS by booting in run level 3 and manually running Sway. My timeshift snapshots all got deleted for some reason so I cannot restore to a prior working state. Is there a good way to solve this or will I have to re-install EndeavourOS?
Edit: I forgot to mention that the only system-related thing that I did yesterday was installing updates, which I suspect may have contributed to my problem.
This didn’t work for me, but I appreciate your help nonetheless. No packages updated when I tried the first thing. And I do not have dkms installed. I also can’t seem to enter a TTY without changing the run level in GRUB to 3. However I can run sway after I do that. Also my computer can boot to the display manager just fine. It’s just that after I log in, my monitor says that there’s no signal.
I use the default for the Sway edition of EndeavourOS, which I think is lightdm. Also, I ran sway by just running the command sway in a TTY. When I said “this didn’t work for me” I meant that what you linked did not completely solve my problem, although I think in saying that, I ignored that information was still gleaned from being able to run sway from a TTY.
Edit: I’m a dummy. I can actually access a TTY without changing the run level. I was accidentally using the wrong key combination for doing so.
I’m experiencing the same problem. I’m glad @Anomalocaris did not have to change the run level because I did not have to either. My problems started after performing a system update on friday. After logging in with lightdm I get a black screen on my laptop. After some time the system shows me the lightdm login screen again.
The linked troubleshooting guide unfortunately didn’t solve my problem. Updating pacman mirrors and running the update didn’t install any different packages. startx is not available, but I managed to start sway by executing sway. dkms wasn’t installed either. After installing it and running sudo dkms autoinstall the program terminates without output.
My /var/log/pacman.log for the time of the update time looks as follows
According to the log, the packages that were updated the day before I noticed my problem were this:
linux
linux-headers
qt5-base
qt5-declarative
r8168
yarn
betterdiscord-installer
libinput
rubygems
seatd
welcome
wine-mono
haskell-http
cabal-install
haskell-typed-process
haskell-conduit-extra
haskell-monad-logger
haskell-persistent
haskell-casa-types
haskell-http-conduit
haskell-casa-client
haskell-cryptonite-conduit
haskell-rio
haskell-hi-file-parser
haskell-rio-prettyprint
haskell-http-download
haskell-persistent-sqlite
haskell-rio-orphans
haskell-tar-conduit
haskell-pantry
haskell-project-template
shellcheck
stack
libyuv
libavif
gd
libcaca
glances
I got this list using grep and cut to limit the length of my reply. If you would like me to paste the full log section for that day, I would be happy to. However, it is really long and includes unimportant info like logs for running timeshift-autosnap.
I tried downgrading linux and linux-headers and nothing changed.
I’m tempted to try reinstalling all packages as a brute-force solution. Is there a way to reinstall all packages without marking them as explicitly installed?
Sounds like a similar issue as reported in this thread:
Maybe give this a try:
Also I’m curious if it’s related to libinput in some way. Could you try downgrading that one and see if that helps?edit Nah, forget that, it doesn’t help. Just tried on a VM. edit2 Downgrading seatd seems to help though.
Now since downgrading is not really a good option (imho it should only be used to identify the package/source of the problem or when there’s really no other option currently) I would either go for:
a. Apply the workaround linked above
b. Switch to another DM (that’s probably the more sane one )
It’s an ugly, gross workaround and I can’t wait until I can remove it, but it certainly works. Thank you for your help. Also, it’s good to know that I’m certainly not the only one experiencing this problem and that it’s probably not due to any mistake on my end.
Nope. I’d assume everyone with the combination lightdm +sway faces this issue (well, maybe not everyone since it seems to be a timing related thing. With some very slow HDD you might be unaffected )
This bug pushed me to finally try installing the Ly display manager. I am please with the result and especially pleased that I no longer need to rely on a kludge just to login to Sway.