Bug 484162

Summary:	Keyboard brightness OSD always shows up on activity change
Product:	[Plasma] plasmashell	Reporter:	Gábor Katona <katonag>
Component:	Power management & brightness	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	natalie_clarius, nate, nicolas.fella, plasma-bugs-null
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Gábor Katona 2024-03-21 13:35:39 UTC

SUMMARY
***
When changing activity the keyboard brightness OSD always shows up for a few seconds.
***

STEPS TO REPRODUCE
1. Change activity 

OBSERVED RESULT
The keyboard brightness OSD always shows up for a few seconds.

EXPECTED RESULT
It should not show up.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20240319
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

Comment 1 Nate Graham 2025-06-10 17:11:53 UTC

Thanks for the bug report, and I'm sorry nobody looked at it. A ton has changed since it was reported; can you still reproduce this issue in Plasma 6.3.5 or later? I cannot.

Thanks a lot!

Comment 2 Bug Janitor Service 2025-06-25 03:48:02 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Gábor Katona 2025-07-01 07:57:54 UTC

(In reply to Nate Graham from comment #1)
> Thanks for the bug report, and I'm sorry nobody looked at it. A ton has
> changed since it was reported; can you still reproduce this issue in Plasma
> 6.3.5 or later? I cannot.
> 
> Thanks a lot!

Currently with 6.4.0 the issue is not present.