Bug 486621

Summary: Support overscan on drivers that don't support it natively
Product: [Plasma] kwin Reporter: jdl <677ee1vp>
Component: platform-drmAssignee: KWin default assignee <kwin-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: krpisjar, xaver.hugl
Priority: NOR    
Version First Reported In: 6.0.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description jdl 2024-05-05 11:30:24 UTC 
SUMMARY
Setting overscan using kscreen-doctor silently fails

STEPS TO REPRODUCE
1. Have either internal or external display, running wayland
2. Do `kscreen-doctor output.HDMI-A-1.overscan.10` or `kscreen-doctor output.HDMI-A-1.overscan.1`, or similar


OBSERVED RESULT
no output or change whatsoever

EXPECTED RESULT
Terminal output confirming the changes made
The output gets cropped/resized accordingly


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Notebook
Product Name: P95xER 

ADDITIONAL INFORMATION

```
kscreen-doctor -o
Output: 1 eDP-1
	enabled
	connected
	priority 2
	Panel
	Modes:  0:3840x2160@60!  1:3840x2160@40  2:1600x1200@60  3:1280x1024@60  4:1024x768@60  5:2560x1600@60  6:1920x1200@60  7:1280x800@60  8:3840x2160@60  9:3200x1800@60  10:2880x1620@60  11:2560x1440@60  12:1920x1080@60*  13:1600x900@60  14:1368x768@60  15:1280x720@60
	Geometry: 1920,0 1920x1080
	Scale: 1
	Rotation: 1
	Overscan: 0
	Vrr: incapable
	RgbRange: Automatic
	HDR: incapable
	Wide Color Gamut: incapable
	ICC profile: none
Output: 2 HDMI-A-1
	enabled
	connected
	priority 1
	HDMI
	Modes:  0:1920x1080@60*!  1:1920x1080@50  2:1920x1080@24  3:1280x1024@75  4:1280x720@60  5:1280x720@60  6:1280x720@50  7:1024x768@75  8:1024x768@70  9:1024x768@60  10:800x600@75  11:800x600@72  12:800x600@60  13:800x600@56  14:720x576@50  15:720x480@60  16:640x480@75  17:640x480@73  18:640x480@60  19:640x480@60
	Geometry: 0,0 1920x1080
	Scale: 1
	Rotation: 1
	Overscan: 0
	Vrr: incapable
	RgbRange: unknown
	HDR: incapable
	Wide Color Gamut: incapable
	ICC profile: none
```
Comment 1 jdl 2024-05-05 11:43:50 UTC 
Related forum thread: https://discuss.kde.org/t/monitor-overscan-gone/12184/5
Comment 2 Zamundaaa 2024-05-06 17:15:05 UTC 
Intel uses different drm properties for overscan than AMD and Nouveau, and KWin currently doesn't support them. Shouldn't be hard to change that though
Comment 3 jdl 2024-05-06 17:20:30 UTC 
(In reply to Zamundaaa from comment #2)
> Intel uses different drm properties for overscan than AMD and Nouveau, and
> KWin currently doesn't support them. Shouldn't be hard to change that though

Is it the case for proprietary nvidia driver as well, since I'm unable to use overscan for both the internal display (connected to intel iGPU) and external displays (connected to nvidia dGPU)?
Comment 4 Zamundaaa 2024-05-06 17:25:59 UTC 
Judging by https://drmdb.emersion.fr/snapshots/b4bf7bec5647, NVidia doesn't support any of the drm properties that could be used for overscan. We can support it regardless by applying it in software (and by using drm plane scaling) but it'll take a bit more time to do that.
Comment 5 Zamundaaa 2024-05-06 23:57:17 UTC 
I checked which properties were supported on Intel, and it seems I misremembered. There are properties for overscan that KWin could still support, but those are for VC4, and the Intel driver doesn't support them. So it'll have to be implemented in software for Intel as well...
Comment 6 Zamundaaa 2024-09-25 22:15:02 UTC 
*** Bug 493540 has been marked as a duplicate of this bug. ***