Bug 878956 - After installation is complete, Alt+F4 is broken
Summary: After installation is complete, Alt+F4 is broken
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 18
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedNTH RejectedBlocker
Depends On:
Blocks: F18-accepted, F18FinalFreezeExcept
TreeView+ depends on / blocked
Reported: 2012-11-21 16:20 UTC by Kamil Páral
Modified: 2012-12-06 07:20 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-12-06 07:20:04 UTC
Type: Bug

Attachments (Terms of Use)
bug demonstration video (973.33 KB, video/ogg)
2012-11-21 16:20 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2012-11-21 16:20:44 UTC
Created attachment 649297 [details]
bug demonstration video

Description of problem:
After the installation is complete, the system behaves like Ctrl was always pressed. You can use Alt+F4 to close an application, because it switches you to tty4 (like Ctrl+Alt+F4 would do). (But the application is closed after you return back to tty1). If you hit Alt+F2, you are switched to tty2, but gnome-shell's "run command" dialog appears.

This doesn't happen after the system is booted or when the installation is underway. Only after the installation is complete. (I forgot to test what happens when I close Anaconda window, that I do not know).

This is problematic when a user doesn't know what VT is and how to get back to graphical console. He might be forced to hard-reset the machine. It might also look the the installer/system crashed.

Version-Release number of selected component (if applicable):
anaconda 18.29.2
F18 Beta RC1 Live

How reproducible:

Steps to Reproduce:
1. boot Live
2. finish installation
3. try to close some other application with Alt+F4

Comment 1 Kamil Páral 2012-11-21 16:22:53 UTC
I believe this should be a F18 Blocker, because it can't be fixed with an update and it might create a lot of problems and confusions for Fedora LiveCD users.

Use case:
Working with LiveCD and installing in the background. After the installation is complete, I want to close existing windows (browser, chat, etc) -> Alt+F4 -> tty4.

Comment 2 Rubens Takiguti Ribeiro 2012-11-27 23:16:33 UTC
I noticed the same bug using the live cd (Fedora-18-Beta-x86_64-Live-Desktop.iso). So, the problem should not be at anaconda.

Description: the Ctrl key appers to be pressed automatically when the Alt key is pressed.

Minimum steps to reproduce the bug:
1 - starts user session using live cd.
2 - click on "Live System User" menu.
3 - click on "System Settings" option.
4 - click on "Region & Settings" option.
5 - click on "System" tab.
6 - click on "Copy Settings..." button.



before step 6, the System tab was like that:
* Your settings
  - Display language: English (United States)
  - Input source: English (US)
  - Format: United States (Enlish)
* System settings:
  - Display language: English (United States)
  - Input source: [none]
  - Format: United States (English)

after step 6, the System tab was like that:
* Your settings
  - Display language: English (United States)
  - Input source: English (US)
  - Format: United States (Enlish)
* System settings:
  - Display language: English (United States)
  - Input source: English (US)
  - Format: United States (English)

Comment 3 Kamil Páral 2012-11-28 12:23:21 UTC
Great findings, Rubens! Thanks.

This is tightly connected to Anaconda, because this bug does not shown before "Configuring installed system" phase in Anaconda. After that phase is over, this bug manifests. If you check Region&Language afterwards, it contains the same output as you stated in comment 2 after step 6. That means Anaconda performs the exact procedure that you did manually and triggers this bug.

I checked also KDE LiveCD and this problem manifests as well. Before Anaconda installation is complete, Alt+F2 shows "run command" dialog, after it is over (and language preferences are adjusted), it switches to tty2.

The problem must be somewhere in Xorg or other low-level tools. Reassigning.


Comment 4 Rubens Takiguti Ribeiro 2012-11-28 16:28:02 UTC
Based on the bug nature, I suppose the problem may be at new IBUS features:

Comment 5 Adam Williamson 2012-11-28 17:30:03 UTC
I suspect this may be related somehow to https://bugzilla.redhat.com/show_bug.cgi?id=859485 . Josh, Adam, is that the case?

Comment 6 Josh Boyer 2012-11-28 17:34:11 UTC
(In reply to comment #5)
> I suspect this may be related somehow to
> https://bugzilla.redhat.com/show_bug.cgi?id=859485 . Josh, Adam, is that the
> case?

Sounds likely.  Particularly the steps from comment #2.

A kernel fix is already available.  We're waiting on a patched Xorg.

Comment 7 Adam Williamson 2012-11-28 17:48:56 UTC
Discussed at 2012-11-28 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-11-28/f18final-blocker-review-1.2012-11-28-16.59.log.txt . Agreed this is rejected as a blocker - it's an annoying bug, but it doesn't quite hit any of the criteria, and we didn't think it ultimately passed the 'if today was go/no-go and this was the last bug, would we slip?' smell test. It is accepted as NTH as it's a significant user experience bug that cannot be fixed with an update.

Comment 8 Fedora Update System 2012-11-28 18:39:54 UTC
xorg-x11-server-1.13.0-10.fc18 has been submitted as an update for Fedora 18.

Comment 9 Fedora Update System 2012-11-28 21:13:42 UTC
Package xorg-x11-server-1.13.0-10.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-server-1.13.0-10.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 10 Kamil Páral 2012-11-29 09:44:22 UTC
Because I can't simulate the problem on an installed system, I have tested xorg-x11-server-1.13.0-10.fc18 by updating it on LiveCD, restarting gdm a following the reproducer. The bug still happens. Do I also need updated kernel to verify this?

Comment 11 Josh Boyer 2012-11-29 13:02:11 UTC
What kernel is on the livecd?  If it isn't 3.6.7-5.fc18 or newer, then yes you need a newer kernel.

Comment 12 Kamil Páral 2012-11-29 19:27:38 UTC
This is fixed with kernel 3.6.7-5.fc18 and xorg-x11-server-1.13.0-10.fc18. I built a custom LiveCD and checked.

Comment 13 Fedora Update System 2012-11-30 19:56:42 UTC
xorg-x11-server-1.13.0-11.fc18 has been submitted as an update for Fedora 18.

Comment 14 Fedora Update System 2012-12-06 07:20:07 UTC
xorg-x11-server-1.13.0-11.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

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