[kde] [Bug 333908] New: Baloo crashes at startup

Henri hkaustin at luukku.com
Sat Apr 26 12:39:03 BST 2014


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

            Bug ID: 333908
           Summary: Baloo crashes at startup
    Classification: Unclassified
           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: hkaustin at luukku.com

Application: baloo_file (0.1)
KDE Platform Version: 4.13.0
Qt Version: 4.8.5
Operating System: Linux 3.13.7-1.ga68bc7c-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

KDE was loading. Didn't touch keyboard or mouse.

- Custom settings of the application:

My root+home -partition is using btfrs. I've got syslinks in home partition
that point to data partition which uses ext4. By default the data partition was
excluded in Baloo settings but I removed that setting.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo-tiedosto (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>,
std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> >
>::operator= (this=this at entry=0x250e390, __x=...) at
/usr/include/c++/4.8/bits/vector.tcc:161
#7  0x00007f7b348724bc in Xapian::Database::Database (this=0x250e388,
other=...) at api/omdatabase.cc:82
#8  0x00007f7b3487c63a in Xapian::Enquire::Internal::Internal (this=0x250e380,
db_=..., errorhandler_=0x0) at api/omenquire.cc:621
#9  0x00007f7b3487c7ee in Xapian::Enquire::Enquire (this=0x7fffd29e0f30,
databases=..., errorhandler=0x0) at api/omenquire.cc:874
#10 0x0000000000417d93 in _start ()

Reported using DrKonqi

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



More information about the Unassigned-bugs mailing list