[SOLVED] Layout initially different between USB keyboard and laptop's integrated keyboard

BrutalMusic · 12-03-2012, 07:48 AM

First off, a quick thanks to everyone who makes Slackware possible, including those who provide the awesome tech support here.

I'm running Slackware 14.0 on an HP dv2945se. It is a fresh, full install to which I have done the following configuration/setup:

Updates via slackpkg
Use NVidia's proprietary driver
Custom xinitrc and fluxbox config files (but if I revert to the default .fluxbox/keys file the problem persists)
Keyboard layout changed to Dvorak in /etc/X11/xorg.conf.d/90-keyboard-layout.conf (and confirmed as working in fluxbox)
Install wicd

I take notes at each step of installation, and according to them, there was no problem until after I installed wicd.

After I installed wicd I rebooted, and then a call to startx returned, in part:

xmodmap: unable to open file '/home/username/.Xmodmap' for reading

So I commented xmodmap out in .fluxbox/startup

All is well except that when I start fluxbox, my USB wireless keyboard (Logitech K750) types QWERTY until I use the laptop's integrated keyboard (which types Dvorak).

After I've used the integrated keyboard once, the USB keyboard reliably types Dvorak as it should. The laptop's integrated keyboard always works as it should.

It's no real inconvenience to use this workaround, of course. But if the same problem happened to a desktop, the user wouldn't have access to the workaround.

Thanks!

zsd · 12-03-2012, 03:11 PM

For starters, did you used to have a .Xmodmap before?

And is there an unreadable .Xmodmap in your home directory now?
(For example, maybe something you did caused your file to get over-written
with one owned by root, and that file does not have general read perms.)

Jim

BrutalMusic · 12-03-2012, 04:36 PM

Quote:

Originally Posted by zsd

For starters, did you used to have a .Xmodmap before?

And is there an unreadable .Xmodmap in your home directory now?

I have never created an .Xmodmap file, so the only way there would be one is if it was automatically generated upon install or some such. I use .fluxbox/keys.

When the error message occurred, I used slocate to determine that there's no .Xmodmap present on my system.

Thanks!

BrutalMusic · 12-04-2012, 01:03 AM

Now that I'm at my computer, here's the output of updatedb then slocate.

Code:

Script started on Mon 03 Dec 2012 11:00:11 PM PST
bash-4.2# updatedb
bash-4.2# slocate -i xmodmap
/etc/X11/xinit/README.Xmodmap
/usr/share/zsh/5.0.0/functions/_xmodmap
/usr/share/vim/vim73/ftplugin/xmodmap.vim
/usr/share/vim/vim73/syntax/xmodmap.vim
/usr/doc/kbd-1.15.3/dvorak/dvorak.xmodmap
/usr/doc/kbd-1.15.3/dvorak/dvorak-l.xmodmap
/usr/doc/kbd-1.15.3/dvorak/dvorak-r.xmodmap
/usr/doc/xmodmap-1.0.7
/usr/doc/xmodmap-1.0.7/INSTALL
/usr/doc/xmodmap-1.0.7/AUTHORS
/usr/doc/xmodmap-1.0.7/COPYING
/usr/doc/xmodmap-1.0.7/README
/usr/doc/xmodmap-1.0.7/ChangeLog
/usr/man/man1/xmodmap.1.gz
/usr/bin/xmodmap
/var/log/packages/xmodmap-1.0.7-i486-1
bash-4.2#

zsd · 12-05-2012, 06:22 AM

Given that the error message was specifically about the /home/username/.Xmodmap file, you could have just used ls to see if it is there.

Anyway, you say you commented something out from .fluxbox/startup.
Perhaps it was just a bit of poor code there?
Did it just say something like
/usr/bin/xmodmap $usermodmap
or
/usr/bin/xmodmap /home/username/.Xmodmap
or equivalent, as opposed to something like (from S64-14.0's /etc/X11/xinit/xinitrc.xfce file)
if [ -f $usermodmap ]; then
/usr/bin/xmodmap $usermodmap
fi

Anyway, this is mostly moot, and probably has nothing to do with your QWERTY issue. On that I regret to report I have no idea.

Jim

BrutalMusic · 12-06-2012, 03:07 AM

Quote:

Originally Posted by zsd

Anyway, you say you commented something out from .fluxbox/startup.
Perhaps it was just a bit of poor code there?

From .fluxbox/startup

Code:

#!/bin/sh
#
# fluxbox startup-script:
#
# Lines starting with a '#' are ignored.

# Change your keymap:
# xmodmap "/home/username/.Xmodmap"

Thanks anyway!

BrutalMusic · 02-07-2014, 04:06 AM

I hope it's okay to put a quick note on such an old thread as I mark it solved...

This turned out to be an issue with the Logitech unifying receiver. Arch's wiki has all the info on it.