Bug 345466 - baloo crashed on login after hard reboot
Summary: baloo crashed on login after hard reboot
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-24 08:38 UTC by Robert Riemann
Modified: 2015-03-25 00:56 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 Robert Riemann 2015-03-24 08:38:35 UTC
Application: baloo_file (0.1)
KDE Platform Version: 4.14.6
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:
- What I was doing when the application crashed:
I restarted my computer and when I logged in, the crash reporting assistant was already openend

- Unusual behavior I noticed:
Before, my system was stuck (only cursor was working) on load 100%. I couldn't change to PTY1 nor reset the X-Server. So I put power off and rebooted.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007f6460516e2a in  () at /usr/lib64/libxapian.so.22
#6  0x00007f6460515edc in Xapian::Database::Database(Xapian::Database const&) () at /usr/lib64/libxapian.so.22
#7  0x00007f646052005a in Xapian::Enquire::Internal::Internal(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#8  0x00007f646052020e in Xapian::Enquire::Enquire(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22
#9  0x0000000000417ea3 in _start ()

Reported using DrKonqi
Comment 1 Vishesh Handa 2015-03-25 00:56:23 UTC

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