indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

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

Bug Description

This happens quite frequently, but I don't know what triggers the bug.
I have the "Show upcoming events i the Evolution calendar" enabled, Evolution is linked to my gCal. Everything seems to work as usual, even after apport offers sending the error report.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
CrashCounter: 1
Date: Fri Dec 21 11:48:45 2012
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2012-10-04 (77 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
SegvAnalysis:
 Segfault happened at: 0x406897: mov 0x8(%rax),%rcx
 PC (0x00406897) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
UpgradeStatus: Upgraded to quantal on 2012-10-17 (64 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (nvidia-settings:2690): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: «oxygen-gtk».
 (Tomboy:2692): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: «oxygen-gtk».
 (dropbox:2711): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: «oxygen-gtk».
 (gtk-window-decorator:2846): Gtk-WARNING **: Kunne ikke finne temamotor i module_path: «oxygen-gtk».
 (gnome-settings-daemon:2653): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed

Revision history for this message
Simen (simen-burud) wrote :
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 this software better. This particular crash has already been reported and is a duplicate of bug #1087410, 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.

information type: 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.