Bug 838501

Summary: console unusable after init 1
Product: [Fedora] Fedora Reporter: GV <rhel>
Component: systemdAssignee: systemd-maint
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, rhel, systemd-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 18:39:07 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
Screenshot none

Description GV 2012-07-09 09:32:23 UTC
Description of problem:

After issuing "init 1" in Fedora 17 the console cannot be used. There is a conflict with agetty).
Please see the attached picture. I only pressed Enter key. In the end console does not accept any key. Ctrl-Alt-Del does not work. plymouthd and agetty seems to crash.

In 18 years of using linux I never had this kind of problem! (slackware/redhat up to rh9/fedora up to 17).

Version-Release number of selected component (if applicable):
systemd-44-17.fc17.x86_64

Steps to Reproduce:
1. Install Fedora 17 (mimimal)
2. yum update
3. reboot without "rhgb quiet"
4. Switch to console 2, 3, 4, 5. Then back to 1.
5. Login as root.
6. init 1
7. Wait for "welcome to rescue mode...." message.
7. Wait a few moments and press enter (sometimes I am able to run a few commands) or try to issue some commands.


Actual results:
Console is unusable.

Expected results:
Console should be usable.

Additional info:

Comment 1 GV 2012-07-09 09:33:49 UTC
Created attachment 597030 [details]
Screenshot

Comment 2 Michal Schmidt 2012-07-11 08:05:15 UTC
Does it help if you comment out the line "IgnoreOnIsolate=yes" in /lib/systemd/system/getty@.service ?

Comment 3 GV 2012-07-11 08:26:05 UTC
No. Same thing.

Comment 4 Lukáš Nykrýn 2012-07-20 13:41:31 UTC
It seems to me that this bug does not occur in rawhide.

Comment 5 Jóhann B. Guðmundsson 2013-06-15 16:13:05 UTC
Could you retest and confirm that this issue is still present with the latest release of systemd for F17/F18/F19?

Thanks

Comment 6 GV 2013-06-15 19:19:06 UTC
I cannot reproduce this bug using F18 and F19. In F17 I can reproduce the bug.

The difference that I see between F17 and F18/F19 is that systemd from F17 does not kill all the agetty processes when runlevel 1 is requested.

Comment 7 Fedora End Of Life 2013-07-04 06:57:59 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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 to Fedora 17's end of life.

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.

Comment 8 Fedora End Of Life 2013-08-01 18:39:12 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.