Bug 2348

Summary:	Alt-Fx does a chvt, even without the Ctrl.
Product:	Mageia	Reporter:	Richard Neill <mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	balcaen.john, thierry.vignaud
Version:	1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kdebase4	CVE:
Status comment:

Description Richard Neill 2011-07-31 16:56:21 CEST

Description of problem:

When I press Alt-Fx  (for x = 1...n), this is interpreted as if it were Ctrl-Alt-Fn. So, for example, 
  Alt-F2  causes X to switch to VT number 2.
On manually switching back (with Ctrl-Alt-F7), I find the KDE command-entry dialog (the expected result of Alt-F2) waiting for me.

How reproducible:

All the time.
See also: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/730307

Steps to Reproduce:
1. Log into KDE as normal.
2. Press "Alt-F2". Expect to see the KDE-command-dialog.
3. Be startled, when it does a "chvt 2".
4. Press Ctrl-Alt-F7 to get back to KDE.
5. See the expected command-dialog has appeared.

Comment 1 Thierry Vignaud 2011-08-01 14:34:51 CEST

This is not a xserver bug. Either KDE or from xkbd

CC: (none) => thierry.vignaud
Source RPM: x11-server-xorg-1.10.1-1.mga1 => kdebase4

Comment 2 Richard Neill 2011-08-01 15:58:55 CEST

(In reply to comment #1)
> This is not a xserver bug. Either KDE or from xkbd

You're right. I couldn't possibly see how it could be a KDE bug because none of the KDE keyboard shortcuts include Ctr-Alt-Fx, and I had thought that Ctrl-Alt-Fx are trapped by the x-server, in the same way as Ctrl-Alt-Bksp.

However, I can confirm that Gnome behaves correctly (i.e. Alt-F2 brings up the command-entry dialog without any chvt). 

Is there any other diagnostic I could run for you?

Manuel Hiebel 2011-08-02 00:27:13 CEST

CC: (none) => balcaen.john

Comment 3 Richard Neill 2011-08-27 21:11:20 CEST

This has been fixed - it no longer affects the latest KDE packages (4.6.5). As the original reporter, I'm marking this as resolved - thanks for your time.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Richard Neill 2012-05-15 16:45:25 CEST

I hate to say this, but this is back again, in KDE 4.8.2

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 John Balcaen 2012-05-15 17:24:02 CEST

Could you open a new bug report against cauldron (& later mga2)  ?
This bug report is against mageia 1 (so kde 4.6.x not 4.8.x)
(One more thing is that i'm not able to reproduce it.)

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 6 Richard Neill 2012-05-16 23:12:06 CEST

That's very strange: it's gone away again after reboot. I'm guessing that the cause might be some inconsistency created by doing urpmi --auto-update and not restarting the X-session.  No need to re-open.