Thanks for the heads up - I will definitely avoid 15.10 until this is
fixed :).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/173350
Title:
Caps lock LED changes state even when caps lock is mapped
Came back in 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/173350
Title:
Caps lock LED changes state even when caps lock is mapped to ctrl
To manage notifications about this bug go to:
** 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/173350
Title:
Caps lock LED changes state even when caps lock is mapped to ctrl
--
** 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/173350
Title:
Caps lock LED changes state even when caps lock is mapped to ctrl
--
** Changed in: gnome-control-center
Status: Invalid = Unknown
** Changed in: gnome-control-center
Importance: Unknown = Medium
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are
I am seeing this again in Lucid, with the virtual key LED on the
Logitech DiNovo.
The workaround of using xmodmap still works, though.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a
Correction: the workaround described above *does not* work any more. I
can't figure out a way to prevent my keyboard from beeping constantly.
This is really annoying :(.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this
So, after trying every combination of options I could think of to no
effect, as well as several reboots, I gave up. However, after rebooting
the *keyboard itself*, the beeps are gone! So it's possible that this
is a firmware bug in the keyboard and not in ubuntu. I will update if I
discover
This is still an issue for me.
I'm running 8.04 (up to date) on a HP DV 1700 series laptop. When I use the GUI
to swap the ctrl and caps keys, the key marked caps lock is still the only
one that is triggering the LED. Actually, I ran the command
xmodmap -e clear lock -e add lock = Caps_Lock
It doesn't stick. But, rather than mess around with config files, I've got
another work around. Put the command:
xmodmap -e clear lock -e add lock = Caps_Lock
into the sessions thingy (System- Preferences - Sessions - Add, the name is
whatever, the command is the one above etc.).
Also after
This bug is still present for me on my fully-updated Hardy.
Jake
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Still a problem for me in Intrepid with an external keyboard on my
laptop
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: xorg-server (Ubuntu)
Assignee: Sebastien Bacher (seb128) = (unassigned)
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Not for me, although there is a weird thing that xmodmap mappings now
only apply to the keyboards that are plugged in - remap, and then plug
an external keyboard and it'll behave like you never ran xmodmap on the
new keyboard. Remap afterwards, and it behaves like you expect. Are you
possibly
Still having this issue on Hardy.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
All my Hardy systems still have this problem. My one Intrepid system
doesn't. Please be clear what release you're using when reporting
issues.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because
Eythian: I am also having his problem with a hotpluggable USB keyboard.
This is a work laptop that I take to and from home; both locations have
a USB keyboard and every time I hotplug, I am required to unset and
reset (through System|Preferences|Keyboard|Layouts|Other Options...) my
ctrl/caps swap
[Intrepid] This was a problem for me last night on my laptop's
integrated keyboard, but appears to be okay today. The fix may have come
in the xkb-data package update that came this morning.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
After having been okay for a while, has this recently become a problem
for anyone else, once again?
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was seeing this on my Thinkpad X300 in Hardy, but after upgrading to
test Intrepid alphas, the problem has gone away, so I believe this is
fixed somehow.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Fix Released
--
Caps lock LED changes state even when caps lock is mapped
** Changed in: xorg-server
Status: Confirmed = Fix Released
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Jodo, .bash_profile is only evaluated for bash shell sessions - so
settings there won't affect other Gnome or KDE applications. And
rc.local is used for system-wide settings; so it is executed as root.
setxkbmap configures individual users' settings. So you need to run that
command as the user you
Thanks Jesse :)
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
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.com
'setxkbmap' fixes this and also keyboard layout switching Bug #196277.
However I have to execute it every time. I tried adding 'setxkbmap' line to
.bash_profile or rc.local but it didn't work. Why?
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/14935538/Xorg.0.log
--
Caps
bryce, I don't know the detail, svu who is the libxklavier, xkeyboard-
config, GNOME keyboard capplet maintainer just told me that's a known
xserver issue, I'll ask him for details
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You
I'm also experiencing this issue. Currently I'm using a workaround
posted above and have a permanently lit LED.
Up to date with all recent updates.
Xorg log attached.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/14656466/Xorg.0.log
--
Caps lock LED changes state even when
seb128, please explain what the xorg issue is, not just it's an xorg
issue - we need some additional clues in what needs
changed/reverted/fixed...
Also, can someone who is experiencing this problem please post their
/var/log/Xorg.0.log (to get version #'s etc.)
** Changed in: xorg-server
Happening to me, too; I agree that it's just cosmetic, but it's still
annoying.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The permanent solution does not work for me. I have to execute the sudo
xmodmap /etc/SwapCapsCtrl.kmap every time that I restart.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a
** Bug watch added: freedesktop.org Bugzilla #15359
https://bugs.freedesktop.org/show_bug.cgi?id=15359
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=15359
Importance: Unknown
Status: Unknown
--
Caps lock LED changes state even when caps lock is
** Changed in: xorg-server
Status: Unknown = Confirmed
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
that's not a gnome-control-center bug
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = Low
Status: New = Invalid
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because
I'll throw my experience with this bug into the hat. I just upgraded
from Gutsy, in which this feature worked correctly, to Hardy, in which
the bug appeared. Hardy is currently up to date.
First, I reverted my Gnome keyboard preferences to the default. I tried
Jay Finger's suggestion of
I just created a brand new account, and verified that my observations in
comment 42 are still happening in a new account. That is, using the
xorg.conf workaround, with all defaults for Gnome keyboard preferences
and *no* ~/.xmodmaprc file, the default behavior of Gnome overrides the
xorg.conf
upstream says that's an xorg issue
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: gnome-control-center = xorg-server
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)
Status: Triaged = New
--
Caps lock LED changes state even when caps lock is mapped to ctrl
Just confirming this bug on Ubuntu 8.04 final.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-control-center
Status: New = Invalid
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have this problem as well on Hardy B5, to which I upgraded this
morning 27 April from Gutsy. (My system has incrementally updated since
Dapper, so there *may* be cruft, but I've been pretty good about
revisiting my dotfiles.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
I have noticed this also with swapping control and caps lock. Another
workaround is to enable this option specifically in /etc/X11/xorg.conf
by adding the following line to your keyboard Device section:
Option XkbOptions ctrl:swapcaps
This illuminates the LEDs correctly, but applies
As an alternative to what MountainX described, name the file
~/.xmodmaprc. The first time that file is present at login the user
will be asked if they want to load the file. There is an option to not
be asked again. Check that, select the file to load, and from there on
out the ~/.xmodmaprc
the ubuntu team appreciate your concern, this behaviour is not
constructive though, the distribution gets hundred bugs every week and
there is a really small team working on those, there is lot of bug about
hardware not working correctly, applications crashing, etc so the work
has to be
note that we don't have keyboard hackers in the team so the fix is not
that obvious, I talked with the upstream maintainer who also works on
xkeyboard-config and he said that the issue is an xorg server one which
changed the way keyboard indicators are working and something which
should be fixed
What's not constructive about I'd be willing to work on this if there
was a chance for a freeze exception?
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which
the comment was not meant to you but rather to the comment before the
post, you are welcome to work on a patch and we will review your changes
if you get something working, though the workaround might create other
issues and not be a good idea
--
Caps lock LED changes state even when caps lock
Sebastien: Upstream does think this bug doesn't matter. Really, how
hard would it be to insert the equivalent of remove Lock = Caps_Lock
before remapping caps lock? It probably won't take much longer than
insisting that this is not a gnome bug (even though it could trivially
be worked around
Okay, so this really isn't gnome-control-center's fault. Please move
the bug to libxklavier12.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is
what made you change opinion?
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I didn't really. libxklavier is the library that actually takes care of
the keyboard settings, gnome-control-center is just the front-end.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you
A curiosity related to this: alt-ctrl-F1 requires you to press the
'real' control, not the remapped one. This also didn't happen in the
previous version.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification
I think I was wrong about libxklavier. I don't actually know where the
changes to the keyboard settings are applied, it's probably some gconf
backend, who knows? That's not the point, the point is that if I can
work around the issue by typing xmodmap -e remove Lock = Caps_Lock
before reassigning
Hmmm..a bug not worth fixing ?? Doesn't that sound like Microsoft
??? I thot we were different ; ((
Tom Jaeger wrote:
I think I was wrong about libxklavier. I don't actually know where the
changes to the keyboard settings are applied, it's probably some gconf
backend, who knows? That's
On Fri, 2008-04-11 at 02:19 +, mrklean wrote:
Hmmm..a bug not worth fixing ?? Doesn't that sound like Microsoft
??? I thot we were different ; ((
We are different because we provide the fix.
Tom Jaeger wrote:
I think I was wrong about libxklavier. I don't actually know where
I found a workaround. I'm using Hardy beta.
Do not use gnome's keyboard control (Ubuntu System Preferences Keyboard
Layout Options).
Instead follow the example in man xmodmap as explained below.
NOTE: before doing this, undo any changes in Keyboard layout options.
Put the options back to
the prior comment has a typo:
loadkeys should be xmodmap
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
https://bugs.launchpad.net/xkeyboard-config/+bug/105538
similar bug report
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Adding a 'me too'.
Ubuntu hardy + Edubuntu, up to date as of today. experiencing the same problem,
and as with the others, its a regression.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you
Just to hilight the seriousness of this, my girlfriend just about took
my head off because she got locked out of her email account because
she didn't know caps-lock was on when she was typing her password.
I think this must get fixed for Hardy.
--
Caps lock LED changes state even when caps lock
the option is not on by default so no that's not a priority for hardy
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Gnome developers need to learn that regressions do matter. It doesn't
matter if the new features are better if you piss off previous users.
Maybe it's time to go back to KDE like Linus
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You
what a constructive comment and behaviour and good luck to find a
software which never introduce a breakage, mistakes happens in any
project and it's doubtful than linux or kde are exceptions there
--
Caps lock LED changes state even when caps lock is mapped to ctrl
you can also note than nobody thinks that bug don't matter but there is
ten thousand bugs open right now in ubuntu and a really small team
working on those, that sucks but everything can't be fixed right now.
The people contributing at making those software better do it mostly for
free after work
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs,
I was about to file a bug on this myself, but found this duplicate.
This is pretty annoying from a usability standpoint...especially since
it's a regression from Gutsy.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this
I just had this problem on a my laptop. One important clue is that it started
only after I enabled:
Automatic Login
Perhaps part of the keyboard initialization process is being accidentally
skipped during automatic
login?
--
Caps lock LED changes state even when caps lock is mapped to ctrl
On Sunday 30 March 2008 16:17:04 Stephen Hemminger wrote:
I just had this problem on a my laptop. One important clue is that it
started only after I enabled: Automatic Login
Perhaps part of the keyboard initialization process is being accidentally
skipped during automatic login?
Neither of
I see this as well, running an HP 8710w. I have swapped Ctrl and
CapsLock. The key labeled caps lock works as control but toggles the
caps-lock LED. They key labeled ctrl works as caps-lock, but does
not toggle the caps-lock LED.
I agree that this did not happen in Gutsy.
Using Hardy x86
I see this bug as well in Hardy i386 beta (up to date) on a desktop computer. I
posted about it here:
http://ubuntuforums.org/showthread.php?p=4599879#post4599879
At that post another person said it did not happen in earlier versions.
Even using the keyboard layout utility to assign the capslock
I have this problem as well (Fujitsu Siemens Esprimo E5916, USB
keyboard). From the gnome keyboard preferences, I have chosen Swap ESC
and Caps Lock
The keys work as far as typing output goes (checked in vim) but the caps
lock key turns the caps lock light on and off, and the Escape key does
Can be resolved by executing
xmodmap -e clear lock -e add lock = Caps_Lock
This should however be done automatically so it's still a bug.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you
Still happening here on my Thinkpad X60s, with an up-to-date hardy
system.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This doesn't happen to me anymore, do you guys have the latest updates?
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This problem is definitely Hardy specific. I'm on an Aspire 5100 and it worked
on eisty But not on hardy !
Thanks ; )
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed = Triaged
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Changed in: gnome-control-center
Status: Unknown = New
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: xorg-server = gnome-control-center
** Bug watch added: GNOME Bug Tracker #509804
http://bugzilla.gnome.org/show_bug.cgi?id=509804
** Also affects: gnome-control-center via
http://bugzilla.gnome.org/show_bug.cgi?id=509804
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: xorg = xorg-server
Importance: Undecided = Low
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which
I started seeing this with Hardy on my Thinkpad X60s -- I have caps lock
and ctrl switch, and the key labeled CapsLk still toggles the caps
lock LED, even though it actually behaves like the control key. (And
the key labeled Ctrl does not affect the caps lock LED, even though it
does work like
Similar situation: I have exchanged left Control with Caps Lock, and now
* left Control changes the real caps lock state (ie, whether or not letters
are capitals)
* but Caps Lock changes the led state on the keyboard (though it works as a
Control key)
I've noticed that since Hardy,
Attaching the bug to Compiz, where I think the problem originates.
** Changed in: compiz (Ubuntu)
Sourcepackagename: None = compiz
Status: New = Confirmed
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug
I am seeing this problem even with Metacity.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This is not a bug in compiz, what you're seeing is compiz outputting the
data from `xset q` because it can't find your log file.
** Changed in: xorg (Ubuntu)
Sourcepackagename: compiz = xorg
--
Caps lock LED changes state even when caps lock is mapped to ctrl
81 matches
Mail list logo
