lock goes to black screen

Lahorde commented 6 years ago

Distro : arch kernel : 4.18.6-arch1-1-ARCH

local/light-locker 1.8.0-1
    A simple session locker for LightDM
local/lightdm 1:1.28.0-1
    A lightweight display manager

Since last update, unlocking with light-locker-command --lock displays a black screen with a cursor, then cursor disappear. Before it worked like a charm. From black screen get lightm lock screen I have to switch to tty1 using Ctrl+Alt+F1 and then Ctrl + Alt + F7

melroy89 commented 6 years ago

xpaulnim commented 6 years ago

I'm having a similar issue with

distro: Xubuntu 18.10
kernel: x86_64 Linux 4.18.0-10-generic
lightdm: 1.28.0
light-locker: 1.8.0

I noticed that I can still login if I type my password into the black screen and press the enter key.

sarbash commented 6 years ago

The same is here.

sergey@debian:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (buster)
Release: testing
Codename: buster

Dual monitor configuration (notebook and hdmi-external).

Some sort of log if help:

sergey@debian:~$ light-locker --debug
[gs_debug_init] gs-debug.c:106 (01:07:21):   Debugging enabled
[main] light-locker.c:142 (01:07:21):    initializing light-locker 1.8.0
[main] light-locker.c:164 (01:07:21):    Platform:
gtk:        3
systemd:    yes
ConsoleKit: yes
UPower:     yes
[main] light-locker.c:196 (01:07:21):    Features:
lock-after-screensaver: yes
late-locking:           yes
lock-on-suspend:        yes
lock-on-lid:            yes
settings backend:       GSETTINGS
[main] light-locker.c:198 (01:07:21):    lock after screensaver 15
[main] light-locker.c:199 (01:07:21):    late locking 0
[main] light-locker.c:200 (01:07:21):    lock on suspend 1
[main] light-locker.c:201 (01:07:21):    lock on lid 0
[main] light-locker.c:202 (01:07:21):    idle hint 0
[query_session_id] gs-listener-dbus.c:2101 (01:07:21):   org.freedesktop.login1.NoSessionForPID raised:
 PID 19953 does not belong to any known session

[init_session_id] gs-listener-dbus.c:2193 (01:07:21):    Got session-id: (null)
[query_sd_session_id] gs-listener-dbus.c:2177 (01:07:21):    Couldn't determine our own sd session id: Нет доступных данных
[init_session_id] gs-listener-dbus.c:2198 (01:07:21):    Got sd-session-id: (null)
[init_seat_path] gs-listener-dbus.c:2279 (01:07:21):     Got seat: /org/freedesktop/DisplayManager/Seat0
[gs_listener_delay_suspend] gs-listener-dbus.c:449 (01:07:21):   Delay suspend
[gs_listener_x11_acquire] gs-listener-x11.c:172 (01:07:21):  ScreenSaver Registered
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (01:07:21):    obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.869
[listener_dbus_handle_session_message] gs-listener-dbus.c:1010 (01:08:15):   Received Lock request
[gs_grab_grab_root] gs-grab-x11.c:647 (01:08:15):    Grabbing the root window
[gs_grab_get_keyboard] gs-grab-x11.c:153 (01:08:15):     Grabbing keyboard widget=174
[gs_grab_get_mouse] gs-grab-x11.c:213 (01:08:15):    Grabbing mouse widget=174
[gs_manager_create_windows_for_screen] gs-manager.c:548 (01:08:15):  Creating 2 windows for screen 0
[gs_manager_create_window_for_monitor] gs-manager.c:324 (01:08:15):  Creating window for monitor 0 [0,414] (1600x900)
[gs_manager_create_window_for_monitor] gs-manager.c:324 (01:08:15):  Creating window for monitor 1 [1600,0] (1920x1080)
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 1: x=1600 y=0 w=1920 h=1080
[gs_manager_timed_switch] gs-manager.c:445 (01:08:15):   Start switch to greeter timer
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[window_map_event_cb] gs-manager.c:233 (01:08:15):   Handling window map_event event
[gs_listener_resume_suspend] gs-listener-dbus.c:513 (01:08:15):  Resume suspend: fd=14
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (01:08:15):    obj_path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:381 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[window_map_event_cb] gs-manager.c:233 (01:08:15):   Handling window map_event event
[gs_listener_resume_suspend] gs-listener-dbus.c:513 (01:08:15):  Resume suspend: fd=-1
[manager_maybe_grab_window] gs-manager.c:204 (01:08:15):     Moving grab to 0x55c0f012e780
[gs_grab_move_keyboard] gs-grab-x11.c:450 (01:08:15):    Moving keyboard grab from 174 to 4000010
[gs_grab_move_keyboard] gs-grab-x11.c:457 (01:08:15):    *** doing X server grab
[gs_grab_release_keyboard] gs-grab-x11.c:279 (01:08:15):     Ungrabbing keyboard
[gs_grab_get_keyboard] gs-grab-x11.c:153 (01:08:15):     Grabbing keyboard widget=4000010
[gs_grab_move_keyboard] gs-grab-x11.c:479 (01:08:15):    *** releasing X server grab
[gs_grab_move_mouse] gs-grab-x11.c:395 (01:08:15):   Moving pointer grab from 174 to 4000010
[gs_grab_move_mouse] gs-grab-x11.c:402 (01:08:15):   *** doing X server grab
[gs_grab_release_mouse] gs-grab-x11.c:320 (01:08:15):    Ungrabbing pointer
[gs_grab_get_mouse] gs-grab-x11.c:213 (01:08:15):    Grabbing mouse widget=4000010
[gs_grab_move_mouse] gs-grab-x11.c:425 (01:08:15):   *** releasing X server grab
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[gs_window_xevent] gs-window-x11.c:369 (01:08:15):   not raising our windows
[window_map_event_cb] gs-manager.c:233 (01:08:15):   Handling window map_event event
[gs_listener_resume_suspend] gs-listener-dbus.c:513 (01:08:15):  Resume suspend: fd=-1
[manager_maybe_grab_window] gs-manager.c:204 (01:08:15):     Moving grab to 0x55c0f012e780
[gs_grab_move_keyboard] gs-grab-x11.c:443 (01:08:15):    Window 4000010 is already grabbed, skipping
[gs_grab_move_mouse] gs-grab-x11.c:383 (01:08:15):   Window 4000010 is already grabbed, skipping
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 0: x=0 y=414 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 0: x=0 y=414 w=1600 h=900
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:197 (01:08:15):    got geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[update_geometry] gs-window-x11.c:210 (01:08:15):    using geometry for monitor 1: x=1600 y=0 w=1920 h=1080
[gs_window_move_resize_window] gs-window-x11.c:243 (01:08:15):   Move and/or resize window on monitor 1: x=1600 y=0 w=1920 h=1080
[gs_listener_send_lock_session] gs-listener-dbus.c:180 (01:08:16):   Send lock session
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (01:08:16):    obj_path=(null) interface=(null) method=(null) destination=:1.869
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (01:08:18):    obj_path=/org/freedesktop/login1/session/_3109 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1343 (01:08:18):    obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
dbus[19953]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Аварийный останов (Abnormal termination)

DE: XFCE 4.12 (latest in the official Debian repo)

Symptoms:

the locker starts
turns off both monitors (notebook's LVDS and an external HDMI-connected)
won't turn on them again till switching forth and back into another tty. Or until you blindly enter the password.

melroy89 commented 6 years ago

In my case TTY is also getting stuck and typing my password blindly + enter doesn't do anything.

I removed light-locker and installed xscreensaver with success.

ghost commented 6 years ago

The last release of light-locker was on Jul 25, 2017. It seemed to work fine on Xubuntu 18.04 but broke in Xubuntu 18.10. Has anyone reported this bug to the XFCE team?

bserem commented 6 years ago

Could this be related to https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1303736 ? It is an old issue.

dreieinhalb commented 6 years ago

Same issue here, after upgrade from Xubuntu 18.04 to 18.10.

Behaviour is the same as described above: When I switch tty to 1-6 and again to 7 it works. Also typing password with blank screen unlocks it.

For now switched also to xscreensaver.

dschrempf commented 6 years ago

Same here, I am on Arch

Linux schwarzbaer 4.18.16-arch1-1-ARCH #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018 x86_64 GNU/Linux

Name            : lightdm
Version         : 1:1.28.0-1

Name            : light-locker
Version         : 1.8.0-1

casta commented 6 years ago

Same issue here. The issue raised after upgrading to xorg-server 1.20.X, screen stuck in sleep state on unlock screen. Waking up by switching to tty then going back to X, or blindly typing the password to unlock.

Other lockers does not suffer from this (xscreensaver, xfce4-screensaver for example), so this is related to light-locker doing something unusual with DPMS that is triggered by xorg 1.20 and not 1.19.

enihcam commented 5 years ago

same issue. manjaro latest stable. intel GPU but modesettings driver.

beckmi commented 5 years ago

Seems that the only events captured by light-locker are VT switches and a successful logon. Individual keystrokes or incorrect passwords are likely to be handled by logind. There seems a signal to be missing from systemd which can cause light-locker to show the logon screen.

padrm commented 5 years ago

Same issue here (Debian unstable) for intel GPU with modesetting driver. No issue when using Xorg intel video driver.

greejb commented 5 years ago

Try the new xfce beta screensaver. Works well... Instructions on this page: https://bluesabre.org/2018/11/25/xfce-screensaver-0-1-3-released/

greejb commented 5 years ago

You may also wish to prevent other packages from updating to the experimental branch by creating the following file:

/etc/apt/preferences.d/xubuntu-dev-experimental-pin-400

with the following contents:

Package: * Pin: release o=LP-PPA-xubuntu-dev-experimental Pin-Priority: 400

Package: xfce4-screensaver Pin: release o=LP-PPA-xubuntu-dev-experimental Pin-Priority: 500

joshuah345 commented 5 years ago

same here arch linux latest acer switch alpha 12 laptop

Pleune commented 5 years ago

I'm not sure if this will help anyone, but after experiencing the same issues I found a solution here: https://bbs.archlinux.org/viewtopic.php?pid=1581078#p1581078

create a file /etc/X11/xorg.conf.d/20-intel.conf with the contents:

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod" "uxa"
EndSection

I also found that specifying the default sna instead of uxa also fixes the issue. This leads me to believe this is not directly light-locker's fault, but instead some unfortunate combination of events including light-locker locking causing X to misbehave. But, I have no real clue...

I only recently began experiencing this issue on Debian testing after updating to kernel 4.19, but I can't for the life of me track down exactly what part of update caused it.

beckmi commented 5 years ago

Might be that it helps - but with this setting Xorg uses much more CPU time. So also the battery will be drained by this setting.

vsemenoff commented 5 years ago

It seems that this behavior happens only with 'modesettting' driver which is used by default by Xorg, config file from above just switching to 'intel' driver and in such combination it works fine. But question is: why such happens?

mikeymop commented 5 years ago

Does everyone here experiencing this issue use lightdm v1.28.0?

Also do you see this line in lightdm.log:

[+48415.81s] DEBUG: Launching process 19517: /usr/bin/X -core -noreset :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt2 -novtswitch

beckmi commented 5 years ago

I am using lightdm 1.26 with Debian testing. The line in lightdm.log looks a little bit different: [+115699.02s] DEBUG: Launching process 31885: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch

mikeymop commented 5 years ago

So you're on vt7/8 and I'm on vt1/2. However we both have the -novtswitch option which on the xorg man page reads:

−novtswitch
     Disable the automatic switching on X server reset and shutdown to the VT that was active when the 
     server started, if supported by the OS.

This could be the issue, however, lightdm is switching to vt2 for the lockscreen however it's just not displaying properly.

Maybe we should look at the lightdm.conf directories

 /usr/share/lightdm/lightdm.conf.d
 /usr/share/lightdm/lightdm.conf.d/50-backup-logs.conf
 /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
 /usr/share/lightdm/lightdm.conf.d/50-minimum-vt.conf
 /usr/share/lightdm/lightdm.conf.d/50-session-wrapper.conf
 /usr/share/lightdm/lightdm.conf.d/50-user-authority-in-system-dir.conf
 /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
 /usr/local/share/lightdm/lightdm.conf.d
 /etc/xdg/lightdm/lightdm.conf.d
 /etc/lightdm/lightdm.conf.d/40-io.elementary.greeter.conf
 /etc/lightdm/lightdm.conf

@vsemenoff , @Pleune do you have any idea what generated the /etc/X11/xorg.conf.d/20-intel.conf? I dont have that file.

mikeymop commented 5 years ago

Can anyone with this issue on a modern Intel notebook (and using Intel for graphics) check if they have 20-intel.conf in /etc/X11/xorg.conf.d/?

I didn't, if you dont, try adding the following to /etc/X11/xorg.conf.d/20-intel.conf:

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod" "sna"
EndSection

When I did this I was able to see my greeter however it does still flicker (which I think is by light-locker design).

casta commented 5 years ago

indeed, it’s only an issue with modesetting driver. It’s fine with intel driver. May be related to https://gitlab.freedesktop.org/xorg/xserver/issues/52

beckmi commented 5 years ago

Did you check your CPU usage? If I use the intel driver Xorg uses constantly one core at 100%. In a multicore system you probabely don't see it immediately, but it consumes a lot of power ...

casta commented 5 years ago

No CPU issue, but I uses the last git version of intel driver. No battery power issue on my laptop.

mikeymop commented 5 years ago

@beckmi did you see that CPU usage on the lockscreen or oh your desktop to?

beckmi commented 5 years ago

I did not check remotely while the screen is locked. On the desktop Xorg constantly uses one core.

mikeymop commented 5 years ago

I dont experience this issue on the desktop. Intel 6200u, Pantheon DE.

beckmi commented 5 years ago

Have played around a little bit with this setting now:

The CPU usage seems to be bound to gnome-terminal. When using the terminal with normal size (24x80) the CPU usage is at an acceptable level (2-3%). But as soon as I make use of the full monitor size (72x313) the CPU usage increases. Funny enough this does not happen with xterm, thunderbird, firefox, ...

GoogleBeEvil commented 5 years ago

i remember that when the black screnn shows ,my cpu fans works crazy, and memory ， swap were used up. i do have acpi_backlight=vendor which is mentioned in https://github.com/the-cavalry/light-locker/issues/124

vsemenoff commented 5 years ago

I've just switched to slick-greeter from default gtk-greeter and it works well with modesetting driver. Current soft versions:

local/light-locker 1.8.0-2 local/lightdm 1:1.28.0-3 local/lightdm-slick-greeter 1.2.4-1 local/linux 5.0.2.arch1-1 (base)

cat /boot/loader/entries/default.conf title Default linux /vmlinuz-linux initrd /intel-ucode.img initrd /default.img options [removed unneeded here] intel_iommu=on iommu=pt mem_sleep_default=deep quiet

I'm also using i915 DKMS driver (from 5.0 kernel) patched to fix framebuffer issue on Dell XPS 9570 notebooks, but suppose that is not related to current issue since behavior is the same with 4.x kernels.

Btw, /etc/X11/xorg.conf.d/20-intel.conf usually generated by 3rd party tools like mhwd in Manjaro or driver-manager in Ubuntu, i'm using Arch so all configuration done by myself.

fractilegames commented 5 years ago

I switched to slick-greeter too and haven't seen the black screen anymore.

GoogleBeEvil commented 5 years ago

slick-greeter doesnt help on my notebook

hurricanehrndz commented 5 years ago

on 19.04 slick-greeter does work. You need copy the conf to etc. You can check with greeter is going to be used:

/usr/sbin/lightdm --show-config

ghost commented 5 years ago

Bug Report: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609

Xubuntu 19.04 Workaround if anyone wants:

sudo apt remove light-locker
sudo apt install xfce4-screensaver

casta commented 5 years ago

It seems it’s not a light-locker issue, but a lightdm-gtk-greeter issue:

if the screen is locked using dm-tool lock command (so no light-locker involved), the same issue occur
if using slick-greeter instead of lightdm-gtk-greeter, then locking using either light-locker or dm-tool the issue vanishes
if using xfce4-screensaver to lock, the gtk-greeter is not involved as xfce4-screensaver brings it’s own unlock screen, and the issue do not occur too

corsac-s commented 5 years ago

For what it's worth, I've opened a bug on the i915 component at https://bugs.freedesktop.org/show_bug.cgi?id=110863

It's unclear to me where exactly the problem lies (light-locker, lightdm, lightdm-gtk-greeter, modesetting or i915), and there's a lot of noise surrounding the issue (and I'm adding some myself).

benzkji commented 5 years ago

Some more noise, and maybe help. For me, on xubuntu 19.04, just removing the light-locker package and installing xfce4-screensaver, resolves the problem. With occasional flickr and a somewhat hacky view of lightdm, but it works, even after suspend.

I'm aware that this is another workaround, not targeting the root cause...

snugglej commented 5 years ago

Just to put my input in this, I have the same problem on a brand new install of debain 10. I will get a black screen with a mouse. The momement I move TTY 1-7 and then go back to TTY-8 the lightdm will appear.

I'm calling light-locker-command and this is happening.

If there are some debug settings I can do or more logs I can provide, please let me know.

Logs from lightdm.log [+4496.37s] DEBUG: Seat seat0: Creating greeter session [+4496.37s] DEBUG: Seat seat0: Creating display server of type x [+4496.37s] DEBUG: Using VT 8 [+4496.37s] DEBUG: Seat seat0: Starting local X display on VT 8 [+4496.37s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log [+4496.37s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1 [+4496.37s] DEBUG: XServer 1: Launching X Server [+4496.37s] DEBUG: Launching process 3872: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+4496.37s] DEBUG: XServer 1: Waiting for ready signal from X server :1 [+4496.91s] DEBUG: Seat seat0 changes active session to [+4499.11s] DEBUG: Got signal 10 from process 3872 [+4499.11s] DEBUG: XServer 1: Got signal from X server :1 [+4499.11s] DEBUG: XServer 1: Connecting to XServer :1 [+4499.13s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) [+4499.13s] DEBUG: Seat seat0: Display server ready, starting session authentication [+4499.13s] DEBUG: Session pid=3880: Started with service 'lightdm-greeter', username 'lightdm' [+4499.16s] DEBUG: Session pid=3880: Authentication complete with return value 0: Success [+4499.16s] DEBUG: Seat seat0: Session authenticated, running command [+4499.16s] DEBUG: Session pid=3880: Running command /usr/sbin/lightdm-gtk-greeter [+4499.16s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm [+4499.16s] DEBUG: Session pid=3880: Logging to /var/log/lightdm/seat0-greeter.log [+4499.25s] DEBUG: Activating VT 8 [+4499.25s] DEBUG: Locking login1 session 2 [+4499.25s] DEBUG: Activating login1 session c5 [+4499.25s] DEBUG: Seat seat0 changes active session to c5

bellera commented 5 years ago

Same problem. Very easy to test/reproduce doing:

$ light-locker-command -l

I can return to my session doing Ctrl+Alt+F1 + Ctrl+Alt+F7 and waiting unlock for the greeter.

Also just typing my user password and hit the Return key returns to my session.

Lubuntu 18.04.3 64 bit fresh install + updates

$ lsb_release -d Description: Ubuntu 18.04.3 LTS

$ uname -rm 5.0.0-27-generic x86_64

Acer TravelMate B118-M (TMB118-M-C4AL manufactured date 2019/05/23)

bellera commented 5 years ago

slick-greeter is a good workaround but I had to configure it manually. Perhaps for this some people is saying that doesn't work for them.

apt-get install slick-greeter cd /etc/lightdm/lightdm.conf.d cp -p /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf .

lightdm --show-config

shows:

I greeter-session=slick-greeter

reboot and it works! No more blank screen when light-locker is activated.

ThibautSF commented 4 years ago

Thanks! I made some progression, now I have a black/blank screen after the login instead of before. Still only after the system wakes up.

Versions :

Ubuntu 18.04.4 LTS (Bionic Beaver)
lightdm 1.26.0
light-locker 1.8.0
slick-greeter 1.1.4

~$ lightdm --show-config
   [Seat:*]
K  allow-guest=false
M  greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session
N  guest-wrapper=/usr/lib/lightdm/lightdm-guest-session
U  greeter-session=slick-greeter
P  xserver-command=X -core
Q  greeter-setup-script=xubuntu-numlockx
S  user-session=xubuntu
T  type=xlocal
T  display-setup-script=/sbin/prime-offload
T  display-stopped-script=/sbin/prime-switch

   [LightDM]
L  backup-logs=false

Sources:
K  /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
L  /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
M  /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
N  /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
O  /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
P  /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
Q  /usr/share/lightdm/lightdm.conf.d/50-xubuntu-numlock.conf
R  /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
S  /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf
T  /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
K  /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
L  /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
M  /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
N  /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
O  /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
P  /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
Q  /usr/share/lightdm/lightdm.conf.d/50-xubuntu-numlock.conf
R  /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
S  /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf
T  /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf
U  /etc/lightdm/lightdm.conf.d/50-slick-greeter.conf

EddieB216 commented 4 years ago

I believe I have this same issue, but it doesn't appear to be related to light-locker or even LightDM. When I "Switch User" and then click unlock, I get a black screen with only mouse cursor for 2 seconds plus an amount of time that is directly proportionate to how long my PC was in DPMS (after 495 minutes in DPMS the black screen is up for a very long 327 seconds). This only happens with NVidia drivers (nouveau drivers don't have any delay at all). I tested on fresh installs of both Ubuntu 19.10 with default gdm and UbuntuStudio 19.10 with LightDM. If I prevent DPMS by moving my mouse every few minutes, then I only have the 2 second delay. I might have even had the same results on Ubuntu 18.04, but I'm not entirely sure if those issues then were because of old NVidia video card that is no longer supported by NVidia.

Methods that cause delay:

Click "Switch User" on the Whisker menu.
Click "Switch User" on the "Action Buttons" on panel 0.
dm-tool switch-to-greeter #(displays greeter)
dm-tool lock #115 (starts DPMS, then greeter)

Methods that DO NOT cause delay:

Click "Lock" on the "Action Buttons" on panel 0.
xdotool key Ctrl+alt+l #(runs screensaver, only delay if click "Switch User")
xflock4 #(runs screensaver, only delay if click "Switch User")
xset dpms force off (runs screensaver, but does not ask for password)

The switch to slick-greeter fixed my issue, but I'd still like to get this fixed so that I can use Ubuntu with gdm. Another interesting fix that slick-greeter provided is that under LightDM only the first user logged in was able to read any USB flash sticks that were plugged in during boot, but with slick-greeter I can now have both users read the USB sticks at the same time. Thank you so much for providing this fix!

EddieB216 commented 4 years ago

Sorry, I was wrong... slick-greeter did not fix my issue. I don't seem to have the 2 second delay anymore, but I still have the delay (blank screen) after DPMS.

corsac-s commented 4 years ago

Can you try with a recent enough kernel? https://bugs.freedesktop.org/show_bug.cgi?id=110863 pointed to a kernel commit in 5.3.7 which fix (or workarounds) the issue. Not sure if it has been backported to older kernels but it's worth trying.

EddieB216 commented 4 years ago

Last night I tried the nightly build of UbuntuStudio 20.04 (kernel 5.4.0-14-lowlatency) and it was no better. Today I installed kernels 5.4.22-050422-lowlatency and 5.5.6-050506-lowlatency and they were also no better. The other day I did fresh install of UbuntuStudio 18.04 and could not reproduce this issue on that OS. I'm not sure if the link you provided was talking about the issue being in the kernel or xorg/xserver. I'll see if I can figure out how to update xorg.

sohrob commented 4 years ago

Experiencing the same issue here on Debian Buster Stable running Xfce. Kernel version: 4.19.0-8-amd64

zoof commented 4 years ago

The backported Debian 10 kernel (5.5.0-0.bpo.2-amd64) fixed it for me on both an Acer S7 and a Dell E6530.

the-cavalry / light-locker

lock goes to black screen #114