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 crashes with nixos kernel: QQmlThread[2129]: segfault at 0 ip 00007fb27bef93ea sp 00007fb2622494b0 error 4 in libQt5Qml.so.5.9.1[7fb27bdec000+3e0000]
#32072
Comments
Do you use a nixpkgs checkout? Or on which channel are you? I thought that the bug should be fixed... Did you updated regularly or did that bug occur after an recent update? Could you please enable sddm again and try the following: |
I use nixos-unstable. I have some software from a nixpkgs checkout (IntelliJ IDE updates, the moment they come out) and I have older SpiderOaks Groups installed that I build myself from RPM which my company provided. I am on 18.03pre121253.2f1a818d00, as stated in the first post. The bug appeared right after the update I did today. I do update regularly, but infrequently, once every two months, or so. That |
@bkchr Purging the Anything wrong or problematic about my update strategy (as outlined in my previous comment)? |
Nice that it worked. But that is weird, as that should be done automatically :/ You can close the ticket by yourself (I can not do that). |
Had a similar issue today, where sddm (& lightdm) were unable to be used together with plasma 5 (sddm greeter stayed black, whereas lightdm simply fallback to none+xmonad) . Deleting the qmlcache dir solved this for me. |
Issue description
When booting into upgraded system, I was welcomed by an empty black nonresponisive screen on vt7 with single white underscore in the top left corner. Instead, I was expecting SDDM to start there. I was able to switch to vt1 and rescue the system from there.
I "resolved" this by switching from
services.xserver.displayManager.sddm.enable
toservices.xserver.displayManager.lightdm.enable = true
.Steps to reproduce
Happens on every reboot.
Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
journalctl -xe
provides this information, which seems to be the cause of my problemI will be happy to provide more debugging information if specifically asked.
The text was updated successfully, but these errors were encountered: