On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;)
Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
