gnome-panel crashed with SIGSEGV in gdk_threads_dispatch()

Bug #179080 reported by Matti Lindell
8
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-panel

Ubuntu Hardy (alpha2)
Version: 1:2.20.1-0ubuntu2

ProblemType: Crash
Architecture: i386
Date: Fri Dec 28 16:47:49 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.20.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/matti
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 gdk_threads_dispatch (data=0x83a9260)
 g_idle_dispatch (source=0x83b99a8, callback=0xaaaaaaaa,
 IA__g_main_context_dispatch (context=0x80eca58)
 g_main_context_iterate (context=0x80eca58, block=1,
 IA__g_main_loop_run (loop=0x8235760)
Title: gnome-panel crashed with SIGSEGV in gdk_threads_dispatch()
Uname: Linux sandbox 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio dialout dip floppy lpadmin netdev plugdev powerdev pulse-access pulse-rt scanner src video

Tags: apport-crash
Revision history for this message
Matti Lindell (mlind) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_threads_dispatch (data=0x83a9260) at /build/buildd/gtk+2.0-2.12.3/gdk/gdk.c:470
g_idle_dispatch (source=0x83b99a8, callback=0xaaaaaaaa, user_data=0x83a9260)
IA__g_main_context_dispatch (context=0x80eca58)
g_main_context_iterate (context=0x80eca58, block=1, dispatch=1, self=0x80c6588)
IA__g_main_loop_run (loop=0x8235760)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-panel:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #123480. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, can you tell us a few steps in order to trigger the crash? thanks you.

Revision history for this message
Matti Lindell (mlind) wrote :

Sorry, I have no idea how to reproduce this. It happens very randomly, usually when CPU is under heavy load.

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.