mate-desktop / mate-screensaver Goto Github PK

In Pidgin with MATE does not work automatically change your status to "Away" when the screen is locked. In Xfce everything was normal.

When you exit the screen lock status in a quickly changing, but when the screen is locked automatically the status of "Away" can not be installed.

Debian Wheezy amd64
Pidgin 2.10.6
MATE 1.6.0

mate-screensaver has the following change listed in the announcement for Mate 1.12:
"Don’t fade to black when locking the screen"

This is a regression. I have my screen set to lock automatically after a short idle period, for security reasons. Previously, the screen would start to slowly fade, giving the user a chance to prevent the screen from locking by moving the mouse (or doing anything else to interact with the system), in case they're sitting there just reading a long page or something. Now the screen just goes black. This makes for a very bad user experience :-(

Please revert this change, or make this a configurable option!

Hi,

serveral screensavers from the xscreensaver project can be configured concerning their behaviour. From the xscreensaver setup tool, the settings of each individual screensaver can be opened in a separate configuration window.

Would it be possible to add a [ Settings ] button to the mate-screensaver setup tool that would then open those screensaver configuration windows (if available)?

Mike

Here is the backtrace when this happens, http://paste.mate-desktop.org/view/8790c680

Starting program: /usr/bin/mate-screensaver 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe71b8700 (LWP 2389)]
[New Thread 0x7fffe69b7700 (LWP 2390)]

Program received signal SIGSEGV, Segmentation fault.
_gdk_display_enable_motion_hints (display=0x0, device=device@entry=0x647080) at gdkdisplay.c:490
490 gdkdisplay.c: No such file or directory.
#0  _gdk_display_enable_motion_hints (display=0x0, device=device@entry=0x647080) at gdkdisplay.c:490
#1  0x00007ffff6e1cd5b in gdk_window_get_device_position (window=0x67e600, device=device@entry=0x647080, x=x@entry=0x7fffffffdc28, 
    y=y@entry=0x7fffffffdc2c, mask=mask@entry=0x7fffffffdc24) at gdkwindow.c:5187
#2  0x00007ffff6e0d36a in synthesize_crossing_events (display=display@entry=0x671020, device=device@entry=0x647080, 
    source_device=source_device@entry=0x647380, src_window=0x67e600, dest_window=dest_window@entry=0x0, 
    crossing_mode=crossing_mode@entry=GDK_CROSSING_UNGRAB, time=time@entry=2359662, serial=serial@entry=847) at gdkdisplay.c:817
#3  0x00007ffff6e0e04c in switch_to_pointer_grab (display=display@entry=0x671020, device=device@entry=0x647080, 
    source_device=source_device@entry=0x647380, grab=grab@entry=0x0, last_grab=last_grab@entry=0x86be60, time=time@entry=2359662, serial=serial@entry=847)
    at gdkdisplay.c:994
#4  0x00007ffff6e0e20b in _gdk_display_device_grab_update (display=0x671020, device=0x647080, source_device=0x647380, current_serial=847)
    at gdkdisplay.c:1065
#5  0x00007ffff6e27d53 in roundtrip_callback_idle (data=0x68fe20) at gdkasync.c:670
#6  0x00007ffff6e08498 in gdk_threads_dispatch (data=0x73d040) at gdk.c:788
#7  0x00007ffff6024876 in g_main_dispatch (context=0x65ab00) at /var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3054
#8  g_main_context_dispatch (context=context@entry=0x65ab00) at /var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3630
#9  0x00007ffff6024bc8 in g_main_context_iterate (context=0x65ab00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3701
#10 0x00007ffff6024fca in g_main_loop_run (loop=0x6be390) at /var/tmp/portage/dev-libs/glib-2.36.4-r1/work/glib-2.36.4/glib/gmain.c:3895
#11 0x00007ffff720488d in gtk_main () at gtkmain.c:1156
#12 0x000000000040bbde in main (argc=1, argv=0x7fffffffdfa8) at mate-screensaver.c:118
A debugging session is active.

    Inferior 1 [process 2385] will be killed.

Quit anyway? (y or n) 

#43 fixes it.

Many xscreensaver hacks are unusable without the configuration screens that go with them. Can this be remedied?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This is not a duplicate of similarly named request #18. I rather mean to have current time (and optionally date) to float around black screen when the computer is idle. So it will be either new screensaver or an option for floater screensaver

Locking my screen via "Lock Screen" in the MATE menu gives the following error in mate-screensaver:

$ mate-screensaver
Xlib:  extension "RANDR" missing on display ":0.0".
The program 'mate-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 178 error_code 2 request_code 149 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

LM 17.1
mate-screensaver 1.8.1
xorg.conf:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 1680 0
    Screen      1  "Screen1" 0 550
    Screen      2  "Screen2" 4240 550
    Option         "Xinerama" "1"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nouveau"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 470"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nouveau"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GT"
    BusID          "PCI:2:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nouveau"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GT"
    BusID          "PCI:2:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
EndSection

I've installed MATE 1.8.1 on Arch Linux and my clock is set to 24 hours mode, however the lockscreen it doesn't respect this and shows 9:49 if my system time is set to 21:49.

It would be nice if the lockscreen was able to show the clock based on system settings.

Orginal report at fedora bugzilla.
https://bugzilla.redhat.com/show_bug.cgi?id=985068

Description of problem:
This bug exist with MATE only, not when login as Gnome3

Version-Release number of selected component (if applicable):
Current, on Fedora 19

How reproducible:
Solid

Steps to Reproduce:
Just watch a video, using VLC, the display dims after a few minutes (may ten) , the power management is properly set.

1. Updated
   3.

Actual results:
Display dims after a few minutes. Unlike Gnome3 which works OK.

Expected results:
Display power management works exactly the same with MATE and Gnome3

Additional info:
This bug was reported about two years ago, in Gnome 2, and then fixed.
I suppose current MATE version uses an older Gnome 2 as base, so this bug is creeping up again.

I can confirm this issue on my systems.
Some usefull links to solve the issue maybe.
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/428884
https://bugzilla.gnome.org/show_bug.cgi?id=579430

the screensaver "floating feet" should be called something else more suitable for Mate Desktop theme.
(for example: "Floating Mate", "Floating Yerba", "Floating Herb" etc)

When selecting no screensaver - just a blank screen - the external monitors do not get disabled and stay enabled with just a black screen.
In Ubuntu Unity it seems to behave in other ways and disables the monitors to save energy and preserve monitors lifetime.

Could you please add an optional color argument for the "Pop art squares" screen saver?

I would like to be able to use a different color for the screensaver than the one specified by my theme. I know I can customize the color by changing the color in my theme, but I don't want to change my theme's colors.

If the argument is added, I will be able to add a color-customized version of the screensaver at /usr/share/applications/screensavers/popsquares-red.desktop like follows ...

[Desktop Entry]
Name=Pop art squares (red)
Comment=A pop-art-ish grid of pulsing colors.
Exec=/usr/libexec/mate-screensaver/popsquares #ff0000
TryExec=/usr/libexec/mate-screensaver/popsquares
StartupNotify=false
Terminal=false
Type=Application
Categories=Screensaver;
OnlyShowIn=MATE;
X-Desktop-File-Install-Version=0.22

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

SUBJ VERY NEED.
http://www.linuxmint.com/tmp/cinnamon-blog/261/screensaver.png
Good example.

incorrect-fsf-address in COPYING and others

It would be really, really nice to see option to change background of lock-screen that MATE has. This feature would fit perfectly inside "Desktop Settings" window, accessible from Control Center :)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Settings, idle time 1 minute and lock screen enabled. You can reproduce it with either waiting for it to start after a minute or issuing mate-screensaver-command --lock.

With gtk2 the saver starts immediately. And only when I move the mouse/hit a key the unlock window shows.

With gtk3, this is reversed. It shows me the unlock window not the saver. I do see the saver if I wait for a bit or hit the cancel button on the unlock window.

afaics there is nothing logged.

This is continuation of thread I posted on MATE forums (http://forums.mate-desktop.org/viewtopic.php?f=16&t=3289&sid=43f98d434e70d225c26f788a23d63b02).

To be honest I further checked and my first solution was wrong (in fact it was 10 minutes past hour and we have October, so %m modifier showed proper value). The source of the issue is not C code but translations.

Polish translation in 1.8.1 have (%k:M) for (%l:%M %p) which is wrong (missing % sign before M).
Other issue (at least for me) is date format used in polish translation (in fact it does not change anything while it should). Using (%A, %e %B %G) would be more common in Poland.

simple test case:
1 - set the mate screen saver timeout to 1 minute (system>preferences>screensaver, "Regard the computer as idle after:" slider set all the way to the left = 1 minute) for this testing to avoid the long wait.
2 - in mate-terminal (bash command line) execute the following command that waits for 63 seconds then pokes the screen saver to simulate user activity; as soon as you press the return key on the command, avoid touching the keyboard or mouse for at least 65 seconds

      while true; do sleep 58; mate-screensaver-command --poke; echo -n poked...; done

What you get is that every 58 seconds, "poked..." gets printed, but the screensaver activates at 60 seconds. The poking should have reset the screensaver timeout so that the screensaver should not activate.

The equivalent command in Ubuntu Gnome 10.10:

      while true; do sleep 58; gnome-screensaver-command --poke; echo -n poked...; done

works as expected and keeps the screensaver from activating.

You can change the time to 63 seconds. In Ubuntu Gnome, you see the screen begin to noticeably dim and then come back to full brightness the instant it gets poked. In Mint Mate the screen dims and blanks out, but before it goes completely black, you see that "poked..." gets printed, but it didn't help.

For reference: https://mail.gnome.org/archives/commits-list/2012-February/msg03038.html

Maybe during the dbus/GSettings portage we can include this? other we will loose features in distributions with systemd, since most of them are removing ConsoleKit (openSUSE is one of them).

Ocasionally when my computer is locked through mate-screensaver, I cant select the password field to enter password to unlock computer.

Linux 3.11.3
Gentoo Linux
mate-screensaver 1.6.0

mate-screensaver doesn't disable display backlight even when "no screensaver" is set.

When pressing Caps Lock a warning message appears, but when I press it again, the message does not disappear. Only when I type in another letter in the input.

Problem: The lock screen doesn't show up but is active. The screen is black.

OS: Linux Mint 15 (dual booted with Win7 Pro) 64 bit
Versions:
Mate 1.6.0
Mate-Screensaver 1.6.0

Computer: HP 4525s Probook

Steps to reproduce:

• Download xscreensaver themes (I'm using glxscreensaver themes)
• modify themes to show up in mate-screensaver configuration app (modify the line in /usr/share/applications/screensavers/<screensaver_name>.desktop: "OnlyShowIn=GNOME;MATE;")
• select the theme with mate-screensaver-preferences
• choose the option "Lock screen when screensaver is active"
• wait for the screensaver to become active
• move the mouse
• screensaver will stop, the screen will turn black
• the lock window is active but not visible
• type in the password blindly to get back to desktop

It would be great if mate could use light-locker instead it's own locker because it's using the lightdm theme.

I was testing the news builds and notice that for me mate-screensaver isn't working as intended; to replicate:

• launch 'Screensaver' from Preferences and select the mate logo screen saver;
• hit 'Lock Screen' on System menu;

Check if the screensaver is the one you choose; Repeat the processes and choose another, example, Cosmos... lock your screen... and check again.

To me it isn't updating; If the user kills/restarts mate-screensaver, then the last changes are loaded. Something seems broken here, mate-screensaver should read updated settings when locking the screen and display the correct screensaver.

Anyone else run against it ?

System: Up to date Mint Mate 17 x64 with Mate 1.8.1
Priority: Medium to High (data security)

Issue: When using suspend-to-disk (S4) serval times, sometimes when the system restarts the desktop with all open programs and data is visible for 2-3 seconds. After 2-3 sec. the lockin-window appears.

What should happend: The lockin-window should appear initially.

Whats the problem: Everybody how starts my pc/notebook is able to have a (short) look at my private data.

If mate-screensaver isn't responsible for locking the screen, please move this issue to the correct mate-module.

Mate-screensaver does not enforce the option 'disable the screensaver when playing " in Totem.

The source language for translation has screensaver and screen saver. In the interests of making work easier for both programmers and translators it would be good if this could be standardised and then the translators (especially translators translating to languages other than English) can translate to teh most appropriate form for their language.

I documented the bug here http://forums.mate-desktop.org/viewtopic.php?f=5&t=1760#p5504 and it is confirmed by a 2nd user in that forum.
Meantime one can remove mate-screensaver and use XScreenSaver.
Another Debian7/MATE1.6 user assumes an influence of the fglrx drivers and/or the patched libpciaccess0, see here http://forums.debian.net/viewtopic.php?f=6&t=102933#p495844

#%PAM-1.0

# Fedora Core
auth include        system-auth
auth optional pam_mate_keyring.so
account include        system-auth
password include        system-auth
session include        system-auth

# SuSE/Novell
#auth include common-auth
#auth optional pam_mate_keyring.so
#account include common-account
#password include common-password
#session include common-session

better use
auth optional pam_gnome_keyring.so

The notice that appears when caps lock becomes activated while typing the password to unlock (e.g. after suspend, screensaver) isn't shown if the lock screen is displayed while caps lock is already activated (toggling caps lock off then on will still display it). This is a minor inconvenience where caps lock is usually warned if on; i.e. I expect the notice to already be present when the lock screen appears if the caps lock is on, and that the state of caps lock is always reflected by the presence or absence of the alert.
(tested on mate-screensaver 1.8.1-2 and 1.10.2-1, Ubuntu MATE 15.04 amd64)

No keyboard input available in the lock screen if the screen locks whilst Virtual Box has the current focus. All other UI elements respond to mouse interaction as expected.

Running Windows 7 as the guest OS (untested with other guest OS's).
I have 3 displays with the guest OS (Windows 7) running with 3 displays and generally in seamless mode.

In general use I've noticed that I have to click on the MATE panel to get focus away from Virtual Box to interact with the desktop via the keyboard (in other window managers e.g. KDE I've only had to click on parts of the desktop not occupied by a window from the guest OS).

GNOME and KDE already implement it and at least VLC and Firefox (33+) make use of it. It's not an "offical" Freedesktop specification but it has become a "defacto-standard".
Link: http://people.freedesktop.org/~hadess/idle-inhibition-spec/

Things to do:

1. Claim DBus bus name org.freedesktop.ScreenSaver additionally to org.mate.ScreenSaver
2. Expose the MATE ScreenSaver interface (org.mate.ScreenSaver) as org.freedesktop.ScreenSaver on the object paths /ScreenSaver and /org/freedesktop/ScreenSaver
3. That's it! MATE ScreenSaver already implements the required methods: Inhibit and UnInhibit correctly!

The reason why you have add both the /ScreenSaver and /org/freedesktop/ScreenSaver object paths is because KDE orginally only added /ScreenSaver while /org/freedesktop/ScreenSaver fits into the official scheme. The spec fails to mention object paths entirly, but GNOME adds both paths so I guess that is what should be used...
Also GNOME exports all for its ScreenSaver methods via org.freedesktop.ScreenSaver althrough the spec only says you have to export the Inhibit and UnInhibit methods so I guess that's how it should be done...

He notado que el demonio no se cierra cuando se elije deshabilitar el salva pantallas.
Sería bueno liberar esos 2.4mb de memoria desperdiciados.

When the screen is locked, the screensaver is shown, but upon moving the mouse, I am returned to the desktop without password authentication (despite the setting "Lock screen when screensaver is active"). The following output is generated:

Xlib: extension "RANDR" missing on display ":0.0".
Xlib: extension "RANDR" missing on display ":0.0".

(mate-screensaver:4629): GLib-GObject-CRITICAL **: g_object_ref: assertion >'G_IS_OBJECT (object)' failed
Xlib: extension "RANDR" missing on display ":0.0".

(mate-screensaver:4629): GLib-GObject-CRITICAL **: g_object_ref: assertion >'G_IS_OBJECT (object)' failed
Xlib: extension "RANDR" missing on display ":0.0".

(mate-screensaver:4629): GLib-GObject-CRITICAL **: g_object_ref: assertion >'G_IS_OBJECT (object)' failed

tagatac/mate-screensaver@aa395dc912c8fe57ecb3162055288a039d287c89
nouveau + Xinerama (causing the XRANDR issues)

After resuming from hibernation my system freezes before the login window shows up and the only way to get the system back to working is to log into a TTY and kill mate-screensaver. Every time this happens, syslog shows the following messages:

Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_drawable_get_colormap: assertion 'GDK_IS_DRAWABLE (drawable)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_colormap_alloc_colors: assertion 'GDK_IS_COLORMAP (colormap)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_drawable_get_colormap: assertion 'GDK_IS_DRAWABLE (drawable)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_set_background: assertion 'GDK_IS_WINDOW (window)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_clear: assertion 'GDK_IS_WINDOW (window)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-WARNING **: /build/gtk+2.0-czQfyJ/gtk+2.0-2.24.25/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

I'm running Mate 1.8.1 on Debian Jessie and this problem started after I upgraded from wheezy.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

origin downstream report at fedora bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=984333#c16

 David Gibson 2013-07-14 21:01:17 EDT

Description of problem:

Sometimes when returning to a MATE session when the screensaver has kicked in, the password box to unlock the screen does not have keyboard focus, and so cannot be completed.  The only way to proceed is to kill mate-screensaver from a VT.

Version-Release number of selected component (if applicable):

mate-screensaver-1.6.0-1.fc19.x86_64

(also observed in Fedora 18)

How reproducible:

Intermittent, no obvious pattern so far.

Steps to Reproduce:
1. Configure screensaver to lock with password
2. Allow screensaver to start
3. Attempt to unlock screen with password

Actual results:

Sometimes, although pressing a key does bring up the password prompt, the prompt does not appear to have keyboard focus and nothing appears when attempting to type password.  Other times it works as expected.

If this happens once, allowing the password prompt to time out (or pressing Cancel with the mouse) then retriggering the password prompt will suffer the same problem.

Expected results:

Password box works, and unlocks screen.

Additional info:

Suspect this may be related to some other windows on the locked desktop which attempt to grab all focus (e.g. VM console from virt-manager) but I don't have confirmation or a clear reproducer yet.

confirmation with 1.10 in fedora 22:

 David Gibson 2015-09-24 21:36:04 EDT

Yes, I'm still seeing this quite often with Fedora 22 and mate-screensaver-1.10.2-1.fc22.x86_64.  I'd say it happens maybe 60-70% of the times the screensaver activates.

Note, this is in xnomad session, i will try to reproduce it

Any chance you guys will implement a setting so that the screen won't always lock when you wake up from suspend on systemd distros like fedora?

I tried running dconf-editor and changing:

org -> mate -> power-manager

lock-blank-screen (unchecked)
lock-hibernate (unchecked)
lock-keyring-hibernate (unchecked)
lock-keyring-suspend (unchecked)
lock-suspend (unchecked)
lock-use-screensaver (unchecked)

and also

org -> mate -> screensaver

lock-enabled (unchecked)

and changing these settings has no effect. It still always locks the screen when it wakes from suspend.

Cheers.

Please provide a complete NEWS / changelog history with all 1.8.x releases included.

My distro:
Release: Linux Mint 15 "olivia"
Edition: MATE 32-bit

I have set my mate-screensaver settings to "Regard the computer as idle after: 15 minutes". The screen goes dark after 5 (FIVE) minutes of inactivity anyway. I think 5 was the default setting before I changed it to 15 (FIFTEEN), so it seems it ignores my settings completely.

I use smplayer as my default video player and noticed that when it is in the paused state, mate-screensaver doesnt start. I filed a bug report with smplayer (https://sourceforge.net/p/smplayer/bugs/670/) and the developer stated "SMPlayer just passes the option -stop-xscreensaver to mplayer, so mplayer handles the screensaver." I was wondering if mate-screensaver is intercepting this or whether this is a problem with mplayer.

Hi, I'm using MATE under ubuntu 14.04:
Linux trusty 3.16.0-28-generic #38-Ubuntu SMP Sat Dec 13 16:15:36 UTC 2014 i686 i686 i686 GNU/Linux
mate-screensaver-command 1.8.1

The problem appears about 3-4 times a day. It's more often when you use sleep mode. Text field for password is present but I'm not able to type anynything inside. One and only option is to click switch user and then type password. Probably related to #30

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Because have_systemd=no was dropped

checking for crypt in -lcrypt... yes
checking for SYSTEMD... no
checking for SYSTEMD... no
configure: error: Package requirements (libsystemd-login >= ) were not met:

Comparison operator but no version after package name 'libsystemd-login' in file '(command line arguments)'

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables SYSTEMD_CFLAGS
and SYSTEMD_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Ubuntu 15.10 Mate alpha screensaver will not unlock with user password. Have to remove lock from screensaver to have functioning PC

For details see Debian bug 749629 [1].

[1] http://bugs.debian.org/749629

Release: Linux Mint 15 "olivia"
Edition: MATE 32-bit

This is strange thing. When I watch a movie in TOTEM in fullscreen mode and the screensaver starts after 5 minutes, the screen goes dim and then black for a blink but then it's back to "normal" and I can still see the movie. It seems the screensaver runs in the background because I have no control over the player. Clicking mouse or using keys to control movie player fails. However if I guess there's screensaver in the background and type my password into the invisible dialog window I get the control back, the screen is unlocked.

OS and version: Ubuntu 14.04
mate-screensaver-command version: 1.8.1
display manager: lightdm

When attempting to switch user from the MATE screensaver, nothing happens. After unlocking the screensaver I see a popup window with the following displayed:
Unable to start new display
Could not identify the current session.

Please let me know if you need any additional information.

Thanks!

Steve

[rave@f21-qemu-mate-gtk3 ~]$ mate-screensaver-preferences 

** (mate-screensaver-preferences:14528): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mate-screensaver-preferences:14528): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

** (mate-screensaver-preferences:14528): WARNING **: Couldn't load builder file: Invalid property: GtkDialog.has_separator on line 38

(mate-screensaver-preferences:14528): Gtk-CRITICAL **: gtk_label_set_mnemonic_widget: assertion 'GTK_IS_LABEL (label)' failed

(mate-screensaver-preferences:14528): Gtk-CRITICAL **: gtk_label_set_mnemonic_widget: assertion 'GTK_IS_LABEL (label)' failed

(mate-screensaver-preferences:14528): Gtk-CRITICAL **: gtk_widget_set_no_show_all: assertion 'GTK_IS_WIDGET (widget)' failed

** (mate-screensaver-preferences:14528): CRITICAL **: widget_set_best_visual: assertion 'widget != NULL' failed

(mate-screensaver-preferences:14528): Gtk-CRITICAL **: gtk_range_set_value: assertion 'GTK_IS_RANGE (range)' failed

<snip>

The error with the builder file is simple to fix. This line needs to be removed from https://github.com/mate-desktop/mate-screensaver/blob/master/data/mate-screensaver-preferences.ui#L38
which is saved. i did that already with a package of mine today.
Now

[rave@f21-qemu-mate-gtk3 ~]$ mate-screensaver-preferences 

** (mate-screensaver-preferences:14602): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkMisc:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkMisc:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkMisc:xpad is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14602): GLib-GObject-WARNING **: The property GtkMisc:ypad is deprecated and shouldn't be used anymore. It will be removed in a future version.

** (mate-screensaver-preferences:14602): WARNING **: Couldn't load builder file: Invalid property: GtkHScale.update_policy on line 296

(mate-screensaver-preferences:14602): Gtk-CRITICAL **: gtk_widget_set_no_show_all: assertion 'GTK_IS_WIDGET (widget)' failed
<snip>

This ends up in an empty window only with buttons.
Removing this line
https://github.com/mate-desktop/mate-screensaver/blob/master/data/mate-screensaver-preferences.ui#L297
starts the window.

[rave@f21-qemu-mate-gtk3 ~]$ mate-screensaver-preferences 

** (mate-screensaver-preferences:14647): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkMisc:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkMisc:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkMisc:xpad is deprecated and shouldn't be used anymore. It will be removed in a future version.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: The property GtkMisc:ypad is deprecated and shouldn't be used anymore. It will be removed in a future version.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

** (/usr/libexec/mate-screensaver-gl-helper:14649): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mate-screensaver-preferences:14647): GLib-GObject-WARNING **: gsignal.c:2461: signal 'size-request' is invalid for instance '0x1c71370' of type 'GtkScrolledWindow'

I'm not shure about remomoving this line so i won't do a PR for the moment.
Let me know if this is save too.
Full log.
https://dl.dropboxusercontent.com/u/49862637/Mate-desktop/Bugs/mate-screensaver