- Mar 13, 2017
- Feb 13, 2017
-
-
monsta authored
-
- Feb 10, 2017
-
-
raveit65 authored
-
- Jan 18, 2017
-
-
Martin Wimpress authored
-
Martin Wimpress authored
Change shake times to even number, so the dialog can return to its original position.
-
Martin Wimpress authored
Avoid deprecated gdk_window_set_background functions
-
- Jan 17, 2017
-
-
Hao Lee authored
-
- Jan 16, 2017
-
-
Alexei Sorokin authored
-
- Jan 15, 2017
-
-
Alexei Sorokin authored
Which are completely broken in GTK+ 3.22.
-
- Jan 13, 2017
-
-
Martin Wimpress authored
Update mate-screensaver NEWS to use consistent, project wide, markdown-like formatting. This will make generating release announcements easier.
-
- Jan 08, 2017
-
-
raveit65 authored
-
- Dec 27, 2016
-
-
raveit65 authored
-
- Dec 26, 2016
-
-
Oliver Mangold authored
-
- Nov 28, 2016
-
-
monsta authored
-
- Nov 24, 2016
- Nov 20, 2016
- Oct 19, 2016
-
-
George Vlahavas authored
In some systems the gdm binary is actually called "gdm-binary", so we need to check for that too.
-
- Oct 02, 2016
-
-
- Sep 19, 2016
-
-
raveit65 authored
-
- Sep 18, 2016
- Jul 15, 2016
-
-
raveit65 authored
-
- Jun 30, 2016
- Jun 25, 2016
-
-
raveit65 authored
-
- Jun 24, 2016
-
-
Sorokin Alexei authored
-
- Jun 22, 2016
-
-
Sorokin Alexei authored
-
Sorokin Alexei authored
-
- Jun 18, 2016
-
-
Sorokin Alexei authored
-
Marc Deslauriers authored
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
-
Sorokin Alexei authored
-
Sorokin Alexei authored
-
Ray Strode authored
commit adfc2809 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
-
- Jun 07, 2016