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

Bug #762804 reported by SaCroJazz
104
This bug affects 18 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Incomplete
Medium
Unassigned
indicator-datetime (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: indicator-datetime

After login, logout, and login again indicator-time crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 16 11:26:01 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=es_ES.UTF-8
 LANGUAGE=es:en
 LANG=es_CL.UTF-8
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-service crashed with SIGABRT in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:
 datetime_interface_update (self=0xa3fd80) at datetime-interface.c:201
 session_active_change_cb (proxy=<value optimized out>, sender_name=<value optimized out>, signal_name=<value optimized out>, parameters=0xa780f0, user_data=0xa3fd80) at datetime-service.c:1211
 g_closure_invoke (closure=0x7f3f34002fc0, return_value=0x0, n_param_values=4, param_values=0xa9eea0, invocation_hint=0x7ffffd838900) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0xa92200, emission_return=0x0, instance_and_params=0xa9eea0) at /build/buildd/glib2.0-2.28.5/./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.5/./gobject/gsignal.c:2983

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 indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Charles Kerr (charlesk) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in indicator-datetime:
status: New → Incomplete
importance: Undecided → Medium
Charles Kerr (charlesk)
Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
Charles Kerr (charlesk)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.]

Changed in indicator-datetime (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Antonio Carlos Santos Galvão (ancasaga) wrote :

O indicador de data e tempo parou de funcionar e desapareceu do painel. APos pedir para reexecutar, tornou a funcionar. como faço para ativa-lo pelo terminal??

Revision history for this message
Bill (billsalatino-gmail) wrote :

thanks for your efforts, I hope it will br fine soon.

Revision history for this message
WoolF (woolf911) wrote :

Ubuntu 14.04 have this bug too.

Revision history for this message
Charles Kerr (charlesk) wrote :

@Woolf: session_active_change_cb() no longer exists in indicator-datetime-service, so I doubt it's the same bug. If I had to guess, you're probably experiencing bug #1283834 which is fixed now. If you still get a crash, please file a new ticket. Thanks!

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.