[Pkg-utopia-maintainers] Bug#503250: network-manager segfault

Sam Morris sam at robots.org.uk
Thu Oct 23 22:38:53 UTC 2008


Package: network-manager
Version: 0.6.6-2
Severity: normal

n-m was unable to connect to an access point. After trying for a while,
the notification area icon disappeared. Then I noticed the following in
the system log:

Oct 23 20:08:15 durandal NetworkManager: <info>  SWITCH: no current connection, found better connection 'wlan0'. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Will activate connection 'wlan0/MIDGARD'. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Device wlan0 activation scheduled... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) started... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0/wireless): access point 'MIDGARD' is encrypted, but NO valid key exists.  New key needed. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) New wireless user key requested for network 'MIDGARD'. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) New wireless user key for network 'MIDGARD' received. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
Oct 23 20:08:15 durandal NetworkManager: <info>  Activation (wlan0/wireless): access point 'MIDGARD' is encrypted, and a key exists.  No new key needed. 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'AP_SCAN 1' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'ADD_NETWORK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was '0' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 4d494447415244' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0' 
Oct 23 20:08:16 durandal NetworkManager: <info>  SUP: response was 'OK' 
Oct 23 20:08:16 durandal NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
Oct 23 20:08:22 durandal NetworkManager: <info>  Old device 'wlan0' activating, won't change. 
Oct 23 20:08:43 durandal last message repeated 2 times
Oct 23 20:09:15 durandal last message repeated 3 times
Oct 23 20:09:16 durandal NetworkManager: <info>  Activation (wlan0/wireless): association took too long (>60s), failing activation. 
Oct 23 20:09:16 durandal NetworkManager: <info>  Activation (wlan0) failed for access point (MIDGARD) 
Oct 23 20:09:16 durandal NetworkManager: <info>  Activation (wlan0) failed. 
Oct 23 20:09:16 durandal NetworkManager: <info>  Deactivating device wlan0. 
Oct 23 20:09:16 durandal NetworkManager: <info>  Activation (wlan0) failure scheduled... 
Oct 23 20:09:16 durandal NetworkManager: <WARN>  nm_signal_handler(): Caught signal 11.  Generating backtrace... 
Oct 23 20:09:16 durandal NetworkManager: ******************* START **********************************
Oct 23 20:09:16 durandal NetworkManager: (no debugging symbols found)
Oct 23 20:09:16 durandal last message repeated 3 times
Oct 23 20:09:17 durandal NetworkManager: [Thread debugging using libthread_db enabled]
Oct 23 20:09:17 durandal NetworkManager: [New Thread 0x7f1cd60756e0 (LWP 3911)]
Oct 23 20:09:17 durandal NetworkManager: [New Thread 0x41ef9950 (LWP 19259)]
Oct 23 20:09:17 durandal NetworkManager: [New Thread 0x4083a950 (LWP 19256)]
Oct 23 20:09:17 durandal NetworkManager: [New Thread 0x426fa950 (LWP 4471)]
Oct 23 20:09:17 durandal NetworkManager: 0x00007f1cd4296b66 in poll () from /lib/libc.so.6
Oct 23 20:09:17 durandal NetworkManager: ******************* END **********************************

Unfortunately I was not able to reproduce the crash, so filing with a
low severity.

It would be nice if n-m shipped a -dbg package so that the
automatically-captured backtraces would be more useful. :)

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                       3.110      add and remove users and groups
ii  dbus                          1.2.1-3    simple interprocess messaging syst
ii  dhcdbd                        3.0-4      D-Bus interface to the ISC DHCP cl
ii  hal                           0.5.11-5   Hardware Abstraction Layer
ii  ifupdown                      0.6.8+nmu1 high level tools to configure netw
ii  iproute                       20080725-2 networking and traffic control too
ii  libc6                         2.7-14     GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.1-3    simple interprocess messaging syst
ii  libdbus-glib-1-2              0.76-1     simple interprocess messaging syst
ii  libgcrypt11                   1.4.1-1    LGPL Crypto library - runtime libr
ii  libglib2.0-0                  2.16.6-1   The GLib library of C routines
ii  libgpg-error0                 1.4-2      library for common error values an
ii  libhal1                       0.5.11-5   Hardware Abstraction Layer - share
ii  libiw29                       29-1.1     Wireless tools - library
ii  libnl1                        1.1-2      library for dealing with netlink s
ii  libnm-util0                   0.6.6-2    network management framework (shar
ii  lsb-base                      3.2-20     Linux Standard Base 3.2 init scrip
ii  wpasupplicant                 0.6.4-2    Client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  network-manager-gnome         0.6.6-2    network management framework (GNOM

network-manager suggests no packages.

-- no debconf information





More information about the Pkg-utopia-maintainers mailing list