springshades
March 15th, 2018, 10:24 PM
Hi everyone,
After a recent "apt-get dist-upgrade", I started to get a black screen from sddm. The system boots successfully otherwise, so Ctl + Alt + 1 gives me a command line, but I can't get to a graphical environment.
Per /var/log/apt/term.log, the main things that seem like they may have caused the issue are updates to:
nvidia-settings
pulseaudio (Seems unlikely to cause this, but I know many people have had issues in the past?)
Many packages with "mesa" in the name.
Several "libgl" packages.
A single package that starts with "libwayland".
Things that I have done to try to fix this myself:
1. Booted in "nomodeset". No effect.
2. I installed nvidia-390 which replaced my previously installed nvidia-384 just in case there was an issue with that specific driver. No effect.
3. Ran "systemctl isolate multi-user" followed by "systemctl isolate graphical" as a turn it off turn it on again type of thing. No effect.
4. Ran "systemctl --failed" to look for boot failures. Found one unrelated thing that wasn't causing the issue (vmware). Just in case, I disabled it and rebooted. No effect. I'm running vmware as a host, not as a client, so it shouldn't be causing a boot issue.
5. Emptied the contents of ~/.cache and rebooted since that causes issues for some people. No effect.
6. Searching through kernel logs doesn't show anything coming up consistently that didn't also show up before I started having the problem.
Any ideas?
After a recent "apt-get dist-upgrade", I started to get a black screen from sddm. The system boots successfully otherwise, so Ctl + Alt + 1 gives me a command line, but I can't get to a graphical environment.
Per /var/log/apt/term.log, the main things that seem like they may have caused the issue are updates to:
nvidia-settings
pulseaudio (Seems unlikely to cause this, but I know many people have had issues in the past?)
Many packages with "mesa" in the name.
Several "libgl" packages.
A single package that starts with "libwayland".
Things that I have done to try to fix this myself:
1. Booted in "nomodeset". No effect.
2. I installed nvidia-390 which replaced my previously installed nvidia-384 just in case there was an issue with that specific driver. No effect.
3. Ran "systemctl isolate multi-user" followed by "systemctl isolate graphical" as a turn it off turn it on again type of thing. No effect.
4. Ran "systemctl --failed" to look for boot failures. Found one unrelated thing that wasn't causing the issue (vmware). Just in case, I disabled it and rebooted. No effect. I'm running vmware as a host, not as a client, so it shouldn't be causing a boot issue.
5. Emptied the contents of ~/.cache and rebooted since that causes issues for some people. No effect.
6. Searching through kernel logs doesn't show anything coming up consistently that didn't also show up before I started having the problem.
Any ideas?