Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
|
|
|
|
and require libmatekbd and libmate-desktop >= 1.17
|
|
|
|
taken from:
https://git.gnome.org/browse/gnome-screensaver/commit/?id=214ab95
https://git.gnome.org/browse/gnome-screensaver/commit/?id=4f0124a
|
|
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
|
|
Has been in Gtk since 2.22
|
|
|
|
(Fix #46) Patch by Steven Chamberlain
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=bug749629.patch;att=1;bug=749629
|
|
|
|
|
|
|