Mate-Screensaver does not engage after some amount of uptime

Bug #1783224 reported by Michael Swierczek
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mate-screensaver (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu Mate 18.04 64-bit, single monitor setup. When I first login to my account and lock screen with Ctrl+Alt+l, it locks normally and unlocks normally. After my computer is on for 12+ hours, at some point Ctrl+Alt+l no longer works.

If I run the command in the foreground in a terminal, I see this:
$ mate-screensaver --debug
[gs_debug_init] gs-debug.c:109 (19:19:05): Debugging enabled
[main] mate-screensaver.c:92 (19:19:05): initializing mate-screensaver 1.20.0
[init_session_id] gs-listener-dbus.c:2406 (19:19:05): Got session-id: /org/freedesktop/login1/session/c2
[gs_fade_init] gs-fade.c:908 (19:19:05): Fade type: 3
[set_status] gs-watcher-x11.c:363 (19:19:05): GSWatcher: not active, ignoring status changes
[gs_watcher_set_active] gs-watcher-x11.c:289 (19:19:05): turning watcher: ON
[listener_dbus_handle_system_message] gs-listener-dbus.c:1633 (19:19:05): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.254
[on_bg_changed] gs-manager.c:1038 (19:19:05): background changed
...several minutes later, I see the following but the screen is still not locked.
[listener_service_deleted] gs-listener-dbus.c:1106 (19:20:10): DBUS service deleted:
[listener_service_deleted] gs-listener-dbus.c:1106 (19:20:16): DBUS service deleted: :1.17

Should this be reported upstream to the mate-screensaver on Github? Or is there some way to determine if it's an Ubuntu-specific error?

Revision history for this message
Michael Swierczek (mike-swierczek) wrote :

Sorry, I've figured out that once I start mate-screensaver manually at the terminal hitting Ctrl+Alt+l does lock the screen. So that's a manual workaround.

Maybe when the keyboard shortcut fails, the mate-screensaver process in the background has exited? I will try to reproduce the problem and report back if mate-screensaver is still running when it occurs.

Devs, please feel free to close this ticket if you wish. And thanks for making an awesome project. I've been running The Distribution That Shall Not Be Named for years now.

Revision history for this message
Michael Swierczek (mike-swierczek) wrote :

Okay, I was able to reproduce the bug just by waiting. I have attached the output of mate-screensaver --debug from when I started it until now when the bug is active.

Revision history for this message
Michael Swierczek (mike-swierczek) wrote :
Revision history for this message
Plutocrat (plutocrat) wrote :

My screensaver is set to lock screen, but never does. Additionally, suspending the laptop doesn't lock the screen. But ctl-alt-L does work. Running Ubuntu Mate 18.04 64-bit. Have been running various flavours of Ubuntu for 12 years and this is the first one that does this.

Norbert (nrbrtx)
tags: added: bionic
Revision history for this message
Ian (superian) wrote :

In my case, the screensaver is not set to lock the screen, just show the contents of ~/Pictures, but still does not engage after a while.

The time taken to (not) do this appears random, but once it's failed to engage, it never does do so until stopped and restarted.

mate-screensaver 1.24.0-1 amd64 on focal

The output of four examples attached: ^C was used to exit each time when it failed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mate-screensaver (Ubuntu):
status: New → Confirmed
Revision history for this message
Ian (superian) wrote :

What's happening here is that the screensaver kicks in, blanks the screen to black, but ~/Pictures is not shown.

It seems to follow having Caja crash / the window manager decide that it has to rewrite all the windows in all workspaces.

Another bunch of debug outputs attached. See the number of times mate-screensaver had to be closed via ^C and restarted.

no longer affects: ubuntu-mate
Revision history for this message
thom (tsk) wrote :

still affecting: ubuntu-mate

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.