Open tblancher opened 8 years ago
raku-cat
commented
8 years ago Had this exact problem was trying to fix it for a couple hours, issue appeared to be missing xorg.conf, as the problem was occurring I sshed in and read some logs, literally the second after I ran nvidia-xconfig the lockscreen popped up. So I would run that as root or if you don't use nvidia verify that you have an /etc/xorg.conf.
dd23
commented
7 years ago I have the same problem using an up-to-date Manjaro Linux with xfce. This happened with both X server 1.18 and 1.19 and kernels 4.4, 4.8, and 4.9.
I'm using a Thinkpad T440s with integrated Intel graphics, docked with 2 external screens, in case that's relevant.
The problem occurred when using kernel modesetting as well as when I was using the default xf86-video-intel driver.
I do have an /etc/xorg.conf now, but the problem happens both with and without it.
My workaround involves logging into e.g. tty2 and killing light-locker from there…
smiddy
commented
7 years ago Same problem for ubuntu 16.04.1 with Intel Graphics on a Thinkpad T440s.
Only by ussing tty and killing lightdm
cavalier38
commented
7 years ago This sounds more like a lightdm or xorg issue. To verify if it is a light-locker issue. Run light-locker-command -l. If this gives a problem try to see if killing light-locker solves it. And try this this without light-locker: kill light-locker and run dm-tool lock. Log back in to verify everything is working properly.
Linuturk
commented
6 years ago Hey @cavalier38,
I've got the same issue, and here's what happened when I tried your suggested steps.
loginctl unlock-session <id> unlocks tty7 and I get my session back.dm-tool lock. This brought up the lock wallpaper on my 2 external monitors. The login box was most likely on my closed laptop screen. I entered my password, and I was brought to another lock screen that looked like light-locker. I logged in again and was presented with my session.After going through these steps I can no longer lock my screen with the Control + Alt + L keyboard shortcut that calls xflock4.
I launched light-locker & in my current terminal, and the system is working similar to the dm-tool lock session earlier.
Any suggestions for me or logs you need?
chronics23
commented
6 years ago I have the similiar problem on debian buster with light-locker 1.8.0.1. dm-tool switch-to-greeter and light-locker-command -l both cause the screen to go black with no ability to even switch to another tty, I end up having to ssh in and restart lightdm. The same problem happens when clicking new login on xscreensaver, I am using nvidia drivers 375.82 with multi monitor setup, one display port and one hdmi, note the display port screen turns off with no signal (even though its set as the primary), the hdmi shows the blinking cursor. A bug has also been opened on debian for this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868087
cavalier38
commented
6 years ago You can run light-locker --debug and capture the output. Also you can check /var/log/Xorg.#.log and the logs in /var/log/lightdm. light-locker should have no effect on the lock screen itself, nor the VT switching.
@Linuturk do you mean that after restarting light-locker the behaviour changed? As for xflock4, it will try different screen lockers not sure it if works without one running (also I think there was a problem that light-locker-command incorrectly reported light-locker was running)
@chronics23 if the problem is the same with dm-tool switch-to-greeter when light-locker isn't running, this is more likely to be a Xorg or driver problem, you could look at the Xorg and lightdm logs to see if they provide some information.
Linuturk
commented
6 years ago @cavalier38 Yes, restarting light-locker caused the behavior to change.
I've noticed an interesting pattern in the fast blinking mouse behavior.
loginctlchronics23
commented
6 years ago @cavalier38 agreed, at this point I'm pretty sure its a nvidia driver problem not light-locker seeing as the problem also occurs with gdm and others have mentioned it happening with nvidia legacy drivers. One interesting point i noticed is the original display seems to be running on DISPLAY :0.0 but then attempts to start the new session on DISPLAY=:1.0 , not sure if this can be changed anywhere or is even part of the problem
Linuturk
commented
6 years ago @cavalier38 Unlike @chronics23 I don't have an Nvidia chipset on the system where I experience this problem.
$ lspci
00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
3a:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
3c:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)$ lsmod
Module Size Used by
rfcomm 77824 2
ccm 20480 2
ipt_MASQUERADE 16384 1
nf_nat_masquerade_ipv4 16384 1 ipt_MASQUERADE
nf_conntrack_netlink 36864 0
nfnetlink 16384 2 nf_conntrack_netlink
xfrm_user 32768 1
xfrm_algo 16384 1 xfrm_user
iptable_nat 16384 1
nf_conntrack_ipv4 16384 3
nf_defrag_ipv4 16384 1 nf_conntrack_ipv4
nf_nat_ipv4 16384 1 iptable_nat
xt_addrtype 16384 2
iptable_filter 16384 1
xt_conntrack 16384 1
nf_nat 28672 2 nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack 131072 7 nf_conntrack_ipv4,ipt_MASQUERADE,nf_conntrack_netlink,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
libcrc32c 16384 1 nf_nat
br_netfilter 24576 0
bridge 139264 1 br_netfilter
stp 16384 1 bridge
llc 16384 2 bridge,stp
aufs 237568 0
cmac 16384 1
bnep 20480 2
nls_iso8859_1 16384 1
snd_soc_skl 65536 0
snd_soc_skl_ipc 49152 1 snd_soc_skl
snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc
snd_soc_sst_dsp 28672 1 snd_soc_skl_ipc
snd_hda_ext_core 24576 1 snd_soc_skl
snd_soc_sst_match 16384 1 snd_soc_skl
arc4 16384 2
intel_rapl 20480 0
uvcvideo 90112 0
x86_pkg_temp_thermal 16384 0
snd_hda_codec_hdmi 49152 1
videobuf2_vmalloc 16384 1 uvcvideo
intel_powerclamp 16384 0
videobuf2_memops 16384 1 videobuf2_vmalloc
snd_hda_codec_realtek 90112 1
coretemp 16384 0
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
videobuf2_v4l2 24576 1 uvcvideo
snd_soc_core 233472 1 snd_soc_skl
kvm 593920 0
snd_compress 20480 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2
irqbypass 16384 1 kvm
iwlmvm 368640 0
snd_hda_intel 36864 5
videodev 172032 3 uvcvideo,videobuf2_core,videobuf2_v4l2
snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
mac80211 782336 1 iwlmvm
media 40960 2 uvcvideo,videodev
snd_hda_core 81920 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 102400 9 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
input_leds 16384 0
joydev 20480 0
iwlwifi 229376 1 iwlmvm
serio_raw 16384 0
cfg80211 602112 3 iwlmvm,iwlwifi,mac80211
btusb 45056 0
btrtl 16384 1 btusb
mei_me 40960 0
thinkpad_acpi 94208 1
mei 102400 1 mei_me
nvram 16384 1 thinkpad_acpi
shpchp 36864 0
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
intel_pch_thermal 16384 0
ucsi 16384 0
snd_rawmidi 32768 1 snd_seq_midi
snd_seq 65536 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
hci_uart 98304 0
snd_timer 32768 2 snd_seq,snd_pcm
btbcm 16384 2 hci_uart,btusb
btqca 16384 1 hci_uart
snd 77824 23 snd_compress,snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,thinkpad_acpi,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_soc_core,snd_pcm
btintel 16384 2 hci_uart,btusb
soundcore 16384 1 snd
bluetooth 557056 33 btrtl,hci_uart,btintel,btqca,bnep,btbcm,rfcomm,btusb
tpm_crb 16384 0
intel_lpss_acpi 16384 0
intel_lpss 16384 1 intel_lpss_acpi
acpi_pad 180224 0
mac_hid 16384 0
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,parport_pc,ppdev
ip_tables 24576 2 iptable_filter,iptable_nat
x_tables 36864 5 ip_tables,iptable_filter,ipt_MASQUERADE,xt_addrtype,xt_conntrack
autofs4 40960 2
algif_skcipher 20480 0
af_alg 16384 1 algif_skcipher
dm_crypt 28672 1
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
pcbc 16384 0
uas 24576 0
i915 1449984 11
aesni_intel 167936 8
aes_x86_64 20480 1 aesni_intel
crypto_simd 16384 1 aesni_intel
glue_helper 16384 1 aesni_intel
cryptd 24576 4 crypto_simd,ghash_clmulni_intel,aesni_intel
i2c_algo_bit 16384 1 i915
usb_storage 69632 1 uas
drm_kms_helper 151552 1 i915
psmouse 139264 0
e1000e 249856 0
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
ahci 36864 3
ptp 20480 1 e1000e
drm 352256 6 i915,drm_kms_helper
pps_core 20480 1 ptp
libahci 32768 1 ahci
wmi 16384 0
video 40960 2 thinkpad_acpi,i915
pinctrl_sunrisepoint 28672 0
i2c_hid 20480 0
pinctrl_intel 20480 1 pinctrl_sunrisepoint
hid 114688 1 i2c_hid
fjes 73728 0
f35f0ef9d0e827dae86552d3899f78fc
commented
6 years ago I ran into these symptoms yesterday and was able to resolve it with raku-cat's post.
Here is how I caused the problem on my fresh Antergos + XFCE system with AMD CPU and Nvidia GPU:
To fix, I ran sudo nvidia-xconfig and then rebooted.
I did a lot of tests when I was in the problem state to conclude that it was not triggered by the screensaver setting the monitor to black or putting the monitor to sleep or turning the monitor off. The problem only happened when locking was enabled.
In my case, I would way I definitely broke it and it wasn't a light locker bug.
moobyfr
commented
6 years ago I found this issue as finding how to resolve the described bug.
nvidia + dual screen, fast flashing cursor after sleep or running dm-tools lock .
As I remember, the current process is to start another X ( DISPLAY = :1) and to show a text.
In my case, X :1 can't be run (I tested manually on tty1), because of "EE: no screen found" (I don't have any xorg.conf, which explains the error.
The X on DISPLAY 0 was started with auto configuration of the X configuration (and is working fine).
The X on DISPLAY 1 can't be started. this explains probably why it's flashing.
If I create a xorg.conf, the bug is no more presend I can use light-locker or dm-tools lock
melroy89
commented
5 years ago Same problem I have as well using Nvidia driver, Xfce v4.12 and light-locker v1.8.0. I'm using Manjaro Linux (based on Arch). Any permanent fix? Very rapidly flickering cursor in a black screen.
Maybe this issue should be taken more seriously? Since people using Manjaro will get this problem with a clean install out of the box XFCE setup.
nodiscc
commented
5 years ago I was having the same problem on Debian 9 after installing the proprietary NVIDIA drivers (nvidia-driver 390.87-8~deb9u1 from backports) with light-locker and lightdm.
Locking the screen (I use xflock4 from Xfce but any other locking command had the same effect) would send me to a black screen with a fast blinking cursor.
Using Ctrl+Alt+F1...F7 to change vtty would not work (vtty would appear for a very short time and I was sent back to the blinking cursor).
The solution I found was simply to generate a /etc/X11/xorg.conf file using sudo nvidia-xconfig.
The docs at https://wiki.debian.org/NvidiaGraphicsDrivers suggests it is no longer needed to run nvidia-xconfig, but for me it was. After running it, the screen locking mechanism immediately started working correctly.
alexIsAtGitHub
commented
4 years ago I was having the same problem on Debian 9 after installing the proprietary NVIDIA drivers (
nvidia-driver 390.87-8~deb9u1from backports) withlight-lockerandlightdm. Locking the screen (I usexflock4from Xfce but any other locking command had the same effect) would send me to a black screen with a fast blinking cursor. Using Ctrl+Alt+F1...F7 to change vtty would not work (vtty would appear for a very short time and I was sent back to the blinking cursor).The solution I found was simply to generate a
/etc/X11/xorg.conffile usingsudo nvidia-xconfig.The docs at https://wiki.debian.org/NvidiaGraphicsDrivers suggests it is no longer needed to run nvidia-xconfig, but for me it was. After running it, the screen locking mechanism immediately started working correctly.
This also addressed my issue. I confirmed the issue was still present by issuing 'light-locker-command -l' and receiving the blinking cursor. I then rebooted and generated an /etc/xorg.conf via nvidia-settings and tried the command again. This time it worked successfully.
Could this be related to dual monitors, I believe I read somewhere while troubleshooting that someone else was having the issue but only in a dual monitor configuration.
nodiscc
commented
4 years ago I had to apply this workaround again (sudo nvidia-xconfig) on Debian 10
$ LANG=C apt policy light-locker lightdm nvidia-driver
light-locker:
Installed: 1.8.0-3
100 /var/lib/dpkg/status
lightdm:
Installed: 1.26.0-4
100 /var/lib/dpkg/status
nvidia-driver:
Installed: 440.82-1~bpo10+1
ghost
commented
3 years ago Hey, i have same problem, but i have no nvidea card, i have only intel video. Artix linux, XFCE4
I'm running light-locker 1.6.0-1 and lightdm 1.16.7-1 in Arch Linux, and on one of my Arch systems locking with light-locker causes lightdm to go to a blank, non-X virtual terminal screen, with a rapidly blinking cursor (faster than the usual kernel blinking cursor). No virtual terminal is available to me, their contents flash when I switch to them, only to be immediately replaced by the rapidly blinking cursor. I thought it might be the video driver, but both nouvea and nvidia have the same problem.
If I use xscreensaver I don't have this problem, but xscreensaver is ugly and I only use it as a last resort.