indicator-datetime-service crashed with SIGSEGV in g_object_ref()
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+
ProcVersionSign
Uname: Linux 3.10.0-6-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Wed Jul 31 16:05:21 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-03-30 (123 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130328)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=it_IT
LANG=it_IT.UTF-8
SegvAnalysis:
Segfault happened at: 0xb74400ee <g_object_ref+30>: cmpl $0x50,(%eax)
PC (0xb74400ee) ok
source "$0x50" ok
destination "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
g_object_ref () from /usr/lib/
g_weak_ref_get () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/i386-
g_main_
Title: indicator-
UpgradeStatus: Upgraded to saucy on 2013-05-21 (70 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
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 #1197645, 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.