indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
Uname: Linux 3.10.9-
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 23 15:49:16 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2011-07-23 (762 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f9dd7fd4f90 <_IO_vfprintf_
PC (0x7f9dd7fd4f90) ok
source "%es:(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to saucy on 2013-07-10 (43 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd lp lpadmin netdev plugdev powerdev pulse sambashare scanner tape vboxusers video
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 #1195874, 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.