Bug 511518 - DVI connection to the docking station is broken
Summary: DVI connection to the docking station is broken
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.5.1
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-02 14:31 UTC by pipapo
Modified: 2025-11-10 09:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pipapo 2025-11-02 14:31:05 UTC
SUMMARY

STEPS TO REPRODUCE
1. Connect the monitor to one DVI-Slot at the docking station

OBSERVED RESULT
kwin or sddm crashing

EXPECTED RESULT
The monitor works as usual.

SOFTWARE/OS VERSIONS
Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-34-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz
Memory: 32 GiB of RAM (31.0 GiB usable)
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20N3SA4P00
System Version: ThinkPad T490

ADDITIONAL INFORMATION
After the last update, the DVI monitor connection to the docking station no longer works. sddm/kwin crashes. The HDMI connection at the dock is working.
The log says:
‘kwin_wayland_drm: failed to open drm device at \’\‘\n’
It's a docking station for ThinkPad T490 with Intel UHD Graphics 620 on KDE Neon.
Comment 1 TraceyC 2025-11-04 00:10:19 UTC
As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.
Comment 2 pipapo 2025-11-10 09:24:52 UTC
With the upgrade to KDE 6.5.2, the problem has disappeared and can no longer be reproduced.