[RESOLVED] Hyprland crash-loops after returning from suspend

BlueElectivire · 2026-07-28 18:23:54

This is a relatively new issue I encountered with this setup in the last week or so, around the release of hyprland 0.56 if i'm not mistaken.
I am using hyprland and hypridle+hyprlock.
If hypridle sends the system into sleep, when returning from sleep hyprlock comes on as usual, but then after inputting the password the session exits back to the login manager, without generating a hyprland crash report.
Trying to log-in again doesn't work, as the new hyprland session that's starting crashes immediately.
I can, however, manually use start-hyprland through a different TTY to start a working session without using a login manager.

Has anybody else encountered this? I can't seem to figure out what is causing this problem.

Adding some relevant logs:
journal of attempted login after crash:

Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): Error writing /proc/self/loginuid: Operation not permitted
Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): set_loginuid failed
Jul 28 21:14:04 ravnica lemurs[1664]: pam_unix(lemurs:session): session opened for user blue(uid=1000) by (uid=0)
Jul 28 21:14:04 ravnica systemd-coredump[42178]: Process 42167 (Hyprland) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jul 28 21:14:04 ravnica systemd[1]: Started Process Core Dump (PID 42178/UID 0).
Jul 28 21:14:04 ravnica systemd-coredump[42179]: [?] Process 42167 (Hyprland) of user 1000 dumped core.

                                                 Stack trace of thread 42167:
                                                 #0  0x00007f14dc6256ea abort (libc.so.6 + 0x256ea)
                                                 #1  0x000055c0c2f4e734 n/a (Hyprland + 0x3bc734)
                                                 #2  0x00007f14dc63e6f0 n/a (libc.so.6 + 0x3e6f0)
                                                 #3  0x00007f14dc69a09c n/a (libc.so.6 + 0x9a09c)
                                                 #4  0x00007f14dc63e5d0 raise (libc.so.6 + 0x3e5d0)
                                                 #5  0x00007f14dc625685 abort (libc.so.6 + 0x25685)
                                                 #6  0x00007f14dca9ac54 n/a (libstdc++.so.6 + 0x9ac54)
                                                 #7  0x00007f14dcab58ba n/a (libstdc++.so.6 + 0xb58ba)
                                                 #8  0x00007f14dca9a5ed _ZSt9terminatev (libstdc++.so.6 + 0x9a5ed)
                                                 #9  0x00007f14dcab5b76 __cxa_throw (libstdc++.so.6 + 0xb5b76)
                                                 #10 0x000055c0c2d47047 n/a (Hyprland + 0x1b5047)
                                                 #11 0x000055c0c2f5b753 _ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi (Hyprland + 0x3c9753)
                                                 #12 0x000055c0c2e0ebf1 main (Hyprland + 0x27cbf1)
                                                 #13 0x00007f14dc627781 n/a (libc.so.6 + 0x27781)
                                                 #14 0x00007f14dc6278b9 __libc_start_main (libc.so.6 + 0x278b9)
                                                 #15 0x000055c0c2f37525 _start (Hyprland + 0x3a5525)

                                                 Stack trace of thread 42170:
                                                 #0  0x00007f14dc6a0872 n/a (libc.so.6 + 0xa0872)
                                                 #1  0x00007f14dc6948bc n/a (libc.so.6 + 0x948bc)
                                                 #2  0x00007f14dc694c07 n/a (libc.so.6 + 0x94c07)
                                                 #3  0x00007f14dc69790c pthread_cond_clockwait (libc.so.6 + 0x9790c)
                                                 #4  0x00007f14de1163b8 _ZN12Hyprgraphics22CAsyncResourceGatherer18asyncAssetSpinLockEv (libhyprgraphics.so.4 + 0x263b8)
                                                 #5  0x00007f14dcaea919 n/a (libstdc++.so.6 + 0xea919)
                                                 #6  0x00007f14dc697fd9 n/a (libc.so.6 + 0x97fd9)
                                                 #7  0x00007f14dc71f02c n/a (libc.so.6 + 0x11f02c)
                                                 ELF object binary architecture: AMD x86-64
Jul 28 21:14:04 ravnica systemd[1]: systemd-coredump@6-12290-42178_53543-0.service: Deactivated successfully.
Jul 28 21:14:04 ravnica lemurs[1664]: pam_unix(lemurs:session): session closed for user blue
Jul 28 21:14:05 ravnica wireplumber[1889]: spa.bluez5: BlueZ system service is not available

hyprland crash report of attempted login:

Log tail:
DEBUG ]: Old rlimit: soft -> 1024, hard -> 524288
DEBUG ]: New rlimit: soft -> 524288, hard -> 524288
DEBUG ]: Creating the EventLoopManager!
DEBUG ]: Creating the KeybindManager!
DEBUG ]: Creating the AnimationManager!
DEBUG ]: Creating the DynamicPermissionManager!
DEBUG ]: Creating the MonitorState!
DEBUG ]: Creating the WorkspaceState!
DEBUG ]: Creating the ConfigManager!
DEBUG ]: [cfg] Regular config at /home/blue/.config/hypr/hyprland.lua
DEBUG ]: [cfg] Using lua config found at /home/blue/.config/hypr/hyprland.lua
DEBUG ]: Creating the Error Overlay!
DEBUG ]: Creating the LayoutManager!
DEBUG ]: Creating the TokenManager!
DEBUG ]: Creating the EventManager!
DEBUG ]: Disabling stdout logs (debug.enable_stdout_logs = 0). Further logs will be written to /run/user/1000/hypr/5c9377c15f85c50648f35ca5a213754f95b93ca0_1785262444_2092845910/hyprland.log
DEBUG ]: Creating the PointerManager!
DEBUG ]: Creating the AsyncResourceGatherer!
DEBUG from aquamarine ]: Creating an Aquamarine backend!
DEBUG from aquamarine ]: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
DEBUG from aquamarine ]: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
DEBUG from aquamarine ]: [libseat] [libseat/libseat.c:76] Backend 'logind' failed to open seat, skipping
ERR from aquamarine ]: [libseat] [libseat/libseat.c:79] No backend was able to open a seat
ERR from aquamarine ]: libseat: failed to open a seat
ERR from aquamarine ]: Failed to open a session
ERR from aquamarine ]: DRM Backend failed
DEBUG from aquamarine ]: Starting the Aquamarine backend!
DEBUG from aquamarine ]: Starting the Wayland backend!
ERR from aquamarine ]: Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
ERR from aquamarine ]: Requested backend (wayland) could not start, enabling fallbacks
ERR from aquamarine ]: Implementation wayland failed, erasing.
CRIT from aquamarine ]: Cannot open backend: no allocator available

lemurs (which seems to me to be operating normally, but adding the logs for good measure):

[2026-07-28T18:14:04Z INFO  lemurs] Starting new session for 'blue' in environment 'Wayland { script_path: "/usr/bin/start-hyprland" }'
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Setting XDG Session Parameters
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_SESSION_CLASS' to 'user'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_SESSION_TYPE' to 'wayland'
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Clearing XDG preemptively to set later
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Preemptively removed environment variable 'XDG_SESSION_CLASS'
[2026-07-28T18:14:04Z INFO  lemurs::auth] Login attempt for 'blue'
[2026-07-28T18:14:04Z INFO  lemurs::auth::pam] Started opening session
[2026-07-28T18:14:04Z INFO  lemurs::auth::pam] Gotten Authenticator
[2026-07-28T18:14:04Z INFO  lemurs::auth::pam] Got handler
[2026-07-28T18:14:04Z INFO  lemurs::auth::pam] Validated account
[2026-07-28T18:14:04Z INFO  lemurs::auth::pam] Opened session
[2026-07-28T18:14:04Z INFO  lemurs::ui] Setting cached information
[2026-07-28T18:14:04Z INFO  lemurs::info_caching] Attempting to set cache: /var/cache/lemurs
[2026-07-28T18:14:04Z INFO  lemurs::info_caching] Successfully set username in cache file
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Setting XDG Seat Variables
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_SEAT' to 'seat0'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_VTNR' to '2'
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Setting XDG Session Variables
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_RUNTIME_DIR' to '/run/user/1000'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_SESSION_ID' to '1'
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Setting Basic Environment Variables
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Successfully changed working directory to /home/blue!
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'HOME' to '/home/blue'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'SHELL' to '/usr/bin/zsh'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'USER' to 'blue'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'LOGNAME' to 'blue'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'PATH' to '/usr/local/sbin:/usr/local/bin:/usr/bin'
[2026-07-28T18:14:04Z INFO  lemurs::post_login::env_variables] Setting XDG Common Paths
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_CONFIG_HOME' to '/home/blue/.config'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_CACHE_HOME' to '/home/blue/.cache'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_DATA_HOME' to '/home/blue/.local/share'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_STATE_HOME' to '/home/blue/.local/state'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_DATA_DIRS' to '/usr/local/share:/usr/share'
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Set environment variable 'XDG_CONFIG_DIRS' to '/etc/xdg'
[2026-07-28T18:14:04Z INFO  lemurs::post_login] Starting Wayland session
[2026-07-28T18:14:04Z INFO  lemurs::auth::utmpx] Adding UTMPX record
[2026-07-28T18:14:04Z INFO  lemurs::auth::utmpx] Added UTMPX record
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Removing session environment variables
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Reverting to environment before session
[2026-07-28T18:14:04Z INFO  lemurs::env_container] Reverting to environment before session
[2026-07-28T18:14:04Z INFO  lemurs] Waiting for environment to terminate
[2026-07-28T18:14:04Z INFO  lemurs::post_login] Waiting for client to exit
[2026-07-28T18:14:04Z INFO  lemurs::post_login::wait_with_log] Joining with logging thread.
[2026-07-28T18:14:04Z INFO  lemurs::post_login] Client exited with exit code `exit status: 0`
[2026-07-28T18:14:04Z INFO  lemurs] Environment terminated. Returning to Lemurs...
[2026-07-28T18:14:04Z INFO  lemurs::auth::utmpx] Removing UTMPX record

Last edited by BlueElectivire (2026-08-02 15:43:03)

seth · 2026-07-28 19:49:31

Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): Error writing /proc/self/loginuid: Operation not permitted
Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): set_loginuid failed
Jul 28 21:14:04 ravnica lemurs[1664]: pam_unix(lemurs:session): session opened for user blue(uid=1000) by (uid=0)

Remove lemurs from the equation.

BlueElectivire · 2026-07-28 20:23:17

seth wrote:

Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): Error writing /proc/self/loginuid: Operation not permitted
Jul 28 21:14:04 ravnica lemurs[1664]: pam_loginuid(lemurs:session): set_loginuid failed
Jul 28 21:14:04 ravnica lemurs[1664]: pam_unix(lemurs:session): session opened for user blue(uid=1000) by (uid=0)

Remove lemurs from the equation.

I'm not really sure that is the root cause though, It worked just fine last week and there was no update to lemurs in that time (or since I started using it, for that matter).
There were versions of basically all the hypr packages, and their update coincides with this behavior appearing.
Also, the initial login with lemurs works just fine and the lemurs log doesn't show any errors.

I also failed to mention it but hypridle works weird when I log in from the TTY too, it locks the screen when I'm watching long videos for example which it doesn't do when logging in with lemurs.

I can read the logs fine enough to find the errors myself, it's the root cause I'm asking for help with.

seth · 2026-07-28 20:38:09

I'm not really sure that is the root cause though

Become sure by removing it from the euqation.

I can read the logs fine enough to find the errors myself, it's the root cause I'm asking for help with.

If you want to know what might go wrong ahead of "pam_loginuid(lemurs:session): set_loginuid failed" it might be beneficial to post the data illustrating it - iow the entire journal…

Also, the initial login with lemurs works just fine and the lemurs log doesn't show any errors.

So? Ly has a long standing track-record of screwing the logind integration after the first successful login. This is kinda meaningless. Things work and then they're broken - nature of life.

I also failed to mention it but hypridle works weird when I log in from the TTY too, it locks the screen when I'm watching long videos for example which it doesn't do when logging in with lemurs.

There were versions of basically all the hypr packages, and their update coincides with this behavior appearing.

Would that likewise be a regression?
Since apparently you've tested this: do you get the same abort w/o lemurs?

then after inputting the password the session exits back to the login manager, without generating a hyprland crash report.

Assuming the status quo is that hypridle results in hyprland actually crashing and the unclean termination freaks out lemurs and results in subsequent, unrelated issues:
Does hyprwhatever leave behind a https://wiki.archlinux.org/title/Core_d … _core_dump ?

BlueElectivire · 2026-08-02 13:10:57

So I had some time to do more experimenting and get some more logs and such, here are some more results:

You were right that lemurs is in some way a part of the problem:
- The session crashes when returning from sleep only when it was started from lemurs and not when i start it manually from a tty.
- The second login doesn't work even when the session exits gracefully
The thing about hypridle malfunctioning when I log in from the tty must have been a one-time thing because I can't reproduce it again
Hyprland itself doesn't leave a coredump. Other processes (notably hypridle) do, but they crash after hyprland (because they don't find a session to attach to), so the coredump isn't really informative.

for the context, here is the hypridle stacktrace:

#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007f6b76e9a0e3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89
#2  0x00007f6b76e3e5d0 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3  0x00007f6b76e25685 in __GI_abort () at abort.c:77
#4  0x00007f6b7729ac54 in __gnu_cxx::__verbose_terminate_handler () at ../../../../gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#5  0x00007f6b772b58ba in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#6  0x00007f6b7729a5ed in std::terminate () at ../../../../gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#7  0x000055cbe2936bba in std::__terminate () at /usr/include/c++/16/x86_64-pc-linux-gnu/bits/c++config.h:358
#8  std::thread::~thread (this=<optimized out>, this=<optimized out>) at /usr/include/c++/16/bits/std_thread.h:184
#9  CHypridle::enterEventLoop (this=<optimized out>) at /usr/src/debug/hypridle/hypridle-0.1.8/src/core/Hypridle.cpp:284
#10 CHypridle::run (this=<optimized out>) at /usr/src/debug/hypridle/hypridle-0.1.8/src/core/Hypridle.cpp:144
#11 0x000055cbe293ab6b in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /usr/include/c++/16/bits/unique_ptr.h:192

I'll not include the whole journal here (because that seems like a waste of everyone's time), but the initial lemurs login gives this journal log:

Aug 02 15:28:14 ravnica lemurs[1657]: pam_loginuid(lemurs:session): Error writing /proc/self/loginuid: Operation not permitted
Aug 02 15:28:14 ravnica lemurs[1657]: pam_loginuid(lemurs:session): set_loginuid failed
Aug 02 15:28:14 ravnica lemurs[1657]: pam_unix(lemurs:session): session opened for user blue(uid=1000) by (uid=0)
Aug 02 15:28:14 ravnica systemd-logind[1634]: New session 'c1' of user 'blue' with class 'user' and type 'wayland'.
Aug 02 15:28:14 ravnica systemd[1]: Created slice User Slice of UID 1000.
Aug 02 15:28:14 ravnica systemd[1]: Starting User Runtime Directory /run/user/1000...
Aug 02 15:28:14 ravnica systemd-user-runtime-dir[1677]: Successfully configured disk quota for UID 1000 on /tmp to 6.1G
Aug 02 15:28:14 ravnica systemd-user-runtime-dir[1677]: Successfully configured disk quota for UID 1000 on /dev/shm to 6.1G
Aug 02 15:28:14 ravnica systemd[1]: Finished User Runtime Directory /run/user/1000.
Aug 02 15:28:14 ravnica systemd[1]: Starting User Manager for UID 1000...
Aug 02 15:28:14 ravnica (systemd)[1680]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[blue] ruser=[<unknown>] rhost=[<unknown>]
Aug 02 15:28:14 ravnica (systemd)[1680]: pam_unix(systemd-user:session): session opened for user blue(uid=1000) by blue(uid=0)
Aug 02 15:28:14 ravnica systemd-logind[1634]: New session '1' of user 'blue' with class 'manager' and type 'unspecified'.
Aug 02 15:28:14 ravnica systemd[1680]: Queued start job for default target Main User Target.
Aug 02 15:28:14 ravnica systemd[1680]: Created slice User Application Slice.
Aug 02 15:28:14 ravnica lemurs[1657]: pam_systemd(lemurs:session): Failed to set ambient capabilities, ignoring: Operation not permitted

All in all, I figure that the hypr* updates changes some behavior such that it now trips on the bugs lemurs always had or something of this sort. I think I'll just ditch it from now (also, I am using a single user and a single session so login managers seem a bit redundant honestly.)

Thanks for the help

seth · 2026-08-02 13:25:56

using a single user and a single session so login managers seem a bit redundant

Yup, I'd (and personally do) just boot into a locked autostarted session.

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.

Edit: hypridle aborts out of a thread termination, there's likely some error message somewhere (since an abort is a controlled exit)

Last edited by seth (2026-08-02 13:27:35)

Arch Linux

#1 2026-07-28 18:23:54

[RESOLVED] Hyprland crash-loops after returning from suspend

#2 2026-07-28 19:49:31

Re: [RESOLVED] Hyprland crash-loops after returning from suspend

#3 2026-07-28 20:23:17

Re: [RESOLVED] Hyprland crash-loops after returning from suspend

#4 2026-07-28 20:38:09

Re: [RESOLVED] Hyprland crash-loops after returning from suspend

#5 2026-08-02 13:10:57

Re: [RESOLVED] Hyprland crash-loops after returning from suspend

#6 2026-08-02 13:25:56

Re: [RESOLVED] Hyprland crash-loops after returning from suspend

Board footer