Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
*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 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?
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)
Besides, doing only the media makes a smaller hole, more cheaply patched!
Heheheh...I always think of that quote in conjunction with the gravity demonstration in Sideways Stories from Wayside School
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!
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:
Code:
# xmodmap -pp -pk | grep BackSpace
It should show:
Code:
22 0xff08 (BackSpace) 0xff08 (BackSpace)
But if there is something about zapping X beteen the parentheses, you should change it back to BackSpace:
Code:
# xmodmap -e "keycode 22 = BackSpace 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...
Quote:
Doing "xmodmap /usr/share/xmodmap/xmodmap.us" fixed the Shift|Backspace bug, but now my F12 hotkey and Ctrl+Alt+Workspace number hotkey doesn't work. Anyone else? That sucks!
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:
Code:
# xmodmap -pp -pk | grep BackSpace
It should show:
Code:
22 0xff08 (BackSpace) 0xff08 (BackSpace)
But if there is something about zapping X beteen the parentheses, you should change it back to BackSpace:
Code:
# xmodmap -e "keycode 22 = BackSpace 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...
Quote:
Doing "xmodmap /usr/share/xmodmap/xmodmap.us" fixed the Shift|Backspace bug, but now my F12 hotkey and Ctrl+Alt+Workspace number hotkey doesn't work. Anyone else? That sucks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.