[kde] [Bug 340197] New: Baloo crash at every startup
Salvatore Brigaglia
opensourcecat at gmail.com
Tue Oct 21 14:54:11 BST 2014
https://bugs.kde.org/show_bug.cgi?id=340197
Bug ID: 340197
Summary: Baloo crash at every startup
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: opensourcecat at gmail.com
Application: baloo_file (0.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.5
Operating System: Linux 3.11.10-21-desktop i686
Distribution: "openSUSE 13.1 (Bottle) (i586)"
-- Information about the crash:
- What I was doing when the application crashed:
Just normal kde login
- Custom settings of the application:
I have another machine (workstation) with same OS (opensuse 13.1) and same
update repos and it is not crashing. the one crashing is a MacBook pro late
2012. Can it be related to power management?
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#6 0xb6809be4 in
std::vector<Xapian::Internal::RefCntPtr<Xapian::Database::Internal>,
std::allocator<Xapian::Internal::RefCntPtr<Xapian::Database::Internal> >
>::operator= (this=this at entry=0x9e04f20, __x=<error reading variable: Cannot
access memory at address 0x8>) at /usr/include/c++/4.8/bits/vector.tcc:161
#7 0xb6808beb in Xapian::Database::Database (this=0x9e04f1c, other=...) at
api/omdatabase.cc:82
#8 0xb6813b82 in Xapian::Enquire::Internal::Internal (this=0x9e04f18, db_=...,
errorhandler_=0x0) at api/omenquire.cc:621
#9 0xb6813d77 in Xapian::Enquire::Enquire (this=0xbfe2c420, databases=...,
errorhandler=0x0) at api/omenquire.cc:874
#10 0x0805eb94 in _start ()
The reporter indicates this bug may be a duplicate of or related to bug 333772.
Possible duplicates by query: bug 334831, bug 334229.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list