Bug 901918 - USB LiveCD - Press any key to interrupt just resets timer
Summary: USB LiveCD - Press any key to interrupt just resets timer
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: syslinux
Version: 18
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-19 23:23 UTC by Cybertimber2011
Modified: 2014-02-05 15:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 749937
Environment:
Last Closed: 2014-02-05 15:21:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cybertimber2011 2013-01-19 23:23:07 UTC
+++ This bug was initially created as a clone of Bug #749937 +++

Description of problem:
After using LiveUSB Creator to make a bootable live usb disk, on boot, the system presents the "Fedora 18" screen with "Start Fedora 18" "Troubleshoot" and a message saying "Starting Fedora 18 in x seconds. Press any key to interrupt".
When I press any key (sans a few exceptions) the timer is not stopped, but is instead reset to 10 seconds.  

Version-Release number of selected component (if applicable):
syslinux

How reproducible:
Always on USB

Steps to Reproduce:
1. Grab Fedora 18 Final (LiveCD)
2. Use LiveUSB Creator or dd to create a usb stick per wiki instructions.
3. Create a USB stick
4. Try to boot
5. On boot, try to interrupt by pressing "any" key (example, "m").
  
Actual results:
Timer resets to 10 seconds

Expected results:
Boot is interrupted

Additional info:
If I press ".", it resets to 10.
If I press "a", it resets to 10.
If I press the up arrow, it resets to 10.
If I press the left arrow, it resets to 10.
If I press "s"... it interrupts.
If I press the down or right arrow key, it interrupts.
If I press the space bar, it interrupts.

--- Additional comment from Mads Kiilerich on 2011-11-09 13:49:21 EST ---

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?

--- Additional comment from Cybertimber2011 on 2011-11-09 14:45:03 EST ---

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.

--- Additional comment from Cybertimber2011 on 2011-11-10 13:19:10 EST ---

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.

--- Additional comment from Cybertimber2011 on 2011-11-14 12:14:44 EST ---

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?

--- Additional comment from Mads Kiilerich on 2011-11-14 12:42:22 EST ---

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.

--- Additional comment from Cybertimber2011 on 2011-11-14 18:27:33 EST ---

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.

--- Additional comment from Mads Kiilerich on 2011-11-14 19:12:10 EST ---

D'oh!

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

--- Additional comment from Cybertimber2011 on 2012-03-23 12:27:42 EDT ---

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 1 Fedora End Of Life 2013-12-21 10:35:21 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 2 Fedora End Of Life 2014-02-05 15:21:52 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.