zeitgeist-datahub crashed with SIGSEGV in g_slice_alloc()

Bug #1512367 reported by Akshay Bhat
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
New
Undecided
Unassigned

Bug Description

App crashed during normal usage

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: zeitgeist-datahub 0.9.14-2.2ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 2 09:15:56 2015
ExecutablePath: /usr/bin/zeitgeist-datahub
ProcCmdline: zeitgeist-datahub
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f2440abd645 <g_slice_alloc+117>: mov (%r12),%rax
 PC (0x7f2440abd645) ok
 source "(%r12)" (0xc3cc36cd) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: zeitgeist
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_source_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_timeout_source_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: zeitgeist-datahub crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to vivid on 2015-06-13 (142 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Akshay Bhat (nodeax-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1216751, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.