baloo_file_extractor crashed with SIGSEGV in size()

Bug #1301742 reported by Tom H on 2014-04-03
188
This bug affects 34 people
Affects Status Importance Assigned to Milestone
baloo (Ubuntu)
Medium
Unassigned

Bug Description

No idea

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Apr 3 01:23:48 2014
ExecutablePath: /usr/bin/baloo_file_extractor
ProcCmdline: /usr/bin/baloo_file_extractor 1193 1192 1191 1190 1189 1188 1187 1186 1185 1184 1183 1182 1181 1180 1179 1175 1170 1169 1168 1167 1165 1164 1162 1161 1160 1159 1158 1157 1156 1155 1154 1153 1152 1151 1150 1149 1148 1147 1146 1145
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffb1505de78 <_ZNK6Xapian8Database12get_documentEj+8>: mov 0x10(%rsi),%rcx
 PC (0x7ffb1505de78) ok
 source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
Stacktrace:
 #0 0x00007ffb1505de78 in Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 No symbol table info available.
 #1 0x0000000000408f2e in _start ()
 No symbol table info available.
StacktraceTop:
 Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 _start ()
Title: baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Tom H (tomh0665) wrote :

StacktraceTop:
 size (this=<optimized out>, this=<optimized out>) at /usr/include/c++/4.8/bits/stl_vector.h:646
 Xapian::Database::get_document (this=0x0, did=1193) at ../api/omdatabase.cc:439
 Baloo::App::processNextUrl (this=0x7fff567f2990) at ../../../../src/file/extractor/app.cpp:129
 QObject::event (this=0x7fff567f2990, e=<optimized out>) at kernel/qobject.cpp:1194
 QApplicationPrivate::notify_helper (this=this@entry=0x19c78a0, receiver=receiver@entry=0x7fff567f2990, e=e@entry=0x1b76650) at kernel/qapplication.cpp:4567

Changed in baloo (Ubuntu):
importance: Undecided → Medium
summary: - baloo_file_extractor crashed with SIGSEGV in
- Xapian::Database::get_document()
+ baloo_file_extractor crashed with SIGSEGV in size()
tags: removed: need-amd64-retrace
information type: Private → Public
Tom H (tomh0665) wrote :

Sorry. I was in a hurry when I "filed" this bug report.

I was in the LightDM section of the KDE System Settings when the "you've crashed" dialog appeared.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in baloo (Ubuntu):
status: New → Confirmed
Harald Sitter (apachelogger) wrote :

Do you still get this crash with 4:4.12.97-0ubuntu2?

Changed in baloo (Ubuntu):
status: Confirmed → Incomplete

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
  The crash occurred under KDELibs version 4.12.07.

uname -a == "Linux sherlock 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4
06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"

Though I have gotten the same seg fault before, it is not reliably
reproducible on demand. Sorry about that

One issue I discovered late yesterday is a soft error on one of the two
drives in the raid 0 (mdadm) that comprises my home. The drive passes
the full smart diagnostics so I'm not sure if it relates as the time of
the soft error is not the same as the time of the seg fault. Of course,
this does not mean they are unrelated, only that I'm not seeing any
relationship.

Please let me know if there's anything you need, or want, me to do
regarding assisting with this or any other issue? I'd be happy to run
any tests you need.

Also, I've been upgrading as per the updater reminders; would it be
helpful if I do get another problem if I leave the system in the same state?

Thanks!

In Peace
Rich Wallick
503.324.9189

On 04/08/2014 03:30 AM, Harald Sitter wrote:
> Do you still get this crash with 4:4.12.97-0ubuntu2?
>
> ** Changed in: baloo (Ubuntu)
> Status: Confirmed => Incomplete
>

- --
Puritanism, the haunting fear that someone somewhere may be happy.
  -- H. L. Mencken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTRAA/AAoJEPcEvC/5KGke0yEIAKNCBnfq13aOgYlsGYyaHpM8
m96bHlQKw7IOFYd58PYYe3887zHeR/H+DRU3phOFu+v53jwudKP9Ba/3RDMWNGcc
dDo6kLXPPe7tZuRKu4ek1hjqaCe23TeoKueYtYdIBnR0Ca3cDWmi4a+vZYFUgChD
7CZY2E72rc0rSU5+yRWQdDVg+xwHL8F2wv8g2/qu+/t2mLNXoSoLRwCAgIgGalcy
xauOqx3DZhSdLNdB+OMJU7SDMW8t+aQBZPLKg9bnrSl4hPZlLaXhqf0dhJoxBhMp
2NKkRJiTEBW8r7cYrg/sqFS7CDeL4jn0GaNpfhPk4+HVzNtpKtbdXHLAKXJjFGg=
=8BrJ
-----END PGP SIGNATURE-----

Harald Sitter (apachelogger) wrote :

If anyone affected sees this crash again, please make sure you are using baloo 4:4.12.97-0ubuntu2 or ubuntu3 and if that is the case, please file a bug against baloo at http://bugs.kde.org

Chances are that a fix that is part of those two versions fixes this.

Changed in baloo (Ubuntu):
status: Incomplete → Invalid
Patrick O'Dea (pfodea) wrote :

Hi Harald

After I filed the bug report, and the update to Baloo later that day, the problem seems to have gone away.

Thanks

Patrick
On Tuesday, April 8, 2014 10:35 PM, Harald Sitter <email address hidden> wrote:

If anyone affected sees this crash again, please make sure you are using
baloo 4:4.12.97-0ubuntu2 or ubuntu3 and if that is the case, please file
a bug against baloo at http://bugs.kde.org

Chances are that a fix that is part of those two versions fixes this.

** Changed in: baloo (Ubuntu)
      Status: Incomplete => Invalid

--
You received this bug notification because you are subscribed to a
duplicate bug report (1303512).
https://bugs.launchpad.net/bugs/1301742

Title:
  baloo_file_extractor crashed with SIGSEGV in size()

Status in “baloo” package in Ubuntu:
  Invalid

Bug description:
  No idea

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: baloo 4:4.12.97-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  3 01:23:48 2014
  ExecutablePath: /usr/bin/baloo_file_extractor
  ProcCmdline: /usr/bin/baloo_file_extractor 1193 1192 1191 1190 1189 1188 1187 1186 1185 1184 1183 1182 1181 1180 1179 1175 1170 1169 1168 1167 1165 1164 1162 1161 1160 1159 1158 1157 1156 1155 1154 1153 1152 1151 1150 1149 1148 1147 1146 1145
  ProcEnviron:
  LANGUAGE=en_US
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=<set>
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SegvAnalysis:
  Segfault happened at: 0x7ffb1505de78 <_ZNK6Xapian8Database12get_documentEj+8>:    mov    0x10(%rsi),%rcx
  PC (0x7ffb1505de78) ok
  source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
  destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: baloo
  Stacktrace:
  #0  0x00007ffb1505de78 in Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
  No symbol table info available.
  #1  0x0000000000408f2e in _start ()
  No symbol table info available.
  StacktraceTop:
  Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
  _start ()
  Title: baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baloo/+bug/1301742/+subscriptions

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers