Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12412 - X ignores ctrl+alt+(Fn|backspace) key combos.

Attached to Project: Arch Linux
Opened by Peter Gebauer (rusty) - Thursday, 11 December 2008, 12:28 GMT
Last edited by Allan McRae (Allan) - Saturday, 27 June 2009, 03:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Sometimes X will freeze up or the WM will crash, no biggie, ctrl+alt+backspace has always allowed for a restart, but not with the 1.5.3 version. None of the ctrl+alt combinations work. This is probably some upstream bug, but it would be nice if the "stable" arch would downgrade to an X version that doesn't force reboots a la Winblows.I put the severity as high because in four years I have not had to reboot my Debian machine and now I've had to reboot my Arch box TWICE in one day. Not very good for "stable".

Additional info:
xorg 1.5.3

/etc/X11/xorg.conf:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection

Section "Module"
Load "extmod"
Load "glx"
Load "xtrap"
Load "dbe"
Load "dri"
Load "freetype"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "se"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 60.0
EndSection

Section "Device"
Identifier "Card0"
Driver "ati"
VendorName "ATI Technologies Inc"
BoardName "RS480 [Radeon Xpress 200G Series]"
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
EndSection

Section "ServerFlags"
Option "AllowEmptyInput" "False"
Option "AutoAddDevices" "False"
Option "HandleSpecialKeys" "Always"
EndSection


Steps to reproduce:
Just make your WM crash, I did it to fluxbox by killall -HUP fluxbox (should work for reloading configs, unless fluxbox too is super buggy) until X suddenly froze.
Also, when my monitor was out of sync or unable to display the resolution, X froze and I could not exit it or switch to TTY. Very very bad.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 27 June 2009, 03:22 GMT
Reason for closing:  Works for me
Additional comments about closing:  No response from submitter.
Comment by Glenn Matthys (RedShift) - Thursday, 11 December 2008, 18:59 GMT
Can you try commenting out Option "HandleSpecialKeys" "Always" and see if ctrl+alt+backspace behaves correctly?
Comment by Peter Gebauer (rusty) - Friday, 12 December 2008, 08:52 GMT
Hey Glenn! I tried before without that option and it froze, but I'll run it a while without it for a while and see.

Btw, this reminds me of the early nvidia problems in X and sometimes svgalib probs where graphics driver would freeze, locking graphics card. As you can see I'm using ATI, I've seen a few driver bugs reporting freezes in the past, might be something like that. OR the new hot plug input thingie, I've got a remote box available now so I can hopefully extract more information next time this happens.

Maintainers of Xorg should beware of new features, maybe check them out for a while in testing or unstable. For as long as I can remember, X has always been bit dodgy, even in the old xfree86 days.
Comment by Glenn Matthys (RedShift) - Friday, 12 December 2008, 08:59 GMT
The new Xorg has been sitting in testing for a very long time... Anyway, I think your whole system is locking up instead of just Xorg, can you login from remote and gather what information you can get? Can you try any of the stock xf86-video* drivers for your video card and see if the lockups still occur?
Comment by Zoltan Beihuber (zoltan) - Tuesday, 27 January 2009, 12:27 GMT
Hi,

I encounters a very similar problem even if X stops normally not by crash. After exiting X (e.g. exiting WM which was started by startx, or killing DM) the vt07 remains somehow alive. I can switch to it with alt+F7, but I can't find any way to switch back to another working vt. I see a black screen somtimes with some dummy characters on it and the only thing I can do is to push the power button of my computer.

I am not sure this is the same problem then yours but I dicided to comment here first instead of creating a duplicated bug report. If it seems a completly different issue to you please let me know, and I will create a separate bug entry for it.

Have a nice day,

Zoltan
Comment by Roman Kyrylych (Romashka) - Thursday, 28 May 2009, 18:01 GMT
what is the current status of the issue?

Loading...