Public bug reported:
Binary package hint: network-manager
Upgraded from Feisty to Gutsy, on startup the NetworkManagerDispatcher
process is using whatever CPU it can to push the CPU usage up to 100%.
Upon stopping the process, there is a wired network connect active
(which I don't have) instead of the wireless connection (which I do
have). Switching to wireless connection works.
I understand this may have something to do with the file:
/etc/NetworkManager/dispatcher.d/01ifupdown
so I am pasting its contents herein:
#!/bin/sh -e
# Script to dispatch NetworkManager events
#
# Runs ifupdown scripts when NetworkManager fiddles with interfaces.
if [ -z "$1" ]; then
echo "$0: called with no interface" 1>&2
exit 1;
fi
# Fake ifupdown environment
export IFACE="$1"
export LOGICAL="$1"
export ADDRFAM="NetworkManager"
export METHOD="NetworkManager"
export VERBOSITY="0"
# Run the right scripts
case "$2" in
up)
export MODE="start"
export PHASE="up"
exec run-parts /etc/network/if-up.d
;;
down)
export MODE="stop"
export PHASE="down"
exec run-parts /etc/network/if-down.d
;;
pre-up)
export MODE="start"
export PHASE="pre-up"
exec run-parts /etc/network/if-pre-up.d
;;
post-down)
export MODE="stop"
export PHASE="post-down"
exec run-parts /etc/network/if-post-down.d
;;
*)
echo "$0: called with unknown action \`$2'" 1>&2
exit 1
;;
esac
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: cpu gutsy network-manager
** Tags added: cpu gutsy network-manager
--
NetworkManagerDispatcher uses 100% CPU on startup
https://bugs.launchpad.net/bugs/123332
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
