Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
gtk_style_context_add_provider_for_screen (gdk_screen_get_default(),
GTK_STYLE_PROVIDER (style_provider),
GTK_STYLE_PROVIDER_PRIORITY_USER);
https://developer.gnome.org/gtk3/stable/GtkStyleContext.html#gtk-style-context-add-provider-for-screen
css data is located at /usr/share/mate-screensaver/lock-dialog-THEME.css,
XDG_CONFIG_HOME/gtk-3.0/gtk.css, /usr/share/themes/...
/usr/share/mate-screensaver/lock-dialog-THEME.css file has highest priority, if exists:
$ gsettings get org.mate.screensaver lock-dialog-theme
'test'
$ grep lock-dialog /usr/share/mate-screensaver/lock-dialog-test.css
.lock-dialog.background {
.lock-dialog frame {
.lock-dialog notebook {
.lock-dialog entry,
.lock-dialog entry:focus {
.lock-dialog button,
.lock-dialog button:focus {
.lock-dialog button:hover,
.lock-dialog button:hover:active {
...
Otherwise:
/usr/share/themes folder if lock-dialog-theme is set to 'debault'
$ gsettings get org.mate.screensaver lock-dialog-theme
'default'
$ gsettings get org.mate.interface gtk-theme
'TraditionalOk'
$ grep lock-dialog /usr/share/themes/TraditionalOk/gtk-3.0/*.css
/usr/share/themes/TraditionalOk/gtk-3.0/mate-applications.css:.lock-dialog {
/usr/share/themes/TraditionalOk/gtk-3.0/mate-applications.css:.lock-dialog notebook {
Priority order: https://developer.gnome.org/gtk3/stable/GtkStyleProvider.html
|
|
|
|
The X server hasn't implemented it in over 10 years.
and it was dropped from debian since a long time.
fixes https://github.com/mate-desktop/mate-screensaver/issues/199
|
|
|
|
Reuses WITH_SYSTEMD #define to reduce #ifdef mess.
ELOGIND is not officially supported, but since it's
a subset of systemd, it should work out of the box.
Co-authored-by: Joakim Tjernlund <[email protected]>
|
|
|
|
commit https://github.com/mate-desktop/mate-screensaver/commit/599bc81
changed the fade time out to be less than a 1000ms.
Unfortunately, this broke the fade because the math for computing
the number of fade steps used integer arithmetic,
and performed a division by a 1000.
https://bugzilla.gnome.org/show_bug.cgi?id=672583
origin commit:
https://gitlab.gnome.org/GNOME/gnome-screensaver/commit/7e2085a
|
|
This is a follow-up to 5d4416a to fix #126
|
|
|
|
|
|
Signed-off-by: Zhang Xianwei <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Password dialog is now scaled
* Background of lock screen is now scaled
|
|
ignoring return value of ‘fscanf’, declared with attribute warn_unused_result
|
|
This commit reverts:
https://github.com/mate-desktop/mate-screensaver/commit/816394c1a6ce9968dba3e1b0ecc884c8ccca4d43
And it applies an alternative to fix the deprecated functions:
gdk_screen_get_width
gdk_screen_get_height
|
|
|
|
|
|
Fixes #101
|
|
|
|
|
|
|
|
OpenBSD does not have nor use pam(8) for password authentication but
instead uses bsd_auth(3): add a bsd_auth authentication scheme to
make locking possible.
This has been a part of gnome-screensaver already but was probably
removed at one point. This is mostly identical to that code, with some
minor modifications.
|
|
The function g_get_real_name is used to get user's full name, but when the full
name is not existed, it will return an empty string instead of NULL.
|
|
configurations with overlapping monitor geometries
|
|
This changes the code quite a lot as both grabbing the pointer and the keyboard
have to be done simultaneously now.
|
|
and set grid property only once, after grid is created
|
|
|
|
Change shake times to even number, so the dialog can return to its original position.
|
|
position.
|
|
|
|
Which are completely broken in GTK+ 3.22.
|
|
|
|
and require libmatekbd and libmate-desktop >= 1.17
|
|
|
|
In some systems the gdm binary is actually called "gdm-binary", so we
need to check for that too.
|
|
fixes https://github.com/mate-desktop/mate-screensaver/issues/104
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
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
|
|
|