[tumbleweed] sddm-greeter segfaulting with new AMD Mesa drivers 18.0.0-X

New 18.0.0-X Mesa drivers for AMD crashing sddm-greeter so I get a black screen and a cursor when I try to login. X Server is fine and I can launch virtual ttys to rollback snapshots. Its Mesa drivers because I’ve had no issue with them thus far, and no issue with 17.3.3-184.1 the version prior to roll-out of the new kernel supported drivers.

Feb 06 21:14:00 localhost kernel: sddm-greeter[2690]: segfault at 557fbdb23cb8 ip 00007f26db097030 sp 00007ffe31725e68 error 4 in libc-2.26.so[7f26daf5f000+1b1000]
Feb 06 21:14:00 localhost systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Feb 06 21:14:00 localhost update_postmaps[2244]: postmap: fatal: parameter inet_interfaces: no local interface found for ::1
Feb 06 21:14:00 localhost postfix/postmap[2894]: fatal: parameter inet_interfaces: no local interface found for ::1
Feb 06 21:14:00 localhost systemd[1]: Started Process Core Dump (PID 2892/UID 0).
Feb 06 21:14:00 localhost sddm-helper[2682]: [PAM] Closing session
Feb 06 21:14:00 localhost sddm-helper[2682]: pam_unix(sddm-greeter:session): session closed for user sddm
Feb 06 21:14:00 localhost sddm-helper[2682]: [PAM] Ended.
Feb 06 21:14:00 localhost systemd-logind[1610]: Removed session 1.
Feb 06 21:14:00 localhost sddm[2355]: Auth: sddm-helper exited with 11
Feb 06 21:14:00 localhost sddm[2355]: Greeter stopped.
Feb 06 21:14:00 localhost systemd[1]: Stopping User Manager for UID 467...
Feb 06 21:14:00 localhost systemd[2684]: Stopping D-Bus User Message Bus...
Feb 06 21:14:00 localhost systemd[2684]: Stopped target Default.
Feb 06 21:14:00 localhost systemd[2684]: Stopped D-Bus User Message Bus.
Feb 06 21:14:00 localhost systemd[2684]: Stopped target Basic System.
Feb 06 21:14:00 localhost systemd[2684]: Stopped target Paths.
Feb 06 21:14:00 localhost systemd[2684]: Stopped target Timers.
Feb 06 21:14:00 localhost systemd[2684]: Stopped target Sockets.
Feb 06 21:14:00 localhost systemd[2684]: Closed D-Bus User Message Bus Socket.
Feb 06 21:14:00 localhost systemd[2684]: Reached target Shutdown.
Feb 06 21:14:00 localhost systemd[2684]: Starting Exit the Session...
Feb 06 21:14:00 localhost systemd[2684]: Received SIGRTMIN+24 from PID 2896 (kill).
Feb 06 21:14:00 localhost systemd[2685]: pam_unix(systemd-user:session): session closed for user sddm
Feb 06 21:14:00 localhost systemd[1]: Stopped User Manager for UID 467.
Feb 06 21:14:00 localhost systemd[1]: Removed slice User Slice of sddm.
Feb 06 21:14:00 localhost systemd-coredump[2895]: Process 2690 (sddm-greeter) of user 467 dumped core.

both the initial update to the 18 version and new ones today crash the greeter.

Sounds like this bug in Mesa 18:
https://bugzilla.opensuse.org/show_bug.cgi?id=1079465
https://bugs.freedesktop.org/show_bug.cgi?id=104762

It should help to delete the user’s .cache folder (/var/lib/sddm/.cache/ for sddm).
There are also testing packages with a fix offered in the openSUSE bug report.

I have Intel drivers, but after the last tumbleweed update with mainly mesa updates, I had a white screen after reboot and could do nothing more.
I have last tumbleweed iso downloaded with other PC and booted with it and update done and previous mesa package installed.
now it works happily again.

sorry for my bad English.

GJ

Same here with Intel.

See

https://bugzilla.opensuse.org/show_bug.cgi?id=1079804

and linked post.

Deleting

~/.cache
folder ultimately worked for me.

Initially following woli323 suggestion of deleting

/var/lib/sddm/.cache/
got me past sddm-greeter.

Feb 07 06:39:22 localhost sddm-greeter[2636]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 07 06:39:22 localhost sddm[2269]: Message received from greeter: Login
Feb 07 06:39:22 localhost sddm[2269]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 07 06:39:22 localhost sddm[2269]: Reading from "/usr/share/xsessions/plasma5.desktop"
Feb 07 06:39:22 localhost sddm[2269]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startkde"
Feb 07 06:39:22 localhost sddm-helper[2848]: [PAM] Starting...
Feb 07 06:39:22 localhost sddm-helper[2848]: [PAM] Authenticating...
Feb 07 06:39:22 localhost sddm-helper[2848]: [PAM] Preparing to converse...
Feb 07 06:39:22 localhost sddm-helper[2848]: [PAM] Conversation with 1 messages
Feb 07 06:39:22 localhost sddm-helper[2848]: [PAM] returning.
Feb 07 06:39:22 localhost sddm[2269]: Authenticated successfully

but plasma core dumped right after

Feb 07 06:39:34 localhost systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Feb 07 06:39:34 localhost systemd[1]: Started Process Core Dump (PID 3212/UID 0).
Feb 07 06:39:34 localhost systemd-coredump[3213]: Resource limits disable core dumping for process 3191 (plasmashell).
Feb 07 06:39:34 localhost systemd-coredump[3213]: Process 3191 (plasmashell) of user 1000 dumped core.

looking through the bugzilla links linked here and deleting ~/.cache after the driver update, allowed me to boot successfully using the recently push drivers 18.0.0-187-1

Thank you for the support and links, really loving snapper’s ability to rollback after issues.

Greetings , i want to share what worked for me at the moment.

I have an APU with integrated VGA and after the update today with a fresh installation i got the message you say and when i rebooted via terminal i presented with a white screen that lasted for ever.

I entered the following commands while in the white screen (or black) in some systems.

Press : Ctrl + Alt + F1
Enter your user credentials
While in your home directory >> rm -rf .cache
Deleting one more cache folder >> sudo rm -rf /var/lib/sddm/.cache
After that  >> sudo reboot
 

You can login to your system now .

By the way, by deleting only the .cache from home folder didn’t work for me i had to delete the other file too.

Thanks everyone above for the initial replies

Yes.
The cache files are stored in .cache in the corresponding user’s home, and sddm’s home is /var/lib/sddm/… :wink:

For the record, it’s also possible to restart the display with :


sudo systemctl restart display-manager.service

(I haven’t tested, but Ctrl ] + Alt ] + <- “Backspace” ] from the white screen should also restart the display).