nm-applet crashed with SIGSEGV in applet_find_active_connection_for_device()

Bug #321273 reported by Per Ångström
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This could be a dupe of bug #261921, but that was in 8.10 and this is in 9.04 Alpha 3, so I'm opening a new bug.

I had created a new wireless network, and now I was trying to connect to that same network, on the same machine. And nm-applet crashed.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
Package: network-manager-gnome 0.7-0ubuntu1
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 applet_find_active_connection_for_device ()
 ?? ()
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: nm-applet crashed with SIGSEGV in applet_find_active_connection_for_device()
Uname: Linux 2.6.28-4-generic x86_64
UserGroups: adm audio cdrom dialout dip fax floppy fuse plugdev tape video

Tags: apport-crash
Revision history for this message
Per Ångström (autark) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:applet_find_active_connection_for_device (
applet_update_icon (user_data=<value optimized out>)
IA__g_main_context_dispatch (context=0x1ba6f10)
g_main_context_iterate (context=0x1ba6f10, block=1,
IA__g_main_loop_run (loop=0x1c599f0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in network-manager-applet:
importance: Undecided → Medium
Revision history for this message
Oliver Joos (oliver-joos) wrote :

I am using 9.04 stable since one month and boot it from an USB stick with a persistent partition on it. (still testing some ATI issues)

Today I added jaunty-backports and jaunty-proposed as package sources. A few reboots later the nm-applet failed to start and crashed like described by this bug. Restarting it manually in a terminal worked. Logout and in again made it start as usual.

This happened the first time. I'll add another comment if it gets reproduceable.

Revision history for this message
Alexander Sack (asac) wrote :

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

Changed in network-manager-applet (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.