Bug 806560

Summary:	useradd usermod utilities causes gdm to fail
Product:	[Fedora] Fedora	Reporter:	Bill Gradwohl <bill>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	rstrode
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 22:04:09 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 Gradwohl 2012-03-24 19:46:36 UTC

Description of problem:
With a graphical.target boot up, but with no one graphically logged in, logging into a tty session as root and adding a user via useradd causes the tty session to be replaced by the GUI login screen. It is possible to return to the tty session, but it should never have left to begin with.

Same scenario but with someone logged in to the DE while root is working on a tty, adding a user with useradd or modifying a user with usermod causes the DE session to terminate showing the login screen with the new user in the list of known users.

Logged in to a DE as root, executing useradd utility within a gnome-terminal randomly kills the GUI session offering a login screen. Anything that was running in the DE is history.

Logged in to the DE as a mere mortal and using su to adduser does the same thing.

I don't know if its related, but I also put up a bug 804354 incident for :

TMOUT=1; read; echo $?

via the gnome-terminal that behaves similarly.


Version-Release number of selected component (if applicable):
F16 fully patched.

Comment 1 Bill Gradwohl 2012-05-27 14:34:07 UTC

Do you need additional information?

Is this fixed in F17?

Comment 2 Fedora End Of Life 2013-01-16 17:25:23 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Comment 3 Fedora End Of Life 2013-02-13 22:04:13 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.