[Intrepid] nm-applet crashed with SIGSEGV when connecting to WPA network (in g_slist_append())

[David McBride]

Attemping to connect to the UK "eduroam" wireless network (which appears to use the "WPA / WPA2 Enterprise", "Tunnelled TLS", and "MSCHAPv2" options) results in a crash after saying "Ignore" to the "You haven't set a CA certificate.." dialog.

This crash appears to occur every time, i.e. it's not a Heisenbug.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nm-applet
Package: network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: nm-applet
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 g_slist_append () from /usr/lib/libglib-2.0.so.0
 ws_wpa_fill_default_ciphers ()
 nma_wireless_dialog_get_connection ()
 ?? ()
 g_closure_invoke ()
Title: nm-applet crashed with SIGSEGV in g_slist_append()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:IA__g_slist_append (list=0x200200000074, data=0x245a420)
ws_wpa_fill_default_ciphers (connection=<value optimized out>) at wireless-security.c:192
nma_wireless_dialog_get_connection (self=<value optimized out>, device=0x7fff5d210110,
wireless_dialog_response_cb (foo=0x1bb1730, response=-5, user_data=0x1b220a0)
IA__g_closure_invoke (closure=0x2456fe0, return_value=0x0, n_param_values=2,

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.