Latest xkeyboard-config prevents ctrl-alt-backspace from killing X

well, as I wrote in the topic latest xkeyboard-config (1.6-1) is preventing ctrl-alt-backspace combination from killing X. I have DonZap option set to false in my xorg.conf. I don't know if it should be like that. Is it a bug? If not, is it any workaround to make it work again?

karol wrote:@whoops
How did you get that magic spell? RTFM or sth else?
I searched for stuff in google, opened a lot of tabs and somewhere in between there was a site about some patch that said something like "this patch removes the ctrl+alt+backspace keyboard shortcut in xorg - to reenable it, you have to type...".
So I pasted it into a terminal, hit strg+alt+backspace and it worked. Which is why I don't know, where I found that Information.
Might have been an ubuntu patch... maybe I should have mentioned that (in case someone added an ubuntu patch to xorg recently to make it "safer" and this is the result...?). edit: no, it wasn't - just found the ubuntu page I was on, and the information isn't from there. But it was on a patch site. Mostly plain text, code, patch info & lots of stuff I didn't understand.
edit2: Aaaah, there it was: http://lists.freedesktop.org/archives/x … 00627.html
Last edited by whoops (2009-05-29 21:41:33)

Similar Messages

Something on my Gnome-Settings prevents Ctrl-Alt-Backspace

Hi
It is quite strange - I have Dontzap disabled in my xorg.conf, I told hal to zap X properly and added setxkbmap -option terminate:ctrl_alt_bksp to my .xinitrc.
But when I log into a Gnome session I won't have a chance to use this key combination. The weird thing about this is that it only happens when I am logged in with my username and use Gnome. Using another user with Gnome or starting another wm with my username works perfectly.
slightly confused
strigyskow

I can confirm there is something in gnome preventing from restarting x with ctrl-alt-backspace. I have both don't zap set in xorg.conf as adjusted my fdi keyboard file. I know that the configuration works because i can use ctrl-alt-backspace in the gdm login screen and xmonad, but in gnome. Executing setxkbmap after gnome has been started (more or less) solves the problem.

[SOLVED] Ctrl+Alt+Backspace Wont restart X

It just does nothing, is it disabled somewhere somehow? I used to work before, broke from upgrade or something?
Last edited by degmic71 (2009-04-15 13:45:54)

man xorg
Ctrl+Alt+Backspace
Immediately kills the server -- no questions asked. This is
disabled by default. It can be enabled with the -retro command
line flag or by setting the DontZap xorg.conf(5) file option to
a FALSE value.
add this to you xorg.conf
Section "serverFlags"
Option "DontZap" "false"
EndSection

Getting SLiM to restart after ctrl-alt-backspace

I recently installed SLiM (Simple Login Manager) and it's quite nice. My only problem with it is that if I do a ctrl-alt-backspace at the log-in prompt it will drop me into text-mode log-in without restarting X or SLiM.
Can it be configured to respawn if X is killed?
i have the following in my inittab:
# /etc/inittab
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
x:5:respawn:/usr/bin/slim >& /dev/null
# End of file

Same problem here.
I have this problem since 2007-10-14 and can't find a solution.
There was a huge update amongst others "xkeyboard-config (0.9-2 -> 1.0-1)", and I think there is the problem.
I use slim too, but I don't believe slim is the problem.
EDIT:
After a try ctrl-alt-backspace, my slim.log says this:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux arch 2.6.23-ARCH #1 SMP PREEMPT Sat Oct 27 09:04:14 UTC 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 30 21:44:55 2007
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
/usr/bin/xauth: creating new authority file /home/jean/.Xauthority
Warning: Only changing the first 14 of 20 buttons.
** Message: This build doesn't include support for XF86Misc extension
** Message: Querying Xkb extension
** Message: Xkb extension found
** Message: Querying Xkb extension
** Message: Xkb extension found
Conky: desktop window (1000003) is subwindow of root window (1a5)
Conky: window type - override
Conky: drawing to created window (1800001)
Conky: drawing to double buffer
(xfwm4:8279): libxfcegui4-WARNING **: ICE I/O Error
(xfwm4:8279): libxfcegui4-WARNING **: Disconnected from session manager.
xfce-mcs-manager: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
xfwm4: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
xfdesktop: Fatal IO error 104 (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) on X server :0.0.
xfce4-panel: Fatal IO error 4 (Unterbrechung während des Betriebssystemaufrufs) on X server :0.0.
terminal: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 3, should be 1; fixing.
/usr/bin/xauth: creating new authority file /var/run/slim.auth
Jean-Paul
Last edited by jean-paul (2007-10-31 22:17:14)

Ctrl+alt+backspace doesn't work anymore after system update

After a recent system update (xorg got updated among other packages), ctrl+alt+backspace doesn't restart gdm anymore.
Before you say it, I have the following in my /etc/X11/xorg.conf
Section "ServerFlags"
Option "DontZap" "false"
EndSection
Here is the relevant portion from my /var/log/pacman.log and as you can see, xorg-server did get updated.
[2009-05-29 18:37] starting full system upgrade
[2009-05-29 18:39] upgraded dhcpcd (5.0.2-1 -> 5.0.4-1)
[2009-05-29 18:39] NOTE
[2009-05-29 18:39] ----
[2009-05-29 18:39] Add your user to group 'camera' to use camera devices.
[2009-05-29 18:39] upgraded libgphoto2 (2.4.5-1 -> 2.4.6-1)
[2009-05-29 18:39] upgraded gphoto2 (2.4.4-1 -> 2.4.5-1)
[2009-05-29 18:39] upgraded gtkam (0.1.15-1 -> 0.1.16.1-1)
[2009-05-29 18:39] upgraded lib32-glibc (2.9-4 -> 2.10.1-2)
[2009-05-29 18:39] upgraded lib32-alsa-lib (1.0.19-1 -> 1.0.20-1)
[2009-05-29 18:39] upgraded lib32-gcc-libs (4.3.3-1 -> 4.4.0-2)
[2009-05-29 18:39] upgraded lib32-libdrm (2.4.9-1 -> 2.4.11-1)
[2009-05-29 18:39] upgraded lib32-libgl (7.4.1-1 -> 7.4.2-2)
[2009-05-29 18:39] upgraded lib32-mesa (7.4.1-1 -> 7.4.2-1)
[2009-05-29 18:39] upgraded libdrm (2.4.11-1 -> 2.4.11-2)
[2009-05-29 18:39] upgraded live-media (2009.02.23-1 -> 2009.04.20-1)
[2009-05-29 18:39] upgraded qt (4.5.1-2 -> 4.5.1-3)
[2009-05-29 18:39] upgraded phonon (4.3.1-1 -> 4.3.1-2)
[2009-05-29 18:39] upgraded pygobject (2.16.1-1 -> 2.18.0-1)
[2009-05-29 18:39] upgraded python-numpy (1.3.0-1 -> 1.3.0-2)
[2009-05-29 18:39] upgraded qt3 (3.3.8-10 -> 3.3.8-11)
[2009-05-29 18:39] upgraded whois (4.7.33-1 -> 4.7.33-2)
[2009-05-29 18:39] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
[2009-05-29 18:39] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-1)

Check out http://bbs.archlinux.org/viewtopic.php?id=73064

R60 shouts at me when pressing [ctrl+alt+backspace] in openSUSE

Whenever I try to restart the X server in openSUSE 11.3, as I like to do with the [ctrl+alt+backspace]-shortcut, I just get a loud *beep* from the onboard speaker and nothing happens. I tried booting into Windows and pressing the key combination, same thing.
Help?

Are you getting the same beep from Windows?Or is it only OpenSuse?
Every time I restart the system my 3000H system also gives me a loud beep from the board.Your X server might not be supported by the GPU which is causing the system to give out the beep sound..
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

CTRL + ALT + BACKSPACE or F1, F2, etc lock

I've read many posts from this forum about this subject, tried every suggestion, but the things remains the same:
After X has started, the combination of keys ctrl + alt +F1 or any other vc combination gives me a black screen, idem for ctrl + alt + backspace. Even exit from the window manager (fluxbox, in this case) does the same.
I've a Phitronics AM2N1K-M motherboard, chipset Nvidia MCP61v (nforce 4) , vga onboard GeForcr 6100. An AMD 64 3200+ processor and 512Mb ddr2 RAM. I'm using Arch 32 , because i'm waiting for the TI market wakes for the 64 bit world.
I've tried many xorg configurations, in all of them the driver used is "nvidia" , the 3d reosurces works, the windowm manager starts, (using xinitrc), the maximum resolution is 1024x768, (maximum supported by the monitor). The only problem is described above.
Any help is welcome.

Yes, i could switch between them, with no X . I used the same xorg.conf in the distributions above, and in the new Debian etch, in the same hardware, and it works. Maybe i've missed some file in the arch system installation, I don't know, because i've removed Arch.
I'm a big fan of Arch. I came from Slackware, and I love the Arch way. I've tried Arch64, but get tired of the 32 bit chroot solution. I'd really like to go back to Arch, but my projects (at work and home) make me use the (bleargh) Fedora64, the easyest solution to everything but java-plugin.
But I digress.I will give Arch a try in the same machine again at some point of my projects, but time is crucial for me now. Thank you for you help.

[Solved]No X, No Ctrl+Alt+Backspace, cant get to console...HELP!

I did a new install and went for the ext4 option, I installed everything I usually do but went with nvidia-xcofig rather than the usual Xorg -configure, now having set everything up all I get is a blank screen, I cant ctrl alt backspace to get to console and mt laptop just reboots after about 10 seconds or so.
I have Mint installed on another partition hoping that I could get into rc.conf and ! out gdm but ext4 isn't supported! lol
What do I do, I'm well and truely stumped!
I left arch for 4 days as I got tired of things breaking but had to come back, I miss my arch, well until this peach of a problem came up
Thanks
Last edited by Andy Mack (2009-03-10 15:39:08)

What would I need to edit rc.conf for?
to comment out gdm!!
I hope you have installed hal and read the news about disabling autoadddevices, enabling ctrl alt backspace with DontZap etc

Ctrl-Alt-Backspace issue with Fluxbox and SLiM

Hi folks :)
I'm pretty new to Arch, had a few attempts at installing it in the past but wasn't quite ready and so decided to expand my Linux knowledge a little more, first. Well, I've done that and now I'm having another go, and things are going quite well. However, I have one minor problem. In ~/.xinitrc, I have the line 'exec startfluxbox' to start Fluxbox and do everything that is contained within the ever-so-handy 'startfluxbox' file. That works perfectly. However, if I restart X by pressing the Ctrl-Alt-Backspace combination, I'm sent to the command line rather than SLiM. However, if I replace 'exec startfluxbox' with 'exec fluxbox' it works fine and brings me straight back to the SLiM login window. Of course, I then can't make use of the 'startfluxbox' file.
Could anybody shed some light on why this might be happening? I know it's more than likely going to be something simple that I've missed, but any help would be appreciated. :)
Thanks,
Joel.

And using fluxbox instead of startfluxbox still works? Strange.
I had the same problem as well with slim and Xfce (sometimes SLiM would respawn after some minutes if I logged out normally), and ended up just giving up on SLiM.
I'll give it a try with my openbox-setup (should be similar enough to the fluxbox way).
What happens if you log out of your session instead of killing the xserver?
You could always give some other login manager a try, kdm/gdm or qingy if you want things lite.
[edit: I tried it, SLiM works fine with openbox-session. It needs rather a lot of time to start up after booting but that might have something to do with me having backgrounded daemons rather indiscriminately.
Probably a stupid idea, but have you tried waiting a bit? As I've mentioned, sometimes SLiM took a few minutes to respawn due to some bug or other.
Last edited by lastchancetosee (2009-05-16 20:51:31)

Kill Session with Ctrl+Alt+backspace+backspace, doens't kill but disconnect

I've got 4 Oracle Solaris servers with SRS 5.1.2 installed. The servers are configured in failover configured in SRS. When I try to kill (terminate) a session with Ctrl+Alt+backspace+backspace the session will not be terminate. Instead of killing it will be in the state of disconnected on the Sun Ray Administration. I can only terminate the session if I'm on the Sun Ray Administration by selecting the session and click terminate. Does anybody has the same issue, if the sun ray servers are configured as failover?

A simple google for "terminate:ctrl_alt_bksp" yields https://bbs.archlinux.org/viewtopic.php?pid=602885 as the first hit.
You could also use an xorg configuration file as is mentioned in the link you posted (a bit higher than the part you linked) and there is an entry for "XkbOptions".

SRSS2.0 Sunray150 hangs at 26D after ctrl-alt-backspace-backspace

After ctrl-alt-backspace-backspace the Sunray terminal (DTU) resets and intermittently hangs at 26D.
Ctrl+moon has no effect. The only way to rectify is to remove the session, using utsession -k -t <token>.
Software; SRSS2.0, Solaris 9 04/04, Sparc.

If the sessions being killed are normal desktop login sessions then the dtlogin daemon should start a new X server for the session. Make sure that you have the most recent dtlogin patch installed. For Solaris 9 on SPARC that's patch 112807-17.
If the sessions being killed are some other kind of session, perhaps CAM or NSCM,
then make sure that you have the most recent SRSS patches installed or, even better,
upgrade to a newer release of SRSS. 2.0 is old; 3.1 is current.
OttoM.

Restart X (ctrl-alt-backspace) doesn't respond

Subject says it all. Under my old distro, ctrl-alt-backspace would restart X. This doesn't seem to be the case w/ Arch. How can I enable this behavior?
Thanks!

darthaxul wrote:
xorg claims that there are newer ways of closing the X server.
If im on openbox now. what do i put in the logout event?
<item label="logout">
<action name="Execute">
<command>kill `ps -e | grep startx| awk '{print $1}'`</command>
<startupnotify>
<enabled>yes</enabled>
</startupnotify>
</action>
</item>
i havent tried this yet but is that something anyone else is using?
I guess you could bind that output to a key and use it in place of Ctl+Alt+Bksp.

Change Ctrl+Alt+Backspace to something else

Hi
Is there any way to change the Ctrl+Alt+Backspace key combination in X to something else, e.g. Ctrl+Alt+Windows+Backspace?
Note that I don't want to disable the "zapping" behavior by changing DontZap, but simply change the combination.

This _looks_ like it, but doesn't really make a lot of sense:
xmodmap -pke | grep BackSpace
keycode 22 = BackSpace Terminate_Server BackSpace Terminate_Server BackSpace Terminate_Server
The first keysym is used when no modifier key is pressed in conjunction with this key, the second with Shift, the third when the Mode_switch key is used with this key and the fourth when both the Mode_switch and Shift keys are used. The last four are not used in any major X server implementation.

X not terminated by ctrl+alt+backspace

Whenever I hit ctrl+alt+backspace, it does not kill X. I have the serverflag DontZap set to false, but it still won't work.

scv5 wrote:
i thought you could put this in your xorg.conf and it would work? (not able to test right now)
Section "ServerFlags"
Option "DontZap" "false"
EndSection
In addition you need to add either:
<merge key="input.xkb.options" type="string">terminate:ctrl_alt_bksp</merge>
to the keyboard fdi file or run
setxkbmap -option terminate:ctrl_alt_bksp
as is indicated in the wiki.

Ctrl+alt+backspace does not kill X

I ran
# nvidia-xconfig --logo-path=
to set the logo that X starts with, but now I cannot kill X with the normal ctrl+alt+backspace.

The point of users never reading stickies is just as valid . It is a good suggestion, but it will get lost in the myriad of stickies anyway - stickies that, by experience, everyone overlooks.
Those who know where to look (and search) will find it - stickied or not. As said: there's coverage in the Arch wiki, on the BBS, and even on the world wide web.
If you have SysRq enabled, you can always do AltGr + SysRq + K to restart X if needed.
http://en.wikipedia.org/wiki/Magic_SysRq_key
We're not stickying it, the information is all over the place. There's no point in discussing this.

Latest xkeyboard-config prevents ctrl-alt-backspace from killing X

Similar Messages

Maybe you are looking for