I am experiencing this bug too, on a fully updated feisty:
After confirming that my system is up to date
$ sudo apt-get update
$ sudo apt-get upgrade
I run
$ gksudo "update-manager -c -d"
GTK Accessibility Module initialized
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: 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.
GTK Accessibility Module initialized
GTK Accessibility Module initialized
andersja@plasken:~$
The meta-release bug appears present still? (the referenced 'fix released' has not yet been published?)
I am experiencing this bug too, on a fully updated feisty:
After confirming that my system is up to date
$ sudo apt-get update
$ sudo apt-get upgrade
I run .DBus.Error. NoReply: 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.
$ gksudo "update-manager -c -d"
GTK Accessibility Module initialized
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop
GTK Accessibility Module initialized
GTK Accessibility Module initialized
andersja@plasken:~$
The meta-release bug appears present still? (the referenced 'fix released' has not yet been published?)