Bug 480068

Summary: Display Configuration Module cannot handle a LG 5K monitor
Product: [Applications] systemsettings Reporter: Paul Hands <jphands>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.27.10   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Two monitors of same vertical pixel count show different heights

Description Paul Hands 2024-01-19 22:34:23 UTC
Created attachment 165054 [details]
Two monitors of same vertical pixel count show different heights

SUMMARY
I just acquired a new LG 34BK95U-W monitor, which has a max resolution of 5120 x 2160 at 60Hz.  It works just fine on a Macbook Pro, but when connected to my KDE Neon box, it just won't work properly.  I added some new modes via xrandr because KDE thought it has a max resolution of 4K -  3840 x 2160,  When I added those modes, the monitor shows up as 5120 x 2160 capable, but it's impossible to configure the 5K monitor beside another 4k monitor at 3840 x 21260, without the displays overlapping.  Also, the Neon Display Configuration module shows two monitors with a vertical resolution of 2160 as different heights.  See attached screenshot.  Because of the height difference the cursor jumps vertically when moving from one monitor to another, and the cursor won't go between the two monitors at all if in the upper zone where they don't touch.

I'm sure this is an underlying EDID problem, rather than with Plasma, but I didn't expect Linux to be unable to handle new hardware these days.


Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.5.0-14-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 46.9 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: ASUS
Comment 1 Paul Hands 2024-01-22 18:48:23 UTC
Update.  A bunch of internet searching revealed that this isn't a bug.  It's actually a problem with what kind of cable you use to connect the GPU to the  monitor.  An HDMI cable displays the problems seen in this report. Using a Display Port cable works immediately, but this information is not at all obvious.