Bug 631584

Summary:	getty and firstboot running on the same virtual console tty
Product:	[Fedora] Fedora	Reporter:	Ira Malinich <thub>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	awilliam, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-08 15:20:07 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 Ira Malinich 2010-09-07 22:56:28 UTC

Description of problem:
Installed from systemd Test Day LiveCD (didn't get firstboot at all) and updated via yum.  After reboot to runlevel 5, still no firstboot, but booting to runlevel 3 (or 2 or 4) starts text mode firstboot on tty1 and the regular login prompt redraws the screen after about ten seconds.  Thereafter, keystrokes randomly get sent to either getty/login or firstboot.
Other virtual consoles (tty2 through tty6) work fine.

Version-Release number of selected component (if applicable):
systemd-9-3.fc14

How reproducible:
Consistently

Steps to Reproduce:
1. Install from F14 systemd Test Day LiveCD (http://adamwill.fedorapeople.org/systemd_test_day_20100907/systemd_20100907.iso) (may not be necessary with an up-to-date F14 system)
2. Update system with yum
3. "rm /etc/sysconfig/firstboot" if it exists
4. Reboot and add "3" to boot parameters
  
Actual results:
Quantum firstboot where it both exists and doesn't exist.

Expected results:
Either a working firstboot followed by getty login or just the getty login, not both.

Comment 1 Bill Nottingham 2010-09-08 02:38:14 UTC

What version of firstboot?

Comment 2 Adam Williamson 2010-09-08 15:20:07 UTC

I'm fairly sure all current firstboot weirdness is caused by the problem I explain in 628241.

*** This bug has been marked as a duplicate of bug 628241 ***