network-manager does not recognize usb modem when it is plugged in again

1. please do https://wiki.ubuntu.com/DebuggingModemmanager

2. also check whether you can make your modem work again if you run "sudo killall modem-manager" before plugging your device in after unplugging
2a. also check whether you can make your modem work again if you run "sudo killall modem-manager" after plugging your device in after unplugging

3. run apport-collect 446695 to attach more valuable input.

Thanks!

Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
Gconf:

IpRoute:
 192.168.123.0/24 dev eth0 proto kernel scope link src 192.168.123.141 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.123.254 dev eth0 proto static
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20091008t231804.c31b3e4-0ubuntu1~nmt1
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers
WpaSupplicantLog:

XsessionErrors: (polkit-gnome-authentication-agent-1:2244): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

I've done the debugging you've requested:

1.) I've installed the packages from trunk and run the test. I'll attach the log files.

You will see in the log of modem-manager that there are some critical errors when I remove the modem. After that it finds the modem when it is plugged in again, but cannot initialize it.

2.) If I kill the modem-manager (before/after plugging in the device again) then nm-applet shows the modem again, but when I try to connect the modem to the network, Network-Manager goes wild with lots of error messages (see log) and uses 100% CPU time.

(ttyUSB0): device state change: 3 -> 4 (reason 0)
(ttyUSB0): device state change: 4 -> 6 (reason 0)
(ttyUSB0): device state change: 6 -> 4 (reason 0)
...

I can only kill network-manager in this case.

Hope this helps finding the problem.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 446146, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.