Bug 300796

Summary: krunner always crashes
Product: [Plasma] krunner Reporter: Jaxxed <jaxxed>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version: 4.8.3   
Target Milestone: ---   
Platform: Chakra   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jaxxed 2012-05-29 07:40:45 UTC 
Application: krunner (0.1)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.2
Operating System: Linux 3.2-CHAKRA x86_64
Distribution: "Chakra Linux"

-- Information about the crash:
On startup and if I run krunner from command line, I get a QT exception that crashes it.

This may duplicate another bug report, but none of them seemed to match the fact that I can't get krunner to start.
This is using chakra-linux.  I guess it could be a library mismatch?

The crash can be reproduced every time.

-- Backtrace:
Application: Run Command Interface (krunner), signal: Aborted
[Current thread is 1 (Thread 0x7f7441a41780 (LWP 1792))]

Thread 2 (Thread 0x7f74266b5700 (LWP 1793)):
#0  0x00007f743cea4e95 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x00007f743683e831 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#2  0x00007f74368030e4 in g_main_context_query () from /usr/lib/libglib-2.0.so.0
#3  0x00007f743680382a in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007f74368039e4 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5  0x00007f743ddfcef6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x00007f743ddcdb1f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0x00007f743ddcdda8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#8  0x00007f743dcd1530 in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0x00007f743ddae6ef in ?? () from /usr/lib/libQtCore.so.4
#10 0x00007f743dcd447b in ?? () from /usr/lib/libQtCore.so.4
#11 0x00007f743cea2ede in start_thread () from /lib/libpthread.so.0
#12 0x00007f744136a60d in clone () from /lib/libc.so.6

Thread 1 (Thread 0x7f7441a41780 (LWP 1792)):
[KCrash Handler]
#5  0x00007f74412bac35 in raise () from /lib/libc.so.6
#6  0x00007f74412bc0b8 in abort () from /lib/libc.so.6
#7  0x00007f743d73b9cd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#8  0x00007f743d739ad6 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00007f743d739b03 in std::terminate() () from /usr/lib/libstdc++.so.6
#10 0x00007f743d739d76 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007f743ddce014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007f743ddd2a48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007f744165148f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#14 0x00007f74412a7455 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000400661 in _start ()

Possible duplicates by query: bug 300718, bug 300713, bug 300688, bug 300644, bug 300632.

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2012-05-29 22:28:24 UTC 
Your backtrace lacks debugging symbols, please install those and provide a better backtrace. See also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Jaxxed 2012-05-30 08:57:57 UTC 
I have added the kde-workspace-debug package for my system (chakra/arch) but I don't see any qt debug packages.  I am looking for a way to install it now.  If I can't get it installed then we should close the bug.
Comment 3 Myriam Schweingruber 2012-05-31 19:56:03 UTC 
Hm, In your distribution Qt needs to be compiled with debugging enabled, I don't think it is by default.
Anyway, a backtrace with all necessary KDE debugging symbols would already be helpful.
Comment 4 Andrew Crouthamel 2018-09-23 02:32:53 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 set the bug status 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 5 Andrew Crouthamel 2018-10-27 02:38:39 UTC 
Dear Bug Submitter,

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!