Public bug reported:
When I shut down Hardy (8.04) first, the gdm takes a long time (about a minute)
to shut down. The GUI dissappears and this is what's on screen at the time:
setting up ALSA
starting anac(h)ronistic cron
starting deferred execution scheduler
starting periodic command scheduler
checking battery state
running local boot scripts etc/rc.local
If the system shuts down normally (it does so every once in a while) i
don't see these at all
After that, I get a whole bunch of messages, which go more or less like
this (im transcribing this from sight, so it might have a typo or two):
Network Manager: <WARN> nm_signal_handler(): Caught signal 15. shutting down
Network Manager: <info> caught termination signal
Network Manager: <debug> [1209069304,808145] nm_print__open socks(): Open
sockets
List:
Network Manager: <debug> [1209069304,808366] nm_print_open_socks(): Open sockets
List Done.
Network Manager: <info> Deactvativing device eth0
Network Manager: <WARN> nm_hal_deinit(): libhal shutdown failed connection is
Closed
Network Manager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system
bus. Make sure the messagebus daemon is running!
Network Manager: <WARN> nm_dbus_signal_device_status_change: asserion
`cb_data->data->d
bus_connect xxxx failed
This happens approx. 80% of the time when shutting down.
the numbers in the square brackets differ.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Hardy takes a long time to shut down, prints network manager error message
https://bugs.launchpad.net/bugs/221525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
