Wayland session crashes continuously with sddm enabled

manos00 · 2024-10-28 14:46:04

Hi everyone,
I recently did a fresh install of Linux on a new Laptop and decided to try Hyprland. So far everything has been working well, except for sddm. I decided on sddm as a window manager, because it was listed as a recommendation on their Hyprland's wiki page. Unfortunately I haven't gotten it to work yet.
When enabled, there are two (probably correlated) problems occur:

The screen goes black for 30s after logging in.
After exactly one minute, i get logged out.

~/.local/share/sddm/wayland-session.log says:

Environment variable $QT_QPA_PLATFORMTHEME not set, ignoring.
Environment variable $XDG_DATA_DIRS not set, ignoring.
2024/10/28 15:11:35 socat[832] W address is opened in read-write mode but only supports read-only
Environment variable $QT_QPA_PLATFORMTHEME not set, ignoring.
Environment variable $XDG_DATA_DIRS not set, ignoring.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
[0.205] [glfw error 65544]: process_desktop_settings: failed with error: [org.freedesktop.DBus.Error.UnknownMethod] No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop

EDIT: I just noticed the first timestamp in the log says 15:11:35, which is one second before the black screen went away. Thought this was worth mentioning.
After 60s I get thrown to the sddm login screen. If I log back in and check the output of systemctl status --user xdg-desktop-portal-hyprland I get:

○ xdg-desktop-portal-hyprland.service - Portal service (Hyprland implementation)
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-hyprland.service; static)
Active: inactive (dead)
Oct 28 15:12:34 thinkpadL13 systemd[716]: xdg-desktop-portal-hyprland.service: Scheduled restart job, restart counter is at 1.
Oct 28 15:12:34 thinkpadL13 systemd[716]: Starting Portal service (Hyprland implementation)...
Oct 28 15:12:34 thinkpadL13 systemd[716]: Started Portal service (Hyprland implementation).
Oct 28 15:12:34 thinkpadL13 xdg-desktop-portal-hyprland[1620]: [LOG] Initializing xdph...
Oct 28 15:12:34 thinkpadL13 xdg-desktop-portal-hyprland[1620]: [CRITICAL] Couldn't connect to a wayland compositor
Oct 28 15:12:34 thinkpadL13 systemd[716]: xdg-desktop-portal-hyprland.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 15:12:34 thinkpadL13 systemd[716]: xdg-desktop-portal-hyprland.service: Failed with result 'exit-code'.
Oct 28 15:12:35 thinkpadL13 systemd[716]: xdg-desktop-portal-hyprland.service: Scheduled restart job, restart counter is at 2.
Oct 28 15:12:35 thinkpadL13 systemd[716]: Starting Portal service (Hyprland implementation)...
Oct 28 15:12:35 thinkpadL13 systemd[716]: Started Portal service (Hyprland implementation).

Before the first crash the output of the same command is just:

● xdg-desktop-portal-hyprland.service - Portal service (Hyprland implementation)
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-hyprland.service; static)
Active: active (running) since Mon 2024-10-28 15:11:35 CET; 48s ago
Invocation: 2c49416a433b4cf2be7dc5cfd8b375a2
Main PID: 907 (xdg-desktop-por)
Tasks: 9 (limit: 17586)
Memory: 10.9M (peak: 11.6M)
CPU: 37ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/xdg-desktop-portal-hyprland.service
└─907 /usr/lib/xdg-desktop-portal-hyprland
Oct 28 15:11:35 thinkpadL13 systemd[716]: Starting Portal service (Hyprland implementation)...
Oct 28 15:11:35 thinkpadL13 systemd[716]: Started Portal service (Hyprland implementation).

Then the process loops until I disable sddm and reboot. My sddm config is as follows:

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
[Theme]
Current=sugar-candy
FacesDir=/usr/share/sddm/faces

Thanks in advance for any help.

Last edited by manos00 (2024-10-28 14:48:36)

Trilby · 2024-10-28 14:57:34

Do you need a DM? All they do is tend to break things. If you just want to run hyprland, just run hyprland.

seth · 2024-10-28 15:29:10

I decided on sddm as a window manager, because it was listed as a recommendation on their Hyprland's wiki page. Unfortunately I haven't gotten it to work yet.
When enabled, there are two (probably correlated) problems occur:
The screen goes black for 30s after logging in.
After exactly one minute, i get logged out.

SDDM isn't a "Window manager" but a https://wiki.archlinux.org/title/Display_manager (that's why it's not called SDWM ) and the symptoms sound more like aHyprland issue?
Does Hyprland at all start properly from the console? (also see Trilby's comment)

The xdg-desktop-portal-hyprland.service should™ be irrelevant here, it fails because it can't get access to a wayland display.
Speaking of which: what does your hyprland config look like? It might be the cause here.

manos00 · 2024-10-28 20:48:55

Thanks for the quick replies!
Without a display manager Hyprland works just fine
The main reasons I wanted to use one was that my thinkpad has a fancy fingerprint reader and i wanted to make use of it somehow
Here's my Hyprland config: http://0x0.st/X0Zi.txt
It's pretty much all the defaults. If you can't think of any other obvious possible solution, I'd be fine just starting Hyprland from tty each time (since it's not such a huge effort after all ).

Trilby · 2024-10-28 21:03:09

You can have it autostart, there's no need to do it manually. That's my point: what does a DM do for you that wouldn't be simpler without it?

Now we have one criteria: it uses your fingerprint reader. Okay, but is that something you really want to use for logging in? Because the way you phrased it wasn't like it was a feature you wanted, but rather than your computer just has one, so you want to use it.

If you really do want to use the fingerprint reader to log in, it can be used for the actual log-in on the tty (via pam as outline in the wiki) and hyprland autostarted after that. Though if you want a graphical prompt to touch the fingerprint reader, then a DM does make more sense.

seth · 2024-10-28 21:21:58

As for SDDM, no suspicious environment variables that would get in the way.
Check whether hyprland crashes and consider trying https://wiki.archlinux.org/title/SDDM#Wayland

As for the alternative aproach, you could autologin into a lockd hyprland session (ie. immediately lock the screen) and use your fingerprint to unlock the screenlocker to get a GUI prompt.
(Though that doesn't work if you want to allow multiple users and identify and authorize them via fprint)

manos00 · 2024-10-29 10:34:55

I think I'll try the alternative and close the topic in a few days, if I don't run into any further issues. Thank you guys!

Arch Linux

#1 2024-10-28 14:46:04

Wayland session crashes continuously with sddm enabled

#2 2024-10-28 14:57:34

Re: Wayland session crashes continuously with sddm enabled

#3 2024-10-28 15:29:10

Re: Wayland session crashes continuously with sddm enabled

#4 2024-10-28 20:48:55

Re: Wayland session crashes continuously with sddm enabled

#5 2024-10-28 21:03:09

Re: Wayland session crashes continuously with sddm enabled

#6 2024-10-28 21:21:58

Re: Wayland session crashes continuously with sddm enabled

#7 2024-10-29 10:34:55

Re: Wayland session crashes continuously with sddm enabled

Board footer