baloo_file crashed with SIGSEGV in ChertTable::find_in_block()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
baloo (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 6 23:59:47 2014
ExecutablePath: /usr/bin/baloo_file
InstallationDate: Installed on 2014-04-06 (0 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.2)
ProcCmdline: /usr/bin/baloo_file
ProcEnviron:
LANGUAGE=fr_FR
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f74c5429c3f <_ZN10ChertTabl
PC (0x7f74c5429c3f) ok
source "0x9(%rdi)" (0x00000049) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
StacktraceTop:
ChertTable:
ChertTable:
ChertCursor:
?? () from /usr/lib/
?? () from /usr/lib/
Title: baloo_file crashed with SIGSEGV in ChertTable:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip 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 #1300413, 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.