Bug 467539 - Shortcuts for VT have changed from Ctrl+Alt+Fkey to Alt+Fkey
Summary: Shortcuts for VT have changed from Ctrl+Alt+Fkey to Alt+Fkey
Keywords:
Status: CLOSED DUPLICATE of bug 467636
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-evdev
Version: rawhide
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 467479 (view as bug list)
Depends On:
Blocks: 409791
TreeView+ depends on / blocked
 
Reported: 2008-10-18 06:22 UTC by Edney Matias
Modified: 2018-04-11 13:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-19 22:10:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Edney Matias 2008-10-18 06:22:59 UTC
Description of problem: Shortcuts for VT have changed from Ctrl+Alt+Fkey to Alt+Fkey. So, switching to VTs happens all the time.


Version-Release number of selected component (if applicable):
[matias@r2d2 ~]$ rpm -qa | grep xorg-x11-server
xorg-x11-server-common-1.5.2-5.fc10.x86_64
xorg-x11-server-utils-7.4-3.fc10.x86_64
xorg-x11-server-Xorg-1.5.2-5.fc10.x86_64

running kde 4.1.2 from Live CD.


How reproducible: Always.


Steps to Reproduce:
1. Press Alt+F2 and get VT2
2. Press Alt+F1 and get blank screen from VT1
3. and so on
  
Actual results: If I press Alt+F2 I go to VT2 and when come back to graphical mode krunner is on the screen.


Expected results: Alt+F2 would give me krunner but i go directly to VT2


Additional info: just in case Linux r2d2 2.6.27.2-23.rc1.fc10.x86_64 #1 SMP Thu Oct 16 23:42:46 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Ralph Loader 2008-10-18 08:37:39 UTC
Also Alt-Left / Alt-Right / Ctrl-Alt-Left / Ctrl-Alt-Right under X are switching VT not workspace.

Comment 2 Edney Matias 2008-10-18 19:54:11 UTC
I'm raising to urgent cause if i press the 'two' key X is restarted! And I wrote 'two' instead of actually pressing 'two' cause X would be restarted.

Comment 3 Edney Matias 2008-10-18 20:02:13 UTC
If i press the 'r' key the third LED of my keyboard lights up (first comes numlok, than capslock, than the LED i'm talking about). If i press the 'w' or ''' key the LED is turned off. I have a Dell Vostro 1400 with an ABNT keyboard.

Comment 4 Edney Matias 2008-10-18 20:04:04 UTC
Without updating again the first problem disappeared. Don't know what happened.

Comment 5 Mathieu Bridon 2008-10-19 13:06:05 UTC
I'm still seeing this problem in latest Rawhide.

In fact, this is rather expected as:
- usually, on TTY 7 (graphical), you have to use CTRL + ALT + Fx / arrow key / tab key to swith VTs
- on text VTs, CTRL is not needed anymore
- X is running on TTY 1 here !

Why did X was switched from TTY 7 to TTY 1 ?

Can the shortcuts from TTY 7 be backported to TTY 1 ?

Comment 6 Andrew Cathrow 2008-10-19 19:09:20 UTC
I saw the same thing on my machine with the following configuration

Rawhide 9.92
X86_64
Graphics : 82G965 

xorg-x11-server-utils-7.4-3.fc10.x86_64
xorg-x11-server-common-1.5.2-5.fc10.x86_64
xorg-x11-server-Xorg-1.5.2-5.fc10.x86_64
plymouth-0.6.0-0.2008.10.17.1.fc10.x86_64

To fix the issue I created a *very* simple xorg.conf file (see below)
If I startup without the xorg.conf file I get the odd keyboard mappings (ALT-F2) -> tty2, but if I have a xorg.conf present it's fine.


Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "intel"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Comment 7 Matěj Cepl 2008-10-19 21:59:56 UTC
I have my suspicion, that this is actually duplicate of bug 467636

Comment 8 Matěj Cepl 2008-10-19 22:02:30 UTC
*** Bug 467479 has been marked as a duplicate of this bug. ***

Comment 9 Matěj Cepl 2008-10-19 22:10:30 UTC

*** This bug has been marked as a duplicate of bug 467636 ***


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