On 23/09/12 01:33, Daniel Hartwig wrote:
reassign -1 packagekit
On 22 September 2012 23:53, Sharon Kimble <[email protected]> wrote:
I expect apt to continue and complete
It has. The error you receive:
Processing triggers for man-db ...
Setting up alpine (2.02+dfsg-1.1) ...
Setting up alpine-doc (2.02+dfsg-1.1) ...
Error: Timeout was reached
is not from apt but output as a result of one of the Post-Invoke triggers.
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.
Searching your apt conf. for the term “timeout” matches this entry:
DPkg::Post-Invoke:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service
&& /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest
org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 1 --method
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null";
which is calling /usr/bin/gdbus. Grepping the source of that package
(libglib2.0-bin) indicates that it does contain a “Timeout was
reached” error.
This entry is added by packagekit, so reassigning.
Fair enough, thanks.
Regards
Sharon.
--
A taste of linux = http://www.sharons.org.uk/taste/index.html
efever = http://www.efever.blogspot.com/
efever = http://sharon04.livejournal.com/
Debian Wheezy, xfce 4.8, LibreOffice 3.5.4.2
Registered Linux user 334501
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
