Suzan's ifconfig trick does indeed work! I also got some libpulse updates from Daniel's repository so I tried with and without the ifconfig in alsa-utils. Without gives the shutdown delay, with does work fine.
Still unclear to me why the network interface influences alsa. If all is up and running (so network interfaces not shut down), shutting down alsa within Gnome works fine.
A wild guess:
- either the shut down of Gnome (a few steps before) is not complete. The nm resets the network to an initial state but does not shutdown the interfaces.
- or there's a nasty dependency between alsa and nm. For some reason alsa needs a fully configured network, or no network at all. A half configured network (up, but no IP address) causes delays for each control.
Suzan's ifconfig trick does indeed work! I also got some libpulse updates from Daniel's repository so I tried with and without the ifconfig in alsa-utils. Without gives the shutdown delay, with does work fine.
Still unclear to me why the network interface influences alsa. If all is up and running (so network interfaces not shut down), shutting down alsa within Gnome works fine.
A wild guess:
- either the shut down of Gnome (a few steps before) is not complete. The nm resets the network to an initial state but does not shutdown the interfaces.
- or there's a nasty dependency between alsa and nm. For some reason alsa needs a fully configured network, or no network at all. A half configured network (up, but no IP address) causes delays for each control.
Just a guess of course ;)