Bug 2138870

Summary: The "Switch User" option is missing in the default XFCE screensaver.
Product: [Fedora] Fedora Reporter: ar324
Component: xfce4-screensaverAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: aekoroglu, awilliam, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedFreezeException
Fixed In Version: xfce4-screensaver-4.16.0-8.fc37 xfce4-screensaver-4.16.0-8.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-05 01:17:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Notice the lack of the "Switch User" option. none

Description ar324 2022-10-31 14:29:02 UTC 
Created attachment 1921386 [details]
Notice the lack of the "Switch User" option.

Description of problem: XFCE Screensaver has an option to switch users from the lock screen (https://docs.xfce.org/apps/screensaver/start — notice the last feature in the bullet list, "User switching").

However, on a fresh install of Fedora 37, this feature does not seem to work correctly. The "Switch User" option is missing from the options. Please refer to the attached image.

The following link points to the related upstream issue: https://gitlab.xfce.org/apps/xfce4-screensaver/-/issues/39. However, it is not an upstream issue, in my opinion. After doing some digging around, I can see that we start the screensaver daemon using both, the XDG autostart mechanism, and DBUS:

https://src.fedoraproject.org/rpms/xfce4-screensaver/blob/rawhide/f/xfce4-screensaver.spec#_69
https://src.fedoraproject.org/rpms/xfce4-screensaver/blob/rawhide/f/xfce4-screensaver.spec#_82

I fixed this issue on my system by overwriting the DBUS service (I got this from the foregoing Gitlab link):

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

In my understanding, DBUS starts the screensaver daemon too early, before it is able to detect the users on the system. Could we please just use the autostart mechanism? Are there any downsides to it?

Could we please fix this issue, as being able to switch users from the lock screen, on a default installation, is imperative? As it is, even Fedora KDE does not have this option by default, because of some issues that are tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1929643.


Version-Release number of selected component (if applicable): 4.16.0


How reproducible: 100%


Steps to Reproduce:
1. Perform a fresh installation of Fedora 37.
2. Lock the screen.
3. Look for "Switch User" on the lock screen.

Actual results: There is no "Switch User" option on the lock screen.


Expected results: There must be a "Switch User" option on the lock screen.


Additional info:
Comment 1 Fedora Blocker Bugs Application 2022-10-31 14:34:03 UTC 
Proposed as a Freeze Exception for 37-final by Fedora user ar324 using the blocker tracking app because:

 Being able to switch users from the lock screen, on a default installation, is imperative. As it is, even Fedora KDE does not have this option by default, because of some issues that are tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1929643. I think this can be fixed very easily for Fedora XFCE.
Comment 2 Mukundan Ragavan 2022-11-04 10:36:29 UTC 
> In my understanding, DBUS starts the screensaver daemon too early, before it
> is able to detect the users on the system. Could we please just use the
> autostart mechanism? Are there any downsides to it?
> 

There was some issue in the past that I cannot seem to recall now without the dbus file. But I am willing to try with only the autostart mechanism.
Comment 3 Adam Williamson 2022-11-04 20:49:11 UTC 
-5 for FE (-6, +1) in https://pagure.io/fedora-qa/blocker-review/issue/999 , so marking rejected.
Comment 4 Fedora Update System 2022-12-30 21:03:01 UTC 
FEDORA-2022-191eea6337 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-191eea6337
Comment 5 Fedora Update System 2022-12-30 21:03:19 UTC 
FEDORA-2022-e83b01a7cb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e83b01a7cb
Comment 6 Fedora Update System 2022-12-31 02:08:22 UTC 
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.
Comment 7 Fedora Update System 2022-12-31 02:18:19 UTC 
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.
Comment 8 Fedora Update System 2023-01-05 01:17:10 UTC 
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.
Comment 9 Fedora Update System 2023-01-08 01:28:39 UTC 
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.