Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) #55

Closed
N0rbert opened this issue Apr 20, 2021 · 6 comments

Comments

@N0rbert
Copy link

N0rbert commented Apr 20, 2021

Steps to reproduce:

  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press <Caps Lock> key, enter some letters in CAPITALS (while CapsLock LED is on)
  5. Press <Caps Lock> key again, enter some letters in lowercase (while CapsLock LED is off)

Expected results:

  • CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function

Actual results:

  • CapsLock LED is always off

Downstream bug-report:

@legionus
Copy link
Owner

According to comment #3 the bug in the dpkg package.

@N0rbert
Copy link
Author

N0rbert commented Apr 21, 2021

The bug is really in kbd package. Removal of kbd package solves the CapsLock LED issue.
The command in the comment #3 is used to remove executable bit from all kbd executables.

If you can please test and confirm this bug on any modern Ubuntu version.

@legionus
Copy link
Owner

The steps to reproduce described in this issue refer to kbd only indirectly. I am not using ubuntu, but I suspect some scripts in ubuntu are calling setleds utility with wrong arguments.

@legionus
Copy link
Owner

It looks like the issue has been resolved.

@N0rbert
Copy link
Author

N0rbert commented Mar 22, 2022

How it was resolved? By which commit? Have you tried to reproduce it in 2022?

@legionus
Copy link
Owner

How it was resolved? By which commit? Have you tried to reproduce it in 2022?

As I said earlier, I believe that the problem is not in the utility, but in how it is used in ubuntu scripts. I have nothing to do with these scripts. This is up to the ubuntu maintainers to decide.

This has been resolved as WORKSFORME.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants