Version: unspecified (using Devel) OS: Linux Brightness OSD is not displayed when increasing the brightness with the Fn key, only when decreasing is displayed. This is on KDE 4.5.95. Reproducible: Always Steps to Reproduce: 1. On KDE4 Plasma Desktop, press the increase brightness key. 2. The brightness is increased correctly, but the OSD is not displayed. Actual Results: The brightness is increased correctly, but the OSD is not displayed. Expected Results: The brightness should be increased correctly and the OSD should also be displayed.
please try with the released 4.6.0; it's working here quite nicely (on several systems)
There is indeed a very long delay, so if one only has a few stps left until 100% brightness the osd is not displayed.
Forgot to add. There is hardly any delay when decreasing the brightness, so the bug is that the delay for increasing is longer.
I have now KDE 4.6.0, if I start from complete rest, and I hit the increasing key, the OSD is not displayed, I am not talking about delay (never displayed).
I have 7 brightness steps and for the first 4 the OSD is not shown so it might be that users with less steps never see the OSD. IMHO there is already a bug if the OSD does not appear instantly as soon as one hits the key once to increases/decreases the brightness.
I have now KDE 4.6.0 When using the Fn keys to adjust screen brightness does not show progress bar signaling the level of brightness in percentages. It only shows when you start to use the slider to the level of brightness in a widget "Battery"
have this bug. kde 4.6, gentoo @ macbook 4.1.
*** This bug has been confirmed by popular vote. ***
since 4.6.0 OSD doesnt show the progress bar for changing brightness, arch, asus k40in
This bug is still present in KDE 4.6.1
laptop DELL Inspiron 1520, KDE 4.6.1 in suse rpm's
is this a plasma desktop, or a battery plasmoid bug? i can reproduce it too by the way (kubuntu 10.10 kde 4.6.1)
I can not say for sure, but when I adjust the brightness slider in the applet battery (battery plasmoid), the indicator appears at the level of brightness, but it does not appear as it should in regulating the level of brightness hotkeys. Я не могу уверенно сказать, но когда я регулирую бегунком уровень яркости в апплете батареи, то появляется индикатор уровня яркости, но он не появляется, как должен, при регулировани уровня яркость горячими клавишами. OpenSUSE 11.3 KDE 4.6.1
Laptop Acer Aspire-5732Z. I had to add my user name to the video group before I could see the OSD when changing brightness level. The OSD appears intermittently when decreasing brightness, but not when increasing.
Laptop Acer Aspire-5732Z. I had to add my user name to the video group before I could see the OSD when changing brightness level. The OSD appears intermittently when decreasing brightness, but not when increasing. ...forgot to mention, using KDE 4.6.2
When using hot keys on the keyboard brightness slider is not shown (see Figure 1) when the slider are using the brightness slider in battery plasmoid, I brightness displays (see Figure 2) should be the opposite
Created attachment 59308 [details] Figure 1 Expand plasmoid batteries when using the keyboard brightness level, brightness level is not visible
Created attachment 59309 [details] Figure 2 When you adjust the brightness slider in the plasmoid battery indicator appears on the screen brightness
Dunno why, but now it works. Using the function keys on my keyboard, and using the plasmoid battery indicator. In my case I'll say [SOLVED] ...till it misbehaves again. --- On Mon, 4/25/11, Igor Strelnikoff <Freiheits@mail.ru> wrote: From: Igor Strelnikoff <Freiheits@mail.ru> Subject: [Bug 265357] Brightness OSD is not displayed when increasing the brightness (KDE 4.5.95) To: henry.duc64@yahoo.com Received: Monday, April 25, 2011, 6:21 PM https://bugs.kde.org/show_bug.cgi?id=265357 --- Comment #18 from Igor Strelnikoff <Freiheits mail ru> 2011-04-25 20:21:17 --- Created an attachment (id=59309) --> (http://bugs.kde.org/attachment.cgi?id=59309) Figure 2 When you adjust the brightness slider in the plasmoid battery indicator appears on the screen brightness
And I have the keys always worked, but indicator brightness level does not work correctly. What I wrote in the post above
I've modified GRUB thusly to actually control my display brightness: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux acpi_backlight=vendor" --- On Mon, 4/25/11, Igor Strelnikoff <Freiheits@mail.ru> wrote: From: Igor Strelnikoff <Freiheits@mail.ru> Subject: [Bug 265357] Brightness OSD is not displayed when increasing the brightness (KDE 4.5.95) To: henry.duc64@yahoo.com Received: Monday, April 25, 2011, 6:21 PM https://bugs.kde.org/show_bug.cgi?id=265357 --- Comment #18 from Igor Strelnikoff <Freiheits mail ru> 2011-04-25 20:21:17 --- Created an attachment (id=59309) --> (http://bugs.kde.org/attachment.cgi?id=59309) Figure 2 When you adjust the brightness slider in the plasmoid battery indicator appears on the screen brightness
I think last comment represent also a bug, I think the OSD shouldn't be displayed when the brightness is adjusted by the applet slider, neither when the brightness is automatically changed by powerdevil by computer inactivity or low battery.
>>I've modified GRUB thusly to actually control my display brightness: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux acpi_backlight=vendor" Works for me change the brightness of the screen. Not working indicator brightness when I adjust the brightness level.
This bug is still present in KDE 4.6.3
Runner battery plasmoid will not respond to changes in the level of brightness on the keyboard Fn + Up / Down (DELL specific combination of keys) http://www.youtube.com/watch?v=sKuXa71x9ow Brightness keys Fn + Up / Down changes the brightness level, but the indicator of the brightness level is not displayed. http://www.youtube.com/watch?v=TFPxGU7a-M4 When you use the slider in the plasmoid battery indicator brightness which appears not to be. But the slider is behaving incorrectly. http://www.youtube.com/watch?v=Q-FlGotK3Oc
Created attachment 59806 [details] Plasmoid batteries hidden
Created attachment 59807 [details] Plasmoid batteries deployed incorrectly
Created attachment 59808 [details] System tray without battery plasmoid icons
Regression is enhanced KDE 4.6.3, the battery applet is not used as a hiding. See attached. After the release of the monitor from standby mode indicator appears on the brightness level, which should not be. http://www.youtube.com/watch?v=S_lTmQ8lUQA
*** Bug 268453 has been marked as a duplicate of this bug. ***
>>Assigned To: Plasma Bugs List I think that this bug should be forwarded Dario Freddi or anyone else from Solid Teams
For me everything works well till 4.7.1 and now in current 4.7.2 release the brightness OSD is not displayed if you change it by FN keys, but when you change it once by applet OSD would be displayed both for applet and FN keys as it should be.
Working well now after updating to KDE 4.8 on Arch Linux. Regards. Antonio.
True, forgot to close this bug.
On my Chakra-linux KDE 4.8 it doesn't show the brightness. I wonder if it is a regression problem now
For sure it is not related to this bug, since OSD has been implemented for any brightness change now. It is more likely something is broken in your configuration in the lower part of the stack, hear from your distributor.
For me and KDE 4.8.1 this is not fixed, too. I get brightness OSD when moving brightness slider using mouse, but not when adjusting it through Fn+Home and Fn+End keys. The system in Lenovo X220 laptop with xf86-video-intel 2.18.0 driver and xorg-server 1.11.4. Dario, how do I check whether this is KDE bug or a flaw in underlying stack? Is there a signal the stack should emit when the brightness changes? It it visibile in tools like xev?
Yes, and it is likely your bios is catching the event and handling brightness for you - if that's the case, there is nothing we can do to handle this properly, as we do not have control over this. In short, if an X event is triggered and powerdevil detects it, there is something wrong - otherwise, this is probably out of our league. P.S.: Please do not reopen bugs until there's a clear confirmation the issue still persists, it's rather confusing otherwise.
(In reply to comment #38) > Yes, and it is likely your bios is catching the event and handling > brightness for you - if that's the case, there is nothing we can do to > handle this properly, as we do not have control over this. In short, if an X > event is triggered and powerdevil detects it, there is something wrong - > otherwise, this is probably out of our league. I forgot to mention that `xbacklight -get` shows correct brightness and the battery applet too - but it needs to be hidden & shown for its brightness slider to update. > P.S.: Please do not reopen bugs until there's a clear confirmation the issue > still persists, it's rather confusing otherwise. Sorry about that.
(In reply to comment #39) > (In reply to comment #38) > > Yes, and it is likely your bios is catching the event and handling > > brightness for you - if that's the case, there is nothing we can do to > > handle this properly, as we do not have control over this. In short, if an X > > event is triggered and powerdevil detects it, there is something wrong - > > otherwise, this is probably out of our league. > > I forgot to mention that `xbacklight -get` shows correct brightness and the > battery applet too - but it needs to be hidden & shown for its brightness > slider to update. This clearly means that powerdevil wasn't signaled a brightness change occurred, and in the same fashion didn't even process the request itself. This means it's extremely likely your BIOS handles the brightness keys (very likely). If that's the case, game over, unless you find a way to disable that. Still, might be worth it to find out if X gets the correct key event and if it's forwarded to Qt correctly in case. > > > P.S.: Please do not reopen bugs until there's a clear confirmation the issue > > still persists, it's rather confusing otherwise. > > Sorry about that. No problem :)
No-no, this is(was) a regression. I have X220 too and in kde 4.6 I definitely had brigthness slider when controlling brightness level with buttons. But then, I don't know the release, something broke and I just disabled hotkey trigger for brightness up and down and now it's controlled by bios. There was another bug that made brightness level more or less by 3 levels, not by 1.
Then this is probably something you should have your distribution notice. As you might imagine, KDE has no control about what happens in the stack below. From what you read, it looks like your distributor moved brightness handling to a different position in the system stack (hardly to the BIOS, as this is not something which can change by upgrading a distribution)
Hello, my laptop also handle Fn brightness keys by BIOS, so in KDE I don't see the OSD, you consider this normal, but in GNOME I can see the OSD, why GNOME can do it and KDE cannot?
GNOME might be listening to different brightness change events - or to a different system component handling brightness keys. Again, there's not much I can tell without knowing your distribution, and if an X event is triggered or not.
I've got some aditional information: 1- the keys ARE being captured by KDE:i can reassing the brightness key (up and down) at System Settings->Shortcut and Gestures ->Global Keyboard Shortcuts -> decrase / increase screen brightness 2- dbus is capturing the key and seems to be sending messages to kded: $ dbus-monitor member=globalShortcutPressed signal sender=org.freedesktop.DBus -> dest=:1.153 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.153" signal sender=:1.11 -> dest=(null destination) serial=4545 path=/component/kded; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "kded" string "Increase Screen Brightness" int64 1751437 signal sender=:1.11 -> dest=(null destination) serial=4547 path=/component/kded; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "kded" string "Decrease Screen Brightness" int64 1752383 IMHO, it may be a problem inside kded. Any thoughts on this?
What i mean was 1: I can re-assign the actions to the Fn+brighness up and Fn+brightness down and KDE will recognize these keys. 2: The events happens when I press the Brightness Fn keys.
I use to test multiple Linux distributions (Debian, OpenSUSE, Ubuntu), on all of them, OSD is displayed in GNOME, Unity and XFCE I can read these events in xev: KeyRelease event, serial 34, synthetic NO, window 0xd400001, root 0xab, subw 0x0, time 907110, (81,-15), root:(924,166), state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 34, synthetic NO, window 0xd400001, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 34, synthetic NO, window 0xd400001, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 34, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 KeyRelease event, serial 34, synthetic NO, window 0xd400001, root 0xab, subw 0x0, time 908886, (81,-15), root:(924,166), state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
Thanks. Next step is to find out if Qt gets this correctly. This requires some modification to powerdevil's core, to place a couple debug lines to make it print a message when such a key is triggered. Could you do that, if I provided you with a patch?
(In reply to comment #48) > Thanks. Next step is to find out if Qt gets this correctly. This requires > some modification to powerdevil's core, to place a couple debug lines to > make it print a message when such a key is triggered. Could you do that, if > I provided you with a patch? I can do this. I have the same xev output as Rafael.
Before the patch, bug 295982 probably identifies the cause of the issue. Can we please move the discussion there?
*** Bug 271623 has been marked as a duplicate of this bug. ***