Bug 453751 - kwin_wayland crashes in Plasma::AbstractRunner::name() when starting plasmashell from the Overview effect search field
Summary: kwin_wayland crashes in Plasma::AbstractRunner::name() when starting plasmash...
Status: RESOLVED DUPLICATE of bug 448825
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.5
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Lohnau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-13 17:09 UTC by Lyubomir
Modified: 2022-10-19 10:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lyubomir 2022-05-13 17:09:41 UTC
SUMMARY
Same as https://bugs.kde.org/show_bug.cgi?id=453697#c3 but with different stacktrace.

OBSERVED RESULT
(gdb) backtrace 
#0  0x00007f9c85140405 in QExplicitlySharedDataPointer<QCborContainerPrivate>::operator!() const (this=<optimized out>, this=<optimized out>)
    at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:231
#1  QJsonObject::valueImpl<QStringView>(QStringView) const (key=..., this=<optimized out>) at serialization/qjsonobject.cpp:371
#2  QJsonObject::value(QStringView) const (this=0x2d323465342d344c, key=...) at serialization/qjsonobject.cpp:353
#3  0x00007f9c851406dd in QJsonObject::operator[](QStringView) const (key=..., this=<optimized out>)
    at ../../include/QtCore/../../src/corelib/serialization/qjsonobject.h:102
#4  QJsonObject::operator[](QString const&) const (this=<optimized out>, key=...) at serialization/qjsonobject.cpp:393
#5  0x00007f9c8616cc50 in KPluginMetaData::rootObject() const (this=<optimized out>)
    at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:351
#6  0x00007f9c8616d10b in KPluginMetaData::pluginId() const (this=0x2d323465342d344c)
    at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:473
#7  0x00007f9c86169b5e in KPluginMetaData::isValid() const (this=0x2d323465342d344c)
    at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:341
#8  0x00007f9c4867aadd in Plasma::AbstractRunner::name() const (this=0x55fc39cf0b60) at /usr/src/debug/krunner-5.93.0/src/abstractrunner.cpp:336
#9  0x00007f9c48686b7a in Plasma::DefaultRunnerPolicy::free(QSharedPointer<ThreadWeaver::JobInterface>)
    (this=0x7f9c486a2100 <Plasma::DefaultRunnerPolicy::instance()::policy>, job=...) at /usr/src/debug/krunner-5.93.0/src/runnerjobs.cpp:98
#10 0x00007f9c4864fcce in ThreadWeaver::Private::Job_Private::freeQueuePolicyResources(QSharedPointer<ThreadWeaver::JobInterface>)
    (this=0x55fc39487650, job=...) at /usr/src/debug/threadweaver-5.93.0/src/job_p.cpp:30
#11 0x00007f9c48653185 in ThreadWeaver::Job::defaultEnd(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*)
    (this=<optimized out>, job=...) at /usr/src/debug/threadweaver-5.93.0/src/job.cpp:125
#12 0x00007f9c486530f7 in ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&, ThreadWeaver::Thread*)
    (this=<optimized out>, self=..., th=0x55fc394c4cd0) at /usr/src/debug/threadweaver-5.93.0/src/job.cpp:79
#13 0x00007f9c48656dd9 in ThreadWeaver::Thread::run() (this=0x55fc394c4cd0) at /usr/src/debug/threadweaver-5.93.0/src/thread.cpp:98
#14 0x00007f9c84f338cc in QThreadPrivate::start(void*) (arg=0x55fc394c4cd0) at thread/qthread_unix.cpp:331
#15 0x00007f9c847503dd in start_thread () at /usr/lib/libc.so.6
#16 0x00007f9c847d52c4 in clone () at /usr/lib/libc.so.6

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.5-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 1 Alexander Lohnau 2022-05-13 19:12:03 UTC
No idea why this crashes, the stacktrace looks Qt-internal. I did not experience any crash recently, though I do not use Arch which is the distro that the other bug reporter uses too.
Comment 2 Nate Graham 2022-05-16 17:31:30 UTC
Cannot reproduce; no crash here.
Comment 3 Lyubomir 2022-05-20 15:59:49 UTC
@Nate is it possible that these crashes on plasmashell startup are related to the following crash: https://bugs.kde.org/show_bug.cgi?id=451939?
I think it usually happens when plasmashell and some different apps receive SIGABRT for some reason. So then I have to start plasma from the launcher.
Today I started it and got yet another crash, with different stacktrace (AFAIS). I've filed a new bug for that. Is it possible that something else (like Systemd --user instance) is sending this SIGABRT to the apps and the apps themselves are not the cause, thus the stacks appearing different?

Or maybe nevermind, cause this is SIGSEGV and not SIGABRT?
Comment 4 Nicolas Fella 2022-10-19 10:30:19 UTC

*** This bug has been marked as a duplicate of bug 448825 ***