You are not logged in.
Hi guys.
I'd like to turn on the leds of my keyboard (CM Devastator) before the login of the user: i've inserted the command "xset led 3" into /etc/gdm/Init/Default but it does not work, does someone know why?
Last edited by brofjst (2019-02-09 08:56:34)
Offline
No clue, but you are aware setting the leds is not the same as activating their function ?
If this happens to be the numlock setting, check https://www.archlinux.org/packages/comm … /numlockx/
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I've already installed numlockx but it does not help.
Just to be clear, for keyboard's led i mean the leds under the buttons of the keyboard.
example
I can't find anything strange in the journal's log, i post it if someone wanna give it a look.
Journal's log
Last edited by brofjst (2019-02-09 09:19:38)
Offline
Good day ![]()
Did you see the wiki page about this issue? [https://wiki.archlinux.org/index.php/Keyboard_backlight]
I dont know if it works, but have some options.
Offline
i've tried it but when i run /usr/local/bin/kb-light.py + 1
Traceback (most recent call last):
File "/usr/local/bin/kb-light.py", line 26, in <module>
print(kb_light_set(int(sys.argv[2])))
File "/usr/local/bin/kb-light.py", line 11, in kb_light_set
current = kbd_backlight.GetBrightness()
File "/usr/lib/python3.7/site-packages/dbus/proxies.py", line 70, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python3.7/site-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/lib/python3.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.UPower.KbdBacklight” on object at path /org/freedesktop/UPower/KbdBacklightOffline
output of
$ systemctl status upower.serviceDoes the bash oneliner mentioned in the wiki work ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
$ systemctl status upower.service
upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; enabled; vendor pres>
Active: active (running) since Fri 2019-02-22 20:26:11 CET; 1h 1min ago
Docs: man:upowerd(8)
Main PID: 439 (upowerd)
Tasks: 3 (limit: 4915)
Memory: 6.9M
CGroup: /system.slice/upower.service
└─439 /usr/lib/upowerd
Feb 22 20:26:10 brofjst systemd[1]: Starting Daemon for power management...
Feb 22 20:26:11 brofjst systemd[1]: Started Daemon for power management.the one liner does not work.
Offline