Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2016-06-30 | fix minor warning | monsta | 1 | -1/+1 | |
2016-06-30 | fix UI issues introduced in 296b056 | monsta | 3 | -16/+45 | |
2016-06-24 | use gtk_box_new instead of gtk_{h,v}box_new properly | Sorokin Alexei | 3 | -22/+23 | |
2016-06-18 | Gtk3: fix several deprecations | Sorokin Alexei | 7 | -57/+316 | |
2016-06-18 | properly lock even if already active | Marc Deslauriers | 1 | -6/+11 | |
If the screensaver is already active without a lock, and it got a request to lock, it would bail out without switching to a locked state. https://bugzilla.gnome.org/show_bug.cgi?id=668967 | |||||
2016-06-18 | fix clear background | Sorokin Alexei | 1 | -33/+34 | |
2016-06-18 | Gtk3, gs-window-x11: defer setting bg color until realization | Ray Strode | 1 | -5/+13 | |
commit adfc280 changed the drawing area associated with each monitors screensaver window to get realized early. That change is seemingly causing problems for users. This commit stops preemptively realizing the drawing areas, and instead makes the background color settings get applied reactively in response to realization. http://bugzilla.gnome.org/show_bug.cgi?id=679441 | |||||
2016-04-18 | gtk3: fix assertion 'GTK_IS_WIDGET (widget)' failed | Denis Gorodnichev | 2 | -2/+2 | |
2016-04-09 | add style class lock-dialog | raveit65 | 1 | -0/+7 | |
2016-01-26 | GTK3: fix GtkMisc decperation commit | Wolfgang Ulbrich | 3 | -26/+26 | |
2016-01-21 | drop defines for ancient dbus version | monsta | 2 | -11/+0 | |
2015-12-22 | mate_gdk_spawn_command_line_on_screen can be used with any GTK+ | monsta | 2 | -8/+8 | |
2015-12-14 | get rid of some build warnings when --without-console-kit is set | monsta | 1 | -0/+2 | |
2015-12-13 | GTK3: don't use deprecated GtkMisc | Wolfgang Ulbrich | 3 | -0/+65 | |
2015-12-13 | remove more unused variables | Wolfgang Ulbrich | 2 | -4/+2 | |
this avoid some build warnings | |||||
2015-12-13 | GTK3: don't use deprecated gdk_cursor_new | Wolfgang Ulbrich | 3 | -0/+33 | |
2015-12-11 | drop some unused variables | Wolfgang Ulbrich | 3 | -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-11 | GTK3: don't use deprecated gdk_cursor_unref | Wolfgang Ulbrich | 2 | -0/+12 | |
2015-12-11 | GTK3 window: don't use GtkRC to override drawing area's background | Wolfgang Ulbrich | 1 | -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-10 | GTK3: don't use deprecated gtk_widget_size_request | Wolfgang Ulbrich | 2 | -0/+8 | |
2015-12-10 | GTK3: use new gdk_error_trap_ignored api | Wolfgang Ulbrich | 2 | -0/+34 | |
This gets rid of some compile warnings taken from: https://git.gnome.org/browse/gnome-screensaver/commit/?id=73c0e41 | |||||
2015-12-10 | GTK3: don't use deprecated GDK_THREADS_ENTER/LEAVE | Wolfgang Ulbrich | 1 | -0/+4 | |
2015-12-10 | GTK3: don't use deprecated gtk_button_box_new | Wolfgang Ulbrich | 1 | -0/+4 | |
2015-12-10 | GTK3: don't use deprecated gtk_{v/h}box_new | Wolfgang Ulbrich | 3 | -0/+15 | |
2015-11-30 | fix warnings due to wrong id passed to g_source_remove | monsta | 3 | -0/+4 | |
2015-10-20 | Revert "Lock the screen on systemd sleep under systemd" | monsta | 1 | -17/+0 | |
This reverts commit f1739c03e00a51e87bd49d04827e5b765d1c70de. | |||||
2015-10-14 | Lock the screen on systemd sleep under systemd | Faidon Liambotis | 1 | -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-14 | Fix systemd event handling | Faidon Liambotis | 1 | -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-08 | Merge pull request #79 from paravoid/no-fade | Clement Lefebvre | 1 | -1/+1 | |
Don't fade to black when locking the screen | |||||
2015-09-16 | manager: fade out explicitly locks more quickly | Ray Strode | 2 | -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-15 | Don't fade to black when locking the screen | Faidon Liambotis | 1 | -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-04 | Switch to org.gnome.SessionManager | Clement Lefebvre | 2 | -9/+9 | |
2015-07-09 | Simplify cursur hiding | infirit | 2 | -53/+1 | |
Use GDK_BLANK_CURSOR across Gtk versions for new cursors. | |||||
2015-07-09 | Remove useless call to gtk_dialog_set_has_separator | infirit | 1 | -3/+0 | |
The default is already FALSE | |||||
2015-07-09 | Use accessor functions instead of direct access | infirit | 7 | -129/+30 | |
Make Gtk2 build with GSEAL_ENABLE And cut down on ifdef hell. | |||||
2015-07-09 | Don't use gdkkeysyms-compat for Gtk+2 | infirit | 2 | -10/+8 | |
2015-07-09 | Always use GDK_DISPLAY_XDISPLAY instead of GDK_DISPLAY | infirit | 6 | -87/+2 | |
Has been in Gtk since 2.22 | |||||
2015-07-09 | Remove gtk version check around gdk_x11_screen_lookup_visual | infirit | 3 | -16/+0 | |
The function has been in Gtk 2 since 2.2. | |||||
2015-07-08 | Use the string screensaver consistantly | infirit | 1 | -1/+1 | |
closes #56 | |||||
2015-06-26 | [joequant] fix segfault due to wrong object being destroyed (ported from ↵ | Clement Lefebvre | 1 | -1/+1 | |
https://github.com/linuxmint/cinnamon-screensaver/pull/106) | |||||
2015-04-01 | check for running DM for user switching | raveit65 | 1 | -15/+17 | |
2014-12-16 | Revert "Add back Glib 2.32 support" | infirit | 3 | -12/+0 | |
This reverts commit ddc4152abebd61f14055dec8c2f7c4c1e0d2ddd0. | |||||
2014-12-16 | Add back Glib 2.32 support | infirit | 3 | -0/+12 | |
2014-11-30 | Update to api changes for MateRR* in mate-desktop | infirit | 1 | -3/+1 | |
2014-11-28 | don't leak memory | Monsta | 1 | -0/+4 | |
2014-11-28 | avoid dereferencing NULL pointers | Monsta | 1 | -2/+8 | |
2014-11-28 | zero-init signals array | monsta | 1 | -1/+1 | |
2014-07-21 | Prevent SegFault in the absence of XRANDR | David Tagatac | 1 | -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-02 | Don't use deprecated GLib threading API. | infirit | 1 | -26/+14 | |
2014-07-02 | Dont call g_thread_init | Stefano Karapetsas | 1 | -5/+0 | |