nm-applet crashed with SIGSEGV

Bug #122765 reported by Tomcat
2
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

Tried to connect to my office wpa-psk wireless network. When clicking on the shown network, I am asked whether I want to allow the application to be allowed to access the keyring with deny, once & always, when clicking on always or once, the app crashes. This ca be reproduced on my system after a reboot.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jun 28 12:41:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nm-applet
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.6.5-0ubuntu3
PackageArchitecture: i386
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/benjy
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nm-applet crashed with SIGSEGV
Uname: Linux rapunzel 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Tomcat (bsoans) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:nmi_dbus_get_network_key_callback (result=GNOME_KEYRING_RESULT_OK, found_list=0x0, data=0x8280900) at applet-dbus-info.c:114
gnome_keyring_find_items_reply (op=0x8281b58) at gnome-keyring.c:1542
operation_io (io_channel=0x82ec0f8, cond=<value optimized out>, callback_data=0x8281b58) at gnome-keyring.c:538
g_io_unix_dispatch (source=0x82df330, callback=0xb73e50d0 <operation_io>, user_data=0x8281b58) at /build/buildd/glib2.0-2.13.5/glib/giounix.c:162
IA__g_main_context_dispatch (context=0x809c058) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2061

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.