Description of problem: It is possible to switch away from the xguest session using fast user switching, but not back to it. When switching back you get prompted for a password which isn't usable. Either fast user switching for xguest should be disabled or switching back should get fixed. Note that i was able to fast user switch to xguest to create a session. Was there was a current session I could no longer do this. Version-Release number of selected component (if applicable): xguest-1.0.7-7.fc12.noarch How reproducible: Seems to be 100% Steps to Reproduce: 1. Login into xguest. 2. Switch to another user. 3. Try to switch back to xguest. Actual results: Password is required but not usable. Expected results: No password required. Additional info: This is the first line in /etc/pam.d/gdm-password : auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
I think we need to prevent fast user switching away form xguest, because the login program will not allow you to login without a password if there is a xguest session running.
I can't easily test the F11 version as all of my machines are F12 now. If it looks like you need me to do a test of this (which seems unlikely), I look at making an F12 build based on the changes made for the F11 build.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still an issue on xguest-1.0.9-1.fc14.noarch
Ray, Is there a way to differentiate between fastuser switching and initial login?
Also is there an app that xguest starts that allows it to do fast user switching?
What is doing the PAM authentication when switching back to a running session?
I think it is all being done with gdm.
If it is so, then it's probably just a matter of gdm properly calling PAM for authentication. It needs to set the effective uid to the user's uid so pam_sepermit does not enforce the exclusive session locking. For gnome-screensaver it should work fine as it is always running with the user's uid.
This bug seems to be still there in all recent Fedora Versions, although it is kind of critical for use with 'lesser experienced users' on notebooks. It is possible to prevent them from turning off the system until someone with higher privileges fixes this.
Ray if you have some time next week, maybe we can work on this.
sure.
*** Bug 870592 has been marked as a duplicate of this bug. ***
This is still valid for Fedora 19.
Still valid in F20. BTW, this also happens when the notebook goes to sleep. When it wakes up again, it is impossible to login to the xguest session. Note that both logging in from sleep and user switching is fixed in the RHEL/CentOS6 xguest.
This was dormant for quiet some time now. Is there any chance that the fixes for RHEL6 will make it into fedora?
I am having trouble getting switch user to work in f21 with xfce. I changed to using gdm for the display manager so that dwitch user was not greyed out, but when I selrcted that uption nothing happened. This was the case whether I was logged in a xguest or my normal account.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.