-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDDM 0.16 isn't started automatically by systemd #905
Comments
Same here, but only happens sometimes. OS: Arch Linux x64 |
This can be fixed by building your video module (i915, raedon, etc) module into the initramfs. |
Is this the official solution or just a workaround? |
sudo nano /etc/mkinitcpio.conf
Modified the modules line to MODULES="amdgpu" # Was : MODULES="".
sudo mkinitcpio -p linux
shutdown -h now Then powering back on, did the trick for me. |
This happens when SDDM tries to start before video is totally initialized. By adding your video module to early userspace, you initialize video earlier and avoid the problem, but it doesn't really fix the root issue. Not sure if the issue is here, in systemd, or in the kernel. |
Seems like there was a similar Issue some time ago: I tried adding systemd-vconsole-setup.service to After= but that didn't help |
Unfortunately I cannot add i915 to early userspace, because there is another unrelated issue that will cause the backlight adjusting module not loaded properly on my device. |
Same issue happens to me on Lenovo T400. Reverting back to sddm-0.15 solves the problem. I haven't tried adding any module in /etc/mkinitcpio.conf though. OS: ArchLinux x64 |
Same problem here, with a laptop acer 1410. |
Same problem on Dell Inspiron 7000 |
The workaround works for me as well, but I'd still appreciate a solution that does not require that. I usually do not load the video driver in the initrd as the modesetting-induced flickering delays the display of the LUKS passphrase prompt by a few seconds. |
+1 OS: Manjaro x64 |
The only difference there is |
Given that this seems to be a regression in 0.16, if would be good if someone affected could bisect it |
I just gave it a shot on my htpc (old hardware; ignore the USB and amdgpu errors, they are always there). |
FWIW, I can reproduce it only on my Intel laptop, but not on my desktop with proprietary Nvidia drivers. Both systems run more or less the same Archlinux packages. |
@elvisangelaccio Reproduce with |
@BobbyBabes I didn't add anything, so whatever the default is (without?). |
@elvisangelaccio The default is without on Arch. Can’t vouch for other distros. |
I tried to bisect the problem and if my bisect worked then commit 2187cd8 is where the issue started. |
Does it work if you add systemd-logind.service to the After= line in sddm.service? |
@antonio-rojas Just tried. I postpended P.S. I'm out for a few hours soon. It's dinner time. |
Running
made sddm start for me. |
Yes, worked for me as well. Maybe we need to issue systemd-sysusers specifically during install like the gdm package does: |
It's there since October 8. So I didn't bother issuing the command. :
This is the content of |
Yes, but it doesn't seem to be working properly after the upgrade. It could possibly have something to do with the way in which sddm.tmpfiles is setting permissions and/or user and group causing the issue as well. Here is how I'm doing this with spawny: PS. I updated my previous comment.. |
This commit ba9ab1d fixes this issue for my setup. |
@h4nn35 This wouldn’t have made it into the Arch Linux package yet : |
@BobbyBabes Of course not, Arch pulls releases, not development code. That commit was made only 16 hours ago, is the 130th commit since 0.16.0 was released, and was submitted by h4nn35 themself. @h4nn35 Talk about tooting your own horn. ;) |
@NuLogicSystems He wrote :
|
It seems these other two command were needed for ClickXT over at Manjaro: @BobbyBabes That why the winking smiley face. |
Sorry, that I wasn't clear enough. |
If sddm works after
This will create |
@sanosis this is a good workaround for now that doesn't mess with the driver or the kernel. I just hate seeing that there are available updates and I just couldn't take that anymore :D Btw a shorter delay works too, I myself used 1 second and everything works just as expected. But I still hope the bug will get fixed soon |
Is there any eta on a fix for this? |
Arch Linux users please test 0.16.0-3, I've backported the commit from #905 (comment) |
@antonio-rojas @h4nn35 @grayk79 Confirming that Changed line
|
@antonio-rojas seems to fix it for me, thanks |
@antonio-rojas, yes, it solves the issue for me too. Thank you! |
Multiple users have reported that the issue is solved(me myself can't test it atm). May I close the thread then? |
Before closing I also report that sddm 0.16.0-3 fixes the problem. |
systemctl enable sddm
does link successfully but on the next system restart nothing happens. The last thing seen is how the video driver is loaded successfully and that's all. Loading sddm from a tty withsystemctl start sddm
does work like it should. The logs are empty, no sign of an error. Andsystemctl status
does list sddm as loaded for some reason. Only downgrading to sddm 0.15 helped to get the system booted up automatically like it always has had and should. For now I have blacklisted sddm from upgradingOS: Arch Linux x64
Xorg: 1.19.4
Qt: 5.9.2
Plasma: 5.11
Video driver: AMDGPU
The text was updated successfully, but these errors were encountered: