According to the upstream bug report, this was fixed with commit
836864b65794dc0954a01245e418e714cead8125 which I've confirmed is
included in the natty, maverick, and lucid xservers.
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
** Changed in: xorg-server
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524774
Title:
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
--
ubuntu
** Changed in: xorg-server
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524774
Title:
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
--
ubuntu-bugs ma
** Changed in: xorg-server
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524774
Title:
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
--
ubuntu-bugs ma
Being not literate enought to parse Xorg source code, I tested the
following dirty and unreliable hack. The stupid idea is to use xmodmap
only when the Xorg window is displayed, based on my last comment. This
working (for me) should give some support to that comment:
#!/bin/sh
BLAHBLAH
.
.
.
sta
I've discovered that the addition of the Canadian Multilingual keyboard
(ca-multix) specifically triggers the bug behaviour. I.E. If I add it in the
properties dialog for xfce's Keyboard Settings applet, I will subsequently be
unable to do ``xmodmap -e 'clear Lock'`. Removing the Canadian Multi
Same environment specified in my 10 hours old message.
I do: Ctrl-Alt-F1 to go to a tty. then
t...@box:~$ echo "remove lock = Caecho "remove lock = Caps_Lock"| DISPLAY=:0.0
xmodmap -v -
! stdin:
! 1: remove lock = Caps_Lock
! Keysym Caps_Lock (0xffe5) corresponds to keycode(s) 0x42
remo
I've started using a different machine recently, and was initially not
experiencing this bug. I'm running xfce under 10.10. IIRC I originally
installed xubuntu on this box but have also installed the ubuntustudio
package as well as kubuntu-desktop and possibly ubuntu-desktop. Anyway
this erroneo
Here I have the same bug:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33.3-tinycore i686
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12
17:05:42 EEST 2010 i686
Kernel command line: multivt showapps
I also got this error. But NinoScript's workaround works well. Thank you,
NinoScript!
Here is another tip. The following command can be used to reload the settings,
instead of login/logout.
$ setxkbmap -model evdev
In my environment, I need to reload the settings everytime when I plug-
off/pl
NiñoScript's solution works for me too. I had to do both " = 134;"
and " = 105;" to remap my right Command button as Ctrl; if I don't
remap RWIN, it doesn't work.
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notificatio
I got this error as well, but I kept messing with my script that changes
the key modifiers and it seems to work for me now. The script is
attached in the hopes that it may help someone else until this is
resolved/better understood.
** Attachment added: "remap-keys"
http://launchpadlibrarian.ne
This bug is hugely annoying. Please please fix it.
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
For those who specifically only wish to make Caps Lock into Control, I found
help at this site:
http://mina86.com/2009/10/11/more-control-no-caps-lock/
What it says:
1) Open /etc/default/console-setup
2) Add ctrl:nocaps to XKBOPTIONS,
for example from
XKBOPTIONS=""
to
XKBOPTIONS="ctrl:nocaps"
(
I was bitten by the same bug while using a specific ~/.xmodmaprc to switch the
option and command keys
on a macintosh keyboard.
Applying the following patch works around the problem:
! Remove Mod1 and Mod4 mappings (as shown by xmodmap on fresh config)
-remove Mod1 = Alt_L
-remove Mod1 = Meta_L
Yes, thanks NiñoScript's workaround worked. Not as I anticipated, but in
the end CapsLock became Hyper_L.
I changed
= 66;
to
= 66;
and commented away the original ( = 208; or something like that).
Then I still needed to run
xmodmap -e 'keycode 66 = Hyper_L'
... did not fully understand the k
I found the same problem when I upgraded from 9.04 to 10.04.
Specifically, I was remapping another key to Control_L, with
xmodmap -e 'keycode 133 = Control_L'
xmodmap -e 'add Control = Control_L'
But the 'add Control = Control_L' line fails, with the same error
mentioned above.
NiñoScript's wor
Yay! I helped someone :D
Hooray for me! :)
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Great, NiñoScript's solution works for me!
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I figured out how to change that stuff myself without needing xmodmap,
yay for me :)
In this file: /usr/share/X11/xkb/keycodes/evdev
I found these lines:
= 64;
= 37;
= 65;
= 105;
= 108;
// Microsoft keyboard extra keys
= 133;
= 134;
which I changed for these ones:
= 108;
= 133;
= 65;
This bug is really serious and if not fixed will make me leave Lucid at
once.
My whole workflow is resting on " Hyper_L on CapsLock " or precisely:
xmodmap -e 'remove lock = Caps_Lock'
xmodmap -e 'keycode 66 = Hyper_L'
xmodmap -e 'add mod3 = Hyper_L'
I am using emacs 99% of the time and without
I just tried the patch and it doesn't work for me.
Is there anything else I can test or look at to help get this bug fixed?
It's just destroying every control- shortcut I use because my control
keys aren't where I expect. Oddly, my other keys remapped with xmodmap
work; it's just control keys that
This greatly affects my workflow, I like making my macbookpro's command keys,
Control_L and Control_R, respectively, and the control key a Super.
I and my co-workers are so used to this, that our little fingers ache a little
when we use them for complex and/or repetitive keystroke combinations.
W
Paolo, so did you test the patch?
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Agree with Nathan. This bug might make many people take Ubuntu of their
macbook (et similar) once upgraded to Lucid. Basically many characters
and key combination are unfeasible with this bug around.
Paolo
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/b
** Also affects: xorg-server via
http://bugs.freedesktop.org/show_bug.cgi?id=20145
Importance: Unknown
Status: Unknown
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of U
Kieran, sure that is a patch to xorg-server.
So apt-get source xorg-server, apply the patch (actually it looks like
it won't apply cleanly so you'll need to do it manually), build and
test.
However in looking at that patch, it's not obvious how that fixes the
problem and makes me wonder if it mig
I found the following patch:
https://bugs.freedesktop.org/show_bug.cgi?id=20145
I tried to test it but I couldn't find where the source for xkb is
located, I'd be happy to test if someone could point me in the right
direction.
** Bug watch added: freedesktop.org Bugzilla #20145
http://bugs.fre
xmodmap is not something very high on my priority list given how little
time remains for lucid. If you can obtain a patch from upstream
(bugs.freedesktop.org) we can consider inclusion of it for lucid.
Attach the patch to this bug report and that'll cause it to bubble up to
the top of the priority
Is there any chance of this bug getting fixed for Lucid? I just upgraded
a few days ago, and am feeling the loss of my usual control keys
acutely. If it's not getting fixed, is there a workaround?
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Low
** Package changed: xorg-server (Ubuntu) => x11-xserver-utils (Ubuntu)
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
xmodmap failure BadValue error, 118 (X_SetModifierMapping)
https://bugs.launchpad.net/bugs/524774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39437323/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39437324/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39437325/Dependencies.txt
** A
33 matches
Mail list logo
