You are not logged in.
Yesterday my system hung while trying to run an old game with Steam. After restarting everything seemed fine, but when I quit hyprland I was just greeted with a black/blank screen with just an underline cursor in the top left corner instead of the sddm greeter screen.
Today I've managed to isolate it to only happen *only* when I log in with hyprland(uwsm-managed). hyprland on it's own was ok as was i3.
I can't find anything unique in the journalctl and not even sure where I should be looking...
journalctl output from when this happened https://paste.c-net.org/EduardArmenian,
specifically it hangs at the 15:10 mark
Offline
I have the exact same problem. Initial logging in works but logging out with hyprctl dispatch exit throws to black screen with cursor that is not responsive.
Happens also with a fresh archinstall. It used to work a week ago.
loginctl kill-session $XDG_SESSION_ID works.
Offline
Probably an irrelevant question, since you seem to know what journalctl is, but have you looked at the status of the sddm service?
sudo systemctl status sddm.service
If it's stopped or had errors during start-up, it wouldn't work after the initial initializing. Sorry if you already did this, just trying to help.
Last edited by HasakeShinonome (2025-11-30 12:41:05)
Offline
sddm doesn't 'restart' after quiting hyprland(uwsm-managed)
Don't do that?
uwsm is
A standalone Wayland session manager
- you're effectively running two DMs on top of each other.
Just start a normal hyprland session if you're using SDDM
Online
sddm doesn't 'restart' after quiting hyprland(uwsm-managed)
Don't do that?
uwsm isA standalone Wayland session manager
- you're effectively running two DMs on top of each other.
Just start a normal hyprland session if you're using SDDM
For me just using Wayland without uwsm still does not work for some reason.
Offline
sddm is probably hanging out in another tty, try seeing which one its in
Offline
Thank you for the replies.
systemctl status sddm gives me
Dec 04 17:49:07 archlinux sddm-helper[1118]: [PAM] Authenticating...
Dec 04 17:49:07 archlinux sddm-helper[1118]: [PAM] Preparing to converse...
Dec 04 17:49:07 archlinux sddm-helper[1118]: [PAM] Conversation with 1 messages
Dec 04 17:49:07 archlinux sddm-helper[1118]: [PAM] returning.
Dec 04 17:49:07 archlinux sddm[827]: Authentication for user "XXX" successful
Dec 04 17:49:07 archlinux sddm-helper[1118]: pam_unix(sddm:session): session opened for user XXX(uid=1000) by XXX(uid=0)
Dec 04 17:49:07 archlinux sddm[827]: Auth: sddm-helper exited successfully
Dec 04 17:49:07 archlinux sddm[827]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Dec 04 17:49:07 archlinux sddm-helper[1118]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "Hyprland"
Dec 04 17:49:07 archlinux sddm[827]: Session started true
.Could the problem be the third last line...? Or is this normal behavior? Sorry, I am still very new to this. I have tried to search the internet for an answer but to no avail. Chatting with AI tells me that:
The greeter stops after login and never restarts
This is a classic and well-known SDDM + Hyprland + Xorg-greeter bug.
When the greeter uses Xorg and the session uses Wayland, SDDM frequently fails to reactivate the greeter after the compositor exits — resulting in the blank screen with an underscore cursor.
but I am not sure how reliable this answer is.
Offline
The status is meaningless
Ask the AI for its sources, but you may try https://wiki.archlinux.org/title/SDDM#Wayland (you can also use hyprland as compositor)
Online
sddm doesn't 'restart' after quiting hyprland(uwsm-managed)
Don't do that?
uwsm isA standalone Wayland session manager
- you're effectively running two DMs on top of each other.
Just start a normal hyprland session if you're using SDDM
uwsm-managed is recommended by hyprland https://wiki.hypr.land/Useful-Utilities/Systemd-start/:
Universal Wayland Session Manager wraps standalone Wayland compositors into a set of Systemd units and provides robust session management including environment, XDG autostart support, bi-directional binding with login session, and clean shutdown.
That being said, not using it does allow SDDM to work upon logout, but I lost all my autostart applications. It does not sound like a good solution.
It is probably something to do with SDDM configuration like your later post says. I did not have this issue when I was on Fedora with hyprland setup by jakoolit scripts. Just need to figure out how he setup SDDM differently.
Offline
Maybe recommended but shows constantly up as "does not work", so … future.
I lost all my autostart applications
Lost how? What autostart applications?
https://wiki.archlinux.org/title/Hyprland#Autostart ???
Online
perhaps they are talking about xdg-autostart
Offline
Online
Yes, xdg-autostart... it is apparently handled by the uwsm managed hyprland, but I was able to get it to work without it by doing this:
https://github.com/hyprwm/Hyprland/discussions/3389
And my apologies, you are correct - Vaxry (hyprland dev) doesn't recommend uwsm unless you know what you are doing and have a specific use-case. So I stopped using it now that I got the autostart to work. I didn't want to have to move everything to an "exec-once=" in my config.
Last edited by kerosene8902 (2025-12-07 20:45:06)
Offline
uwsm-managed is recommended by hyprland
It absolutely isn't.
Supported != Recommended
The opposite in fact. @vaxry kinda hates the thing and has un-recommended it many times. From your link...
Please note uwsm is for advanced users and has its issues and additional quirks.
See also:
• https://gitlab.archlinux.org/archlinux/ … /issues/32
• https://gitlab.archlinux.org/archlinux/ … 705309e281
Offline
but I was able to get it to work without it by doing this:
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online