indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Linux kylea-hpxt 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:21:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
ProcVersionSign
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 28 20:38:59 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationDate: Installed on 2013-03-22 (159 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130319)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcCwd: /home/kylea
SegvAnalysis:
Segfault happened at: 0x7f3618bc6f90 <_IO_vfprintf_
PC (0x7f3618bc6f90) 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-08-28 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers
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.