Slackware64-current, KDE4.2.3: Pipe key not working in Konsole
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Slackware64-current, KDE4.2.3: Pipe key not working in Konsole
Hi all,
I have managed to upgrade from Slackware 12.2 (32-bit) to Slackware64-current. Almost everything is fine, and KDE 4 is soooo nice, apart from one little snag: The pipe key (the key with which one types |) is not working everywhere.
I have a German Logitech Wave keyboard, which is compatible with Microsoft Natural keyboards. Selecting the corresponding driver during setup and in KDE, plus activation keyboard layouts in KDE, it works just fine almost everywhere, just not in Konsole and Xterm.
I can type | in a virtual terminal on the command line, and almost everywhere in KDE. I can even type the character in the setup dialog of Konsole. And apart from this, all international keys (äöüß) seem to work and are to be found where I expect them.
Not sure, if it's a bug, or a misconfiguration. And if it's a bug, I don't know, if it is a KDE or a Slackware64-current issue. So I am asking first here, before bothering any busy developers.
What could I look for? Or where should I report/post this?
Thanks,
gargamel
EDIT: Just noticed, that Tilde ~ is also not functional. As you can see, it works in Konqueror, however.
EDIT: Correction, Tilde ~ does work, just have to type it twice, while keeping the ALT-GR key pressed down.
Tried en_GB keyboard layout in KDE, and had £ above 3, and --- ta taah --- pipe, type as left-shift plus \ (the two keys far down on the bottom left corner of the keyboard; not sure, if that is where they are supposed to be, though...).
Back to German keyboard layout, no success again, in Konsole (everwhere else it works).
Weird: Even in the test input/output fields of the Konsole setup, where one can switch between Linux/Solaris/Xfree4, the behaviour is correct. I type | into the input field and get | as output. What the hack is preventing Konsole from behaving just this way, when not in testing mode? This is getting mysterious...
When I start KDE from the CLI as root, I get | in Konsole as expected.
Starting KDE as a normal user, it doesn't work.
I have also meanwhile de-/re-installed kdebase (containing Konsole), and deleted several hidden directories with configuration data for my desktop user, but up to now nothing helped.
I guess, when root can get | and normal user cannot, it has something to do with privileges. But what?
And, BTW: su root doesn't help. Only when I start KDE as root I get | from the usual key combination.
First I created a new user. Logging in with the new account and starting KDE from the CLI I found, my keyboard was perfectly working, even without having to active "Keyboard Layout" in KDE (I guess the Slackware installer and the NVIDIA graphics driver did a real good job, here, creating my /etc/xorg.conf without any need for manual modification). Now, as it worked for a new user, I wanted to become such a new user.
I deleted or renamed all hidden directories, deleted the user account, re-created it and made the new user the owner of the old /home/user directory. Guess what? It works now...
I still don't know what was actually wrong, though...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.