| View previous topic :: View next topic |
| Author |
Message |
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
 Posted: Sun Apr 04, 2004 3:36 pm Post subject: KDE ate my "C" key! |
 |
|
i am experiencing a strange loss of my "C" key when i load up KDE. i had just done an an etc-update, and the disappearing trick began after i rebooted, so i think (but am not certain) that the two things may be connected. i can use the "C" key at the regular console without a problem, and even at the KDE login manager screen, but when i login to KDE, it mysteriously disappears: pressing the "C" key on my keyboard does absolutely nothing. i can, however, use the "Ctrl-C" command, and "Shift-C" or "Shift-Capslock-C" yield "C" and "c" respectively. this is the only problem that i have noticed so far.
_________________
~>})| Quidquid Latine Dictum Sit, Altum Viditur. |({<~ |
|
| Back to top |
|
 |
MasterX
Veteran
Joined: 26 Jun 2003
Posts: 1165
|
| Posted: Sun Apr 04, 2004 4:41 pm Post subject: |
|
|
| If you can write "c" or "C" then what is the problem? |
|
| Back to top |
|
|
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
| Posted: Sun Apr 04, 2004 4:45 pm Post subject: |
|
|
| the problem is that my "C" key has apparently been mapped to something else, and i can only use it when pressing an insane amount of other buttons to compensate for that fact, you insensitive clod. |
|
| Back to top |
|
|
MasterX
Veteran
Joined: 26 Jun 2003
Posts: 1165
|
| Posted: Sun Apr 04, 2004 7:45 pm Post subject: |
|
|
| UnGoddess wrote: | | you insensitive clod. |
I should not be helping you .... but anyhow.
Two solutions:
Check if khotkeys (or something else, run ksysguard) is running, maybe you accidentally assign C (or c) to nothing.
If the above fails then xmodmap comes to your rescue.
Create a file .test and write
keycode 54 = c
and then run xmodmap .test
One other thing, do you have gnome or another WM installed? If you do, log into that WM and check whether you have the same problem. Finally, if you log in as a root can you type "c,C" |
|
| Back to top |
|
|
Seamaiden
n00b
Joined: 02 Apr 2004
Posts: 35
Location: Pine Grove, CA
|
| Posted: Sun Apr 04, 2004 8:09 pm Post subject: |
|
|
Heh.. I was going to comment on how it's easier to draw bees to honey, but thought, "Ah, what difference will that make?" I'm getting a good chuckle, though.
MasterX is clearly big of heart.
_________________
Youth and Enthusiasm
Are No Match
For Age and Treachery
http://www.wetwebmedia.com |
|
| Back to top |
|
|
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
| Posted: Sun Apr 04, 2004 8:37 pm Post subject: |
|
|
| MasterX wrote: | | UnGoddess wrote: | | you insensitive clod. |
|
it was a joke. i guess i can't expect everybody to read slashdot, so i will apologize: i'm sorry. i did not mean to actually offend you.
| MasterX wrote: | | I should not be helping you .... but anyhow. |
thank you. you are quite the gentleman  i really do apprecaite your help.
i did as you suggested... here are the results:
* khotkeys is running, but i have no idea what it's doing. i also killed its process to see what would happen, but nothing did.
* running xmodmap .test caused nothing to happen.
* i can login to Windowmaker as my user and use the "c" button just fine
* root has no problems typing "c, C" under KDE.
i guess this means the problem is in my user KDE config files somewhere, but i really have no idea where it would occur. if anybody could point me in the right direction, i would appreciate it.
(and i promise i will lay off the jokes)
_________________
~>})| Quidquid Latine Dictum Sit, Altum Viditur. |({<~ |
|
| Back to top |
|
|
Unne
l33t
Joined: 21 Jul 2003
Posts: 616
|
| Posted: Sun Apr 04, 2004 9:30 pm Post subject: |
|
|
| If worse comes to worse, mv ~/.kde ~/.kde_backup and start over with fresh config files. |
|
| Back to top |
|
|
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
| Posted: Sun Apr 04, 2004 10:04 pm Post subject: |
|
|
| Unne wrote: | | If worse comes to worse... |
believe me, it did.
ok, so that fixed my "C" problem, and solved the question of where. now i'm going to take apart all the files in that folder until i can pinpoint what caused it.
thank you, sweetie
_________________
~>})| Quidquid Latine Dictum Sit, Altum Viditur. |({<~
Last edited by UnGoddess on Sun Apr 04, 2004 10:27 pm; edited 1 time in total |
|
| Back to top |
|
|
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
| Posted: Sun Apr 04, 2004 10:25 pm Post subject: i found it! |
|
|
i found it!!
apparently, in /home/[username]/.kde/share/config/kdeglobals, the value Switch to Desktop 8 was set to equal my precious, precious "C", instead of the correct value default(Ctrl+F8)
_________________
~>})| Quidquid Latine Dictum Sit, Altum Viditur. |({<~ |
|
| Back to top |
|
|
MasterX
Veteran
Joined: 26 Jun 2003
Posts: 1165
|
| Posted: Sun Apr 04, 2004 11:57 pm Post subject: |
|
|
When you killed KhotKeys, you should have been able to type "ccccccccccccccccccccccccccccccccccccccccccc", Wander, why you were not 
I had a similar problem with "x" and this was because I had assigned a program to run when I pressed "x". When I killed khotkeys, I was able to type "x". |
|
| Back to top |
|
|
UnGoddess
n00b
Joined: 09 Jan 2003
Posts: 7
|
| Posted: Mon Apr 05, 2004 7:20 pm Post subject: |
|
|
| MasterX wrote: | | When you killed KhotKeys, you should have been able to type "c"... |
i would have thought so too, but apparently my being unable to type "c" was because of the value in a KDE config file which had nothing to do with KhotKeys (or overrode it? i don't know).
at any rate, that just leads me to question why KhotKeys is running when i don't really want it to... i think i managed to disable it for good, but is it included by default or something? seems more annoying than useful to me, but that's just me...
oh, and thanks so much for your help 
_________________
~>})| Quidquid Latine Dictum Sit, Altum Viditur. |({<~ |
|
| Back to top |
|
|
|
Desktop Environments
