Bug 855649 - F18 KDE Live (alpha TC5) Anaconda: Debug "switch tty" message seems wrong
F18 KDE Live (alpha TC5) Anaconda: Debug "switch tty" message seems wrong
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
18
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-09 11:00 EDT by Xavier Hourcade
Modified: 2012-11-22 20:58 EST (History)
6 users (show)

See Also:
Fixed In Version: anaconda-18.8-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-22 20:58:12 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Xavier Hourcade 2012-09-09 11:00:12 EDT
Description of problem:

  When a crash occurred while using Anaconda (eg. bug #854586), one may press the Debug button -- then a dialogue appears including the message:

  « Debug will take you to tty1. Press Ctrl+Alt+F6 to return »

Debug not working, I'm not sure what is to expect exactly here. But yet, this message seems wrong anyway : Live KDE actually runs on tty1 (messaging on tty3).

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

  F18 KDE Live alpha TC5
  (in TC6, hitting Debug itself only leads to a crash)

How reproducible:

  Always

Steps to Reproduce:

  1. Reproduce eg. bug #854586
  2. Hit "Debug"
  
Actual results:

  « Debug will take you to tty1. Press Ctrl+Alt+F6 to return »

Expected results:

  « Debug will take you to tty??. Press Ctrl+Alt+F1 to return »

or even (assuming debug will lead to a text-mode tty)

  « Debug will take you to tty??. Press Alt+F1 to return »
Comment 1 Adam Williamson 2012-11-22 20:58:12 EST
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.

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