screensaver: typing password sometimes has no effect (Regression)

I've updated two of my machines to fedora-34/xfce 4.16.0-2.fc34 and I'm having problems unlocking after screensave. When trying to unlock, I see the unlock dialog, but typing has no effect - I don't see anything happening in the dialog box. I've had to ssh in and kill the screensaver; I see the xfce4-screensaver-dialog process running. It doesn't happen every time - but I've had it on both of my machines (that are quite different hardware and displays)

The screensaver is not part of the window manager.

The way those dialog boxes work is by grabbing the keyboard (those are so called “override redirect” windows not managed by the window manager).

All that to say, based on the description, I doubt the issue is actually in xfwm4.

Yep, I couldn't find an obvious other gitlab sub-category though

moved from xfce/xfwm4#533 (moved)

added 5. Lock Screen label

Hi David,

When you killed screensaver, was it xfce4-screensaver, as the lock screen should be controlled by lightdm or something like that.

I guess https://git.xfce.org/apps/xfce4-screensaver/ (so neither lightdm nor xscreensaver)

@philipzae What I saw was:

[dg@dalek ~]$ ps -eaf|grep screen
dg          2203    1932  0 12:02 ?        00:00:00 /usr/bin/xfce4-screensaver
dg          2270    1947  0 12:02 ?        00:00:00 xscreensaver -no-splash
dg          2309    2270  0 12:02 ?        00:00:00 xscreensaver-systemd
dg         21484    2203  0 13:20 ?        00:00:00 /usr/libexec/xfce4-screensaver-dialog --monitor=1 --height=1080 --width=1920 --enable-switch
dg         21560   21521  0 13:20 pts/2    00:00:00 grep --color=auto screen

Looks like you have xfce's screensaver and xscreensaver running.

Interesting; I wonder how that's happened on both my machines (I did copy over the xfce config from one to the other a long time ago); and I don't know whether they were both running prior to the upgrade. OK, I've taken xscreensaver out of my session; lets see for a few days if xfce4-screensaver by itself behaves.

Yep, disabling xscreensaver fixes this. So, lets close this. (Still I'm curious what the change of behaviour on upgrade is; did something enable the other one, or did they start interacting differently; odd).

I suppose you disabled xscreensaver in 'Application Autostart' tab of 'Session and Startup' dialog.

xscreensaver-systemd that you seemed to have running is rather new thing in xscreensaver. (Integrated in XcreenSaver 5.43, and not present e.g. in my system Xubuntu 20.04.) If you have enabled xscreensaver, I think it will lock by it in case of suspend whem using systemd regardless of Xfce's 'Lock screen before' sleep setting.

closed

Glad to hear its resolved.

added 3. Not Xfce label

mentioned in issue xfce/xfce4-session#108 (closed)

The probable reason you had two screensaver daemons running are these bugs: xfce/xfce4-session#108 (closed) and xfce/xfce4-power-manager#127 (moved)

Ah thanks @philipzae and @jarnos - glad to know it wasn't just me going mad!

mentioned in issue #84 (closed)

marked #92 (closed) as a duplicate of this issue

marked this issue as related to #92 (closed)

marked this issue as related to xfce/libxfce4ui#64 (closed)

marked this issue as related to xfce/xfce4-session#60 (closed)

marked this issue as related to #17 (closed)

I'm reopening that one because maybe we could do a better job when grabbing keyboard, or something. There's also xfce/xfce4-session#60 (closed) still open which is related, and whose resolution would make this problem less likely (xfce/libxfce4ui#64 (closed) must have already improved things in that respect).

reopened

removed 3. Not Xfce label

mentioned in issue xfce/xfce4-session#60 (closed)

marked this issue as related to #84 (closed)

added Conflicting App label

marked #57 (closed) as a duplicate of this issue

marked this issue as related to #57 (closed)

mentioned in issue #57 (closed)