Bug 1211821 - Screen brightness keys stopped working
Summary: Screen brightness keys stopped working
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Usability (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-30 09:58 UTC by Lukasz Wieczorek
Modified: 2023-12-01 12:36 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz Wieczorek 2023-05-30 09:58:53 UTC
Hello,

I'm using HP EliteBook 840 G2 with openSUSE Tumbleweed 20230527. At one point Fn+F9/F10 for screen brighntess stopped working. I though the problem would be intermittent, now it is old enough to report :).

I keys are reported as:

keycode 224 press
keycode 224 release
keycode 225 press
keycode 225 release


Having reviewed /lib/udev/hwdb.d/60-keyboard.hwdb I think these keys are not mapped (or I miss something).

Could we have the correct mapping restored please?

Thank you.

lukaswu
Comment 1 Antonio Feijoo 2023-08-07 09:26:39 UTC
It seems related to this upstream issue: https://github.com/systemd/systemd/issues/24714

Quoting https://hansdegoede.livejournal.com/26427.html:

"
You can check if your laptop is affected by this by running "ls /sys/class/backlight" if this shows only 1 entry and that entry is named "intel_backlight", "nouveau_bl", "amdgpu_bl0" or "radeon_bl0" then your laptop might be affected.
"
Comment 2 Lukasz Wieczorek 2023-08-07 11:26:03 UTC
Hello,


> You can check if your laptop is affected by this by running "ls
> /sys/class/backlight" if this shows only 1 entry and that entry is named
> "intel_backlight", "nouveau_bl", "amdgpu_bl0" or "radeon_bl0" then your
> laptop might be affected.
> "

Unfortunately provided path is empty:

(...):/sys/class/backlight # ll
total 0

luk
Comment 3 Franck Bui 2023-08-10 08:26:55 UTC
(In reply to Lukasz Wieczorek from comment #0)
> Hello,
> 
> I'm using HP EliteBook 840 G2 with openSUSE Tumbleweed 20230527.

This snapshot looks pretty outdated already.

Can you please update your system or at least systemd/udev packages and see if that helps after rebooting ?
Comment 4 Lukasz Wieczorek 2023-08-10 08:48:54 UTC
Hello,

> > I'm using HP EliteBook 840 G2 with openSUSE Tumbleweed 20230527.
> 
> This snapshot looks pretty outdated already.
> 
> Can you please update your system or at least systemd/udev packages and see
> if that helps after rebooting ?

This is dated back once problem reported, now it is 20230808 and udev is: udev-253.7-2.1. I pull updated at least once a day and device is rebooted weekly.

Cheers.

luk
Comment 5 Franck Bui 2023-11-30 16:29:02 UTC
Sorry for the delay.

Since your problem is not specific to Tumbleweed, I would suggest to report your issue to systemd upstream instead at https://github.com/systemd/systemd/issues.

Thanks.
Comment 6 Lukasz Wieczorek 2023-11-30 21:48:28 UTC
Well... I'm not sure what makes you think it is not related to Tumbleweed (as long as I understand this is the ditro I'm using) and why systemd is a culprit...

Anyway, this bug can be closed as in the meantime I reinstalled the system on the same laptop and these keys started working again. 

Cheers.

luk
Comment 7 Franck Bui 2023-12-01 07:27:30 UTC
The hw database is primarily used by udev and as such is part of the udev component which in its turn is part of the systemd project.

Apparently the hw database was missing some entries for your system. If it's really the case it makes more sense to report the problem directly to upstream since all distros (not only TW) need to be updated. IOW the problem is not due to the integration of systemd in openSUSE distros. That's the reason why I suggested to report the problem to upstream.

Hope that makes sense.
Comment 8 Lukasz Wieczorek 2023-12-01 12:36:55 UTC
I suspect to be the problem located in udev rules which I presumed are distro specific.

As said previously, it works now and I'm unable to compare old config file with new ones.

luk