summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2016-01-21drop defines for ancient dbus versionmonsta2-11/+0
2015-12-22mate_gdk_spawn_command_line_on_screen can be used with any GTK+monsta2-8/+8
2015-12-14get rid of some build warnings when --without-console-kit is setmonsta1-0/+2
2015-12-13GTK3: don't use deprecated GtkMiscWolfgang Ulbrich3-0/+65
2015-12-13remove more unused variablesWolfgang Ulbrich2-4/+2
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 Ulbrich2-0/+8
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 Ulbrich1-0/+4
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_removemonsta3-0/+4
2015-10-20Revert "Lock the screen on systemd sleep under systemd"monsta1-17/+0
This reverts commit f1739c03e00a51e87bd49d04827e5b765d1c70de.
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-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 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-04Switch to org.gnome.SessionManagerClement Lefebvre2-9/+9
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 accessinfirit7-129/+30
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-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-04-01check for running DM for user switchingraveit651-15/+17
2014-12-16Revert "Add back Glib 2.32 support"infirit3-12/+0
This reverts commit ddc4152abebd61f14055dec8c2f7c4c1e0d2ddd0.
2014-12-16Add back Glib 2.32 supportinfirit3-0/+12
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-07-21Prevent SegFault in the absence of XRANDRDavid Tagatac1-1/+2
(Fix #46) Patch by Steven Chamberlain https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=bug749629.patch;att=1;bug=749629
2014-07-02Don't use deprecated GLib threading API.infirit1-26/+14
2014-07-02Dont call g_thread_initStefano Karapetsas1-5/+0
2014-07-02Remove some old code after GLIB and GTK2 minimum version bumpStefano Karapetsas5-43/+1
2014-06-25Honor locale time settings in lock screenmate-screensaver-1.9.0Stefano Karapetsas1-2/+1
Closes https://github.com/mate-desktop/mate-screensaver/pull/47
2014-06-12Revert "Honor locale time settings in lock screen."infirit1-2/+4
This reverts commit debbeac50a48c78fd0ca1559228e54eebc4d7aa8.
2014-06-12Honor locale time settings in lock screen.brian m. carlson1-4/+2
The time display in the lock screen should honor the LC_TIME variable, including the locale-specific settings for whether to display a 12-hour or 24-hour time. Sending the time and date strings through gettext results in a value which is specific to LC_MESSAGES, which can be different from LC_TIME. Use the %X value for time, which is guaranteed to be appropriate for the locale in question. Signed-off-by: brian m. carlson <[email protected]>
2014-02-21Fix help button in preferences dialog.infirit1-36/+3
2014-01-28Show date and time in lock dialogStefano Karapetsas1-0/+65
Closes #18 https://github.com/mate-desktop/mate-screensaver/issues/18
2014-01-14Check for logind, not for systemdraveit651-2/+3
2014-01-14Fix compile warning if not compiled with systemdraveit651-2/+1
2014-01-14listener-dbus: s/ConsoleKit/systemd/raveit651-2/+2
2013-11-12Improvements for GTK3Stefano Karapetsas1-1/+5
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-02 19:30:23 +0000