dbus failure
Bug #430602 reported by
electhor
This bug report is a duplicate of:
Bug #430125: Karmic Latest - upstart kept back - missing mountall.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu |
New
|
Undecided
|
Unassigned | ||
Bug Description
Karmic had a major break with recent update. Initially had a frozen GUI (no mouse) with message during update that grub 1.97-beta3 did not install nor did apic. Did a further update later from tty1 - now have following message
init: Unable to connect to the system bus: Failed to connect to socket /ver/run/
I think grub is now installed after manually running sudo update-grub2 - not sure about apic. Anyone know what the message means? Google has not been very helpful.
Revision history for this message
| arky (arky) wrote | #1 |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 430125 , so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.