Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when "/etc/init.d/networking stop" is
called.
In other words, whenever "/etc/init.d/networking stop" is called, dbus gets
killed.
That has a nasty effect: when dbus stops, gnome-settings-daemon crashes and
that means the desktop theme is lost.
Please see bug #868095 [1] and my comment #3 on that bug.
VMware Tools does this all the time (calling networking stop) when
suspending the machine. That means you are guaranteed to get a horrible
looking (and not completely functional) desktop whenever you resume your
VMware session.
That also happens if I simply restart the networking service:
/etc/init.d/networking stop
/etc/init.d/networking start
(Of course, because this chain reaction that leads to gnome-
settings-daemon death starts on "networking stop")
In conclusion, this seems to be a serious issue. I wonder if that is
happening with more people besides myself and the other fella on bug
#868095.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/868095
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
