Bug 344960 - Baloo Crash - Unknown Exception
Summary: Baloo Crash - Unknown Exception
Status: RESOLVED FIXED
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-08 20:34 UTC by André Verwijs
Modified: 2015-03-17 12:55 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 André Verwijs 2015-03-08 20:34:59 UTC
Application: baloo_file (0.1)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 3.19.0-2-desktop x86_64
Distribution: "openSUSE 20150227 (Tumbleweed) (x86_64)"

-- Information about the crash:
crash while running .sh files and changing file properties... 
not really related to this bug but still want treport it...

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo-bestand (baloo_file), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007f54f0fa73c7 in raise () at /lib64/libc.so.6
#6  0x00007f54f0fa879a in abort () at /lib64/libc.so.6
#7  0x00007f54f158efe5 in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6
#8  0x00007f54f158d186 in  () at /usr/lib64/libstdc++.so.6
#9  0x00007f54f158d1b3 in  () at /usr/lib64/libstdc++.so.6
#10 0x00007f54f158d426 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6
#11 0x00007f54f4c77296 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#12 0x00007f54f4c7c4f9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#13 0x0000000000409cef in  ()
#14 0x00007f54f0f948c5 in __libc_start_main () at /lib64/libc.so.6
#15 0x000000000040a067 in _start ()

Reported using DrKonqi
Comment 1 Vishesh Handa 2015-03-17 12:55:02 UTC
This is being caused by an exception not being caught. This has probably been fixed with Plasma 5.

Thanks for reporting :)