https://bugzilla.novell.com/show_bug.cgi?id=478418 Summary: KPowersave leads brightness control to take 2 or 3 steps Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers@suse.de ReportedBy: user2304@web.de QAContact: qa@suse.de Found By: --- User-Agent: Opera/9.63 (X11; Linux x86_64; U; de) Presto/2.1.1 Using openSuSE 11.1 with thinkpad x200s: Modules: - thinkpad_acpi.ko is loaded (with options thinkpad_acpi experimental=1 hotkey=enable,0xffffff) - video.ko is not loaded In the KDE Environement without kpowersave started: - the brightness-controls via FN-POS1 and FN-END work perfectly (one brigthness step is changed with every keypress) - lshal -m outputs a single "brightness-down / up" event with every keypress. After starting kpowersave: - FN-POS1 increases brightness by 2 steps with every keypress - FN-END decreases brightness by 3 steps with every keypress - "lshal -m" still outputs a single "brightness-down / up" event with every keypress - "acpi_listen" outputs on single event with every keypress - Switching to an virtual console - on step with every keypress. Searched around and found a lot bugs regarding kpowersave - but none of them with this behaviour. Seems to be a problem of how kpowersave handles the key-events ? Reproducible: Always Steps to Reproduce: 1. Module video.ko not loaded 2. Module thinkpad_acpi loaded (options thinkpad_acpi experimental=1 hotkey=enable,0xffffff) 3. KDE 3.5.10 running 4. KPowersave started Actual Results: Brightness is increased by 2 steps / decreased by 3 steps with every single hotkey-press. Expected Results: Brightness should increased by 1 step / decreased by 1 step with every single hotkey-press. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.