mate-screensaver/src, branch 1.12 MATE screen saver and locker Revert "Lock the screen on systemd sleep under systemd" 2015-10-20T12:51:20+00:00 monsta monsta@inbox.ru 2015-10-16T11:02:16+00:00 372da14ddaf723f5da64413676d774223ab1b68f This reverts commit f1739c03e00a51e87bd49d04827e5b765d1c70de. 
This reverts commit f1739c03e00a51e87bd49d04827e5b765d1c70de.
Lock the screen on systemd sleep under systemd 2015-10-14T08:08:27+00:00 Faidon Liambotis paravoid@debian.org 2015-09-14T22:31:07+00:00 f1739c03e00a51e87bd49d04827e5b765d1c70de Add a handler for the PrepareForSleep event on the system bus under systemd and lock the screen in such an event. This addresses the issue where "systemctl suspend" suspends the system but the system isn't locked on resume, with the obvious negative security connotations. 
Add a handler for the PrepareForSleep event on the system bus under
systemd and lock the screen in such an event. This addresses the issue
where "systemctl suspend" suspends the system but the system isn't
locked on resume, with the obvious negative security connotations.
Fix systemd event handling 2015-10-14T08:08:27+00:00 Faidon Liambotis paravoid@debian.org 2015-09-14T22:26:01+00:00 306599bdbae51788ed2c2faa061adc6966fd814d Right now the systemd event handling is not actually working at all. This happens because _listener_message_path_is_our_session() has code to check if the event came to our session (e.g. "10") and, under systemd, does this by trying to compare it with the object path, by stripping the /org/freedesktop/login1/session/ prefix. However, under -at least recent versions- of systemd, the session ID part of the path is escaped separately, and following D-Bus rules initial numbers are escaped. In the example above, the obj_path is /org/freedesktop/login1/session/_310, so the comparison actually fails. Port a fix that has been present on various distributions (e.g. Arch) and pieces of software (e.g. cinnamon-screensaver) since at least March 2013. The original author is Peter de Ridder <peter@xfce.org>. The bug and the fix can both be easily verified by running "loginctl lock-sessions". 
Right now the systemd event handling is not actually working at all.
This happens because _listener_message_path_is_our_session() has code to
check if the event came to our session (e.g. "10") and, under systemd,
does this by trying to compare it with the object path, by stripping the
/org/freedesktop/login1/session/ prefix.

However, under -at least recent versions- of systemd, the session ID
part of the path is escaped separately, and following D-Bus rules
initial numbers are escaped. In the example above, the obj_path is
/org/freedesktop/login1/session/_310, so the comparison actually fails.

Port a fix that has been present on various distributions (e.g. Arch)
and pieces of software (e.g. cinnamon-screensaver) since at least March
2013.  The original author is Peter de Ridder <peter@xfce.org>.

The bug and the fix can both be easily verified by running "loginctl
lock-sessions".
Merge pull request #79 from paravoid/no-fade 2015-10-08T10:33:15+00:00 Clement Lefebvre clement.lefebvre@linuxmint.com 2015-10-08T10:33:15+00:00 ba3abd99de0c9a16cea2e48265ed57f30983d9d6 Don't fade to black when locking the screen 
Don't fade to black when locking the screen
 manager: fade out explicitly locks more quickly 2015-09-16T13:26:01+00:00 Ray Strode rstrode@redhat.com 2015-09-16T13:26:01+00:00 599bc816e0dca82f921e6d77c2018d7818e7b7b2 If the screensaver is explicitly asked to lock (as opposed to locking because of idle), then we should do it very quickly. 1 second is too long. This commit changes the fade to 60 steps per second and a quarter of second long (put another way, about 15 fade increments). Taken from gnome-screensaver, commit:44edc03104f9757f4d866f24df8793f064b6ce70 And applied to MATE by infirit 
If the screensaver is explicitly asked to lock
(as opposed to locking because of idle), then
we should do it very quickly.  1 second is
too long.

This commit changes the fade to 60 steps per
second and a quarter of second long
(put another way, about 15 fade increments).

Taken from gnome-screensaver,
commit:44edc03104f9757f4d866f24df8793f064b6ce70
And applied to MATE by infirit
Don't fade to black when locking the screen 2015-09-14T22:33:40+00:00 Faidon Liambotis paravoid@debian.org 2015-09-14T22:33:40+00:00 e53692cc3700b4987812718d03894addda3a4117 Fading to black has negative security consequences: the screen locking and actual suspend race with each other, and this can result in the screen's contents being briefly visible after resume. This has been reported as #54 but has been known and patched for in Debian/Ubuntu since at least 2010 (see LP 546578). 
Fading to black has negative security consequences: the screen locking
and actual suspend race with each other, and this can result in the
screen's contents being briefly visible after resume.

This has been reported as #54 but has been known and patched for in
Debian/Ubuntu since at least 2010 (see LP 546578).
Switch to org.gnome.SessionManager 2015-09-04T20:57:30+00:00 Clement Lefebvre clement.lefebvre@linuxmint.com 2015-09-04T20:57:30+00:00 7ddb61c4cb9f17a79a935ff55244f8594b250848 






Simplify cursur hiding
2015-07-09T11:49:39+00:00

infirit
infirit@gmail.com

2015-07-09T11:27:15+00:00

c7fee045db811e12a76894cddbf5604af7d57941

Use GDK_BLANK_CURSOR across Gtk versions for new cursors.





Use GDK_BLANK_CURSOR across Gtk versions for new cursors.







Remove useless call to gtk_dialog_set_has_separator
2015-07-09T11:49:16+00:00

infirit
infirit@gmail.com

2015-07-09T11:03:15+00:00

d69d9dd6a7fabb18ac207c348cac5e2475380c21

The default is already FALSE





The default is already FALSE







Use accessor functions instead of direct access
2015-07-09T10:15:32+00:00

infirit
infirit@gmail.com

2015-07-09T10:08:18+00:00

72dd61aa3a3a98bf38c2cc3aa7e36f99b620be24

Make Gtk2 build with GSEAL_ENABLE And cut down on ifdef hell.





Make Gtk2 build with GSEAL_ENABLE And cut down on ifdef hell.