Bug 749937

Summary: USB LiveCD - Press any key to interrupt just resets timer
Product: [Fedora] Fedora Reporter: Cybertimber2011 <cybertimber2000>
Component: syslinuxAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dennis, mads, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 901918 (view as bug list) Environment:
Last Closed: 2013-02-13 21:10:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Cybertimber2011 2011-10-28 23:14:42 UTC
Description of problem:
After using LiveUSB Creator to make a bootable live usb disk, on boot, the system presents the "Fedora 16" screen with "Start Fedora 16" "Troubleshoot" and a message saying "Starting Fedora 16 in x seconds. Press any key to interrupt".
When I press any key... it just resets the counter to 10.  

I can't get the same to occur in VirtualBox, so I'm not sure if it's because the LiveCD has been put on a USB drive, or if it's a LiveCD issue, or if it's a GRUB(2) issue.

Version-Release number of selected component (if applicable):
Fedora 16 Beta i686
Fedora 16 TC3 x86_64

How reproducible:
Always on USB
Never in VM booting to same LiveCD

Steps to Reproduce:
1. Grab Fedora 16 Beta or TC3
2. Use LiveUSB Creator (no version number seen on it... but the one that supports Fedora 15)
3. Create a USB stick
4. Try to boot
5. On boot, try to interrupt
  
Actual results:
Timer resets to 10 seconds

Expected results:
Boot is interrupted

Additional info:

Comment 1 Cybertimber2011 2011-10-28 23:24:13 UTC
Ok now I'm confused... I'm able to reproduce it in a VM.

If I press ".", it resets to 10.
If I press "a", it resets to 10.
If I press "s"... it interrupts.
If I press the down or right arrow key, it interrupts (no, up or left doesn't)
Some Number pad key buttons interrupt it. Can't figure out if number lock is on or not, but thinking it isn't, and it's defaulting to arrows, which makes sense why some work and others don't.

So...
grub2 issue I think.

Comment 2 Mads Kiilerich 2011-11-09 18:49:21 UTC
That is not the behaviour I see.

What hardware do you use? Is the keyboard special in any way?

Can you reproduce it on other hardware?

Comment 3 Cybertimber2011 2011-11-09 19:45:03 UTC
Nope, no specialized keyboard.  A qwerty.

Experienced it on:
- Compaq TC4400 (tablet)
- VirtualBox VM (using a Logitech keyboard)

I have the Final F16 ISO downloaded so I will test it with that and see if it's still there. Will report back soon.

Comment 4 Cybertimber2011 2011-11-10 18:19:10 UTC
Just tested Fedora 16 Final i686 LiveCD in Virtualbox: Pressing any key resets the timer, but does not interrupt it.

Going to burn a copy to CD (now that I found those nice Lightscribe lables) and test that.

Comment 5 Cybertimber2011 2011-11-14 17:14:44 UTC
Tested the Fedora 16 x64 Full DVD, same thing. When it gets to the screen that says "Automatic boot in ## seconds", pressing any key resets it instead of interrupting it, with the exception of the above listed keys.

Burned copy of the i686 LiveCD? Pressing a key when it says "Starting Fedora 16 in x seconds. Press any key to interrupt" does not interrupt the count, it just resets it, with the exception of the above listed keys.

Performed on a Everex x5000xt, a Compaq TC4400, and VirtualBox.

Do you want a video or something if that would help?

Comment 6 Mads Kiilerich 2011-11-14 17:42:22 UTC
This might essentially be the old joke about problems finding the "any" key.

It would probably be better and less ambiguous if it said "Press Esc to interrupt".

I have however never noticed any problems with the keys I intuitively press - whatever that is. IIRC right arrow or enter boots the default menu item immediately - and I think that is reasonable.

Comment 7 Cybertimber2011 2011-11-14 23:27:33 UTC
Space bar does interrupt it too.  But... the question now is do we have a prompt issue (should say press space/escape to interrupt) or does the programming actually allow for "any" key to be pressed to interrupt, but only working for some keys?

Checking back on Fedora 15, literally ANY key exited the automatic boot.
"D" for example. Or the number "4" key. 
I checked only because I suddenly wasn't sure if a specific key was required.

Comment 8 Mads Kiilerich 2011-11-15 00:12:10 UTC
D'oh!

The live cd uses syslinux, not grub2. Changing component.

Comment 9 Cybertimber2011 2012-03-23 16:27:42 UTC
Peter,
Not sure if you needed an update on this, but it does occur in F17 Beta TC1 (LiveCD). I didn't want to update the version (didn't go so well last time).

Comment 10 Fedora End Of Life 2013-01-16 16:57:34 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 11 Fedora End Of Life 2013-02-13 21:10:53 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.