Bug 372661 - krunner crashes after typing in the first letter since KF 5.28
Summary: krunner crashes after typing in the first letter since KF 5.28
Status: RESOLVED DUPLICATE of bug 372017
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-19 13:01 UTC by madcatx
Modified: 2016-11-19 13:20 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 madcatx 2016-11-19 13:01:32 UTC
Hi,

I just updated to KF 5.28 and krunner now crashes as soon as I start typing. The crash is reproducible every time. Disabling the "Windowed widgets" plugin seems to help.

GDB backtrace:

Thread 6 "GlobalQueue[02]" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc33b3700 (LWP 2340)]
0x00007ffff2a1ea68 in KSycocaEntry::name() const () from /usr/lib/libKF5Service.so.5
(gdb) bt
#0  0x00007ffff2a1ea68 in KSycocaEntry::name() const () from /usr/lib/libKF5Service.so.5
#1  0x00007fffca04149c in ?? () from /usr/lib/qt/plugins/krunner_windowedwidgets.so
#2  0x00007fffd26dfe48 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from /usr/lib/libKF5Runner.so.5
#3  0x00007fffd24bdb88 in ThreadWeaver::Executor::run(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () from /usr/lib/libKF5ThreadWeaver.so.5
#4  0x00007fffd24bca9a in ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*) () from /usr/lib/libKF5ThreadWeaver.so.5
#5  0x00007fffd24bc140 in ThreadWeaver::Thread::run() () from /usr/lib/libKF5ThreadWeaver.so.5
#6  0x00007ffff3e7fd78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x00007ffff1335454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x00007ffff37957df in clone () from /usr/lib/libc.so.6
Comment 1 Kai Uwe Broulik 2016-11-19 13:20:52 UTC
*** This bug has been marked as a duplicate of bug 372017 ***