| 1 |
On 2/6/09, Willie Wong <wwong@×××××××××.edu> wrote: |
| 2 |
> I lost your original mail, so sorry if this is not threaded properly. |
| 3 |
|
| 4 |
Ok, I have to be sorry about my slow replies as well. My excuse is |
| 5 |
that I'm so used to pressing ctrl+c, ctrl+v etc when composing mails |
| 6 |
that I've already killed X twice just while trying to type in this |
| 7 |
reply (not to mention the earlier ones where I was trying to copy and |
| 8 |
paste outputs from the terminal windows ...). |
| 9 |
|
| 10 |
I must have killed X more than 50 times during the last 24 hours, |
| 11 |
sometimes on purpose while trying out things, sometimes accidentally |
| 12 |
and then ending up cursing out loud. :) |
| 13 |
|
| 14 |
> Question: does the bug manifest itself only in KDE apps or in others? |
| 15 |
> |
| 16 |
> Ctrl+c should also copy to clipboard in, say, firefox, if you have it |
| 17 |
> installed. Does it do the same thing? If yes: do you have another WM |
| 18 |
> installed and can you try running firefox under the other WM to see if |
| 19 |
> it behaves similarly? This should help figure out whether it is a KDE |
| 20 |
> issue or an X issue. |
| 21 |
|
| 22 |
It happens under seamonkey and firefox as well. And it's not limited |
| 23 |
to ctrl+c, also ctrl+v kills/crashes X (sometimes) and some other |
| 24 |
ctrl+something combos as well, but they're not so usual keypresses by |
| 25 |
me, so I cannot say for sure how often they would cause a crash. |
| 26 |
|
| 27 |
But that WM was a good idea, I tried with a bare(?) Xsession as the |
| 28 |
XSESSION in rc.conf. It gave just a plain terminal from which I |
| 29 |
started firefox and seamonkey. Result: ctrl+c while trying to |
| 30 |
copy-paste text in a form field on a web page results in X killing |
| 31 |
itself as well. |
| 32 |
|
| 33 |
So it would really seem to be about xorg-server 1.5.3 and that darned |
| 34 |
evdev 2.1.1 which already gave nearly me two evenings without a |
| 35 |
keyboard and a mouse due to configuration issues. I'll probably |
| 36 |
finally get to downgrade it over next night. |
| 37 |
|
| 38 |
Also the other, earlier replies had good ideas, like the kxkb. Just |
| 39 |
clicking on the KDE keyboard layout manager's country flags and |
| 40 |
switching the keyboard from our local gibberish ("fi") to "us" and |
| 41 |
back (and then running extra setxkbmap by checking the xkb settings |
| 42 |
"CTRL in lower left corner"?) had me smiling for a while -- I could |
| 43 |
pound on ctrl+c with impunity in all programs. But then I restarted X |
| 44 |
and retried, and the trick no longer seemed to work, not sure why. |
| 45 |
|
| 46 |
> If you open an xterm, and hit Ctrl+c, does it reboot X (a long shot, |
| 47 |
> but if it does happens, it means something else is grabbing the event |
| 48 |
> and passing it up before the xterm sees it and passes it to the shell |
| 49 |
> in it)? |
| 50 |
|
| 51 |
Ctrl+c in xterm/gterm/kterm == X gone, just like in all other programs. |
| 52 |
|
| 53 |
> Also, what is in your ~/.xinitrc? |
| 54 |
|
| 55 |
I don't have the file in my ~, only the system file in |
| 56 |
/etc/X11/xinit/xinitrc -- not modified by me. |
| 57 |
|
| 58 |
But anyway, since it seems to be focused on xorg-server and/or evdev, |
| 59 |
I'll do the reasonable thing: downgrade back to 1.5.2(or even lower?) |
| 60 |
and normal keyboard and mouse drivers. |
| 61 |
|
| 62 |
Maybe the new xorg-server is only supposed to work reliably on a fully |
| 63 |
~amd64? This box has mostly stable amd64 and only select packages, |
| 64 |
mostly end-used apps like seamonkey, OOo and firefox are allowed to be |
| 65 |
~amd64 along with some of their more obscure requirements (like |
| 66 |
xulrunner). |
| 67 |
|
| 68 |
Anyway, thanks for everyone for the helpful comments and ideas! I'll |
| 69 |
post a short reply about the success with the downgrade hopefully |
| 70 |
tomorrow and then try to leave this for now. |
| 71 |
|
| 72 |
-- |
| 73 |
Arttu V. |
Archives