Keyboard LED Applet doesn't show Caps Lock unless all three indicators are set

[Vicente Herrera Cobo]

Binary package hint: lxpanel

Ubuntu Lucid
Package: lxpanel 0.5.5-0ubuntu2

The only way to get Caps Lock to show is to select all three indicators.
Any other combination may show Caps Lock temporarily, but if you restart
lxpanel, then a different indicator is shown instead of Caps Lock (e.g.
if Caps Lock is set by itself, Scroll Lock will be shown; if Caps Lock
and Scroll Lock are set, Num Lock and Scroll Lock will be shown).

[Graeme (graeme-redhat-bugs)]

Description of problem:
I have put the LXPanel keyboard LED widget on my panel as I have no hardware LEDs to show the status of the Caps/Num/Scroll lock keys.
I have selected to display only the Caps item, but on reboot I get the icon for Scroll Lock, which does not change status with any of the keys.
Checking the config (right click settings menu) indicates that Caps-Lock is the only selected item. Deselecting and reselecting the Caps-Lock item simply removes and readds the Scroll-Lock image to the panel, again not changing the status with any keypresses of any of the locking keys.

To get the desired behaviour I must select the Scroll lock setting, then remove it and the Caps and Num lock status displays behave properly.

Version-Release number of selected component (if applicable):
This is with version 0.5.4.1-2.fc12

How reproducible:
After every reboot.

Steps to Reproduce:
1. Add Keyboard settings LED to your panel, selecting only Caps Lock. Observe that an indicator appears in the panel - an uppercase A.
2. Reboot (or possibly log out).
3. Log in

Actual results:
Observe that the status indicator is on scroll lock. (a down pointing arrow)

Expected results:
That the indicator would be for the caps lock (an uppercase A)

Additional info:

[Christoph (christoph-redhat-bugs)]

Tracked upstream at
https://sourceforge.net/tracker/?func=detail&aid=2977158&group_id=180858&atid=894869

[Chris (chris-redhat-bugs)]

Confirmed for me with the latest lxpanel-0.5.5-3.fc12.i686

It initially gave me num lock and scroll lock indicators, in that order. I configured it to show me caps lock and num lock instead. After logout and login, it showed me num lock and scroll lock again, albeit in reverse order this time. Also, the scroll lock indicator doesn't work at all, but I'm on an EeePC, where the scroll lock is an fn-modified key. The num lock is also fn-modified though, and it works. Anyway, I don't really care about global scroll lock state, since applications these days generally interpret it as a toggle, but I'd really like my caps lock indicator to come back up each time. Unlike the other two, it's very easy to fat-finger that key, especially on my 7" EeePC and other netbooks where LXDE is typically used.

Ooh, I just went to set my Keyboard LED applet config to caps lock and num lock (num lock and scroll lock came up) and found that the buttons for caps lock and num lock were already checked, from my previous session. The check box for num lock worked properly, but the boxes for caps lock and scroll lock toggled each other's buttons, until I got it into a state where the check boxes matched the icons, and then they controlled the right things. There's something very screwy going on with how Keyboard LED is processing that configuration.

It'd be nice if we could bump the priority on this, because while it's not that severe of a bug, it's very annoying, it makes us look bad to the many users who may be encountering Linux for the first time on a netbook, and it should be a fairly obvious fix for anyone who knows that code.

[Christoph (christoph-redhat-bugs)]

(In reply to comment #2)
> It'd be nice if we could bump the priority on this, because while it's not that
> severe of a bug, it's very annoying, it makes us look bad to the many users who
> may be encountering Linux for the first time on a netbook, and it should be a
> fairly obvious fix for anyone who knows that code.

The best way to bump priority is to comment to the upstream bug report and add your comments there. If Marty knows how many people are affected/annoyed by this, he will probably invest more time.

[Christoph (christoph-redhat-bugs)]

Upstream bug report: https://sourceforge.net/tracker/?func=detail&aid=2977158&group_id=180858&atid=894869

I will build an updated package soon.

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Christoph (christoph-redhat-bugs)]

This was fixed in lxpanel 0.5.6. If not, please reopen this bug and change the Fedora version to '14'.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Guiver (guiverc)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.