Bug 403536 - Baloo crashed somewhere in taglibextractor
Summary: Baloo crashed somewhere in taglibextractor
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kfilemetadata
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.54.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2019-01-23 19:54 UTC by Seb
Modified: 2019-03-20 04:33 UTC (History)
2 users (show)

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 Seb 2019-01-23 19:54:15 UTC
Application: baloo_file_extractor (5.54.0)

Qt Version: 5.11.2
Frameworks Version: 5.54.0
Operating System: Linux 4.15.0-43-generic x86_64
Distribution: KDE neon User Edition 5.14

-- Information about the crash:
- What I was doing when the application crashed:
Each time I start ma computer the application baloo crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f94a81d4c80 (LWP 1398))]

Thread 3 (Thread 0x7f948073a700 (LWP 1401)):
#0  0x00007f94a4d736ff in __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x00007f94a4d57be6 in __GI___poll (fds=0x7f947801a360, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#2  0x00007f94a1424539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f94a142464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f94a569204b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f94a563630a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f94a5461bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f94a6fb8e45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x00007f94a546cadb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f94a395e6db in start_thread (arg=0x7f948073a700) at pthread_create.c:463
#10 0x00007f94a4d6488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f9499aaf700 (LWP 1399)):
#0  0x00007f94a4d57bf9 in __GI___poll (fds=0x7f9499aaeca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f94a0fb3747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f94a0fb536a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f949ca6fed9 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f94a546cadb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f94a395e6db in start_thread (arg=0x7f9499aaf700) at pthread_create.c:463
#6  0x00007f94a4d6488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f94a81d4c80 (LWP 1398)):
[KCrash Handler]
#6  0x00007f9480b530ab in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_taglibextractor.so
#7  0x000055e8d201b22b in  ()
#8  0x000055e8d201bb6e in  ()
#9  0x00007f94a5673ef4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f94a5667b9b in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f94a63c4e1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f94a63cc3ef in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f94a5637fe8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f94a56914be in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f94a5691cb9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f94a1424387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f94a14245c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f94a142464c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f94a569202f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f949cafb761 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f94a563630a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f94a563f4d0 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000055e8d201a204 in  ()
#24 0x00007f94a4c64b97 in __libc_start_main (main=0x55e8d2019fc0, argc=1, argv=0x7fffd4e0ba18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffd4e0ba08) at ../csu/libc-start.c:310
#25 0x000055e8d201a2aa in  ()

Reported using DrKonqi
Comment 1 Alexander Stippich 2019-02-10 21:00:03 UTC
Can you determine the file where it hangs using balooctl monitor? Is it a .spx file?
Comment 2 Alexander Stippich 2019-02-18 18:52:31 UTC
Can you determine the file type?
Comment 3 Bug Janitor Service 2019-03-05 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-03-20 04:33:09 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!