Hi Sebastian, On Mon, 2006-11-27 at 12:36 +0100, Sebastian Fontius wrote:
> I agree. I have no real idea of the inner workings of fnfx, its > client, or the kernel in regard to this, but the symptoms reminded me > of #328085. So I concluded (or merely hoped) that it would be a > matter of simply making the patch dependant on what version of Linux > actually runs or something as easy as this. Agreed, #328085 sounds very similar. > I wanted to ask another (more rhetorical) question: Why is a seperate > daemon needed anyway, why not unify it so that acpi/hal/ivman can be > used? But then I found http://developer.berlios.de/projects/ial and > noticed the little box "Developers" with "thoenig" in it :). (I > assume that this "thoenig" is indeed the same "thoenig" that has > answered this bug report, i.e. you.) > > So now my question is rather: How good is IAL working and is there a > possibility that it will enter Debian? > > If I can help anyway else please let me know. IAL is basically not under development any longer. Please do not spend any time on getting it into Debian. I am planning to cleanup the hotkey mess in 2007 by adding some bits to HAL. Again, not only for Toshiba laptops but an abstract approach which should help any system, vendor independent. If FnFX is missing key events, IAL will miss them, too as it is basically the same backend code. > Greetings, > > BTW: I updated to linux 2.6.18.3 and the problem has not gone away. If you want to succeed I'd suggest breaking it down to the kernel version where it broke. If you can tell "it worked with 2.6.16.3 but stopped working with 2.6.1.16.4" you will have a realistic chance to find the culprit. Timo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
