[Solved] No password field in login screen after resume

[stippi (Uwe S.)]

System:

• Kernel: 5.7.6-201.fc32.x86_64 x86_64 bits: 64 Desktop: Cinnamon 4.6.5 *
• Distro: Fedora release 32 (Thirty Two) *
  Machine:
• Type: Laptop System: LENOVO product: 20FB006BGE v: ThinkPad X1 Carbon 4th *
• serial: *
• Mobo: LENOVO model: 20FB006BGE v: SDK0J40697 WIN serial: *
• UEFI: LENOVO v: N1FET71W (1.45 ) date: 12/10/2019*
  I have the following issue:
  After reopening the lid and resume from standby (suspend to RAM) I don’t have the expected login screen with the password field in the center or on the left side, but a picture of the desktop without any functionaltity. Inserting the users password (blind, w/o seeing it) will open the desktop and everything is fine. If I lock the screen with CTRL + L and then press ESC, the usual login screen appears as I would expect with the password field in the center. Entering the password as usual works fine - everything is okay.

Has anyone else faced this issue? Has anyone a solution to it?

Thank you in advanced for any suggestions
stippi

[jpbn (Jaap Bosman)]

@stippi Some laptops do have this problem with resume. (lots of pages with like questions on the web) When did this problem start?

[stippi (Uwe S.)]

Hi jpbn,

Thank you for your reply.

It appears for the first time recently, this week, a few days (maybe 3) ago.

[jpbn (Jaap Bosman)]

Did you update, install smthing?

[stippi (Uwe S.)]

Hi jpbn,

I often do updates as soon, they are available.
From /var/log/dnf.log

2020-06-30

libX11-1.6.9-3.fc32.i686
libX11-xcb-1.6.9-3.fc32.i686
libXScrnSaver-1.2.3-5.fc32.i686
libXau-1.0.9-3.fc32.i686
libXcomposite-0.4.5-2.fc32.i686
libXcursor-1.2.0-2.fc32.i686
libXdamage-1.1.5-2.fc32.i686
libXext-1.3.4-3.fc32.i686
libXfixes-5.0.3-11.fc32.i686
libXft-2.3.3-3.fc32.i686
libXi-1.7.10-3.fc32.i686
libXinerama-1.1.4-5.fc32.i686
libXrandr-1.5.2-3.fc32.i686
libXrender-0.9.10-11.fc32.i686
libXtst-1.2.3-11.fc32.i686
libXxf86vm-1.1.4-13.fc32.i686

mesa-dri-drivers-20.1.2-1.fc32.i686
mesa-filesystem-20.1.2-1.fc32.i686
mesa-libGL-20.1.2-1.fc32.i686
mesa-libglapi-20.1.2-1.fc32.i686
mesa-vulkan-drivers-20.1.2-1.fc32.i686

vulkan-loader-1.2.135.0-1.fc32.i686

2020-07-01

cinnamon-4.6.5-1.fc32.x86_64
cinnamon-control-center-4.6.1-1.fc32.x86_64
cinnamon-control-center-filesystem-4.6.1-1.fc32.x86_64
cinnamon-desktop-4.6.2-1.fc32.x86_64
cinnamon-menus-4.6.0-1.fc32.x86_64
cinnamon-screensaver-4.6.0-1.fc32.x86_64
cinnamon-session-4.6.1-1.fc32.x86_64
cinnamon-settings-daemon-4.6.4-1.fc32.x86_64
cinnamon-themes-1:1.8.6-1.fc32.noarch
cinnamon-translations-4.6.1-1.fc32.noarch

lightdm-settings-1.4.2-1.fc32.noarch
mint-themes-1:1.8.6-1.fc32.noarch
mint-themes-gtk3-1:1.8.6-1.fc32.noarch
mint-x-icons-1.5.5-1.fc32.noarch
mint-y-icons-1.4.3-1.fc32.noarch
mint-y-theme-1:1.8.6-1.fc32.noarch

slick-greeter-cinnamon-1.4.0-1.fc32.noarch

Can this be of any help?

To be clear: This is not a serious problem, the machine is working, although I was wondering how does it come that way. Maybe it’ll be repaired by a future update.

[stippi (Uwe S.)]

Hi jpbn,

I found out what it was! I had “Xpra” (https://xpra.org/) installed here. A friend of mine reported yesterday he also hat Xpra installed on his Linux Mint machine. At some point after removing Xpra his Xwindow-system broke and he had no access to the desktop anymore and only could boot in recovery mode. After reinstalling Xwindow-Xorg packages he had access to the desktop again.

This made me thinking and I came to the conclusion to get rid of the Xpra installation as well. That was the solution. Now I have the login screen back again and everything is fine again.

Closing the lid, let the machine go to suspend, wait a second and reopen the lid - login screen shows background picture, user-picture and password field as expected.

Don’t ask me where this Xpra thing comes from. Knowingly I didn’t installed it, maybe it has come together with some other tools or piece of software. It has it’s own codecs brought to the system as a part of the installation plus some other packages. Maybe there is some kind of incompatibility in one of the packages.

Thank your for your support. Have a nice day.
stippi