nm-applet crashed with SIGSEGV

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

Bug Description

When I start the System I am asked to let the /usr/bin/nm-applet to acess or not the key ring. When I press the "always allow", the nm-applet crash and I cant acess the internet. I only can acess the internet when I press the button "don't let the acess", when I restart my system.

I use Ubuntu Gutsy 7.10 and nm-applet 0.6.5.

ProblemType: Crash
Architecture: i386
Date: Wed Jun 27 13:07:01 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nm-applet
NonfreeKernelModules: cdrom
Package: network-manager-gnome 0.6.5-0ubuntu3
PackageArchitecture: i386
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/paozinho
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nm-applet crashed with SIGSEGV
Uname: Linux paozinho-laptop 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
paozinho (paonoforno) 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=0x84cdee0) at applet-dbus-info.c:117
gnome_keyring_find_items_reply (op=0x84cb690) at gnome-keyring.c:1542
operation_io (io_channel=0x84cb500, cond=<value optimized out>, callback_data=0x84cb690) at gnome-keyring.c:538
g_io_unix_dispatch (source=0x84cdb58, callback=0xb735c0d0 <operation_io>, user_data=0x84cb690) at /build/buildd/glib2.0-2.13.5/glib/giounix.c:162
IA__g_main_context_dispatch (context=0x809dc98) 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.