xmodmap doesn't work in feisty

Package: xmodmap
Version: 1:1.0.1-0ubuntu1

I have he himself problem.

Not work:
xmodmap /usr/share/xmodmap/xmodmap.es

-- System Information:
Debian Release: 4.0
  APT prefers feisty
  APT policy: (500, 'feisty')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.20-8-lowlatency
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)

Versions of packages xmodmap depends on:
ii libc6 2.5-0ubuntu11 GNU C Library: Shared libraries
ii libx11-6 2:1.0.3-4ubuntu1 X11 client-side library

xmodmap recommends no packages.

-- no debconf information

New test. Now work fine my keyboard.

$xmodmap /usr/share/xmodmap/xmodmap.la

Change of xmodmap.es to xmodmap. Not problem

My keyboard is "Latino americano". Not "spanish".

James, can you try if 1.0.2-0ubuntu1 works better, you can grab it from here (only i386 binary, but sources available):

http://users.tkk.fi/~tjaalton/xorg72/pool/feisty/xorg-test/

it probably doesn't help upgrading xmodmap, since I can't reproduce this.. at least xmodmap -pk lists the entries correctly if I change them.

Ok, so I've confirmed that a) this is not due to my dotfiles, I've reproduced it on the same machine with a freshly created user. b) this is a gnome not X or xmodmap problem as if I start a 'failsafe terminal' session, xmodmap works fine. Reassigning to control-centre as discussed with Seb.

Milestoning for beta (regression)

Multiple people are reporting that xmodmap works perfectly for them, so removing milestone. Please see if you can come up with reproducibility criteria.

This sounds very suspiciously like an xkb problem I've heard of before

* Scott James Remnant

| This sounds very suspiciously like an xkb problem I've heard of before

Can you elaborate?

James, could you add the output of setxkbmap -print to this bug?

--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Tollef Fog Heen <email address hidden> writes:

> James, could you add the output of setxkbmap -print to this bug?

xkb_keymap {
        xkb_keycodes { include "xfree86+aliases(qwerty)" };
        xkb_types { include "complete" };
        xkb_compat { include "complete" };
        xkb_symbols { include "pc(pc105)+us+ctrl(nocaps)" };
        xkb_geometry { include "pc(pc105)" };
};

--
James

I've also had problems with .Xmodmap not "working". But my problem seems to be that it does work, but then the modmap subsequently gets reset to the default. This seems very much like bug #97175 (https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/97175/).

The work around suggested by Oliver[1], removing the x bit from /usr/bin/xkbcomp, resolved the problem for me.

[1] https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/97175/comments/6

could you try if that's still an issue in hardy?

I can no longer reproduce this problem on hardy.

thank you for the update, seems to be fixed, closing the bug