Bug 406667 - Screen gets extrem blurry after being in a fullscreen game
Summary: Screen gets extrem blurry after being in a fullscreen game
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
: 395957 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-04-19 01:31 UTC by Kanonenfuta
Modified: 2021-03-10 19:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kanonenfuta 2019-04-19 01:31:54 UTC
I have the problem that screen get blurry while and after I launched a fullscreen game


STEPS TO REPRODUCE
To reproduce this I just had to run a game like dota 2

OBSERVED RESULT
Many things get very blurry, like text or everything displayed by a browser, also context menus and task bars. Some objects are excluded by effect, like the cursor



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.04, Kernel Version 5.0.0-13
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
I have a GTX 1070 ti and the latest (418.56)proprietary driver installed.
I have 2 screens, one with a resolution of 2560 x 1440(144hz) and the other with 1600 x 900(60hz)

i made a video of this and uploaded it to Youtube. The flickering of the taskbars is only visible in the video, it does not happen on screen

https://youtu.be/ihB5OH62hcM

When you need additional information like logs ask me
Comment 1 David Edmundson 2019-04-22 15:53:15 UTC
Do you have nvidia? If so do you have something non-default in the

nvidia-settings "antialiasing" tab?
Comment 2 Kanonenfuta 2019-04-22 17:41:42 UTC
(In reply to David Edmundson from comment #1)
> Do you have nvidia? If so do you have something non-default in the
> 
> nvidia-settings "antialiasing" tab?

I have an nvidia card.
I'm not sure, but i think i havent changed anything in the antialiasing settings.
The used settings are "Use  Application Settings" and FXAA is enabled, Override Applications Setting is NOT marked

i also just discovered that then i disable the desktop compositor the blurring stops, and when i enable it again the blurring starts again

I hope that was helpful :)
Comment 3 Kanonenfuta 2019-04-22 17:48:17 UTC
I can now easily reproduce this bug. This happens every time when FXAA is turned on in the Nvidia-Settings and the Compositor is deactivated. As soon as you activate the compositor again the blurring starts. When FXAA is disabled nothing happens, the display stays clear
Comment 4 Bug Janitor Service 2019-05-07 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Christoph Feck 2019-05-14 19:14:13 UTC
New information was added with comment #3; changing status for inspection.
Comment 6 Christoph Feck 2019-05-14 19:14:53 UTC
Changing status for inspection.
Comment 7 David Edmundson 2019-05-14 20:21:21 UTC
> This happens every time when FXAA is turned on in the Nvidia-Settings and the Compositor is deactivated.

At least we understand it makes sense.

There's nothing we can do, if we've told nvidia to override graphic settings it'll do so.
Comment 8 Nate Graham 2021-03-10 19:10:59 UTC
*** Bug 395957 has been marked as a duplicate of this bug. ***