Bug 872817 - rescue mode unavailable
Summary: rescue mode unavailable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-03 14:03 UTC by GV
Modified: 2014-02-05 12:50 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 12:50:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (20.62 KB, image/png)
2012-11-03 14:04 UTC, GV
no flags Details

Description GV 2012-11-03 14:03:55 UTC
Description of problem:
I'm unable to type anything useful in rescue mode. See attached screenshot.

Version-Release number of selected component (if applicable):
Fedora 18 development with all updates up to 03.11.2012.
systemd version 195-2.fc17.x86_64

How reproducible:


Steps to Reproduce:
1. Boot in rescue mode (in grub menu add 1 to kernel command line)
2. Try to type any command once rescue shell has been started.
  
Actual results:
Rescue shell is not functional.

Expected results:
Rescue shell should be functional.

Additional info:

Comment 1 GV 2012-11-03 14:04:38 UTC
Created attachment 637509 [details]
screenshot

Comment 2 Michal Schmidt 2012-11-09 11:32:01 UTC
I can't reproduce this.
Could you paste your complete kernel command line?
Is this with a Fedora packaged kernel, or did you compile your own?

Comment 3 GV 2012-11-09 12:18:26 UTC
> I can't reproduce this.
Well, you can if you generate an initrd with plymouth installed, erase all plymouth packages and boot in single mode. I just find this.

> Could you paste your complete kernel command line?
BOOT_IMAGE=/vmlinuz-3.6.5-2.fc18.x86_64 root=UUID=82f7de3b-5084-4615-b2f2-61671e6eccb1 ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 biosdevname=0 1

> Is this with a Fedora packaged kernel, or did you compile your own?
# rpm -qa | grep kernel
kernel-3.6.5-2.fc18.x86_64
kernel-3.6.6-3.fc18.x86_64

I cannot run anything in single mod with 3.6.5-2.fc18.x86_64 since plymouth is initrd.
If I generate a new initrd, added a new entry in grub.cfg (same kernel, the new initrd, etc.), boot in single mode - no problems.

Comment 4 Michal Schmidt 2012-11-09 12:26:27 UTC
(In reply to comment #3)
> > I can't reproduce this.
> Well, you can if you generate an initrd with plymouth installed, erase all
> plymouth packages and boot in single mode. I just find this.

Perhaps a scriptlet in plymouth should try to avoid this kind of a mismatch. Reassigning to plymouth.

Comment 5 Fedora End Of Life 2013-12-21 09:16:24 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 6 Fedora End Of Life 2014-02-05 12:50:10 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.