indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
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
ProcVersionSign
Uname: Linux 3.5.0-21-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
CrashCounter: 1
Date: Fri Dec 21 11:48:45 2012
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-10-04 (77 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/
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_
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to quantal on 2012-10-17 (64 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(nvidia-
(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-
(gnome-
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.