indicator-datetime-service crashed with SIGABRT in g_closure_invoke()

Bug #794212 reported by Cristian Aravena Romero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: indicator-datetime

1) Close session of Gnome
2) Open session
3) Open apport

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Tue Jun 7 15:05:03 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=es_CL:en
 LANG=es_CL.UTF-8
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke (closure=0x1ddf660, return_value=0x0, n_param_values=4, param_values=0x7f74240019e0, invocation_hint=0x7fffbdc2b160) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x1d9c9d0, emission_return=0x0, instance_and_params=0x7f74240019e0) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:2983
Title: indicator-datetime-service crashed with SIGABRT in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-06-03 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XsessionErrors: (<unknown>:5006): GLib-CRITICAL **: g_markup_escape_text: assertion `text != NULL' failed

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #762804, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
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.