https://bugs.kde.org/show_bug.cgi?id=430656
--- Comment #2 from julien_palmi...@hotmail.fr --- Created attachment 134486 --> https://bugs.kde.org/attachment.cgi?id=134486&action=edit New crash information added by DrKonqi plasmashell (5.20.4) using Qt 5.15.2 - What I was doing when the application crashed: logged in with Wayland and a second screen connected. it does crash either the second screen is the only active screen or both screen are active -- Backtrace (Reduced): #4 0x00007f6e4bc92c76 in QScreen::name (this=this@entry=0x560c2f87b770) at kernel/qscreen.cpp:195 #5 0x0000560c2ebf17a2 in ShellCorona::load (this=0x560c2f8b70c0) at ./shell/shellcorona.cpp:729 #6 0x00007f6e4b8c06be in QtPrivate::QSlotObjectBase::call (a=0x7ffcc3d79eb0, r=0x560c2f8b70c0, this=0x560c2fae62b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate<false> (sender=0x560c2f9136b0, signal_index=4, argv=0x7ffcc3d79eb0) at kernel/qobject.cpp:3886 [...] #9 0x00007f6e4dae4dc5 in KActivities::Consumer::serviceStatusChanged (this=<optimized out>, _t1=<optimized out>) at ./obj-x86_64-linux-gnu/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:253 -- You are receiving this mail because: You are watching all bug changes.
