Manjaro ARM 20.04

[Der Geist der Maschine]

I installed Manjaro xfce end of November 2019. I keep on upgrading without a fresh install.

When the screensaver xfce4-screensaver kicks in (either on its own timeout or, surprisingly through "xset dpms force off"), it blanks the screen. Upon a keyboard click, the desktop does not completely come back:

• I see the desktop with all its windows. Windows also show updates (e.g. top in a terminal)
  
• I can move the mouse.
  
• I can not click on anything.
  
• I can not type anything.
  

I need to kill xfce4-screensaver to click and type, again. It looks like the screensaver is not undoing all its tasks. It only disabled its own window so that the deskop becomes visible, again.

xfce4-screensaver would probably call that "Request unlock but we don't have any windows!":

Code:

[gs_debug_init] gs-debug.c:115 (22:42:17.334):     Debugging enabled
[main] xfce4-screensaver.c:97 (22:42:17.335):     Initializing xfce4-screensaver 0.1.10
[init_session_id] gs-listener-dbus.c:2186 (22:42:17.392):     Got session-id: /org/freedesktop/login1/session/_310
[gs_listener_init] gs-listener-dbus.c:2212 (22:42:17.392):     Acquiring logind sleep inhibitor lock
[gs_listener_x11_set_timeouts] gs-listener-x11.c:312 (22:42:17.421):     Saver timeout updated to 300 seconds
[gs_listener_x11_acquire] gs-listener-x11.c:288 (22:42:17.581):     ScreenSaver Registered
[gs_manager_request_unlock] gs-manager.c:1325 (22:42:18.427):     Request unlock but manager is not active
[xroot_filter] gs-listener-x11.c:251 (22:42:18.977):     ScreenSaver timer reset
[xroot_filter] gs-listener-x11.c:256 (22:42:21.176):     Activating screensaver on ScreenSaverOn
[gs_grab_grab_root] gs-grab-x11.c:347 (22:42:21.177):     Grabbing the root window
[gs_grab_get] gs-grab-x11.c:104 (22:42:21.367):     Grabbing devices for window=389
[gs_manager_create_windows_for_display] gs-manager.c:1178 (22:42:21.369):     Creating 1 windows for display :0
[add_overlays] gs-manager.c:1016 (22:42:21.370):     Reconfiguring monitors, adding overlays
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:224 (22:42:21.370):     Sending the ActiveChanged(TRUE) signal on the session bus
[xroot_filter] gs-listener-x11.c:251 (22:42:22.072):     ScreenSaver timer reset
[remove_overlays] gs-manager.c:1045 (22:42:23.372):     Done reconfiguring monitors, removing overlays
[gs_manager_request_unlock] gs-manager.c:1335 (22:42:26.470):     Request unlock but we don't have any windows!

I temporarily removed the ~/.config/ directory for a fresh configuration of xfce4. No change. Google is not helpful.


Update 1: further logs

Before screensaver kicks in

Code:

manjaro:~$ xfce4-screensaver-command -q
The screensaver is inactive
The screensaver is not inhibited

When screensaver kicks in

Code:

manjaro:~$ xfce4-screensaver-command -q
The screensaver is active
The screensaver is not inhibited

When I press a key, the desktop comes back (but I can neither click or type)

Code:

manjaro:~$ xfce4-screensaver-command -q
The screensaver is active
The screensaver is not inhibited

Instead of killing xfce4-screensaver, I can also ask the screensaver to deactivate itself

Code:

manjaro:~$ xfce4-screensaver-command -d

Code:

manjaro:~$ xfce4-screensaver-command -q
The screensaver is inactive
The screensaver is not inhibited

Somehow, nobody is asking to deactivate the screensaver. I don't want to do that manually all the time from the console.


Update 2: I noticed that I have the screensaver problem with fb-turbo, but no with panfrost. So, how can the screensaver get deactivated with fb-turbo? The more interesting questions are why and how does fb-turbo interfere with the screensaver in the first place?