Bug 380158 - Krunner crashs randomly
Summary: Krunner crashs randomly
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-krunner
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.33.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-24 19:05 UTC by Florian Sievert
Modified: 2020-07-16 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Stacktrace of krunner crash (19.21 KB, text/plain)
2017-05-24 19:05 UTC, Florian Sievert
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Sievert 2017-05-24 19:05:15 UTC
Created attachment 105700 [details]
Stacktrace of krunner crash

This report was provided by a user under support and could not be reproduced on my own system. The target system does have a deactivated NVIDIA card and is running on intel graphic chips. Desktop search and desktop effects are activated.

When using krunner it does randomly crashs. It is not possible to reproduce the crashs in a reliable manner as it seems to be working sometimes fine and then occuring again. Similiar crashs seems not to be reproducable on the system except when using krunner.

Attached to the issue you'll find the stack trace of the issue that was dumped. Asking for further assistance for analyzing he issue or to gather further information.

Many thanks in advance!
Comment 1 Méven Car 2020-06-16 19:41:33 UTC
Looks like an upstream Qt bug :

Thread 3 (Thread 0x7fc38da80700 (LWP 1367)):
[KCrash Handler]
#6  0x00007fc3a85f291f in raise () from /lib64/libc.so.6
#7  0x00007fc3a85f451a in abort () from /lib64/libc.so.6
#8  0x00007fc3a8636200 in __libc_message () from /lib64/libc.so.6
#9  0x00007fc3a86418e8 in _int_malloc () from /lib64/libc.so.6
#10 0x00007fc3a8642f14 in malloc () from /lib64/libc.so.6
#11 0x00007fc3a8f32ab8 in operator new(unsigned long) () from /lib64/libstdc++.so.6
#12 0x00007fc3a949e090 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5
#13 0x00007fc3a949e51a in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5
#14 0x00007fc3acd2cb60 in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5
#15 0x00007fc3a94997e9 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007fc3a94715ea in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#17 0x00007fc3a947170b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007fc3a9473de0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#19 0x00007fc3a94bf653 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#20 0x00007fc3a0649e52 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#21 0x00007fc3a064a1d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#22 0x00007fc3a064a27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#23 0x00007fc3a94bf6cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5


Anyway Is it still reproducible ?
Comment 2 Méven Car 2020-06-16 19:41:59 UTC
Is it reproducible ?
Comment 3 Bug Janitor Service 2020-07-01 04:33:08 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 2020-07-16 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!