Bug 450200

Summary:	xguest behaves very strangely with user switching
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	jmccann, rstrode, rvokal, sgrubb
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pam-1.0.1-1.fc9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-01 10:09:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill Nottingham 2008-06-05 21:01:44 UTC

Description of problem:

xguest doesn't really work with user switching the way I'd expect.

If you switch away from xguest, you get the normal GDM dialog.
'Guest' is marked as 'currently logged in'

OK, I suppose that makes some sense. But, ideally, it would allow you to create
a second guest login. 

In any case, click on it. It asks for a password. But xguest doesn't *have* a
password, so obviously you can't enter a working one to go back to xguest's
session. If you ctrl-alt-backspace out of this greeter (or ctrl-alt-f<whatever>
back to the original session), xguest's screen is locked with the same password.
Oops.

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

xguest-1.0.6-7.fc9.noarch
gdm-user-switch-applet-2.22.0-5.fc9.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Log in as xguest
2. Play around with user switching

Comment 1 Daniel Walsh 2008-06-09 19:58:26 UTC

There was a bug in pam_selinux_permit that would not allow you to login if the
uid was currently logged in.  The problem was for gnome-screensaver this did not
make sense.  So I though tomas changed it to only check if the app that is doing
the checking is running as root.

Comment 2 Tomas Mraz 2008-10-01 10:09:17 UTC

Yes, this was already fixed some time ago.