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
Happens occasionally, already in 12.10.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily13.
ProcVersionSign
Uname: Linux 3.8.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Thu Mar 7 15:58:22 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-01-03 (62 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=de_DE.UTF-8
SegvAnalysis:
Segfault happened at: 0x4061ff: mov 0x0(%rbp),%rdi
PC (0x004061ff) ok
source "0x0(%rbp)" (0x00000026) not located in a known VMA region (needed readable region)!
destination "%rdi" 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 raring on 2013-03-07 (0 days ago)
UserGroups: adm audio cdrom dip disk lpadmin plugdev sambashare sudo vboxusers video
XsessionErrors:
(gnome-
(gnome-
(gnome-
(tracker-
(evolution-
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 #1098812, 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.