summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-10-14Fix systemd event handlingFaidon Liambotis1-21/+35
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 <[email protected]>. The bug and the fix can both be easily verified by running "loginctl lock-sessions".
2015-10-09release 1.11.0mate-screensaver-1.11.0raveit651-0/+5
2015-10-08Merge pull request #79 from paravoid/no-fadeClement Lefebvre1-1/+1
Don't fade to black when locking the screen
2015-10-06pre-bump version to 1.11.0raveit652-1/+5
2015-10-05fix build w/o systemd supportMonsta1-2/+2
fixes https://github.com/mate-desktop/mate-screensaver/issues/83
2015-10-01configure.ac: add support for new libsystemd libraryMonsta1-3/+3
2015-09-16manager: fade out explicitly locks more quicklyRay Strode2-2/+2
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
2015-09-15Don't fade to black when locking the screenFaidon Liambotis1-1/+1
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).
2015-09-08define max/min version of GLibinfirit1-0/+6
2015-09-08Rework gsettings schema buildinginfirit4-6/+7
* Bump intltool required version for gsettings support * Extract strings with intltool directly
2015-09-08Merge pull request #77 from monsta/patch-2Martin Wimpress1-1/+0
configure.ac: drop obsolete macro
2015-09-04Switch to org.gnome.SessionManagerClement Lefebvre2-9/+9
2015-08-25Merge pull request #78 from monsta/laundryMartin Wimpress1-10/+0
stop caring for osx
2015-08-25stop caring for osxMonsta1-10/+0
2015-08-19configure.ac: drop obsolete macromonsta1-1/+0
It's been a no-op for a long time. See https://mail.gnome.org/archives/commits-list/2011-December/msg00681.html for example.
2015-07-12slideshow: Cleanup cairo drawing between gtk versionsinfirit1-30/+12
2015-07-12slideshow: Drop GdkPixmap and use retrieve GdkPixbuf directlyinfirit1-12/+1
2015-07-12popsquares: Use cairo for Gtk+2infirit1-49/+21
2015-07-09Simplify cursur hidinginfirit2-53/+1
Use GDK_BLANK_CURSOR across Gtk versions for new cursors.
2015-07-09Remove useless call to gtk_dialog_set_has_separatorinfirit1-3/+0
The default is already FALSE
2015-07-09Use accessor functions instead of direct accessinfirit12-187/+44
Make Gtk2 build with GSEAL_ENABLE And cut down on ifdef hell.
2015-07-09Don't use gdkkeysyms-compat for Gtk+2infirit2-10/+8
2015-07-09Always use GDK_DISPLAY_XDISPLAY instead of GDK_DISPLAYinfirit6-87/+2
Has been in Gtk since 2.22
2015-07-09Remove gtk version check around gdk_x11_screen_lookup_visualinfirit3-16/+0
The function has been in Gtk 2 since 2.2.
2015-07-08Use the string screensaver consistantlyinfirit1-1/+1
closes #56
2015-07-07popsquares: do not return a value in void function draw_frameinfirit1-2/+2
2015-06-26[joequant] fix segfault due to wrong object being destroyed (ported from ↵Clement Lefebvre1-1/+1
https://github.com/linuxmint/cinnamon-screensaver/pull/106)
2015-06-12Sync translations with transifexmate-i18n3-24/+28
2015-06-11Bump version to 1.10.1mate-screensaver-1.10.1Martin Wimpress2-1/+7
2015-05-19Merge pull request #70 from NiceandGently/masterMartin Wimpress1-15/+17
check for running DM for user switching
2015-05-04Bump version to 1.10.0mate-screensaver-1.10.0Stefano Karapetsas2-2/+2
2015-05-04Sync translations with transifexmate-i18n2-13/+14
2015-04-04Bump version to 1.9.90mate-screensaver-1.9.90Stefano Karapetsas2-2/+2
2015-04-04Sync translations with transifexmate-i18n5-53/+56
2015-04-01check for running DM for user switchingraveit651-15/+17
2015-01-20Bump version to 1.9.2mate-screensaver-1.9.2Stefano Karapetsas2-2/+2
2015-01-20Sync translations with transifexmate-i18n15-200/+209
2014-12-16Revert "Add back Glib 2.32 support"infirit3-12/+0
This reverts commit ddc4152abebd61f14055dec8c2f7c4c1e0d2ddd0.
2014-12-16Revert "Drop back to Glib 2.32 in configure.ac"infirit1-1/+1
This reverts commit d1381afe0285c1fb4dabb2ccf3ad496efab9f3ff.
2014-12-16Drop back to Glib 2.32 in configure.acinfirit1-1/+1
2014-12-16Add back Glib 2.32 supportinfirit3-0/+12
2014-12-15Bump mate-desktop required to version 1.9.4infirit1-1/+1
The materr* changes are not in mate-desktop 1.9.3 yet.
2014-11-30configure.ac: use dots when printing dbus versionmonsta1-1/+1
2014-11-30Update NEWSinfirit1-1/+1
2014-11-30Bump required mate-desktop version for materr* changesinfirit1-1/+1
2014-11-30Update to api changes for MateRR* in mate-desktopinfirit1-3/+1
2014-11-28don't leak memoryMonsta1-0/+4
2014-11-28avoid dereferencing NULL pointersMonsta1-2/+8
2014-11-28zero-init signals arraymonsta1-1/+1
2014-11-19Bump version to 1.9.1mate-screensaver-1.9.1Stefano Karapetsas2-2/+2
generated by cgit v1.2.1 (git 2.18.0) at 2024-12-18 06:57:54 +0000