uwsm: `uwsm stop` doesn't restart sddm?
Is uwsm stop supposed to be the command used for user logout? I was starting to adopt uwsm for Hyprland, but I cannot solve the problem that after logout sddm login screen doesn’t appear. Here’s my setup,
/usr/share/wayland-sessions/uwsm.desktop:
[Desktop Entry]
Name=Hyprland (UWSM)
Exec=uwsm start -- hyprland.desktop
Type=Application
hyprland.conf:
bind = $mainMod ALT SHIFT, E, exec, uwsm stop
With uwsm stop, I can see the following journal entries in jounrnalctl:
Feb 07 14:34:59 sddm[1750]: Auth: sddm-helper exited with 1
Feb 07 14:34:59 systemd[1]: session-2.scope: Deactivated successfully.
Feb 07 14:34:59 systemd-logind[1420]: Session 2 logged out. Waiting for processes to exit.
Feb 07 14:34:59 systemd-logind[1420]: Removed session 2.
While with hyprland native exit, I can see the following two extra journal entries (along with the other sddm entries leading to restart):
Feb 07 14:51:55 sddm-helper[2336]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Feb 07 14:51:55 sddm-helper[2336]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=985) by (uid=0)
I wonder if I’m using uwsm stop for its intended purpose? If not, what is the correct command to achieve user logout?
I was totally wrong in my initial writing. Hyprland seems to cause coredump regardless of stopping method, the difference is that native exit will triger sddm login screen but uwsm stop won’t.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 18 (7 by maintainers)
It seems I have similar problem with SDDM on Fedora. When I execute
uwsm stop, I end up with a black screen with blinking cursor.In my case logs look weird.
There are two core dumps from
session.shandsystemctl, thenVersions:
sway version 1.10.1fedora 6.12.11-200.fc41.x86_640.21.0It seems the reason was found
Can confirm I’m having the same issue. Hyprland always coredumps, but unlike @glebzlat to my knowledge, I don’t have sway-systemd so I can’t think of what else could be interfering with UWSM specifically. Not much else to add, my logs look pretty similar to the ones above.
I found the package and the line that causes this behavior. The package is
sway-systemd. It provides scriptsession.shthat is responsible for environment preparation and cleanup, and this line:in
session_cleanupfunction blocks. It looks like UWSM andsway-systemdinterfere with each other.