Hide Forgot
Description of problem: Pressing Fn+Brightness Up/Fn+Brightness Down combo on Lenovo E420 results in a momentary CPU usage spike (top shows 8% for gnome-shell and 2% for polkitd). Changing the brightness from low to high by simply holding the keys causes non-uniform brightness change (1-20, slight delay, 20-80, delay, 80-100) and may cause the events to keep being processed seconds after the keys are released. During that long press, gnome-shell is consuming around 20% CPU and polkitd uses 14% each. This makes the notification lag behind the actual brightness change/not show completely and the only reliable way of setting brightness to the desired level is to press the keys multiple times waiting for the adjustment to take effect after each keypress. Version-Release number of selected component: gnome-settings-daemon-3.18.2-1.fc23.x86_64 polkit-0.113-4.fc23.x86_64 How reproducible: Always Steps to Reproduce: 1. Press Fn+Brighness Up, hold it for 30 seconds Actual results: CPU usage spikes, the HUD shows that brightness increases, then disappears and reappears randomly. If Fn+Brightness Down is pressed, the effects will not be seen until after all the events from the previous keypresses are completed. Expected results: Brightness change is momentary and does not lag behind the keypresses. Additional info: The kernel has acpi_backlight=vendor override and thinkpad_acpi module is blacklisted due to incorrect backlight range configuration by lenovo. The range for intel_backlight/brightness is 0-4437. I was unable to reproduce this behavior on Ubuntu 15.10 live session and Windows 10. It looks like the gsd receives the keypress, dispatches the /usr/libexec/gsd-backlight-helper through pkexec via g_spawn_sync, but keeps receiving the keypress notifications, which then get piled up and more calls get sent to gsd-backlight-helper, which in turn makes polkitd busy.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.