NM 0.7: applet does not react if "Auto GSM network connection" is selected too fast

Binary package hint: network-manager

When I connect a Nokia E70 to a Dell X1 (Iintrepid) via USB, I usually get the following syslog while Ubuntu detects the modem:

Sep 20 00:12:08 darkly kernel: [ 2756.184186] usb 1-2: new full speed USB device using uhci_hcd and address 9
Sep 20 00:12:08 darkly kernel: [ 2756.365901] usb 1-2: configuration #1 chosen from 1 choice
Sep 20 00:12:08 darkly kernel: [ 2756.393520] cdc_acm 1-2:1.12: ttyACM0: USB ACM device
Sep 20 00:12:08 darkly kernel: [ 2756.402630] usb 1-2: bad CDC descriptors
Sep 20 00:12:08 darkly kernel: [ 2756.403155] usb 1-2: bad CDC descriptors
Sep 20 00:12:11 darkly NetworkManager: <debug> [1221862331.204174] probe_modem(): Found GSM modem
Sep 20 00:12:11 darkly NetworkManager: <info> ttyACM0: driver is 'cdc_acm'.
Sep 20 00:12:11 darkly NetworkManager: <debug> [1221862331.226792] setup_monitor_device(): No monitoring udi provided
Sep 20 00:12:11 darkly NetworkManager: <info> Found new Modem device 'ttyACM0'.
Sep 20 00:12:11 darkly NetworkManager: <info> (ttyACM0): exported as /org/freedesktop/Hal/devices/usb_device_421_418_noserial_if0_2_serial_unknown_0
Sep 20 00:12:12 darkly NetworkManager: <WARN> impl_manager_activate_connection(): Connection (2) /org/freedesktop/NetworkManagerSettings/0 failed to activate: (2) Device not managed by NetworkManager
Sep 20 00:12:15 darkly NetworkManager: <info> (ttyACM0): device state change: 1 -> 2
Sep 20 00:12:15 darkly NetworkManager: <info> (ttyACM0): deactivating device.
Sep 20 00:12:15 darkly NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Sep 20 00:12:15 darkly NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Sep 20 00:12:15 darkly NetworkManager: <info> (ttyACM0): device state change: 2 -> 3

As you can see, the process takes about 7 seconds.

The (minor) problem: The option "Auto GSM network connection" is present from nearly the beginning of the detection process. If a user is fast enough to activate the option during the 7 seconds, NM applet will not react. If the user re-tries after the detection is complete, all works well.

I suggest: either the option should only be present if detection is fully complete, or the activation event should be buffered and be executed after detection is complete. Just swallowing the event unsettles the user.