Bug 27971 - xset led 3 doesnt work
Summary: xset led 3 doesnt work
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Input/XKB (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: low normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 14:27 UTC by Dan Espen
Modified: 2018-12-13 18:39 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Dan Espen 2010-05-04 14:27:55 UTC
Starting with Fedora Core 12, the command:

xset led 3

fails to turn on the scroll lock led.

I've been using this command for years to indicate I have mail waiting.  After installing FC12 on 2 different machines, the scroll lock LED stopped lighting up.

I reported this issue to Red Hat and another user confirmed the same symptom.

I now see a similar problem report for Ubuntu so I think the command is broken for all users of recent versions of xset.

Please let me know if you can duplicate or if you need more information.

Thanks.
Comment 1 Alan Coopersmith 2010-05-04 14:30:20 UTC
xset just passes the request on to the X server which passes it to the
input driver - I've reassigned to the evdev driver, since that's most
likely the input driver being used on Fedora & Ubuntu, but you can check
in /var/log/Xorg.0.log to verify.
Comment 2 Dan Espen 2010-05-04 14:49:25 UTC
Thanks Alan.

As you say, I am using the driver "evdev".  I made changes to my xorg.conf to disable HAL changing the input driver and reverted to xkbd and still had the same problem.  I can not swear I did the changes correctly but I did confirm by the Xorg log that xkbd started instead fo evdev.

You can see my comments over here:

http://forums.fedoraforum.org/showthread.php?p=1354613#post1354613
Comment 3 Peter Hutterer 2010-05-04 20:56:50 UTC
verified. This is a rather deeper issue in XKB though, not in the evdev driver.
Given the limited impact and my todo list, this is rather low priority at the moment. Sorry.

Tracing through DoChangeKeyboardControl and XkbSetIndicators would be the start to investigate this, a quick look with a couple of printfs shows that we never go down into the driver to set the LEDS.
Comment 4 GitLab Migration User 2018-12-13 18:39:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/316.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.