Bug 1001073

Summary: anaconda (text mode) pressing PRINT SCREEN key on a kvm guest causes a 'pane is dead' (kills anaconda)
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-26 18:45:13 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:
Attachments:
Description Flags
screenshot of F20 aTC1, after pressing PRINT SCREEN key
none
anaconda.log
none
program.log none

Description Reartes Guillermo 2013-08-26 12:51:22 UTC
Created attachment 790509 [details]
screenshot of F20 aTC1, after pressing PRINT SCREEN key

Description of problem:

If one presses the 'print screen' key, anaconda dies with a 'pane is dead' message.

Version-Release number of selected component (if applicable):
F20 aTC1 (20.8-1)

How reproducible:
always

Steps to Reproduce:
1. boot with 'text' boot parameter
2. select 'text mode' when prompted
3. press 'print screen' key

Actual results:
'pane is dead'

Expected results:
either handle the print screen (unlikely on text mode) or nothing, 
just do not crash.

Additional info:
i do not know if this also happens on a physical host.

Comment 1 Reartes Guillermo 2013-08-26 12:51:52 UTC
Created attachment 790510 [details]
anaconda.log

Comment 2 Reartes Guillermo 2013-08-26 12:52:20 UTC
Created attachment 790511 [details]
program.log

Comment 3 David Shea 2013-08-26 18:45:13 UTC
From the screenshot, anaconda appears to have received Ctrl-\, which sends a SIGQUIT to the process. What keystroke we receive when print screen is sent is completely out of our control, and changing the default SIGQUIT behavior could interfere with debugging.