screensaver won't start [$65]

[meatballz]

Ubuntu Mate 16.04

The screen fades to black, then comes right back on. I can't get the screen lock to work either, even when waking from a suspended state. Manually locking does work.

--- There is a **[$65 open bounty](https://www.bountysource.com/issues/33778587-screensaver-won-t-start?utm_campaign=plugin&utm_content=tracker%2F1635706&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1635706&utm_medium=issues&utm_source=github).

[monsta]

Seems to work here, though I'm testing in a VM.
Try choosing other screensavers from the list in mate-screensaver-preferences...

Also - do you have any error messages in ~/.xsession-errors when it happens?
Check dmesg | tail output as well.

[meatballz]

I'm still having the same problem. Changing the screensaver didn't help.

I don't know what any of this means...

Also - do you have any error messages in ~/.xsession-errors when it happens?
Check dmesg | tail output as well.

[raveit65]

Do you have compiz running?
I noticed this sometimes in the past if i used compiz, but not everytime.
Looks like it is a random issue and that something wake up the screen from idle before the start of the screensaver is finished.
Sorry, i never found the cause of this issue.

[meatballz]

I have the Mate Tweak Tool, and Marco (Compton GPU compositor) is selected. I tried it with all three Marco options, and Compiz, but I still have the same problem.

I'd check the error messages, as suggested earlier, but I don't know where, or how to look for them.

[monsta]

It seems to me that it's better to ask for support in Ubuntu MATE community - https://ubuntu-mate.org/community/.

[epgfm]

I'm affected by this too. Same setup as meatballz.
Power management is set to do stuff "Never" and to "Do nothing" when closing the laptop, "dim display" unchecked.
There's at least two other users affected on the Ubuntu MATE community forum: https://ubuntu-mate.community/t/automatic-lock-screen-not-activating/5696

[acsipak]

Here's a fresh Launchpad bug report describing something very similar:

https://bugs.launchpad.net/ubuntu/+source/mate-screensaver/+bug/1599331

Bug happens when using Marco+Compton, switching to Compiz fixes it.

[monsta]

@flexiondotorg: maybe you can reproduce it?

[raveit65]

I noticed something similar, mentioned in current m-p-m PR.
Are you using a notebook?
If yes, can can you check if it works if notebook use ac-adapter?
I meant that the screensaver doesn't start.

[acsipak]

Also here's some log output produced when the fade-reawaken glitch happens on session idle timeout:

.xsession-errors

(mate-screensaver:3080): GLib-CRITICAL **: Source ID 603 was not found when attempting to remove it

dmesg | tail

[ 6840.984128] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 6840.984133] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 6840.984136] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 6840.992224] ata1.00: configured for UDMA/133
[ 6841.432126] ata2.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out
[ 6841.432131] ata2.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out
[ 6841.432134] ata2.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out
[ 6841.456118] ata2.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 6841.456122] ata2.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[ 6841.456125] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 6841.472227] ata2.00: configured for UDMA/133
[ 6841.488120] ata2.01: configured for UDMA/100
[ 6841.540255] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 6841.675900] r8169 0000:03:00.0 enp3s0: link down
[ 6841.675905] r8169 0000:03:00.0 enp3s0: link down
[ 6841.675950] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 6843.865151] r8169 0000:03:00.0 enp3s0: link up
[ 6843.865162] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

[acsipak]

@raveit65 As mentioned in the Launchpad bug report, I'm using a desktop machine.

[raveit65]

Better use mate-screensaver --debug

[acsipak]

@raveit65 The --debug option made .xsession-errors a lot more verbose:

[watcher_idle_notice_cb] gs-monitor.c:118 (10:50:25):    Idle notice signal detected: 1
[gs_grab_grab_offscreen] gs-grab-x11.c:558 (10:50:25):   Grabbing an offscreen window
[gs_grab_get_keyboard] gs-grab-x11.c:157 (10:50:25):     Grabbing keyboard widget=1600003
[gs_grab_get_mouse] gs-grab-x11.c:196 (10:50:25):    Grabbing mouse widget=1600003
[_gs_watcher_set_session_idle_notice] gs-watcher-x11.c:210 (10:50:25):   Changing idle notice state: 1
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:25):    obj_path=/org/freedesktop/login1/session/c4 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:25):    obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:25):    obj_path=/org/freedesktop/login1/user/_1000 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:25):    obj_path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[watcher_idle_cb] gs-monitor.c:90 (10:50:35):    Idle signal detected: 1
[gs_listener_set_session_idle] gs-listener-dbus.c:486 (10:50:35):    Setting session idle: 1
[listener_check_activation] gs-listener-dbus.c:340 (10:50:35):   Checking for activation
[listener_check_activation] gs-listener-dbus.c:358 (10:50:35):   Trying to activate
[gs_grab_grab_root] gs-grab-x11.c:539 (10:50:35):    Grabbing the root window
[gs_grab_get_keyboard] gs-grab-x11.c:157 (10:50:35):     Grabbing keyboard widget=262
[gs_grab_get_mouse] gs-grab-x11.c:196 (10:50:35):    Grabbing mouse widget=262
[gs_manager_create_windows_for_screen] gs-manager.c:1732 (10:50:35):     Creating 1 windows for screen 0
[gs_manager_create_window_for_monitor] gs-manager.c:1540 (10:50:35):     Creating window for monitor 0 [0,0] (1600x900)
[update_geometry] gs-window-x11.c:544 (10:50:35):    got geometry for monitor 0: x=0 y=0 w=1600 h=900
[update_geometry] gs-window-x11.c:568 (10:50:35):    using geometry for monitor 0: x=0 y=0 w=1600 h=900
[get_best_visual_for_screen] gs-window-x11.c:759 (10:50:36):     Found best GL visual for screen 0: 0x21
[gs_window_move_resize_window] gs-window-x11.c:603 (10:50:36):   Move and/or resize window on monitor 0: x=0 y=0 w=1600 h=900
[window_map_cb] gs-manager.c:1241 (10:50:36):    Handling window map event
[clear_widget] gs-window-x11.c:429 (10:50:36):   Clearing widget
[widget_clear_all_children] gs-window-x11.c:272 (10:50:36):  Clearing all child windows
[clear_widget] gs-window-x11.c:429 (10:50:36):   Clearing widget
[widget_clear_all_children] gs-window-x11.c:272 (10:50:36):  Clearing all child windows
[window_show_cb] gs-manager.c:1340 (10:50:36):   Handling window show
[apply_background_to_window] gs-manager.c:1277 (10:50:36):   Creating background w:1600 h:900
[gs_job_set_command] gs-job.c:207 (10:50:36):    Setting command for job: 'NULL'
[gs_watcher_set_active] gs-watcher-x11.c:290 (10:50:36):     turning watcher: OFF
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:247 (10:50:36):  Sending the ActiveChanged(TRUE) signal on the session bus
[_gs_watcher_set_session_idle] gs-watcher-x11.c:237 (10:50:36):  Changing idle state: 1
[gs_window_xevent] gs-window-x11.c:969 (10:50:36):   not raising our windows
[window_map_event_cb] gs-manager.c:1228 (10:50:36):  Handling window map_event event
[manager_maybe_grab_window] gs-manager.c:1179 (10:50:36):    Moving grab to 0x24102c0
[gs_grab_move_keyboard] gs-grab-x11.c:365 (10:50:36):    Moving keyboard grab from 262 to 1600020
[gs_grab_move_keyboard] gs-grab-x11.c:374 (10:50:36):    *** doing X server grab
[gs_grab_release_keyboard] gs-grab-x11.c:237 (10:50:36):     Ungrabbing keyboard
[gs_grab_get_keyboard] gs-grab-x11.c:157 (10:50:36):     Grabbing keyboard widget=1600020
[gs_grab_move_keyboard] gs-grab-x11.c:399 (10:50:36):    *** releasing X server grab
[gs_grab_move_mouse] gs-grab-x11.c:303 (10:50:36):   Moving pointer grab from 262 to 1600020
[gs_grab_move_mouse] gs-grab-x11.c:312 (10:50:36):   *** doing X server grab
[gs_grab_release_mouse] gs-grab-x11.c:261 (10:50:36):    Ungrabbing pointer
[gs_grab_get_mouse] gs-grab-x11.c:196 (10:50:36):    Grabbing mouse widget=1600020
[gs_grab_move_mouse] gs-grab-x11.c:338 (10:50:36):   *** releasing X server grab
[manager_maybe_start_job_for_window] gs-manager.c:221 (10:50:36):    Starting job for window
[gs_job_start] gs-job.c:485 (10:50:36):  starting job
[gs_job_start] gs-job.c:503 (10:50:36):  No command set for job.
[gs_window_xevent] gs-window-x11.c:969 (10:50:36):   not raising our windows
[window_obscured_cb] gs-manager.c:1367 (10:50:36):   Handling window obscured: obscured
[gs_job_stop] gs-job.c:538 (10:50:36):   stopping job
[gs_job_stop] gs-job.c:542 (10:50:36):   Could not stop job: pid not defined
[window_obscured_cb] gs-manager.c:1367 (10:50:36):   Handling window obscured: unobscured
[manager_maybe_start_job_for_window] gs-manager.c:221 (10:50:36):    Starting job for window
[gs_job_start] gs-job.c:485 (10:50:36):  starting job
[gs_job_start] gs-job.c:503 (10:50:36):  No command set for job.
[find_window_at_pointer] gs-manager.c:1137 (10:50:36):   Requesting unlock for screen 0
[gs_window_request_unlock] gs-window-x11.c:2018 (10:50:36):  Requesting unlock
[update_geometry] gs-window-x11.c:544 (10:50:36):    got geometry for monitor 0: x=0 y=0 w=1600 h=900
[update_geometry] gs-window-x11.c:568 (10:50:36):    using geometry for monitor 0: x=0 y=0 w=1600 h=900
[gs_window_move_resize_window] gs-window-x11.c:603 (10:50:36):   Move and/or resize window on monitor 0: x=0 y=0 w=1600 h=900
[gs_fade_reset] gs-fade.c:877 (10:50:36):    Resetting fade
[gs_grab_release] gs-grab-x11.c:426 (10:50:36):  Releasing all grabs
[gs_grab_release_mouse] gs-grab-x11.c:261 (10:50:36):    Ungrabbing pointer
[gs_grab_release_keyboard] gs-grab-x11.c:237 (10:50:36):     Ungrabbing keyboard
[gs_job_stop] gs-job.c:538 (10:50:36):   stopping job
[gs_job_stop] gs-job.c:542 (10:50:36):   Could not stop job: pid not defined
[gs_window_dialog_finish] gs-window-x11.c:1694 (10:50:36):   Dialog finished
[keyboard_command_finish] gs-window-x11.c:1560 (10:50:36):   Keyboard finished
[clear_widget] gs-window-x11.c:429 (10:50:36):   Clearing widget
[widget_clear_all_children] gs-window-x11.c:272 (10:50:36):  Clearing all child windows
[clear_widget] gs-window-x11.c:429 (10:50:36):   Clearing widget
[widget_clear_all_children] gs-window-x11.c:272 (10:50:36):  Clearing all child windows
[window_unmap_cb] gs-manager.c:1248 (10:50:36):  window unmapped!
[gs_watcher_set_active] gs-watcher-x11.c:290 (10:50:36):     turning watcher: ON
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:247 (10:50:36):  Sending the ActiveChanged(FALSE) signal on the session bus
[gs_window_dialog_finish] gs-window-x11.c:1694 (10:50:36):   Dialog finished
[keyboard_command_finish] gs-window-x11.c:1560 (10:50:36):   Keyboard finished
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:36):    obj_path=/org/freedesktop/login1/session/c4 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:36):    obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:36):    obj_path=/org/freedesktop/login1/user/_1000 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:1638 (10:50:36):    obj_path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)

[epgfm]

Log file. Note logging stopped at 10:05 AM when the first bug occurred but it subsequently happened three more times. Why the log stopped there is unclear.

2016-07-27-07-56-10.sc.sh.txt

I had to use a wrapper to start mate-screensaver because redirecting the output to a file was not working when started from the "Startup Applications" of Ubuntu MATE 16.04.
The wrapper also timestamped the output.

[epgfm]

OK, interesting: I just noticed that this bug does NOT happen in a specific setting on my laptop, with two different kinds of "not happening" depending on if the laptop is running on battery or not:

Using Marco + Compton on Ubuntu MATE 16.04.1

• Video open in SMPlayer, Full Screen, playback paused, on AC power -> Fade to black, then screensaver "floating mate" starts, as per my settings
• Video open in SMPlayer, Full Screen, playback paused, on battery -> Fade to black, but there's no "floating mate", just black screen

In both cases keyboard action lands me correctly on the lock screen.

@meatballz, @raveit65, @acsipak, can you guys try that?
Cheers

[acsipak]

@epgfm I tried the first described test case (the second is not available, since I cannot run a desktop on battery...), but it still produces the same error as the one described in the original issue.

[epgfm]

Found other test case where screensaver starts correctly on my laptop:
Firefox in fullscreen mode (F11), on AC power

[GeneralFailer]

I have a similar problem on Arch Linux w/ Xfce only the screen doesn't even blank, it goes right to the lock screen on manual activation.

Debug log

EDIT: Never mind, it just takes a minute to work. Still, it doesn't seem to activate on idle computer for me.

[rubenquidam]

You need to add --unredir-if-possible-exclude 'class_g = "Mate-screensaver"' to the compiz parameters.

[flexiondotorg]

I can only reproduce this issue in Ubuntu MATE when MATE Tweak has been used to select the "Marco (Compton GPU Compositor)" is selected. Screen locking works correctly with Compiz and Marco without Compton.

Less upstream commit for MATE Tweak for the issue:

• https://bitbucket.org/ubuntu-mate/mate-tweak/commits/42e50d91214733ea367e6d6d8dc0adaf89da5a96

[monsta]

I got this several times in Mint 18.1 (with MATE built from git master instead of the default 1.16). Marco is in compositor mode, but on its own, w/o Compton. In addition, this issue begins and ends randomly - this day it happens, next day it doesn't... This is confusing. 😕

[hao-lee]

@monsta Hi, could you reproduce it through these steps?

[kafran]

I run mate-desktop with i3wm + compton. I'm using the Ubuntu Mate compton setup and I can confirm this bug. I can't start the screensaver with compton running.

mate-screensaver-command -l works fine and the screen locks.

I can only reproduce this issue in Ubuntu MATE when MATE Tweak has been used to select the "Marco (Compton GPU Compositor)" is selected. Screen locking works correctly with Compiz and Marco without Compton.
Less upstream commit for MATE Tweak for the issue:
https://bitbucket.org/ubuntu-mate/mate-tweak/commits/42e50d91214733ea367e6d6d8dc0adaf89da5a96

I can confirm this works. On Ubuntu Mate marco + compton and i3wm + compton, but only if the screensaver daemon is started with mate-screensaver --class="Mate-screensaver". @flexiondotorg, are you sure the standard class of mate-screensaver is Mate-screensaver?

[kafran]

I have noted another strange behave.
With AC power I get the configured theme Pop art squares.
But if I remove the power cord and run on battery, screensaver works but with a wrong theme, I get the Blank screen theme.