summaryrefslogtreecommitdiff
path: root/src/gs-manager.c
AgeCommit message (Collapse)AuthorFilesLines
2016-11-20move to GTK+3 (>= 3.14), drop GTK+2 code and --with-gtk build optionmonsta1-64/+0
and require libmatekbd and libmate-desktop >= 1.17
2016-11-20fix indent a bitmonsta1-2/+2
2016-06-18Gtk3: fix several deprecationsSorokin Alexei1-1/+47
2015-10-08Merge pull request #79 from paravoid/no-fadeClement Lefebvre1-1/+1
Don't fade to black when locking the screen
2015-09-16manager: fade out explicitly locks more quicklyRay Strode1-1/+1
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).
2014-11-28avoid dereferencing NULL pointersMonsta1-2/+8
2013-11-12Add GTK3 supportStefano Karapetsas1-2/+21
2012-11-18fixed incorrect fsf addressesSteve Zesch1-1/+1
2012-11-03use background system settings from latest libmate-desktopmate-screensaver-1.5.0Stefano Karapetsas1-56/+5
2012-11-03fix org.mate.background gschema nameStefano Karapetsas1-1/+1
2012-11-03fix mate_bg_load_from_preferences callStefano Karapetsas1-4/+2
2012-11-03Port MATE Screensaver to GSettingsraveit1-75/+47
2011-11-04first commitPerberos1-0/+2030