You are not logged in.
Hi everyone,
I have a question regarding GNOME3's Software Update application (gpk-update-viewer). First of all, i find this program very handy, specially to ease a little bit the updating process <by allowing to select just what i want to update>, but...
...when i start it a first time (when logged in, or after a suspension/hibernation) it crashes. The error log message is shown below:
(gpk-update-viewer:1752): PackageKit-WARNING **: failed to get properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Exiting as backend details could not be retrieved: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
...but, a second time it opens normally. This happens from a time ago, i don't know if an update has affected it.
Thanks for your help,
Jaime
Last edited by japenagosc (2012-04-28 18:21:58)
Offline
Nothing???
Offline
Same problem here.
Offline
try with: gpk-update-viewer --verbose
Offline
--This is the output:
11:22:53 GnomePackageKit Verbose debugging enabled (on console 1)
11:22:53 GnomePackageKit ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session2
11:22:53 GnomePackageKit using native mode: 700x1200
11:22:53 GnomePackageKit wrap_width is impossibly small -200
11:22:53 GnomePackageKit wrap_width is impossibly small -200
(gpk-update-viewer:1684): PackageKit-WARNING **: failed to get properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Exiting as backend details could not be retrieved: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Offline
Updating to version 3.4 (GNOME 3.4) the problem's gone.
Offline