Bug 855649

Summary: F18 KDE Live (alpha TC5) Anaconda: Debug "switch tty" message seems wrong
Product: [Fedora] Fedora Reporter: Xavier Hourcade <public.oss>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, public.oss, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-18.8-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-23 01:58:12 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:

Description Xavier Hourcade 2012-09-09 15:00:12 UTC
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-23 01:58:12 UTC
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.