Bug 499611

Summary:	FR: Support overscan in kwin for Intel GPU
Product:	[Plasma] KScreen	Reporter:	Henning <boredsquirrel>
Component:	kscreen-doctor	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	kdedev
Priority:	NOR
Version First Reported In:	6.2.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Henning 2025-02-06 19:53:06 UTC

Since Plasma 6, the overscan feature is gone from the systemsettings page.

This makes many TVs hardly usable.

This might be the wrong repo but maybe the experts are here. Why did it disappear? Meanwhile all sorts of stuff like HDR was added.

Plasma 6.2.5
Wayland
Fedora 41 Kinoite

Comment 1 Henning 2025-02-06 21:16:55 UTC

I am on a Laptop with an intel i7 CPU with an integrated GPU.

Overscan is normally done in the GPU, but the compositor could support it.

So this is a FR to support overscan in Kwin

Comment 2 TraceyC 2025-02-07 18:02:00 UTC

According to this thread:
https://discuss.kde.org/t/monitor-overscan-gone/12184/6

> The option isn’t “gone”, but you seem to be on Intel, and the Intel driver has sadly never supported it

When you saw the overscan setting in Plasma 5, did you also have an Intel GPU?

Also, to address your comment about the compositor, another quote from that thread:
> The compositor could do it, but that’s not implemented right now. Changing that is planned, but idk when it’ll happen

Comment 3 Bug Janitor Service 2025-02-22 03:46:47 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2025-03-09 03:52:31 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.