mixer_applet2 crashed with SIGSEGV in gtk_widget_get_toplevel()

[hwasung]

Binary package hint: gnome-applets

I don't know. I noticed an error message when my laptop were just booted.

ProblemType: Crash
Architecture: i386
Date: Wed Jun 27 22:50:08 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/gnome-applets/mixer_applet2
NonfreeKernelModules: cdrom
Package: gnome-applets 2.18.0-3ubuntu5
PackageArchitecture: i386
ProcCmdline: /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-iid=OAFIID:GNOME_MixerApplet_Factory --oaf-ior-fd=19
ProcCwd: /
ProcEnviron:
 LANG=ko_KR.UTF-8
 LANGUAGE=ko_KR.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-applets
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: mixer_applet2 crashed with SIGSEGV in gtk_widget_get_toplevel()
Uname: Linux mars 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 plugdev scanner video

[Apport retracing service (apport)]

StacktraceTop:gtk_widget_get_screen_unchecked (widget=0xaaaaaaaa) at /build/buildd/gtk+2.0-2.11.4/gtk/gtkwidget.c:6169
IA__gtk_widget_get_screen (widget=0x81c09a0) at /build/buildd/gtk+2.0-2.11.4/gtk/gtkwidget.c:6206
gtk_rc_reset_widgets (settings=0x80a2020) at /build/buildd/gtk+2.0-2.11.4/gtk/gtkrc.c:1658
_gtk_rc_context_get_default_font_name (settings=0x80a2020) at /build/buildd/gtk+2.0-2.11.4/gtk/gtkrc.c:1758
gtk_rc_font_name_changed (settings=0x80a2020, pspec=0x808e730, context=0x80a4300) at /build/buildd/gtk+2.0-2.11.4/gtk/gtkrc.c:695

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=452003

[nullack (nullack)]

I haven't had a repeat occurrence of this bug in sometime. I intend to close the bug unless another tester on the current Intrepid build is able to replicate the problem. Please advise, thanks.

[nullack (nullack)]

Im moving this to fixed released as there has been numerous updates, and no testers have reported the issue as still occurring.