Hide Forgot
Description of problem: On the dialog windows for unlock the screensaver, "Switch user" button is missing. This occurs when Xfce4-screensaver is launched by systemd (auto-launch with session start) If I kill xfce4-screensaver, then re-launch it, lock screen -> "Switch user" button is present Version-Release number of selected component (if applicable): xfce4-screensaver-4.16.0-3.fc35.x86_64 How reproducible: lock screen, then unlock Steps to Reproduce: 1. make sure switch user is enabled in screensaver options (on by default) 2. lock screen 3. press any key to get prompted for password Actual results: no switch user button Expected results: should have switch user button Additional info: issue is described here https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/39 root cause analysis from above link: ==================================== In Fedora 34 (and possibly 33) the xfce4-screensaver package sets both autostart and dbus service for some reason: $ rpm -ql xfce4-screensaver | egrep 'dbus|autostart' /etc/xdg/autostart/xfce4-screensaver.desktop /usr/share/dbus-1/services/org.xfce.ScreenSaver.service So a work-around for this problem would be to disable /usr/share/dbus-1/services/org.xfce.ScreenSaver.service file: sudo mv /usr/share/dbus-1/services/org.xfce.ScreenSaver.service /usr/share/dbus-1/services/org.xfce.ScreenSaver.service.orig # And to prevent future upgrade or reinstall of xfce4-screensaver package from restoring the file sudo tee /usr/share/dbus-1/services/org.xfce.ScreenSaver.service < /dev/null ================================ I verified that the above work around works. Suggest Fedora drops /usr/share/dbus-1/services/org.xfce.ScreenSaver.service from the rpm.
also reproduced with Fedora 36: xfce4-screensaver-4.16.0-4.fc36.x86_64
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
this is still with us in xfce4-screensaver-4.16.0-4.fc36.x86_64 I don't know why I bother reopening it's clear no one even looked at this since the text clearly says it reproduces on 36.
Mukundan Ragavan could you please drop /usr/share/dbus-1/services/org.xfce.ScreenSaver.service from the rpm?
(In reply to Michael S. Tsirkin from comment #4) > this is still with us in xfce4-screensaver-4.16.0-4.fc36.x86_64 > I don't know why I bother reopening it's clear no one even looked at this > since the text clearly says it reproduces on 36. I have been busy with other things and have not been able to spend as much as I would like. I did look at this and the upstream issue but could not get to it. I understand the frustration. I will fix this.
FEDORA-2022-191eea6337 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-191eea6337
FEDORA-2022-191eea6337 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-191eea6337` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-191eea6337 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e83b01a7cb has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e83b01a7cb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e83b01a7cb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e83b01a7cb has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-191eea6337 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.