https://bugs.kde.org/show_bug.cgi?id=340267
--- Comment #59 from Konrad Materka <kmate...@wp.pl> --- I have the same back trace but in different situation. Probably cause is the same. In my situation it is always reproducible. It happens when I disable and enable screen again when it was affected by: https://bugs.kde.org/show_bug.cgi?id=353975 (screen is active but just black - no background or any other plasma widgets). I know that it might be different situation, but my guess is that during screen initialization it tries to delete old configuration that was not fully initialized. Can it happen when configuration of the same monitor changes quickly? Running Neon User 5.7.1 with latest stable Plasma 5.7.1, Qt 5.7 Crash is from here: #7 0x000000000043fe1f in ShellCorona::addOutput (this=0x7a3040, screen=0x43b8bb0) at /workspace/build/shell/shellcorona.cpp:862 QAction *removeAction = containment->actions()->action(QStringLiteral("remove")); if (removeAction) { removeAction->deleteLater(); } #6 Plasma::Applet::actions (this=this@entry=0x0) at /workspace/build/src/plasma/applet.cpp:607 KActionCollection *Applet::actions() const { return d->actions; } Variable d must be already deallocated or not initialized. Is it possible that containment is not fully initialized or it is a dangling pointer? After quick look at the code I was not able to find such situation. -- You are receiving this mail because: You are watching all bug changes.
