SUMMARY The keyboard backlight OSD just doesn't show up most of the time, no matter how many times I cycle it. Occasionally, it will start working again no matter how many times I cycle it. And then the next time I change my keyboard backlight brightness, it doesn't work anymore. STEPS TO REPRODUCE 1. Adjust keyboard backlight with keyboard controls. OBSERVED RESULT The OSD behavior explained above. EXPECTED RESULT The OSD works 100% of the time. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-20R5-sched-ext (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I'm 99.999% sure this is a "broken for me" issue caused by my heavily customized Gentoo installation. A major pain to troubleshoot because it isn't reliably reproducible and eliminating variables requires mass recompiling.
I have a similar issue and have commented in bug #486067. On my system I can get the OSD to show up by logging out and back in. Is that also the case for you?
(In reply to potato1112 from comment #1) > I have a similar issue and have commented in bug #486067. On my system I can > get the OSD to show up by logging out and back in. Is that also the case for > you? You're right. I didn't notice that connection. It works after logging out and logging back in, but not after a reboot. I doubt this is a race condition because it's not like SDDM passes any of this onto the session. (Worth noting that I'm using SDDM in Wayland mode with kwin_wayland.) Something else is going awry. I've updated the title to reflect this.
Restarting SDDM after boot does not fix the issue. Only log out and log in. It looks like the two of us have the same problem, and it is a different problem than #486067.
This is still broken on Plasma 6.2.2. I just switched my system from systemd back to OpenRC (for unrelated reasons, it's amazing that Gentoo just lets you do that in place) and it's still broken. So that's more evidence that this probably isn't a race condition because the startup of the system as well as the desktop (Plasma on systemd makes use of the systemd --user instance; OpenRC does not support user instances so the generic /etc/xdg/autostart mechanism is used instead) is totally different.
During the time when you're experiencing the bug, does the keyboard brightness item fail to appear in the Battery and Brightness widget? And after you log out and back in, does it appear there?
(In reply to Nate Graham from comment #5) > During the time when you're experiencing the bug, does the keyboard > brightness item fail to appear in the Battery and Brightness widget? And > after you log out and back in, does it appear there? Yes and yes, I didn't see that before. So this is not just a problem with the OSD code. I just tried killing and restarting plasmashell, as well as running kwin_wayland --replace and then starting a new plasmashell. Neither of those fixed the problem. I took a look at powerdevil/daemon/controllers/keyboardbrightnesscontroller.cpp and saw it's using UPower (duh), so I figured maybe restarting the upower service would make it work. It did not. So where in the chain could this be?
I don't know, but hopefully one of the Powerdevil folks will be able to help.
It likely doesn't help, but in case it does, my experience is the same as above, OSD and keyboard brightness item in brightness widget don't appear until logging out and back in. I'm on Plasma 6.2.3, Frameworks 6.7.0, Qt 6.8.0, Kernel 6.11.6 in case that matters also.
(In reply to Alex B from comment #8) > It likely doesn't help, but in case it does, my experience is the same as > above, OSD and keyboard brightness item in brightness widget don't appear > until logging out and back in. I'm on Plasma 6.2.3, Frameworks 6.7.0, Qt > 6.8.0, Kernel 6.11.6 in case that matters also. It would be helpful to know what distribution you're using. I'm on a very customized Gentoo, which is the epitome of nonreproducibility. Are you on Gentoo too? I'm gonna try installing Fedora and seeing if it's broken there too. It works totally fine on Fedora 40/41 on my 2012 A1466 MacBook Air.
Forgot to mention that I tried a new, clean user and it didn't help.
(In reply to anhollander516@gmail.com from comment #9) > (In reply to Alex B from comment #8) > > It likely doesn't help, but in case it does, my experience is the same as > > above, OSD and keyboard brightness item in brightness widget don't appear > > until logging out and back in. I'm on Plasma 6.2.3, Frameworks 6.7.0, Qt > > 6.8.0, Kernel 6.11.6 in case that matters also. > > It would be helpful to know what distribution you're using. I'm on a very > customized Gentoo, which is the epitome of nonreproducibility. Are you on > Gentoo too? > > > I'm gonna try installing Fedora and seeing if it's broken there too. It > works totally fine on Fedora 40/41 on my 2012 A1466 MacBook Air. I'm using EndeavourOS/Arch. This install is pretty new and I'm not using any special packages or customization (but one) for plasma or its components that can't be done in the system settings panel. The only non-default configuration related to plasma that I have is sddm set to run under wayland instead of x11.
(In reply to Alex B from comment #11) > (In reply to anhollander516@gmail.com from comment #9) > > (In reply to Alex B from comment #8) > > > It likely doesn't help, but in case it does, my experience is the same as > > > above, OSD and keyboard brightness item in brightness widget don't appear > > > until logging out and back in. I'm on Plasma 6.2.3, Frameworks 6.7.0, Qt > > > 6.8.0, Kernel 6.11.6 in case that matters also. > > > > It would be helpful to know what distribution you're using. I'm on a very > > customized Gentoo, which is the epitome of nonreproducibility. Are you on > > Gentoo too? > > > > > > I'm gonna try installing Fedora and seeing if it's broken there too. It > > works totally fine on Fedora 40/41 on my 2012 A1466 MacBook Air. > > I'm using EndeavourOS/Arch. This install is pretty new and I'm not using any > special packages or customization (but one) for plasma or its components > that can't be done in the system settings panel. The only non-default > configuration related to plasma that I have is sddm set to run under wayland > instead of x11. I'm also running SDDM on Wayland. But it's fine on my MacBook with Fedora, so I don't think that's relevant. You could test with SDDM Xorg if you want. I can't test without rebuilding a ton of stuff with USE=X; I have X11 supoort disabled at compile time where possible because I'm using Wayland and don't need it.
> I'm also running SDDM on Wayland. But it's fine on my MacBook with Fedora, > so I don't think that's relevant. You could test with SDDM Xorg if you want. > I can't test without rebuilding a ton of stuff with USE=X; I have X11 > supoort disabled at compile time where possible because I'm using Wayland > and don't need it. I just went and removed the configuration file I created to make SDDM run under wayland, restarted a few times to try it out, and the result is the same each time. No OSD or slider in the widget until logging out and back in.
*** Bug 495476 has been marked as a duplicate of this bug. ***
(In reply to anhollander516@gmail.com from comment #3) > It looks like the two of us have the same problem, and it is a different > problem than #486067. How does this differ from #486067? This looks like the exact same issue to me.
Indeed, it does appear to be the same issue. *** This bug has been marked as a duplicate of bug 486067 ***