The bug is fixed that after a long time fontglide comes to no longer show any characters.
A bug is found that with some X settings X server sends multiple input signals and xscreensaver cannot handle them properly, making it impossible to unlock screen. This new rpm should fix the issue.
Fixes multiple reported issues.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-c2e2cc1e9aPlease login to add feedback.
This update has been submitted for testing by mtasaka.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted xscreensaver-6.00-3.fc34, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Works. Fixes BZ#1954884 for me. Didn't check the other BZs.
while testing BZ#1956262 in a virtual machine I get this output in terminal when opening "Help -- About...":
$ xscreensaver-demo
libEGL warning: DRI2: failed to authenticate
xscreensaver-auth: 00:11:05 OOM: /proc/1/oom_score_adj: Permission denied
xscreensaver-auth: 00:11:05 To prevent the kernel from randomly unlocking
xscreensaver-auth: 00:11:05 your screen via the out-of-memory killer,
xscreensaver-auth: 00:11:05 "xscreensaver-auth" must be setuid root.
I do not know if the message applies to EarlyOOM on Fedora. Or what the policy is about setuid root programs. The file "/usr/libexec/xscreensaver/xscreensaver-auth" has "-rwxr-xr-x" mode bits.
chmod u+s xscreensaver-authtakes care of the message, no xscreensaver restart necessary.This update can be pushed to stable now if the maintainer wishes
On every system that uses this version of xscreensaver, I am frequently unable to unlock the screen at all, and must jump to a TTY to kill the xscreensaver process.
Downgrading to the version in the stable "fedora" repo fixes the issue instantly. Whatever was changed, it's not an improvement.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
When pushing negative karma with such comments (i.e. not simple dependency issue or so but a issue needs investigation), please file a corresponding bug report.
mtasaka edited this update.
@mtasaka Are you sure you want a bug report for a package only in testing? I can create one if you like, but seems a bit odd, at least to me.
@mtasaka I will post the issue here in any case. On some machines, after several attempts with the correct password, it eventually lets me in. The number of required attempts is unpredictable. On others, the only option is logging in via TTY or ssh and killing xscreensaver.
Yes, please.
@mtasaka Here you go, as requested. https://bugzilla.redhat.com/show_bug.cgi?id=1959761
mtasaka edited this update.
mtasaka edited this update.
This update has been submitted for stable by mtasaka.
This update has been pushed to stable.