On Wed, Sep 26, 2012 at 02:00:44AM +0200, Matthias Klumpp wrote: > Hi! > This issue is really odd, because the DBus call should never ever > fail...
It doesn't fail, someone set the timeout to 1 second, and dbus doesn't reply withing 1 second, so you get that error. > Is DBus working properly? Yes. > Can you easily reproduce the issue? I see it very often, but I can't reproduce it all the time. > What happens if you run the hook command manually in a terminal? It directly returns: () > Does it block? It can't block, it has a timeout of 1 second. Kurt > Cheers, > Matthias > > 2012/9/24 Daniel Hartwig <mand...@gmail.com>: > > On 23 September 2012 16:57, Sharon Kimble <boudic...@talktalk.net> wrote: > >>> How often do you receive such an error and is your system under > >>> increased load when it happens? > >> > >> > >> Every time now, its just happened again with updating this morning. > > > > Assuming then that the system load is not a problem. > > > > You could investigate log files associated with dbus, packagekit, and > > dmesg(1) for anything which may indicate a failure to load, > > communicate, etc.. > > > > I am not familiar with those systems, so can not provide any more > > specific guidance. > > > > Regards > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
