|
Bugzilla – Full Text Bug Listing |
| Summary: | Even with DontZap off, Ctrl+Alt+Backspace doesn't kill the X server | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Jaroslaw Zachwieja <grok> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | badshah400, koenig, novellbmw, qa-bugs |
| Version: | Milestone 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
HWinfo log
rpm -qa log aytoyast profile used to install the system |
||
Any update on this? Hmm. Works for me. Please note our default here:
Option "ZapWarning" "boolean"
This warns the user loudly when the Ctrl+Alt+Backspace sequence
is pressed for the first time but still terminates the Xorg
server when this key-sequence is pressed again shortly after.
Default: on.
Reopening. Stefan, Please note that I'm not complaining about the ZapWarning. I don't mind that behaviour. I'm reporting the Zap not working at all, regardless if it's with warning or not. I thought I was clear about it when describing steps to reproduce (see Description, Step 3). Unless I'm missing something here... But what can I do, if I can't reproduce that issue? I'm already using latest Xserver from X11:Xorg ... Gotcha. Misunderstanding sorted. I'll retest. can reproduce this behavior: I installed in VirtualBox-3.1.3 openSUSE-11.3-MS2 from NET choosing LXDE (has xorg-7.4-67.7) To zap in VirtualBox, one has to hit right-Ctrl+Backspace (tested on other Linux) Regardless of ZapWarning and DontZap options, nothing happens when hitting the zap key several times in short succession. init 3 and rcxdm stop work now (but did not on first boot) Xorg.0.log is not writing anything about it. Are there any other logs that I could check? Please open a seperate bugreport for Virtualbox. This issue is in no part related to VirtualBox as I can now also reproduce it on qemu-kvm (using "sendkey ctrl-alt-backspace") and original poster could reproduce it on real hardware, so I have no doubt that I could do the same. So if I opened another "Zapping X11 doesnt work"-report it would have to be considered a DUPLICATE of this one. Am I missing something that makes opening another report worthwhile? I believe I made it rather clear that I could not reproduce that issue on real hardware. Virtualbox/qemu X support is handled by a different developer, so this person might be lucky and can reproduce the issue. So please be so kind and open a seperate bugreport. Thanks. I have reproduced the issue again on real hardware using Milestone3. Created attachment 349442 [details]
HWinfo log
Created attachment 349443 [details]
rpm -qa log
This has been installed from LiveCD (KDE) Milestone3
(In reply to comment #12) > This has been installed from LiveCD (KDE) Milestone3 Sorry, wrong system, ignore that sentence (attachment concerns the actual system). Created attachment 349445 [details]
aytoyast profile used to install the system
The system is a Dell OptiPlex 780.
Looks it doesn't help to close a bug as worksforme. It gets reopened again and again anyway. Ignoring it for the time being. Stefan, Have you actually tried reproducing it using the attached autoyast profile? Can you verify this still happening for milestone 3 or does it work for your own branch of X11? Would you be so kind and add QA as CC for this? I believe this needs to be addressed, not ignored. Regards, -- JZ As you wish. Problem still exists in Milestone 4. I can reproduce that issue on a freshly installed machine with Milestone 4. Even Section "ServerFlags" Option "DontZap" "off" Option "ZapWarning" "on" EndSection doesn't help. On the other machine I keep udpated on Factory I can reproduce the issue only when starting a second Xserver on top of a running Xserver. If I start a second Xserver from Linux console Ctrl-Alt-BS works fine. Ctrl-Alt-BS works also for the first Xserver. Weird. Just as a hint for myself. https://wiki.ubuntu.com/X/Config/DontZap enable Zapping: setxkbmap -option terminate:ctrl_alt_bksp disable Zapping: setxkbmap -option "" Adding Option "XkbOptions" "terminate:ctrl_alt_bksp" to keyboard snippet in xorg.conf.d appears to fix the issue. Fixed in xorg-x11 now: ------------------------------------------------------------------- Wed Apr 7 14:40:22 CEST 2010 - sndirsch@suse.de - etc/X11/xdm/keytable: * make Zapping possible again; still beeps first (bnc #576481) Thanks! *** Bug 604018 has been marked as a duplicate of this bug. *** (In reply to comment #24) > *** Bug 604018 has been marked as a duplicate of this bug. *** etc/X11/xdm/keytable is the wrong place to fix this! * does not work with explicit xorg.conf (at least I guess so -- and yes, sometimes it's still needed e.g. for non-standard multi screen setups) * does not work for plain Xserver or startup using xinit (not using xdm) * does not fix the inconsistency in keytables between "de" (zapping works) and "us" (zapping broken). see bug #604018 for details why you can't reproduce the problem with "de" keyboard settings... please fix the xkb files and forget about such workarounds, please. thanks! oops, forgot to "REOPEN" this bug.... Harald, as I said I'm not aware of a better fix. Feel free to report upstream or provide a fix. Aren't you part of the openSUSE community? ;-) Still does not work for me with RC1. I mean, if I press Ctrl+Alt+Backspace twice I still cannot kill X. Is Zapping turned off by default? If so how to turn it on since there is no xorg.conf file anymore? Thanks ZapWarning is still our default. Please attach /etc/X11/xorg.conf.d/90-keytable.conf This is the content of the requested file:- Section "InputClass" Identifier "LocalKeyboard" MatchIsKeyboard "on" Option "XkbRules" "base" Option "XkbModel" "evdev" Option "XkbLayout" "us" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection Looks good. I guess you still have a xorg.conf file in place, which overwrites that setting. (In reply to comment #31) > Looks good. I guess you still have a xorg.conf file in place, which overwrites > that setting. No, I don't think so >cat /etc/X11/xorg.conf cat: /etc/X11/xorg.conf: No such file or directory This worked for me now on a fresh install of RC1 on VirtualBox. Atri: is this a fresh install or an updated older system? Maybe some other leftover/cache file? try grep Input /etc/X11 -R Well, you could see in /var/log/Xorg.0.log, whether there is still any xorg.conf in place and being read. The following patch should fix the issue. --- usr/share/X11/xkb/rules/evdev.orig 2010-06-19 13:48:56.059291636 +0200 +++ usr/share/X11/xkb/rules/evdev 2010-06-19 13:52:04.338436260 +0200 @@ -899,8 +899,8 @@ us intl-unicode = +extras/us(intl-unicode):4 ! model = symbols - $evdevkbds = +inet(evdev)+inet(%m) - * = +inet(evdev) + $evdevkbds = +inet(evdev)+inet(%m)+terminate(ctrl_alt_bksp) + * = +inet(evdev)+terminate(ctrl_alt_bksp) ! model layout = compat pc98 nec_vndr/jp = pc98(basic) Now hopefully fixed for real (SR #41767/41768).
41767 State:new By:sndirsch When:2010-06-19T14:27:48
submit: X11:XOrg/xkeyboard-config -> openSUSE:Factory
Descr: - xkeyboard-config.ctrl_alt_bksp.patch
* enable zapping by default (still protected by ZapWarning)
(bnc #576481)
41768 State:new By:sndirsch When:2010-06-19T14:39:59
submit: X11:XOrg/xorg-x11 -> openSUSE:Factory
Descr: - /etc/X11/xdm/keytable:
* model/rules is always "evdev", not matter what you write to
keyboard section
* option terminate:ctrl_alt_bksp no longer required; now fixed
for real in xkeyboard-config
|
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.1) Gecko/20090714 SUSE/3.5.1-1.1 Firefox/3.5.1 # cat /etc/X11/xorg.conf Section "ServerFlags" Option "DontZap" "off" EndSection # grep DontZap /var/log/Xorg.0.log (**) Option "DontZap" "off" Ctrl+Alt+Backspace doesn't work (even twice, three or four times). Reproducible: Always Steps to Reproduce: 1. Add above to /etc/X11/xorg.conf 2. restart xdm 3. press C+A+B twice in rapid succession on the login screen. Actual Results: Nothing. Expected Results: X Server should die and get restarted by xdm. Other Ctrl+Alt combinations work: Ctrl+Alt+Insert, Ctrl+Alt+Delete. I understand that you're trying to shield the lemmings from shooting themselves in the foot and introduce safe defaults, but this is after I've explicitly enabled the feature.