[kde] [Bug 365122] New: repeatable crash of baloo_file because of corrupted Database

[lutz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365122

            Bug ID: 365122
           Summary: repeatable crash of baloo_file because of corrupted
                    Database
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: lutz at eichler-web.de

Application: baloo_file (0.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.19.0-32-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed:
Booting Linux Mint, application is started automatically

- Unusual behavior I noticed:
After crash (i reported another one yesterday) I tried to use baloo manually:

sudo balooctl restart    # the error occurs also if started as non-root
[sudo] password for lutz: 
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
Error: "/var/tmp/kdecache-lutz" is owned by uid 1000 instead of uid 0.
baloo_file(22499): Database Corrupted - What did you do? 
baloo_file(22499):  
baloo_file(22499): Serious Error:   
baloo_file(22499): Cannot open tables at consistent revisions 
DatabaseCorruptError: Cannot open tables at consistent revisions 
KCrash: Attempting to start /usr/bin/baloo_file from kdeinit

So the Question is: What Database is addressed? Is there any way to get more
debug-info? Is there any tool to repair the DB?

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo-Datei (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5  std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>,
std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> >
>::operator= (this=this at entry=0x1f08ed0, __x=<error reading variable: Cannot
access memory at address 0x10>) at /usr/include/c++/4.8/bits/vector.tcc:161
#6  0x00007fcfc36bac7c in Xapian::Database::Database (this=0x1f08ec8,
other=...) at ../api/omdatabase.cc:82
#7  0x00007fcfc36c4dfa in Xapian::Enquire::Internal::Internal (this=0x1f08ec0,
db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621
#8  0x00007fcfc36c4fae in Xapian::Enquire::Enquire (this=0x7ffcdfae9640,
databases=..., errorhandler=0x0) at ../api/omenquire.cc:874
#9  0x00000000004174d3 in Baloo::FileIndexingQueue::fillQueue (this=0x1ed78a0)
at ../../../src/file/fileindexingqueue.cpp:56
#10 0x0000000000415ca9 in Baloo::IndexingQueue::resume (this=0x1ed78a0) at
../../../src/file/indexingqueue.cpp:56
#11 0x00000000004157d1 in Baloo::IndexScheduler::IndexScheduler
(this=0x1ed7560, db=<optimized out>, config=0x7ffcdfae9910, parent=<optimized
out>) at ../../../src/file/indexscheduler.cpp:82
#12 0x000000000040fa48 in Baloo::FileIndexer::FileIndexer (this=0x7ffcdfae9860,
db=0x7ffcdfae9890, config=0x7ffcdfae9910, parent=<optimized out>) at
../../../src/file/fileindexer.cpp:41
#13 0x00000000004092d2 in main (argc=<optimized out>, argv=<optimized out>) at
../../../src/file/main.cpp:86

The reporter indicates this bug may be a duplicate of or related to bug 337199.

Possible duplicates by query: bug 337199.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.