Public bug reported:
Binary package hint: network-manager
Every time NetworkManager (as of 9/13 code all up to date), it crashes after
association timeout:
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) started...
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) Stage 1 of 5
(Device Prepare) scheduled...
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) Stage 1 of 5
(Device Prepare) started...
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) Stage 2 of 5
(Device Configure) scheduled...
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) Stage 1 of 5
(Device Prepare) complete.
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0) Stage 2 of 5
(Device Configure) starting...
Sep 13 10:00:24 vorfeed NetworkManager: <info> Activation (ath0/wireless):
access point '<ESSID>' is encrypted, and a key exists. No new key needed.
Sep 13 10:00:25 vorfeed NetworkManager: <info> supplicant_interface_init() -
connect to global ctrl socket (0/10).
Sep 13 10:00:25 vorfeed NetworkManager: <info> supplicant_interface_init() -
connect to global ctrl socket (1/10).
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'INTERFACE_ADD ath0^I^Imadwifi^I/var/run/wpa_supplicant3^I'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> supplicant_init() - connect to
device ctrl socket (3/10).
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command 'AP_SCAN
2'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was '0'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid <SSID>'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 scan_ssid 1'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt IEEE8021X'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 eap LEAP'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 identity "<identity>"
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 password <password>'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Sep 13 10:00:25 vorfeed NetworkManager: <info> SUP: response was 'OK'
Sep 13 10:00:25 vorfeed NetworkManager: <info> Activation (ath0) Stage 2 of 5
(Device Configure) complete.
Sep 13 10:00:26 vorfeed avahi-daemon[5846]: Registering new address record for
fe80::219:7dff:fe88:fd31 on ath0.*.
Sep 13 10:02:25 vorfeed NetworkManager: <info> Activation (ath0/wireless):
association took too long (>120s), failing activation.
Sep 13 10:02:25 vorfeed NetworkManager: <info> Activation (ath0) failure
scheduled...
Sep 13 10:02:25 vorfeed NetworkManager: <info> Activation (ath0) failed for
access point (IBM)
Sep 13 10:02:25 vorfeed NetworkManager: <info> Activation (ath0) failed.
Sep 13 10:02:25 vorfeed NetworkManager: <info> Deactivating device ath0.
Sep 13 10:02:25 vorfeed NetworkManager: <info> SUP: sending command
'DISABLE_NETWORK 0'
Sep 13 10:02:37 vorfeed NetworkManager: <info> SUP: response was
'TIMEOUT[CLI]'
Sep 13 10:02:37 vorfeed NetworkManager: <WARN>
nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error
for 'DISABLE_NETWORK 0'. Response: 'TIMEOUT[CLI]'
Sep 13 10:02:37 vorfeed NetworkManager: <WARN> supplicant_cleanup():
supplicant_cleanup - couldn't disable network in supplicant_cleanup
Sep 13 10:02:37 vorfeed NetworkManager: <info> SUP: sending command 'AP_SCAN
0'
Sep 13 10:02:49 vorfeed NetworkManager: <info> SUP: response was
'TIMEOUT[CLI]'
Sep 13 10:02:49 vorfeed NetworkManager: <WARN>
nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error
for 'AP_SCAN 0'. Response: 'TIMEOUT[CLI]'
Sep 13 10:02:49 vorfeed NetworkManager: <WARN> supplicant_cleanup():
supplicant_cleanup - couldn't set AP_SCAN 0
Sep 13 10:02:49 vorfeed NetworkManager: <info> SUP: sending command
'TERMINATE'
Sep 13 10:02:51 vorfeed avahi-daemon[5846]: Withdrawing address record for
fe80::219:7dff:fe88:fd31 on ath0.
Sep 13 10:02:51 vorfeed avahi-autoipd(ath0)[6226]: SIOCSIFFLAGS failed:
Permission denied
Sep 13 10:02:51 vorfeed avahi-autoipd(ath0)[6226]: Callout STOP, address
169.254.7.149 on interface ath0
Sep 13 10:02:51 vorfeed dhclient: receive_packet failed on ath0: Network is down
Sep 13 10:02:51 vorfeed avahi-autoipd(ath0)[6227]: client: RTNETLINK answers:
Cannot assign requested address
Sep 13 10:02:51 vorfeed avahi-autoipd(ath0)[6227]: Script execution failed with
return value 2
Sep 13 10:03:01 vorfeed NetworkManager: <info> SUP: response was
'TIMEOUT[CLI]'
Sep 13 10:03:01 vorfeed NetworkManager: <WARN>
nm_utils_supplicant_request_with_check(): supplicant_cleanup: supplicant error
for 'TERMINATE'. Response: 'TIMEOUT[CLI]'
Sep 13 10:03:01 vorfeed NetworkManager: <WARN> supplicant_cleanup():
supplicant_cleanup - couldn't terminate wpasupplicant cleanly.
Sep 13 10:03:01 vorfeed NetworkManager: <WARN> nm_signal_handler(): Caught
signal 11. Generating backtrace...
Sep 13 10:03:02 vorfeed NetworkManager: ******************* START
**********************************
Sep 13 10:03:02 vorfeed NetworkManager: (no debugging symbols found)
Sep 13 10:03:02 vorfeed NetworkManager: Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
Sep 13 10:03:02 vorfeed NetworkManager: (no debugging symbols found)
Sep 13 10:03:02 vorfeed last message repeated 13 times
Sep 13 10:03:02 vorfeed NetworkManager: [Thread debugging using libthread_db
enabled]
Sep 13 10:03:02 vorfeed NetworkManager: [New Thread -1212745280 (LWP 5430)]
Sep 13 10:03:02 vorfeed NetworkManager: [New Thread -1229534320 (LWP 6430)]
Sep 13 10:03:02 vorfeed NetworkManager: [New Thread -1221141616 (LWP 5553)]
Sep 13 10:03:02 vorfeed NetworkManager: [New Thread -1212748912 (LWP 5549)]
Sep 13 10:03:02 vorfeed NetworkManager: (no debugging symbols found)
Sep 13 10:03:02 vorfeed last message repeated 3 times
Sep 13 10:03:02 vorfeed NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Sep 13 10:03:02 vorfeed NetworkManager: ******************* END
**********************************
I do not know the correct way in this context to put in code that has the
debugging symbols for a better stack trace. Let me know how for more info if
this is insuffiecient.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] NetworkManager crashes on LEAP attempt
https://bugs.launchpad.net/bugs/139387
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
