** Changed in: update-notifier (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/59725
Title:
Dbus shutdown crashes
To manage notifications about this bug go
closing the nautilus task since listed that on an update-notifier bug is
confusing and upstream considers restarting dbus as something to not do
you can open a new nautilus bug if you still think that's an issue
though, opening it on bugzilla.gnome.org too would be better though
** Changed in:
** Bug 58903 has been marked a duplicate of this bug
--
Dbus shutdown crashes
https://launchpad.net/bugs/59725
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
dbus restart is not something supported by upstream (that's why you get
the reboot required notify icon on dbus upstream), marking those as
wishlist
** Changed in: nautilus (Ubuntu)
Importance: Untriaged = Wishlist
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed =
I confirm this. Same thing happened to me with nautilus and stacktrace looks
very much the same. Few applications that listen DBUS are known to shutdown
when service is restarted (rhythmbox and bashene), but this time BugBuddy
notified that a crash happened.
I can reproduce same crash with
This gets written in ~/.xsession-errors:
(nautilus:14222): Liboobs-CRITICAL **: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
Liboobs-ERROR **: file oobs-session.c: line 103 (oobs_session_init): should not
be reached
aborting...
--
Dbus shutdown
