Bug 345120 - Baloo crashes on startup
Summary: Baloo crashes on startup
Status: RESOLVED DUPLICATE of bug 333772
Alias: None
Product: Baloo
Classification: Unmaintained
Component: Baloo File Daemon (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-03-13 14:20 UTC by Chris
Modified: 2015-03-17 12:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2015-03-13 14:20:17 UTC
Application: baloo_file (0.1)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 3.16.7-7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
Starting system up Baloo crashes everytime.  That is all I can tell you.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fa2b89d6d0a in std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > >::operator=(std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>, std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> > > const&) () at /usr/lib64/libxapian.so.22
#6  0x00007fa2b89d5dbc in Xapian::Database::Database(Xapian::Database const&) () at /usr/lib64/libxapian.so.22
#7  0x00007fa2b89dedea in Xapian::Enquire::Internal::Internal(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#8  0x00007fa2b89def9e in Xapian::Enquire::Enquire(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#9  0x0000000000417ea3 in _start ()

Possible duplicates by query: bug 334831, bug 334229.

Reported using DrKonqi
Comment 1 Vishesh Handa 2015-03-17 12:52:26 UTC

*** This bug has been marked as a duplicate of bug 333772 ***