Thanks for following up. I'm closing this report due to your last
comment. Don't hesitate to submit any new bug.
** Changed in: update-manager (Ubuntu)
Status: Incomplete => Fix Released
--
edgy upgrade fails: "could not initiate dbus"
https://bugs.launchpad.net/bugs/129163
You received t
[Bug 129163] Re: edgy upgrade fails: "could not initiate dbus"
Date: Tue, 18 Nov 2008 23:07:00 -
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wonde
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in: updat
This is not an edgy upgrade, it is a long running feisty machine. Up to date
with feisty, feisty-updates, and feisty-security.
I haven't seen this before, but today it is there:
0 [EMAIL PROTECTED]:~$gksu update-manager
warning: could not initiate dbus
# Click on "Check" for updates in update-man
Thank you for the suggestion, but I don't believe that it is the same.
I manually added an import dbus to my DistUpgradeFetcher.py, and retried with
no success (import os was already in there).
However I received the same error again.
Also the bug you referenced indicates a global name not being d
This looks similar to bug 141060 but with Edgy not Feisty.
** Changed in: update-manager (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Michael Vogt
Status: New => Triaged
--
edgy upgrade fails: "could not initiate dbus"
https://bugs.launchpad.net/bugs/129163
Y
