https://bugs.kde.org/show_bug.cgi?id=435989
Bug ID: 435989
Summary: Plasma Wayland crashes when using combined (direct)
HDMI and DisplayLink outputs
Product: plasmashell
Version: 5.21.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: si...@ergotech.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.21.4)
Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.10.22-100.fc32.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.4
Distribution: Fedora 34 (KDE Plasma)
-- Information about the crash:
- What I was doing when the application crashed:
I have a Lenovo USB-C dock which uses DisplayLink to drive two monitors. For
reasons unrelated to this bug report I currently have one monitor connected to
the dock and one connected directly to the laptop over HDMI.
I was trying to enable the monitor that I have connected directly to the laptop
using HDMI. When I first start Plasma, the dock monitor is automatically
enabled (due to my display configuration). When I try to enable the HDMI
monitor, Plasma freezes and then stops properly rendering the dock monitor (I
can move the mouse cursor but nothing else. If I find a window title bar I can
move the window around but I can't see the results of my movement). The HDMI
monitor does not come on. My laptop monitor is still functioning normally.
If I move the display settings tool to my laptop monitor and try again to
configure my displays, Plasma crashes (with the backtrace shown here). I aslo
see a lot of other application crashes (Konversation, Dolphin, Konsole, or
anything else I had loaded). I assume these are related to Plasma crashing so I
am not reporting them. My laptop monitor still works but the other two are
black.
If I try to configure the monitors a third time, everything freezes, the caps
lock light doesn't come on any more when I click the key, and my laptop's fans
spin up. I have to hold the power button to shut down.
I have tried this whole operation a couple of times and it is reproduceable.
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#4 0x00007fb332c8fa2a in
QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at
/lib64/libQt5Core.so.5
#5 0x00007fb33320b14c in void
QWindowSystemInterface::handleWindowScreenChanged<QWindowSystemInterface::DefaultDelivery>(QWindow*,
QScreen*) () at /lib64/libQt5Gui.so.5
#6 0x00007fb330b337c0 in
QtWaylandClient::QWaylandWindow::handleScreensChanged() () at
/lib64/libQt5WaylandClient.so.5
#7 0x00007fb332e194b0 in void doActivate<false>(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#8 0x00007fb33122cc04 in ffi_call_unix64 () at /lib64/libffi.so.6
#9 0x00007fb33122c107 in ffi_call () at /lib64/libffi.so.6
#10 0x00007fb3326b5d10 in wl_closure_invoke.constprop () at
/lib64/libwayland-client.so.0
#11 0x00007fb3326b642b in dispatch_event.isra () at
/lib64/libwayland-client.so.0
#12 0x00007fb3326b661c in wl_display_dispatch_queue_pending () at
/lib64/libwayland-client.so.0
#13 0x00007fb330b276d3 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /lib64/libQt5WaylandClient.so.5
#14 0x00007fb332e194fd in void doActivate<false>(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#15 0x00007fb332e1bb3a in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at
/lib64/libQt5Core.so.5
#16 0x00007fb332e1c2d4 in QSocketNotifier::event(QEvent*) () at
/lib64/libQt5Core.so.5
#17 0x00007fb333a57e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#18 0x00007fb332de8f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#19 0x00007fb332e3617f in socketNotifierSourceDispatch(_GSource*, int
(*)(void*), void*) () at /lib64/libQt5Core.so.5
#20 0x00007fb3312bd4cf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#21 0x00007fb3313114e8 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#22 0x00007fb3312bac03 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#23 0x00007fb332e356f8 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib64/libQt5Core.so.5
#24 0x00007fb332de79b2 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib64/libQt5Core.so.5
#25 0x00007fb332def544 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#26 0x0000556a55cc7fd1 in main ()
[Inferior 1 (process 4847) detached]
Possible duplicates by query: bug 435976, bug 435618, bug 435427, bug 435261,
bug 435192.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
