Bug 420042 - Horizontal screen tearing (white line) when KDE is scaled 125%
Summary: Horizontal screen tearing (white line) when KDE is scaled 125%
Status: RESOLVED DUPLICATE of bug 373232
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 19.12.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-13 16:46 UTC by Doug B
Modified: 2020-04-13 17:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
white line (50.30 KB, image/png)
2020-04-13 16:46 UTC, Doug B
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Doug B 2020-04-13 16:46:48 UTC
Created attachment 127518 [details]
white line

SUMMARY Horizontal white line (screen tearing) shows up in Konsole when KDE is scaled to 125%.

STEPS TO REPRODUCE
1. Enter commands and muck around in the terminal until a white line shows up. (I just typed "ls /" to get it.

OBSERVED RESULT

White horizontal line

EXPECTED RESULT

No white horizontal line 

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-46-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz
Memory: 23.3 GiB of RAM

I am using an Nvidia video card, however it is currently in Intel power-saving mode (Intel Corporation UHD Graphics 630). My laptop is a Dell G5 5590

ADDITIONAL INFORMATION

Issue is fixed if you run Konsole without scaling

env QT_SCALE_FACTOR=1 konsole
Comment 1 Doug B 2020-04-13 16:55:57 UTC
EDIT: Actually, the fix I mentioned doesn't work.

You need:

env QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=1 /usr/bin/konsole

Weird bug though. When I add that change using KDE menu editor and launch Konsole, it doesn't fix it. But when I open Konsole and then launch another instance of Konsole with those options, it fixes it.
Comment 2 Patrick Silva 2020-04-13 17:21:13 UTC

*** This bug has been marked as a duplicate of bug 373232 ***