LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-28-2019, 09:36 AM   #1
sairum
Member
 
Registered: Sep 2004
Location: Portugal
Distribution: Slackware
Posts: 118

Rep: Reputation: 56
Warning: Problems in keyboard layout in current


I finally decided to try/"switch to" slackware current. I grabbed an ISO image (26/04/2019) and installed from a DVD. After fiddling a bit with UEFI and GPT installation went as expected and took a few minutes because I don't install either tex or kde. The former I install from a texlive DVD and the latter from Alien Bob's ktown. During the installation I selected the Portuguese keymap as usual but I didn't test it, hitting 1 (the "accept when test is done" key), by assuming that the keyboard map was ok, as it usually is! However, when I logged into KDE I was unable to change the default us keyboard layout to a pt (Portuguese) layout! No flag/label appeared on the taskbar although I had the two layouts selected in KDE's settings. I changed to the stock XFCE but the problem persisted!

An inspection of /etc/X11/xkb/symbols showed that the pt file was somehow damaged. A regular setxkbmap command returned an error for pt but not for other layouts (such as the sp, us or fr)
Code:
# setxkbmap -layout pt
Error loading new keyboard description
# setxkbmap -layout es
# setxkbmap -layout us
# setxkbmap -layout fr
Replacing the pt file with the one that come with slackware64 14.2 solved the problem. The settings' windows of XFCE and Alien's KDE5 are now able to change the keyboard layout in X and in KDE5 a small flag allows me to change the layout on the fly. Regular text editors like kate work correctly.

However, the problem is also present on the console. I usually boot on runlevel 3 and do a startx from there. But if I stay on the console and work with vi, vim or even nano, most of the dead keys do not work or produce strange results depending on the editor. For example typing '~' and 'a' does not echo an 'ã' but a regular 'a' without the tilde! Typing a 'ç' followed by any other character will echo a 'ç ' (a cedilla with a space) followed by the other character. This behavior is somehow reproducible using vi on a terminal in X. Surprisingly, in a X terminal, either vim or nano work flawlessly! I tried to replace the corresponding Portuguese files in /usr/share/kbd/keymaps/i386/qwerty with the ones supplied by slackware64 14.2 with no success...

Just for the record I use a regular 'US' locale and avoid internationalization like the plague!

Code:
bash-5.0$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
 
Old 04-29-2019, 07:28 AM   #2
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Leinster, IE
Distribution: Slackware, NetBSD
Posts: 2,180

Rep: Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763Reputation: 1763
I think you can mark this thread solved now, since the latest changelog for -current suggests the problem has been fixed.
 
1 members found this post helpful.
Old 04-29-2019, 10:33 AM   #3
sairum
Member
 
Registered: Sep 2004
Location: Portugal
Distribution: Slackware
Posts: 118

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by Gerard Lally View Post
I think you can mark this thread solved now, since the latest changelog for -current suggests the problem has been fixed.
It is solved indeed! Took less than one day for Pat to fix the thing. Now that I'm at it, the general behavior I described in the original post is also present in Slackware 14.2 (except for the xkblayout). On the text console (runlevel 3) the three text editors mentioned gave different results. In vim, for example, hitting 'ç' and the 'a' results in 'ç a' (an additional space)! But if a file is saved an reopened with nano, one can read 'ça' correctly! Uppercase characters don't go along with the tilde in any of the editors (e.g., Ã or Õ, which are quite normal in Portuguese). All these means that I don't use the text console often, especially to edit text. As I never use diacritics and spaces in filenames or folders such behavior went unnoticed until today!
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Selecting the correct keyboard layout corresponding to my laptop's physical layout nidra Linux - Newbie 2 08-28-2017 08:14 AM
Environment variable containing the current keyboard layout _ON Linux - Newbie 1 05-18-2010 11:04 PM
Detecting current keyboard layout (using hal) wgac Slackware 10 12-09-2009 09:21 AM
show the current keyboard layout tramni1980 Slackware 2 10-04-2007 08:40 AM
Switching keyboard layout - Mandriva2006 - K.D.E. Windows Layout! itz2000 Mandriva 3 08-13-2006 06:43 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:02 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration