indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()

Bug #864530 reported by bennomaria on 2011-10-02
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
indicator-datetime (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-datetime 0.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Sun Oct 2 11:41:44 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
Signal: 5
SourcePackage: indicator-datetime
 ?? ()
 ?? ()
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/
 ffi_call () from /usr/lib/i386-linux-gnu/
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/
Title: indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()
UpgradeStatus: No upgrade log present (probably fresh install)

bennomaria (benno-m) wrote :

 datetime_interface_update (self=0x8f894a0) at /build/buildd/indicator-datetime-0.3.0/./src/datetime-interface.c:201
 session_active_change_cb (user_data=0x8f894a0, proxy=<optimized out>, sender_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>) at /build/buildd/indicator-datetime-0.3.0/./src/datetime-service.c:1229
 session_active_change_cb (proxy=0x8f9cd20, sender_name=0x8f84738 ":1.18", signal_name=0x8fa32c0 "SystemIdleHintChanged", parameters=0x8fabd18, user_data=0x8f894a0) at /build/buildd/indicator-datetime-0.3.0/./src/datetime-service.c:1221
 ffi_call_SYSV () at ../src/x86/sysv.S:64
 ffi_call (cif=0xbf8821f0, fn=0x804ece0 <session_active_change_cb>, rvalue=0xbf8821a0, avalue=0xbf882140) at ../src/x86/ffi.c:303

Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
visibility: private → public
Olli Ries (ories) wrote :

please reopen if problem still exists

Changed in indicator-datetime:
status: New → Incomplete
tags: added: precise
Pierre Demathieu fr91 (pdm4-b) wrote :

It happens at Restart_after_suspend.

Paul Larson (pwlars) on 2013-10-15
Changed in indicator-datetime:
status: Incomplete → Confirmed
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
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.

In particular, the code listed in this ticket's backtrace -- datetime-indicator.c -- no longer exists in newer versions of Ubuntu.

 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: Confirmed → Incomplete
Changed in indicator-datetime (Ubuntu):
status: Confirmed → Incomplete
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
Launchpad Janitor (janitor) wrote :

[Expired for Indicator Date and Time because there has been no activity for 60 days.]

Changed in indicator-datetime:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers