clock-applet crashed with SIGSEGV in g_main_context_dispatch()

Bug #547198 reported by TheBeest
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: gnome-panel

Tried to add a location for the weather report and the clock crashed.

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 25 19:38:18 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gnome-panel/clock-applet
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Package: gnome-panel 1:2.29.92.1-0ubuntu3
ProcCmdline: /usr/lib/gnome-panel/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=34
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7fbcd4d35671: cmpq $0x0,(%rax)
 PC (0x7fbcd4d35671) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 ?? () from /usr/lib/libsoup-2.4.so.1
 g_main_context_dispatch ()
Title: clock-applet crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1390): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gimp-2.6:1822): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
 (gimp-2.6:1822): Gtk-WARNING **: Attempting to add a widget with type GtkHBox to a GtkFrame, but as a GtkBin subclass a GtkFrame can only contain one widget at a time; it already contains a widget of type GtkHBox
 (gimp-2.6:1822): Gtk-CRITICAL **: gtk_box_pack: assertion `child->parent == NULL' failed
 (gnome-terminal:2301): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Revision history for this message
TheBeest (thebeest) wrote :
TheBeest (thebeest)
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

I am unable to confirm this issue under Lucid with gnome-panel 2.29.92.1-0ubuntu3, all works fine here. What version of gnome-panel do you have? Thanks!

Changed in gnome-panel (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
TheBeest (thebeest) wrote :

I have gnome-panel 1:2.29.92.1-0ubuntu3 and it hasn't been upgraded since i had the problem. Maybe its because i am running on amd64? Any help would be good!

Cheers

Revision history for this message
bcbc (bcbc) wrote :

Same thing happened to me after adding 5 new locations. Not using amd64. I couldn't reproduce the bug, either by adding additional locations, or removing all but the default and adding back the ones that caused the first crash.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 auth_required (session=0x2031440, msg=0x20b5440,
 soup_socket_connect_async (sock=0x205d210,
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-panel (Ubuntu):
importance: Low → Medium
tags: removed: need-amd64-retrace
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.