summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)AuthorFilesLines
2017-03-28[GTK+3.20] Switch to GdkSeatAlexei Sorokin5-304/+227
This changes the code quite a lot as both grabbing the pointer and the keyboard have to be done simultaneously now.
2017-03-18copy theme dialog: fix build warning about wrong variable typemonsta1-2/+1
and set grid property only once, after grid is created
2017-02-10copy-theme-dialog: port GtkTable to GtkGridraveit651-19/+16
2017-01-18Merge pull request #112 from hao-lee/masterMartin Wimpress1-1/+1
Change shake times to even number, so the dialog can return to its original position.
2017-01-17Change shake times to even number, so the dialog can return to its original ↵Hao Lee1-1/+1
position.
2017-01-17GTK+3.22: fix some GdkScreen related deprecationsAlexei Sorokin12-234/+371
2017-01-15avoid deprecated gdk_window_set_background functionsAlexei Sorokin2-76/+73
Which are completely broken in GTK+ 3.22.
2016-12-26patch to use user's background for lock screen also.Oliver Mangold1-1/+4
2016-11-20move to GTK+3 (>= 3.14), drop GTK+2 code and --with-gtk build optionmonsta22-962/+25
and require libmatekbd and libmate-desktop >= 1.17
2016-11-20fix indent a bitmonsta2-3/+3
2016-10-19Also look for gdm-binary processGeorge Vlahavas1-2/+2
In some systems the gdm binary is actually called "gdm-binary", so we need to check for that too.
2016-10-02GTK+-3 gs-grab-x11: use correct GTK_VERSION_CHECKraveit651-1/+1
fixes https://github.com/mate-desktop/mate-screensaver/issues/104
2016-06-30fix minor warningmonsta1-1/+1
2016-06-30fix UI issues introduced in 296b056monsta3-16/+45
2016-06-24use gtk_box_new instead of gtk_{h,v}box_new properlySorokin Alexei3-22/+23
2016-06-18Gtk3: fix several deprecationsSorokin Alexei7-57/+316
2016-06-18properly lock even if already activeMarc Deslauriers1-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-18fix clear backgroundSorokin Alexei1-33/+34
2016-06-18Gtk3, gs-window-x11: defer setting bg color until realizationRay Strode1-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-18gtk3: fix assertion 'GTK_IS_WIDGET (widget)' failedDenis Gorodnichev2-2/+2
2016-04-09add style class lock-dialograveit651-0/+7
2016-01-26GTK3: fix GtkMisc decperation commitWolfgang Ulbrich3-26/+26
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.
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-28 20:25:58 +0000