Mysterious key combination keeps restarting X
 

I'm using Enlightenment on SUSE 9.1. I've searched through my keybindings.cfg file to no avail, so I'm hoping someone here will recognize what I'm doing, so I can stop doing it :)
Some sort of key combination that I'm hitting restarts X. It's happened twice in the last few minutes, once while I (think) I was pressing RSHIFT and had either hit or just hit "1". The second time was shift again, and I think I was near "5" (could've been making a typo, though, so I can't swear to what I actually hit). There may or may not have been some other keys involved, I was in the middle typing code and am not sure precisely where I was :-[

/var/log/messages has this to say:
Jul 2 21:20:30 linux kdm[4573]: X server for display :0 terminated unexpectedly

which a) isn't news to me, I was using it when it "terminated"!, and b) is less than verbose. Anyone know what, other than ctrl+alt+backspace, will restart X?

Thanks!

*sigh* nevermind. It happened again and made me lose about 5 paragraphs of an essay, at which point I started screwing around with keys 'til I figured it out.

Shift + backspace. Does it every time. Doesn't matter which shift, either.

So now the question becomes, how in blazes do I disable that? It's an absurd key combination, waaaay to easy to hit accidentally, especially when one is what could be described as a non-trained typist. It's definitely not in keybindings.cfg.

Could it be that somehow your system does not make the distinction between shift+backspace (supposed to be harmless) and ctrl+alt+backspace (supposed to restart X)?

There is a DontZap option in the X configuration...

I'm not the only one; looks like this may be a suse issue. I'll try the DontZap method for now, thanks!

Did you try this? http://lists.suse.com/archive/suse-l...-Sep/1733.html

Even if the above is not the right setting for you, the cause of your problem seems to be a wrong keyboard model specification.

Nope. I'd seen that before, but didn't try it because my keyboard is set correctly in xorg.conf:

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

A) How can one know for sure?
B) Try xev to see what is going on when you press shift and/or backspace.

I have a standard vanilla 101-key keyboard, no extra buttons, dials or anything not grey, square and sporting an ascii character. xorg.conf has Option "XkbModel" "pc101" ...what other options are there?

I'll try xev...is that something that one runs after one cuts out of X or before?

xev is a standard program for X. It will dump to stdout all the events that happen in its window. (this means an event for every one pixel mouse move, every key press and every key release)

Heh, guess what? Looks like my upgrading to xorg fixed a whole host of problems, this one included. So everything's good :)
Thanks!

"The best Windows accelerator is that which works at 9.81m/s^2"

<GRIN!>

True, but only the Win media -- it's not the *computer's* fault, it's the fualt of whomever put Win on it in the first place.

Besides, doing only the media makes asmaller hole, more cheaply patched!

And yes, xorg seems to have gotten itself together in the last few months, thank $DEITY.

Heheheh...I always think of that quote in conjunction with the gravity demonstration in Sideways Stories from Wayside School :D

In all honestly, though, I have to admit that Win2K wasn't all that bad...it at least had the advantage of being straightforward, assumed a degree of knowledge from its users, and wasn't all bubbly and round (as if its users would accidentally fall and hurt themselves on all the sharp edges...*sigh*). And it only bluescreens once a month or so (as opposed to XP, which will do so on command)! Cedega's still iffy for me, so I preserve a Win2K box to get my gaming fixes.

I think it's pretty funny that this post is #666 for me }:-> That's what I get for saying something nice about Windows!

Alternative solution to Shift-Backspace zapping X

Many people can run "xmodmap /usr/share/xmodmap/xmodmap.us" to fix the shift-backspace X resetting problem. But I my case it made other things worse/break or still resetted my X... so I found an alternative:

If you do this:
It should show:
But if there is something about zapping X beteen the parentheses, you should change it back to BackSpace:
Put this line into ~/.Xmodmap or .kde/Autostart/mystartups (and make the latter one executable) to make it persistent (for every boot).

This saved me from smashing my keyboard into the screen! I now have no problems at all with Dapper...

--
Erik de Bruijn
Budgetdedicated.com

Alternative solution to Shift-Backspace zapping X

Many people can run "xmodmap /usr/share/xmodmap/xmodmap.us" to fix the shift-backspace X resetting problem. But I my case it made other things worse/break or still resetted my X... so I found an alternative:

If you do this:
It should show:
But if there is something about zapping X beteen the parentheses, you should change it back to BackSpace:
Put this line into ~/.Xmodmap or .kde/Autostart/mystartups (and make the latter one executable) to make it persistent (for every boot).

This saved me from smashing my keyboard into the screen! I now have no problems at all with Dapper...

--
Erik de Bruijn
Budgetdedicated.com