[dolphin] [Bug 415190] kdeinit5 PID: 1.967 Signal: Floating point exception (8)

[Thomas Höpping]

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

--- Comment #2 from Thomas Höpping <thomas.hoepping at gmx.net> ---
I installed the mentioned package and now I got this trace:
Application: kdeinit5 (kdeinit5), signal: Floating point exception
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fefd5187e00 (LWP 1896))]

Thread 4 (Thread 0x7fefb94ee700 (LWP 1899)):
#0  0x00007fefd6fda2f8 in g_source_unref_internal () from
/lib64/libglib-2.0.so.0
#1  0x00007fefd6fdb94c in g_source_iter_next () from /lib64/libglib-2.0.so.0
#2  0x00007fefd6fdcc53 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#3  0x00007fefd6fdd6cb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x00007fefd6fdd8d3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x00007fefd87e7da3 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#6  0x00007fefd8791cfb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#7  0x00007fefd85ea3a5 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x00007fefc77ccf4a in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#9  0x00007fefd85eb4f6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x00007fefd79e74e2 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fefd8466693 in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fefb9cef700 (LWP 1898)):
#0  0x00007fefd79edd45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007fefbf2b50eb in util_queue_thread_func () from
/usr/lib64/dri/nouveau_dri.so
#2  0x00007fefbf2b4cfb in impl_thrd_routine () from
/usr/lib64/dri/nouveau_dri.so
#3  0x00007fefd79e74e2 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fefd8466693 in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fefc6ef8700 (LWP 1897)):
#0  0x00007fefd845ba6f in poll () from /lib64/libc.so.6
#1  0x00007fefd8fe938a in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007fefd8feafea in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007fefc70fcac8 in QXcbEventQueue::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x00007fefd85eb4f6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x00007fefd79e74e2 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fefd8466693 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fefd5187e00 (LWP 1896)):
[KCrash Handler]
#6  0x00007fefc400bcdd in GSCreator::create (this=<optimized out>, path=...,
width=128, height=128, img=...) at
/usr/src/debug/kdegraphics-thumbnailers-19.04.3-2.fc31.x86_64/ps/gscreator.cpp:281
#7  0x00007fefd91cd85d in ThumbnailProtocol::createSubThumbnail(QImage&,
QString const&, int, int) () from /usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#8  0x00007fefd91cde7a in ThumbnailProtocol::drawSubThumbnail(QPainter&,
QString const&, int, int, int, int, int) () from
/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#9  0x00007fefd91ce4df in ThumbnailProtocol::thumbForDirectory(QUrl const&) ()
from /usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#10 0x00007fefd91cfbd2 in ThumbnailProtocol::get(QUrl const&) () from
/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#11 0x00007fefc7dd69a6 in KIO::SlaveBase::dispatch(int, QByteArray const&) ()
from /lib64/libKF5KIOCore.so.5
#12 0x00007fefc7dd7046 in KIO::SlaveBase::dispatchLoop() () from
/lib64/libKF5KIOCore.so.5
#13 0x00007fefd91ccb82 in kdemain () from
/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so
#14 0x0000555e971044bf in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#15 0x0000555e97105528 in handle_launcher_request(int, char const*) [clone
.isra.0] ()
#16 0x0000555e97105e0c in handle_requests(int) ()
#17 0x0000555e9710105e in main ()
[Inferior 1 (process 1896) detached]

I want to help analysing this issue. Could this pdf file causing the issue
being stored in any place on the hard drive?

-- 
You are receiving this mail because:
You are on the CC list for the bug.