NM 0.7 nm-applet crash when connecting to Enterprise WiFi

[Thomas Novin]

Binary package hint: network-manager

As soon as I start nm-applet it tries to connect to a WPA/WPA2 Enterprise WiFi Network which is in range. After a while it crashes. This is very reproducible.

$ nm-applet
** Message: <info> New secrets for Auto MySSID/802-1x requested; ask the user

(nm-applet:19008): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed

(nm-applet:19008): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.18.2/gobject/gtype.c:3940: type id `0' is invalid

(nm-applet:19008): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced

$ apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20081018t105859-0ubuntu1
  Candidate: 0.7~~svn20081018t105859-0ubuntu1
  Version table:
 *** 0.7~~svn20081018t105859-0ubuntu1 0
        500 http://se.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

[Thomas Novin (thomasn80)]

Btw, tried adding debug symbols as described on https://wiki.ubuntu.com/DebuggingNetworkManager but it fails:

$ sudo apt-get install network-manager-dbgsym libnm-util0-dbgsym libnm-glib0-dbgsym libglib2.0-0-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libglib2.0-0-dbgsym: Depends: libglib2.0-0 (= 2.18.2-0ubuntu1) but 2.18.2-0ubuntu2 is to be installed
E: Broken packages

[Alexander Sack (asac)]

ThomasNovin wrote:
> Btw, tried adding debug symbols as described on
> https://wiki.ubuntu.com/DebuggingNetworkManager but it fails:
>
> $ sudo apt-get install network-manager-dbgsym libnm-util0-dbgsym libnm-glib0-dbgsym libglib2.0-0-dbgsym
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> libglib2.0-0-dbgsym: Depends: libglib2.0-0 (= 2.18.2-0ubuntu1) but 2.18.2-0ubuntu2 is to be installed
> E: Broken packages
>
>
yes its unfortunate, but true that we dont have dbgsym packages for
-updates :( ... you could try to --force-depends install the "normal"
-dbgsym packages; in mos cases that should give more or less good
result. Unfortunately, we cannot be sure then.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I think bug #296791 refers to the same error/problem, but I am not 100% sure.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Thomas Novin (thomasn80)]

That's OK, I think this problem is fixed. It's now 10 months since I did the original report.