summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2016-05-21update to 1.14.1 releasev1.14.1raveit652-1/+9
2016-05-21sync with transiflexraveit6511-134/+138
2016-04-18gtk3: fix assertion 'GTK_IS_WIDGET (widget)' failedDenis Gorodnichev2-2/+2
2016-04-09add style class lock-dialograveit651-0/+7
2016-04-07 po: add missing languages to LINGUASv1.14.0monsta1-0/+2
2016-04-06release 1.14.0raveit652-2/+3
2016-04-06Add Changelog generationraveit651-0/+10
2016-04-06add new languages and sync with transiflexraveit6586-7813/+18658
2016-04-05NEWS: drop ancient gnome 2.xx changesmonsta1-1577/+0
2016-04-05update NEWS a bitmonsta1-3/+4
2016-02-19Sync with TransifexMartin Wimpress10-1159/+2244
2016-02-01fix build warnings about unused variablesmonsta2-7/+1
2016-01-26release 1.13.0v1.13.0Wolfgang Ulbrich1-0/+4
2016-01-26GTK3: fix GtkMisc decperation commitWolfgang Ulbrich3-26/+26
2016-01-21configure.ac: no need to parse and print dbus version anymoremonsta1-34/+0
2016-01-21drop defines for ancient dbus versionmonsta2-11/+0
2016-01-05pre-bump version to 1.13.0Wolfgang Ulbrich2-1/+5
2016-01-03drop MateConf migration scriptMonsta2-19/+0
2015-12-22mate_gdk_spawn_command_line_on_screen can be used with any GTK+monsta2-8/+8
2015-12-16removed some strings from translation - nothing to translate theremonsta1-4/+4
2015-12-14get rid of some build warnings when --without-console-kit is setmonsta1-0/+2
2015-12-13GTK3: replace deprecated gdk_window_set_backgroundWolfgang Ulbrich1-2/+8
2015-12-13GTK3: don't use deprecated GtkMiscWolfgang Ulbrich3-0/+65
2015-12-13remove more unused variablesWolfgang Ulbrich5-18/+7
this avoid some build warnings
2015-12-13GTK3: don't use deprecated gdk_cursor_newWolfgang Ulbrich3-0/+33
2015-12-11drop some unused variablesWolfgang Ulbrich3-12/+6
taken from: https://git.gnome.org/browse/gnome-screensaver/commit/?id=214ab95 https://git.gnome.org/browse/gnome-screensaver/commit/?id=4f0124a
2015-12-11GTK3: don't use deprecated gdk_cursor_unrefWolfgang Ulbrich2-0/+12
2015-12-11GTK3 window: don't use GtkRC to override drawing area's backgroundWolfgang Ulbrich1-1/+12
That won't work correctly with GTK3, even more so given that we set app_paintable = TRUE on the drawing area. Instead, set the background GdkRGBA to black directly on the GtkDrawingArea's GdkWindow. taken from: https://git.gnome.org/browse/gnome-screensaver/commit/?id=43ee32e
2015-12-10GTK3: don't use deprecated gtk_widget_size_requestWolfgang Ulbrich3-0/+12
2015-12-10GTK3: use new gdk_error_trap_ignored apiWolfgang Ulbrich2-0/+34
This gets rid of some compile warnings taken from: https://git.gnome.org/browse/gnome-screensaver/commit/?id=73c0e41
2015-12-10GTK3: don't use deprecated GDK_THREADS_ENTER/LEAVEWolfgang Ulbrich2-0/+12
2015-12-10GTK3: don't use deprecated gtk_button_box_newWolfgang Ulbrich1-0/+4
2015-12-10GTK3: don't use deprecated gtk_{v/h}box_newWolfgang Ulbrich3-0/+15
2015-11-30fix warnings due to wrong id passed to g_source_removemonsta5-2/+11
2015-11-031.12.0v1.12.01.12Clement Lefebvre1-1/+1
2015-11-03Sync translations with transifexClement Lefebvre2-0/+1490
2015-10-30update NEWS for 1.12monsta1-7/+2
2015-10-27some corrections in NEWSmonsta1-2/+10
2015-10-21release 1.11.1mate-screensaver-1.11.1raveit652-1/+7
2015-10-20Revert "Lock the screen on systemd sleep under systemd"monsta1-17/+0
This reverts commit f1739c03e00a51e87bd49d04827e5b765d1c70de.
2015-10-20add datarootdir to .pc.in file, fix warning during configure processMonsta1-1/+2
2015-10-14Lock the screen on systemd sleep under systemdFaidon Liambotis1-0/+17
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.
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).
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-15 07:27:54 +0000