[Gnome] CTRL+ALT+BKSP doesn't restart Xorg

davcri · 2017-09-19 14:18:51

Problem: CTRL+ALT+BACKSPACE doesn't restart Xorg on my fresh installed Arch Linux Gnome
Description: My /etc/X11/xorg.conf.d/99-killX.conf seems configured in the right way, according to "Terminating Xorg with Ctrl+Alt+Backspace":

Section "ServerFlags"
   Option "DontZap" "false"
EndSection
 
Section "InputClass"
   Identifier      "Keyboard Defaults"
   MatchIsKeyboard   "yes"
   Option         "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

Question:This file seems to not be parsed during the boot or user login. What I'm doing wrong ?

A workaround is this:

setxkbmap -option terminate:ctrl_alt_bksp

Last edited by davcri (2017-09-20 14:17:46)

HalosGhost · 2017-09-19 15:12:39

Can you please post your Xorg.<ttynumber>.log file for a session where this config file appears to have not been read? (please use code tags)

I've tended more towards using setxkbmap in my .xinitrc these days, but I recognize that may not be the preferred option for everyone.

All the best,

-HG

davcri · 2017-09-19 17:21:03

Sure!
Relevant lines of the log:

[     4.952] (II) config/udev: Adding input device Logitech G510 Gaming Keyboard (/dev/input/event0)
[     4.952] (**) Logitech G510 Gaming Keyboard: Applying InputClass "libinput keyboard catchall"
[     4.952] (**) Logitech G510 Gaming Keyboard: Applying InputClass "system-keyboard"
[     4.952] (**) Logitech G510 Gaming Keyboard: Applying InputClass "Keyboard Defaults"
[     4.952] (II) Using input driver 'libinput' for 'Logitech G510 Gaming Keyboard'
[     4.952] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 41 paused 0
[     4.952] (**) Logitech G510 Gaming Keyboard: always reports core events
[     4.952] (**) Option "Device" "/dev/input/event0"
[     4.952] (**) Option "_source" "server/udev"
[     4.953] (II) event0  - (II) Logitech G510 Gaming Keyboard: (II) is tagged by udev as: Keyboard
[     4.953] (II) event0  - (II) Logitech G510 Gaming Keyboard: (II) device is a keyboard
[     4.953] (II) event0  - (II) Logitech G510 Gaming Keyboard: (II) device removed
[     4.953] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:046D:C22D.0001/input/input2/event0"
[     4.953] (II) XINPUT: Adding extended input device "Logitech G510 Gaming Keyboard" (type: KEYBOARD, id 8)
[     4.953] (**) Option "xkb_layout" "it"
[     4.953] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[     4.953] (II) event0  - (II) Logitech G510 Gaming Keyboard: (II) is tagged by udev as: Keyboard
[     4.953] (II) event0  - (II) Logitech G510 Gaming Keyboard: (II) device is a keyboard
[     4.953] (II) config/udev: Adding input device Logitech G510 Gaming Keyboard (/dev/input/event1)
[     4.953] (**) Logitech G510 Gaming Keyboard: Applying InputClass "libinput keyboard catchall"
[     4.953] (**) Logitech G510 Gaming Keyboard: Applying InputClass "system-keyboard"
[     4.953] (**) Logitech G510 Gaming Keyboard: Applying InputClass "Keyboard Defaults"
[     4.953] (II) Using input driver 'libinput' for 'Logitech G510 Gaming Keyboard'
[     4.954] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 42 paused 0
[     4.954] (**) Logitech G510 Gaming Keyboard: always reports core events
[     4.954] (**) Option "Device" "/dev/input/event1"
[     4.954] (**) Option "_source" "server/udev"
[     4.954] (II) event1  - (II) Logitech G510 Gaming Keyboard: (II) is tagged by udev as: Keyboard
[     4.954] (II) event1  - (II) Logitech G510 Gaming Keyboard: (II) device is a keyboard
[     4.954] (II) event1  - (II) Logitech G510 Gaming Keyboard: (II) device removed
[     4.954] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:046D:C22D.0002/input/input3/event1"
[     4.954] (II) XINPUT: Adding extended input device "Logitech G510 Gaming Keyboard" (type: KEYBOARD, id 9)
[     4.954] (**) Option "xkb_layout" "it"
[     4.954] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[     4.954] (II) event1  - (II) Logitech G510 Gaming Keyboard: (II) is tagged by udev as: Keyboard
[     4.955] (II) event1  - (II) Logitech G510 Gaming Keyboard: (II) device is a keyboard

So the file seems to be parsed because of:
[ 4.953] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"

The problem is that it doesn't work

seth · 2017-09-20 07:09:33

what's the output of

setxkbmap -print -query

when it does *not* work?
How do you log in? GDM? Wayland or xorg as well?

Also you seem to have more keyboard configuration files (at least one determining the layout as italian)?
Please paste all of them.

davcri · 2017-09-20 07:32:39

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+it+it:2+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
rules:      evdev
model:      pc105
layout:     it,it
variant:    ,

It doens't work when I log in. To enable this option I have to manually issue "setxkbmap -option terminate:ctrl_alt_bksp", then the output of the query becomes:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+it+it:2+inet(evdev)+terminate(ctrl_alt_bksp)"	};
	xkb_geometry  { include "pc(pc105)"	};
};
rules:      evdev
model:      pc105
layout:     it,it
variant:    ,
options:    terminate:ctrl_alt_bksp

I'm logging in the Gnome X Session with GDM. Wayland session is not enabled because I'm (sadly) using the proprietary Nvidia drivers (GTX970).

seth · 2017-09-20 07:45:34

layout:     it,it

This looks nonsense and means either the session or some additional configlet messes the configuration.
Does zapping work in GDM?

davcri · 2017-09-20 12:30:17

What is zapping ?

seth · 2017-09-20 13:15:57

man 1 Xorg | grep -i zap

;-)

ctrl+alt+backspace "zaps" the server.

davcri · 2017-09-20 14:21:29

Oh nice
However it doesn't work neither in GDM.

seth · 2017-09-20 14:55:50

So he culprit is either GDM or some xorg configlet.
=> Try startx and if this still happens, produce your other keybord configlets for Xorg.

davcri · 2017-09-30 08:07:05

It seems that Gnome/GDM doesn't source .profile, .xprofile, .xinitrc ([reddit], [askubuntu ]).

seth · 2017-09-30 11:41:42

That's unrelated to any /etc/X11/xorg.conf.d/*, though.
Did you try to rule out GDM?

Arch Linux

#1 2017-09-19 14:18:51

[Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#2 2017-09-19 15:12:39

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#3 2017-09-19 17:21:03

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#4 2017-09-20 07:09:33

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#5 2017-09-20 07:32:39

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#6 2017-09-20 07:45:34

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#7 2017-09-20 12:30:17

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#8 2017-09-20 13:15:57

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#9 2017-09-20 14:21:29

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#10 2017-09-20 14:55:50

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#11 2017-09-30 08:07:05

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

#12 2017-09-30 11:41:42

Re: [Gnome] CTRL+ALT+BKSP doesn't restart Xorg

Board footer