nm-applet crashed with SIGSEGV in magazine_cache_push_magazine()

[Linus Hoppe]

Crash

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: fglrx
Package: network-manager-gnome 0.7.1~rc4.1-0ubuntu2
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 magazine_cache_push_magazine (ix=1,
 IA__g_slice_free1 (mem_size=12, mem_block=0x9677b40)
 gconf_value_free () from /usr/lib/libgconf-2.so.4
 gconf_entry_unref () from /usr/lib/libgconf-2.so.4
 gconf_entry_free () from /usr/lib/libgconf-2.so.4
Title: nm-applet crashed with SIGSEGV in magazine_cache_push_magazine()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner video

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Linus Hoppe (linus-hoppe-deactivatedaccount)]

I'll attach a Valgrind log, but you should know that I can't reproduce the Crash. Apport only shows an Error on Startup that time.

Because of the fact that nothing happens after starting valgrind and the crash isn't reproducable, I killed valgrind. You find the log attached.

[Apport retracing service (apport)]

StacktraceTop:magazine_cache_push_magazine (ix=1,
IA__g_slice_free1 (mem_size=12, mem_block=0x9677b40)
gconf_value_free (value=0x9677b40) at gconf-value.c:830
gconf_entry_unref (entry=0x9680708) at gconf-value.c:1492
gconf_entry_free (entry=0x9680708) at gconf-value.c:1501

[Boniek (boniek12p)]

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 if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Boniek (boniek12p)]

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!