For details, see:


sddm-helper is a script usually placed in /usr/libexec/sddm-helper used by sddm.

In /var/log/messages, entries for sddm-helper may appear.

PAM unable to dlopen ...

Sample /var/log/messages entry:

sddm-helper[4821]: PAM unable to dlopen(/lib64/security/ /lib64/security/ cannot open shared object file: No such file or directory


Help us document errors that can be found in this log file, and what each error may mean and the appropriate solution.

Log file used by sddm for its interaction with the server.

A major shortcoming of this file is that the log entries do not include any timestamp.

QXcbConnection: XCB error: 3 (BadWindow)

Sample error:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 886, resource id: 39845897, major code: 18 (ChangeProperty), minor code: 0


Directory used by sddm in particular for its xorg-session.log.

For sddm, see:

sddm breeze: user icons/avatars do not show


ls /usr/share/sddm/faces

but the icons does not show in the login screen.

sddm: open new session gives black screen
I am a new Calculate Linux user.
I have just successfully installed Calculate.
I can log into a KDE Plasma session, with sddm and the nvidia-drivers.
However, when I try to start a new session, I get a black screen. I cannot switch to any tty (tty1 nor back to tty7). I can only hard-reboot the computer.

sddm: unused tty do not expire

With KDM, when a tty remained unused it expired.
E.g. when I start a new session on tty8, but change my mind before actually login in, and go back to tty7, the tty8 login screen will remain there unused for ever.
If I then go to the K-menu and try to start another new session, the tty8 session is not reused. Instead we go to tty9.

KDM handled this more gracefully, by allowing unused tty sessions to expire after a certain time if 1) there was no successful login and 2) the user switched back to another session.

Support elogind as an alterantive session tracker for systemd-logind.

Yamakuzure Support elogind as an alterantive session tracker for systemd-logind.

For users who do not want to run the full systemd suite, but do not
want to patch sddm to use ck-launch-session either, elogind can be
used as an alternative session tracker via its PAM module.


sddm requires systemd to log errors

See #11018: sddm upgrade: missing logs and missing maui theme
for an example of an error that was not properly logged.
Upstream says that logging errors requires systemd :(

Syndicate content