desktop-packages team mailing list archive

[Harald Rudell <869635@xxxxxxxxxxxxxxxxxx>]

If I insert "stop on runlevel [6]" into /etc/init/network-manager.conf on a Lenovo S10-3t,
I get many error messages after Killing all remaining..:

modem-manager[n]: <info> Modem Manager (version 0.5) starting...
modem-manager[n]: Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/869635

Title:
  long delay at shutdown/reboot - network-manager doesn't close
  correctly

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  I've noticed the shutdown and reboot in oneiric is slower than in
  natty. This is reproducible on different machines with fresh
  installations.

  Disabling plymouth and vt.handoff=7 I can see that some processes are not closed:
  * Asking all remaining processes to terminate... [OK]
  * Killing all remaining processes... [fail]

  Killing network-manager at runlevel6, after the dbus shutdown signal,
  makes the shutdown and restart really faster (I'd say 5/10sec on low
  end machines like netbooks)


  --- /etc/init/network-manager.conf.orig 2010-05-03 14:56:09.745071317 +0200
  +++ /etc/init/network-manager.conf 2010-05-03 14:56:43.075152939 +0200
  @@ -8,6 +8,7 @@
   start on (local-filesystems
            and started dbus)
   stop on stopping dbus
  +stop on runlevel [06]

   expect fork
   respawn


  after applying this I get no more errors:
  * Killing all remaining processes... [OK]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/869635/+subscriptions