On Thu, Jun 24, 2010 at 08:26, Michael Meskes <mes...@debian.org> wrote: > On Wed, Jun 02, 2010 at 04:57:20AM -0400, Michel wrote: >> At boot time I get the following message: >> >> 'failed (Could not start /usr/sbin/acpi_fakekeyd).' >> >> The keys for volume up/down and mute work, but does not control >> the volume up/down and mute on alsamixer like before. >> >> Seems similar to #577603, but I have no messages >> like that in /var/log/Xorg.0.log, from #577603: >> >> 'ACPI Virtual Keyboard Device: Dropping event due to full que' >> >> Even after manually stopping and starting with 'invoke-rc.d acpi-fakekey' >> the same thing still happens. This is on a Thinkpad T23. > > 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. > > Michael
After installing 0.136-4, it still fails at boot with the same message. But I now see this message above, which did not show before: 'Starting acpi_fakekey daemon...open device: No such file or directory' Can now manually start with: /usr/sbin/acpi_fakekeyd, acpi_fakekeyd and invoke acpi_fakekeyd start. 'Starting acpi_fakekey daemon...[time] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input8 done.' But still does not control alsamixer like it did before. Thanks, Michel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org