[Michael Meskes] > Do you still see the problem with 0.136-4 in unstable? If so could > you please start /usr/sbin/acpi_fakekeyd manually under strace to > see what happens? It might also be helpful to compile acpi-fakekey > with debugging enabled and run it under gdb. I haven't seen this > problem before.
I've seen it too, but was not sure if it was hardware dependent or not. Could this be a boot ordering problem? Should acpi-fakekey start before acpi-support? This is the ordering of the acpi scripts in a recent Squeeze installation: r...@localhost:/# ls /etc/rc2.d/*acpi* /etc/rc2.d/S20acpi-fakekey /etc/rc2.d/S22acpid /etc/rc2.d/S22acpi-support r...@localhost:/# If they need some specific ordering, the script dependencies are incomplete. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org