[I uploaded all logs here](https://drive.google.com/drive/folders/1eeaPYZiyEWxNmFYkiQlbnQ7g_fO9-4Oz?usp=sharing) . After unlocking the PC after a period of inactivity (a few hours?), I'm often met with a black screen with nothing but a mouse cursor on it (that I can move). The only fix I found is killing the X server with CtrlAltBackspace, but that also kills all my GUI apps. Ideally I'm looking for a full fix, or at least for a more graceful way to recover from this without closing my apps. --- Some more details: I've started getting this issue after switching to a new laptop with an Nvidia card (the previous one had an integrated AMD card and no such issues). This is the same Arch installation (except I added NVidia drivers), so I'm sure this is Nvidia-related. The laptop has both an integrated AMD card and a dedicated Nvidia one, but I disabled the former in the BIOS because it was causing other issues, and the PC feels more repsonsive now. I don't remember if I had this issue while having both cards on, I think not. I can still switch to another TTY and back, and type commands in it, but I didn't find any commands that helped. *One time* pressing random hotkeys made it unstuck, but I wasn't able to replicate that. I can still move the mouse in this state, and the cursor changes according to the apps I'm supposed to have open. But if I click, the cursor shape gets stuck to whatever it is now. Unplugging and plugging a second monitor doesn't help. --- I'm using Xfce, with light-locker and lightdm-gtk-greeter. I haven't tried xfce4-screensaver instead of light-locker because it has other issues (doesn't disable backlight in the locked state). I'm on Arch Linux, on the latest kernel which is 6.12.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:41 +0000 x86_64 GNU/Linux. I'm using open-source Nvidia drivers from the nvidia-open package. I also tried nvidia-open-dkms on the LTS kernel, but no cigar, and the LTS kernel gives me other issues. This is the full list of nvidia-related packages I have installed, from pacman -Qs nvidia:

local/egl-gbm 1.1.2-1
local/egl-wayland 4:1.1.17-1
local/egl-x11 1.0.0-1
local/lib32-libvdpau 1.5-3
local/lib32-nvidia-utils 565.77-1
local/libvdpau 1.5-3
local/libxnvctrl 565.57.01-1
local/nvidia-open 565.77-11
local/nvidia-prime 1.0-5
local/nvidia-settings 565.57.01-1
local/nvidia-utils 565.77-3
local/xf86-video-nouveau 1.0.18-1 (xorg-drivers)

This is a Lenovo LOQ 2024 laptop (15AHP9, 83DX0070RK). Neofetch identifies following hardware:

CPU: AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (16) @ 
GPU: AMD ATI 05:00.0 Phoenix3 
GPU: NVIDIA GeForce RTX 4050 Max-Q / Mobile

After my most recent pamac update my system now has a screen timeout/lock enabled which I didn't have set up before. This seems to stem from light-locker having a _lock after screensaver 5_ setting showing via light-locker --debug, but I don't know what settings the update actually modified since the power manager still claims the screen should never sleep. So how can I figure out what has been modified without my consent and fix this again?

Got a ~10 year old laptop that sometimes has problems with monitor coming back from sleep requiring battery to be pulled to fix. Forums mentioned Lightdm and lightlocker possibly being issues. I swapped Lightdm to LXDM fine, but it looks like light locker is still there. I'm trying to figure out where light locker fits in the proccess, but I can't even recall where the script LXDM kicks off my desktop session resides, so I'm asking you guys. Thnaks

I had the following setup: - For my screensaver, I used xscreensaver (because it's beautiful) - To lock my screen, I used light-locker (because it's more secure then xscreensaver) Recenctly, xscreensaver started binding to org.freedesktop.ScreenSaver on dbus. As a consequence, I cannot run them both anymore in parallel, cause the one I started after the other complains that a screensaver is already running. I read in the ArchWiki that there is some possibility to override services. But it is very vague and I'm not familiar with d-bus. Is there a way to have the two side-by-side without tampering with the source code of one of them? For the record: unsetting the DBUS_SESSION_BUS_ADDRESS environment variable before starting ether screensaver does not work. Edit: As far as I've seen in my research, it does not seem to be possible to prevent a program to listen to a d-bus service without causing trouble to this program. If someone can confirm me this, it would make a very good answer.

When I lock my session on xfce, Firefox and apps that rely on socket connections get their connections terminated. I find such behavior bizarre. I haven't been able to figure out why it happens or how it happens or how to disable it. I've tested with http/XMLHttpRequest ping and they are kept, but WebSockets go down as soon I lock the screen. Is there a reason for this behavior and how to disable?

(Possibly related to https://unix.stackexchange.com/questions/485591/after-unlocking-light-locker-screen-remains-blank-proportional-to-how-long-its) I’ve recently switched from xscreensaver to light-locker because of an annoying bug that hit me during the upgrade to xscreensaver 6.00). Am very happy with the switch except for the following issue: when I unlock back into my session, it appears that browsers were somehow suspended or maybe just lost network, because: * Electron apps show that they are reconnecting (Not really an issue) * Firefox appears to be doing CPU intensive work for ~2 minutes (for an overnight lock) and is unusable during that time frame. I assume it’s catching up with everything it missed? The 2 minutes of inoperative Firefox are a real hassle. Things that narrow it down: * This is on a desktop box that has continuous network access. (Not a laptop that loses wifi when lid closed etc.) * I’ve observed that other apps (launched from the command line prior to locking) have network access while the session is locked. (They continue serving data). * I’ve sshed into the box during lock and using ps/top, I’ve determined that firefox wasn’t “kill -STOPed” So my best guess is that something tells browsers to discontinue their use of network while the session is locked. Any idea what that might be? Maybe something systemd related? It doesn’t sound like such a terrible idea to suspend browsers while session is locked, but then is there any way to understand what Firefox is doing during these 2 minutes? (Trying to go to about:performance doesn't do anything because Firefox is just too busy to even answer that). **Update (10 Oct 2021):** It looks like light-locker invokes loginctl lock-session ... and I think that's what's driving the behavior of the browsers. This answer by @user1686 suggests that loginctl sends a "lock" signal to all the apps and so I guess what I need to do now is find out how Firefox responds to this and why it hangs as a result. **Major Update (16 Oct 2021):** With some strace-ing and experimentation, I've narrowed this down further to an unlikely place: hardware acceleration! During its minutes long busyloop, Firefox was of course making lots of syscall, but these really caught my attention:

[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_BUSY, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_MADVISE, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_PWRITE, 0x7f16e5c96260) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_BUSY, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_MADVISE, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_PWRITE, 0x7f16e5c96260) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_BUSY, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_MADVISE, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_PWRITE, 0x7f16e5c96260) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_BUSY, 0x7f16e5c96220) = 0
[pid 165855] 13:07:06 ioctl(35, DRM_IOCTL_I915_GEM_MADVISE, 0x7f16e5c96220) = 0

(Repeated many times, not exactly in the above pattern) First, I disabled the "Widevine Content Decryption Module provided by Google Inc." plugin. That didn't help. Then I tried disabling "Use hardware acceleration when available" in Performance → Settings and that did the trick: the next day Firefox was available immediately after I unlocked!!! While my immediate problem is solved, it still leaves me with a lot of questions: * This hardware acceleration box seems like a fairly coarse & opaque toggle that controls way more than I though (DRM?!?). What exactly does it do? * I still don't know how loginctl communicates with the browsers. A D-bus message? * How are the two linked? Is there a way to get some internal log that would be easier to make sense of than strace output? **Minor update (17 Oct 2021):** Unticking Digital Rights Management (DRM) Content → Play DRM-controlled content doesn't fix the issue (i.e. I can't turn hardware accelaration back on) **Minor update (18 Oct 2021):** Ticking Performance → Use recommended performance settings doesn't do the right thing either. I guess I'm ready to file that bug report now.

LightDM would display the greeter (login box) after Lock Screen was activated. The display with the greeter would stay on and I suspect that would chew up battery (I'm using a laptop). Is there any option to get the greeter to go blank after a short while, then a key press would turn back on the login box? I'm running Xfce 4.16 on Mint 20.2.

I am running Xubuntu 18.04. When I lock the session, the screen gets turned off instantly. I am using stock lightdm as display manager and lightlocker for locking the session. From my viewpoint the following sequence of events happens. 1. I initiate locking by running xflock4 via keyboard shortcut or clicking "Lock Screen" in the Whisker (Main) menu. 2. VT8 becomes active, a new lightdm greeter is spawned on this VT terminal and physical screen turns off at the same time. 3. My usual VT7 terminal gets seized in background with lightlocker which draws "This session is locked" screen. If press some button on the keyboard or move the mouse, the screen turns on. If I press Control-Alt-F7, I see lightlocker lock screen in my original session. If I press Control-Alt-F8 I go back to the greeter where I can enter my password. After entering the password, VT7 becomes active and lightlocker white-on-black lock screen is no longer shown. If I later go back to VT8 with Control-Alt-F8, I see a completely black screen with only a blinking cursor (seems to be in text mode). If the session timeouts and gets locked automatically, I also end up with the screen turned off. That can happen several times a day. I am using an external monitor which is very slow to turn on again. It takes around 10 seconds and that is quite annoying every single time. I would rather keep it on for an hour or more on password dialog before timing it out and turning off automatically. Also there is a non-zero chance of getting a system freeze due to buggy Intel (KMS?) drivers when doing VT switch and turning of the screen at *almost* the same time. I skimmed through lightdm and lightdm greeter docs and found no hints on how to prevent that. **Update 1** 1. I discovered an "Action" applet for the xfce4-panel that can "switch" user sessions without turning off the screen. This essentially locks the session with light-locker and shows greeter on a new VT. After some digging I discovered a command to show greeter, dm-tool switch-to-greeter. I have reassigned keyboard shortcut to lock the screen from xflock4 to dm-tool switch-to-greeter as workaround. But the problem with automatic locking and turning screen still annoys me. What is interesting that dm-tool lock and light-locker-command --lock (xflock4 calls it) behave the same and produce a turned off monitor. 1. If I uninstall light-locker (with full reboot) and do dm-tool lock, the screen also turns off. So this should not be related to light-locker... **Update 2** The question is how to keep screen turned on when locking the session via light-locker on timeout or locking manually with xflock4, not on how to disable timeouts for locking.

I've been using Awesome+LightDM with the GTK greeter on Arch Linux for some years, and I'm in the process of moving to NixOS. One issue with this has been the screen locker. I've mapped Windows-l to light-locker-command --lock . When activating that the screen goes black, then turns off. To get back to LightDM I have to press Ctrl-Alt-F7 and wait for about 10 seconds while some weird message about "being redirected to the unlock dialog" displays. I've tried installing and enabling both the "gtk" and "mini" greeters (not at the same time), but after restarting X neither of these seem to be used. How do I set either of them up? The relevant part of the configuration : services = { xserver = { displayManager.lightdm.enable = true; enable = true; layout = "us"; libinput.enable = true; windowManager = { awesome.enable = true; default = "awesome"; }; xkbOptions = "compose:caps"; xkbVariant = "dvorak-alt-intl"; }; }; I also tried enabling programs.slock, but that doesn't integrate with lightdm.

Weird problem that I've been having I think since I installed Linux Mint 19. I run xfce and light-locker is my screen locker. Whenever I unlock my screen with my password, my screen remains black for a time before showing me the desktop. From what I can tell, while it's black, my desktop is accessible and I can mouse over things and see the cursor change, even open menus, etc. It's just all black. Eventually the desktop shows up and everything is fine. Another odd aspect of this problem is that the screen remains black for a proportional time to how long it's been locked. The longer it's been locked, the longer it remains black after unlocking. So for instance if I lock the screen for a few minutes, the screen only remains black for a second, but if I lock it for a day, it remains black for a minute. I checked the .xsession-errors and syslog and couldn't find any clues. I've upgraded packages, rebooted, etc. and nothing seems to fix it. Anyone experienced this before or have an idea? I'm running the nouveau video drivers with a GeForce GTX 1050 and a GeForce GT 610 installed with three screens.

For some reason whenever the computer suspends it locks the session and I have to log back in. I'm trying to configure my own lockscreen so this is undesired. Lightlocker is installed but disabled. The behaviour occurs both when closing the lid or suspending manually with systemd or gnome. Edit: narrowed it down to it being just lightdm. GDM does not lock on its own.

I'm using light-locker as my lockscreen for my Arch Linux pc. Every time the lockscreen comes up there is this black white background image of a shoe store (seems to be the default). I really dislike it. Is there a possibility to set it to a random background image, preferably from some folder on my pc?

How to solved or bypass this problem? light-locker can hide my screen but very short time expose my screen contents when first switch to my screen by keyboard. sound contents is always expose nearl like "normal" play. $light-locker --version light-locker 1.7.0 $pulseaudio --version pulseaudio 10.0 #pulseaudio is run as non-root user $sudo pgrep --uid 0 pulseaudio $sudo pgrep --euid 0 pulseaudio $cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian HOME_URL="https://www.debian.org/ " SUPPORT_URL="https://www.debian.org/support " BUG_REPORT_URL="https://bugs.debian.org/ " $

I was reading the Arch Wiki on how to start a screen locker when suspend, but I can't get work light-locker for LightDM from my suspend@kevin.service looks like this: [Unit] Description=Screen Locker LightDM Before=suspend.target [Service] User=kevin Type=forking Environment=DISPLAY=:0 ExecStart=-/usr/bin/light-locker [Install] WantedBy=suspend.target After that I enable the service: # systemctl enable suspend@kevin.service Restarted, but when I suspend my laptop, and resume again, it just doesn't work, the status of suspend@kevin.service looks like this: ● suspend@kevin.service - Screen Locker LightDM Loaded: loaded (/etc/systemd/system/suspend@kevin.service; enabled; vendor preset: disabled) Active: inactive (dead) nov 17 12:08:37 arch-kevin light-locker: failed to commit changes to dconf: Error al lanzar («spawn») el comando «dbus-launch --autolaunch=6409fcf6b77741839c02aa4 nov 17 12:08:37 arch-kevin light-locker: failed to commit changes to dconf: Error al lanzar («spawn») el comando «dbus-launch --autolaunch=6409fcf6b77741839c02aa4 nov 17 12:08:37 arch-kevin light-locker: failed to commit changes to dconf: Error al lanzar («spawn») el comando «dbus-launch --autolaunch=6409fcf6b77741839c02aa4 nov 17 12:08:37 arch-kevin light-locker: failed to commit changes to dconf: Error al lanzar («spawn») el comando «dbus-launch --autolaunch=6409fcf6b77741839c02aa4 nov 17 12:08:37 arch-kevin light-locker: failed to commit changes to dconf: Error al lanzar («spawn») el comando «dbus-launch --autolaunch=6409fcf6b77741839c02aa4 nov 17 12:08:37 arch-kevin light-locker: failed to register with the message bus **PD:** I tried light-locker before in a terminal, typing: $ light-locker --debug Output: [gs_debug_init] gs-debug.c:106 (12:15:13): Debugging enabled [main] light-locker.c:126 (12:15:13): initializing light-locker 1.6.0 [main] light-locker.c:128 (12:15:13): lock after screensaver 5 [main] light-locker.c:129 (12:15:13): late locking 0 [main] light-locker.c:130 (12:15:13): lock on suspend 1 [init_session_id] gs-listener-dbus.c:1882 (12:15:13): Got session-id: /org/freedesktop/login1/session/c2 [init_session_id] gs-listener-dbus.c:1887 (12:15:13): Got sd-session-id: c2 [init_seat_path] gs-listener-dbus.c:1964 (12:15:13): Got seat: /org/freedesktop/DisplayManager/Seat0 [gs_listener_x11_acquire] gs-listener-x11.c:172 (12:15:13): ScreenSaver Registered [listener_dbus_handle_system_message] gs-listener-dbus.c:1084 (12:15:13): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.34 And from another terminal or just closing lid and resuming, it shows me LightDM display, for unlock my session Any workaround for making this work?

I'm using XFCE on Arch Linux and I have Gnome installed too. I wanted to have the possibility of locking the session so I switched to lightdm from gdm and installed light-locker. Now every time I wake my laptop from sleep by opening the lid, I get the following error notification: GDBus.Error:org.freedesktop.login1.OperationinProgress: There's already a shutdown or sleep operation in progress dmesg does not reveal anything that seems related to this minor annoyance. This is no big deal but I would like to get rid of this notification. Any ideas where to look?