New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with systemd / suspend #399
Comments
Same issue. |
I mitigated the bug by adding |
Same issue on Arch linux, is there any solution to this? |
Same here on arch too! |
Same issue on Arch, but this is either regression or something new. This method has been working for at least year without any issue. I would label this as critical, as it might leave users with unlocked devices without their knowledge. It took me time to realize, that I didn't write the password and device is unlocked. As for workaround mentioned by @valentin2105 you'd have to change env every time you reboot or restart X, which isn't really practical. For now, I'm mittigating this with:
This works as user systemd session, at least on Arch linux, is updated with correct XAUTHORITY and DISPLAY on x start. Seems like lot of work, so not sure if this is preferred solution. Another workaround might be creating script in xinitrc, similar as arch one to update XAUTHORITY, which would set some env file which will be loaded in betterlockscreen system systemd service. |
I have the same issue error log is as follows:
Where $USER was my correct username |
bump. I've playing around to see if I missed something in the configuration step, but I'm glad I'm not the only one running into this one |
Not sure if this will be relevant for anyone else, but this hasn’t been an issue for me until recently, when I switched from LightDM to SDDM in search of a display manager that can run both X11 and Wayland sessions. As is, I couldn’t get betterlockscreen to work with any of the old or new suggestions until I stopped using SDDM. I suspect that there might be peculiarities with the way SDDM starts Xsessions that is either incomplete or simply not working for my barebones Openbox config. Regardless, starting my X11 session with LightDM again makes betterlockscreen work as it should. I’ve also begun testing greetd and although other things need work with my session config, the default betterlockscreen setup works as it should in that case as well. YMMV. |
Is there an existing issue for this?
Operating system
Manjaro
Installation method
Package Manager (from OS)
Betterlockscreen & Dependency-Versions
Betterlockscreen: version: v4.2.0 (dunst: true, feh: true) i3lock: version 2.13.c.5 © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li Version: ImageMagick 7.1.1-15 Q16-HDRI x86_64 21298 https://imagemagick.org Copyright: (C) 1999 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5) Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib Compiler: gcc (13.2) Dunst is not running. feh version 3.10 Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama
Bug description
Sorry to open another issue about systemd/suspend but I don't find any answer that work on the closed issue, and the opened ones seem not exactly the same issue.
So, I have added the
betterlockscreen@.service
and enabled it, (after daemon-reloaded systemd), and when it got triggered by LidClosed (systemd-logind) of just by restarting the service, I got this message (and betterlockscreen don't launch) :It seem unable to get the display, or X11 access..
Can you help me ?
Sorry if it's a duplicate issue
Steps to reproduce
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: