gnome-panel crashed with SIGSEGV in g_main_context_dispatch()

Bug #207954 reported by kakukri
148
This bug affects 12 people
Affects Status Importance Assigned to Milestone
GNOME Panel
Fix Released
Critical
gnome-panel (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

It is the same as bug #206774, but since todays update it automatically created a crash report, which might help to analyze the problem.

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 27 21:38:08 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.22.0-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: gnome-panel --sm-client-id default1
ProcEnviron:
 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: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/gnome-panel/libclock-applet.so
 ?? () from /usr/lib/gnome-panel/libclock-applet.so
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: gnome-panel crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

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

StacktraceTop:highlight (user_data=<value optimized out>) at clock-map.c:671
g_timeout_dispatch (source=0xe4b570, callback=0, user_data=0x0)
IA__g_main_context_dispatch (context=0x6c8710)
g_main_context_iterate (context=0x6c8710, block=1, dispatch=1,
IA__g_main_loop_run (loop=0x8b17b0) at /build/buildd/glib2.0-2.16.1/glib/gmain.c:2844

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-panel:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, that's known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=523964

Changed in gnome-panel:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in gnome-panel:
status: Unknown → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue has been fixed before hardy

Changed in gnome-panel:
status: Triaged → Fix Released
Changed in gnome-panel:
status: Invalid → Fix Released
Revision history for this message
Simon Baconnais (smon-deactivatedaccount) wrote :

I still affected

Revision history for this message
Simon Baconnais (smon-deactivatedaccount) wrote :

Oups ... That's an old bug report :P

I'm affected with Lucid

Changed in gnome-panel (Ubuntu):
status: Fix Released → New
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Please don't open old bug reports because you think you might have a similar issue. Please use apport to submit a new report and let the retracer handle that

Changed in gnome-panel (Ubuntu):
status: New → Fix Released
Changed in gnome-panel:
importance: Unknown → Critical
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.