nm-applet crashed with SIGSEGV in nma_marshal_VOID__OBJECT_STRING_POINTER_BOOLEAN_POINTER()

[Mathieu Marquer]

NM didn't appear after starting my session. So I logged out then logged in again, and the crash report appeared (but NM had correctly been launched this time)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
InterestingModules: b 4 4
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.7~~svn20080907t033843-0ubuntu2 [modified: usr/bin/nm-connection-editor usr/bin/nm-applet]
ProcAttrCurrent: unconfined
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 nma_marshal_VOID__OBJECT_STRING_POINTER_BOOLEAN_POINTER ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: nm-applet crashed with SIGSEGV in nma_marshal_VOID__OBJECT_STRING_POINTER_BOOLEAN_POINTER()
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape video

[Apport retracing service (apport)]

StacktraceTop:nma_marshal_VOID__OBJECT_STRING_POINTER_BOOLEAN_POINTER (closure=0xa0470d0, return_value=0x0,
IA__g_closure_invoke (closure=0xa0470d0, return_value=0x0, n_param_values=6,
signal_emit_unlocked_R (node=0xa04cc08, detail=0, instance=0xa044250, emission_return=0x0,
IA__g_signal_emit_valist (instance=0xa044250, signal_id=164, detail=0,
IA__g_signal_emit (instance=0xa044250, signal_id=164, detail=0)

[Austin Lund (austin-lund)]

This bug got me too.

My RF kill switch had disabled my wireless. I turned it on, and then my X session seemed to freeze and the network manager disappeared. I killed X (Ctrl-Alt-Backspace) and logged in again to find a core dump waiting for me.

I have an identical stacktrace.

[Alexander Sack (asac)]

> This bug got me too.

I dont see anything in this bug about a freeze. please dont post stuff to random bugs. if you dont find a perfect match just open anew ones. freezes are always driver issues. so please directly report it against "linux" package

[Alexander Sack (asac)]

closing old crash reports that didn't catch any duplicates for a while. If you have a way to reproduce reliably please reopen.