Bug 1955876 - xfce4 screensaver doesn't offer switch user option without restart
Summary: xfce4 screensaver doesn't offer switch user option without restart
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-screensaver
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-01 06:02 UTC by Eric L.
Modified: 2023-05-25 19:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:30:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Eric L. 2021-05-01 06:02:43 UTC
Description of problem:
after the upgrade to F34 I was impacted by https://bugzilla.redhat.com/show_bug.cgi?id=1944011 so I removed all the parallel screensavers/lockers and kept only xfce4-screensaver. The issue is now that the switch user button doesn't show unless I kill the auto-started xfce4-screensaver process and start it again (with Alt+F2 for example, but I can also start it from a terminal).

The severity is high because the laptop is used by multiple persons and it's not acceptable to have it locked by a single individual in times of homeschooling and homeworking (and the workaround isn't usable by the rest of the family).

Version-Release number of selected component (if applicable):
$ rpm -qa | grep -e saver -e locker
xfce4-screensaver-4.16.0-2.fc34.x86_64

How reproducible:
Always, I rebooted a few times to make it work, but same result

Steps to Reproduce:
1. make sure xfce4-screensaver-preferences shows the "User Switching" option on
2. make sure xfce4-screensaver is autostarted
3. reboot
4. lock -> no switch user button
5. unlock
6. kill/stop xfce4-screensaver
7. Alt+F2 and start xfce4-screensaver
8. lock -> switch user button is available (and works)

Actual results:
See above

Expected results:
Obviously, the switch user button should be there from the beginning

Additional info:
The issue might already have been in F33 because I think, I was transparently using xscreensaver instead of xfce4-screensaver.
I couldn't find any relevant error message in dmesg, journalctl [--user] or in ~/.xsession-errors.

Comment 1 Mukundan Ragavan 2021-05-01 12:27:18 UTC
Thanks for the thorough bug report. I have filed this upstream and push a fix as soon as one is available.


https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/87

Comment 2 Mukundan Ragavan 2021-05-03 22:10:25 UTC
Upstream issue - 

https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/39

Comment 3 Tomasz Ostrowski 2021-05-06 08:12:47 UTC
The xfce4-screensaver package sets both autostart desktop file 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
```

But when started with dbus-services it lacks required environment variables, so it ignores user settings.

So a work-around for this problem would be to disable /usr/share/dbus-1/services/org.xfce.ScreenSaver.service file, as when started with it the process lacks required environment variables:

```
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
```

Maybe the package should install /etc/xdg/autostart/xfce4-screensaver.desktop only and remove /usr/share/dbus-1/services/org.xfce.ScreenSaver.service. I suppose there's no need for both.

Comment 4 Ben Cotton 2022-05-12 16:54:23 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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 34 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.

Comment 5 Eric L. 2022-05-12 20:08:29 UTC
The problem is present until now in F35

Comment 6 Eric L. 2022-05-14 06:27:25 UTC
I just upgraded to F36 and the issue is still there, a fix would be nice after so much time.

Comment 7 Ben Cotton 2023-04-25 18:22:34 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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.

Comment 8 Ludek Smid 2023-05-25 19:30:41 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.


Note You need to log in before you can comment on or make changes to this bug.