• Lockscreen is black, can't log in again


    Hi, I’ve installed Antergos on my desktop machine an now tried for one week to get the lock screen running.

    Whenever I lock the screen, the display turns immediatly black. I can see a mouse pointer, but I can’t enter my password and log back into the session.

    The system is set up with Gnome desktop, I have an Nvidia graphic card.

    I think I tried every suggested solution, but nothing helped up to now…

    Thanks in advance for your help,
    Thomas

  • Are you running Nvidia drivers or Nouveau and also is your machine equiped with solely a Nvidia card or do you have one with a Nvidia and integrated Intel graphics?

  • which locker do you use ? what tells .xsessions-error ?

  • journalctl -b1
    

    ?

  • It suddenly dawned on me, assuming you’ve installed Gnome (the default DE of Antergos)
    Try installing GDM instead of Lightdm.
    In case you don’t know what I’m talking abot: Lightdm is the screen with the Antergos logo where you enter your password. Lightdm is the default greeter of Antergos, but Gnome and all its functions work better with GDM.
    Just open the terminal and type the following:

    sudo pacman -S gdm
    

    Then

    sudo systemctl disable lightdm && sudo systemctl enable gdm
    

    Then reboot and after reboot, the lockscreen will work better.

  • sudo systemctl -f enable gdm
    

    Will do it in one command (-f for force)

  • The system is equiped solely with the Nvidia card

    $ lspci | grep VGA
    01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
    

    I’m using the nvidia drivers:

    $ lspci -v -s 01:00.0
    01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
    	Flags: bus master, fast devsel, latency 0, IRQ 44, NUMA node 0
    	Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
    	Memory at c0000000 (64-bit, prefetchable) [size=256M]
    	Memory at d0000000 (64-bit, prefetchable) [size=32M]
    	I/O ports at e000 [size=128]
    	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
    	Capabilities: <access denied>
    	Kernel driver in use: nvidia
    	Kernel modules: nouveau, nvidia
    
    
    
  • @ringo32 said in Lockscreen is black, can't log in again:

    which locker do you use ? what tells .xsessions-error ?

    I’m using lightdm with lightlocker (well the default, didn’t change it).

    The .xsession-errors and .xsession-errors.old are empty.

  • @judd said in Lockscreen is black, can't log in again:

    journalctl -b1
    

    ?

    The output is too long for this forum, so I’ve uploaded the output to google drive journal.txt

  • @Bryanpwo said in Lockscreen is black, can't log in again:

    It suddenly dawned on me, assuming you’ve installed Gnome (the default DE of Antergos)
    Try installing GDM instead of Lightdm.

    Then reboot and after reboot, the lockscreen will work better.

    I’ve tried this, but then I ran into the next problem with missing shutdown buttons like described here: Shutdown button gone after switching from lightdm to gdm

    Also I find lightdm more beautiful than gdm. But if gdm would realy work I’d swith.

  • @thomass
    If you want to give GDM a try again, (I agree that Lightdm does look better, but Gnome performs better with GDM), go to tweak tools and disable the status menu bar, then reboot. (just type in reboot in the terminal)

  • @thomass said in Lockscreen is black, can't log in again:

    VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

    is a legacy card (340xx driver needed)=> https://antergos.com/wiki/hardware/graphics/antergos-nvidia-installer-2/#All_supported_cards_for_nvidia-390xx
    pacman -Qs nvidia will show what is installed

    logs show a trace nvidia related:

    Feb 02 15:30:07 Knecht kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
    Feb 02 15:30:07 Knecht kernel: WARNING: CPU: 2 PID: 472 at mm/usercopy.c:83 usercopy_warn+0x7d/0xa0
    Feb 02 15:30:07 Knecht kernel: Modules linked in: snd_hda_codec_hdmi nvidia(POE) edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic kvm_amd drm ccp snd_hda_intel snd_hda_codec agpgart rng_core snd_hda_core mousedev snd_hwdep kvm input_leds snd_pcm snd_timer irqbypass snd soundcore r8169 sp5100_tco realtek eeepc_wmi asus_wmi libphy i2c_piix4 crct10dif_pclmul k10temp fam15h_power crc32_pclmul ghash_clmulni_intel sparse_keymap aesni_intel aes_x86_64 wmi_bmof rfkill mxm_wmi crypto_simd cryptd glue_helper pcc_cpufreq acpi_cpufreq evdev pcspkr mac_hid wmi sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto hid_generic usbhid hid sr_mod cdrom sd_mod ohci_pci ahci libahci firewire_ohci firewire_core xhci_pci crc_itu_t crc32c_intel libata xhci_hcd ehci_pci scsi_mod ehci_hcd ohci_hcd
    Feb 02 15:30:07 Knecht kernel: CPU: 2 PID: 472 Comm: Xorg Tainted: P           OE     4.20.6-arch1-1-ARCH #1
    Feb 02 15:30:07 Knecht kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 EVO R2.0, BIOS 2501 04/09/2014
    Feb 02 15:30:07 Knecht kernel: RIP: 0010:usercopy_warn+0x7d/0xa0
    Feb 02 15:30:07 Knecht kernel: Code: 6b a4 41 51 4d 89 d8 48 c7 c0 1d 5b 6a a4 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 80 73 6b a4 4c 89 d2 48 89 c6 e8 4d 66 e1 ff <0f> 0b 48 83 c4 18 c3 48 c7 c6 7e 42 6a a4 49 89 f1 49 89 f3 eb 96
    Feb 02 15:30:07 Knecht kernel: RSP: 0018:ffffbdd70424bbb8 EFLAGS: 00010286
    Feb 02 15:30:07 Knecht kernel: RAX: 0000000000000000 RBX: ffffa28b1a2bae58 RCX: 0000000000000000
    Feb 02 15:30:07 Knecht kernel: RDX: 0000000000000007 RSI: ffffffffa46a427e RDI: 00000000ffffffff
    Feb 02 15:30:07 Knecht kernel: RBP: 0000000000000003 R08: 0000000000000001 R09: 0000000000000397
    Feb 02 15:30:07 Knecht kernel: R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
    Feb 02 15:30:07 Knecht kernel: R13: ffffa28b1a2bae5b R14: ffffa28b1a2bae58 R15: ffffa28b1a2baea0
    Feb 02 15:30:07 Knecht kernel: FS:  00007f34d18a6dc0(0000) GS:ffffa28b2eb00000(0000) knlGS:0000000000000000
    Feb 02 15:30:07 Knecht kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 02 15:30:07 Knecht kernel: CR2: 00007f34caafd000 CR3: 0000000421b72000 CR4: 00000000000406e0
    Feb 02 15:30:07 Knecht kernel: Call Trace:
    Feb 02 15:30:07 Knecht kernel:  __check_object_size+0xc1/0x175
    Feb 02 15:30:07 Knecht kernel:  os_memcpy_to_user+0x21/0x40 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  _nv001372rm+0xa5/0x260 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv004784rm+0x4eba/0x5500 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv004331rm+0xec/0xf0 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv004326rm+0xca/0x650 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv015126rm+0x576/0x5c0 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv000694rm+0x2e/0x60 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _nv000789rm+0x5f5/0x8b0 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? _raw_spin_unlock_irqrestore+0x20/0x40
    Feb 02 15:30:07 Knecht kernel:  ? rm_ioctl+0x73/0x100 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? nvidia_ioctl+0x14f/0x4a0 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? nvidia_frontend_ioctl+0x2d/0x50 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? nvidia_frontend_unlocked_ioctl+0x19/0x20 [nvidia]
    Feb 02 15:30:07 Knecht kernel:  ? do_vfs_ioctl+0xa4/0x630
    Feb 02 15:30:07 Knecht kernel:  ? syscall_trace_enter+0x1d3/0x2d0
    Feb 02 15:30:07 Knecht kernel:  ? ksys_ioctl+0x60/0x90
    Feb 02 15:30:07 Knecht kernel:  ? __x64_sys_ioctl+0x16/0x20
    Feb 02 15:30:07 Knecht kernel:  ? do_syscall_64+0x5b/0x170
    Feb 02 15:30:07 Knecht kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
    

    and gnome + display:

    Feb 02 15:30:43 Knecht gsd-xsettings[802]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
    

    There is also an updated Firmware/BIOS version aviable as far as i can see:

    Feb 02 15:29:59 Knecht kernel: DMI: To be filled by O.E.M. To be filled by O.E.M./M5A97 EVO R2.0, BIOS 2501 04/09/2014
    

    Version 2603
    2015/03/273.07 MBytes
    M5A97 EVO R2.0 BIOS 2603

  • @joekamprad said in Lockscreen is black, can't log in again:

    I think the 340xx drivers are installed.

    $ pacman -Qs nvidia
    local/lib32-libvdpau 1.1.1-3
        Nvidia VDPAU library
    local/lib32-nvidia-340xx-utils 340.107-3
        NVIDIA drivers utilities (32-bit)
    local/libvdpau 1.1.1+3+ga21bf7a-1
        Nvidia VDPAU library
    local/nvidia-340xx 340.107-58
        NVIDIA drivers for linux, 340xx legacy branch
    local/nvidia-340xx-utils 340.107-3
        NVIDIA drivers utilities
    
    

    Concerning the BIOS update: I have never updated the BIOS before, because I’ve always been afraid to crash the system completely. Do you really think that might solve the problem.

  • @thomass said in Lockscreen is black, can't log in again:

    Concerning the BIOS update: I have never updated the BIOS before, because I’ve always been afraid to crash the system completely. Do you really think that might solve the problem.

    as it says only: Enhance compatibility with some USB devices as description for the update i do not see that it will solve the problem…

  • @Bryanpwo said in Lockscreen is black, can't log in again:

    @thomass
    If you want to give GDM a try again, (I agree that Lightdm does look better, but Gnome performs better with GDM), go to tweak tools and disable the status menu bar, then reboot. (just type in reboot in the terminal)

    So, I installed gdm and by disabling the “Status menu buttons” extension in the tweak tool I now can lock the screen and log back in. Thank you very much!
    The remaining pitfall is, that I have to do this manually for ervery user…

    But the lock screen only shows the lock screen image for maybe one second, then the screen goes black. I found this behavior already described here (https://bbs.archlinux.org/viewtopic.php?id=171750) but I haven’t found a solution.

    Are there any hints, how I can configure the lock screen to show the picture for a certain time before going black?

  • @thomass
    Once you’ve changed the setting in every user, it will stay that way.
    I also searched for a solution to show the lockscreen longer, but like you I didn’t find anything. My guess is that it is a build in energy saving setting within Gnome, that can’t be altered. (just like you can’t change the background picture of GDM.)

  • @Bryanpwo said in Lockscreen is black, can't log in again:

    (just like you can’t change the background picture of GDM.)

    You can change the background picture of GDM. Log-in screen background image

  • @thomass
    I’ve seen that one, but Gnome devs have changed things with version 3.20/3.30.

  • @Bryanpwo
    Well, it worked for me. I now have a picture in the background instead of flat grey.

  • @thomass
    okay, to be honest I’ve heard and read that this method didn’t work in 3.30, so I didn’t try. I’m going to try it later, Thanks for sharing your experience.

black83 lockscreen15 Posts 21Views 157
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.