Bug 481778

Summary: Text in lines is cut in half, only lower half of the line text is visible when font size less than 14
Product: [Applications] kompare Reporter: Jure Repinc <jlp>
Component: viewpartAssignee: Kompare developers <kompare-devel>
Status: CONFIRMED ---    
Severity: normal CC: bjoernv, fisiu82, i.a.rodin, karl, kermit, m.lincetto, mrintala43, s_chriscollins, whilesharp, xalt7x.service
Priority: NOR Keywords: qt6
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of the line bug

Description Jure Repinc 2024-02-24 19:04:25 UTC
Created attachment 166069 [details]
Screenshot of the line bug

SUMMARY
When I open Kompare to show differences between two files the text in each line is only partially shown, only the bottom half is shown. I tried selecting different fonts (e.g. Hack, DejaVU Sans Mono) and it made no difference. Only when the font size was 14 or more it was fine. See the attached screenshot.


STEPS TO REPRODUCE
1. Open Kompare
2. Select two files to show diff of
3. Set font size to less than 14

OBSERVED RESULT
Text in each line is cut off in half and only the bottom line is shown

EXPECTED RESULT
Entire text should be shown in the line

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240220
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 480 Graphics

ADDITIONAL INFORMATION
I have two screen setup, one is set to 150% scale the other to 200%
Comment 1 Matti Rintala 2024-03-26 11:22:26 UTC
I have just noticed exactly the same problem, also on Tumbleweed.

Operating System: openSUSE Tumbleweed 20240320
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: X11
Processors: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Memory: 16 GiB of RAM
Graphics Processor: Intel Corporation UHD Graphics 620
Comment 2 Karl Ove Hufthammer 2024-07-06 14:20:44 UTC
I can confirm this bug. It makes Kompare almost unusable.

Operating System: openSUSE Tumbleweed 20240703
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2
Manufacturer: MSI
Product Name: MS-7673
System Version: 1.0
Comment 3 Yevhen Popok 2024-08-31 07:13:03 UTC
Didn't have this problem when Fedora built package with QT5  (v24.05.2).
Now, for v24.08 min required KDE Framework version was raised from 5.24 to 6.0, so I expect that many users will be affected by this.
The last unaffected Flatpak version for me was 24.02.2 built with runtime 5.15-23.08 (see https://github.com/flathub/org.kde.kompare/issues/36).
Comment 4 Kevin Kofler 2024-10-14 02:38:12 UTC
*** Bug 494597 has been marked as a duplicate of this bug. ***
Comment 5 Suzuco 2024-10-24 03:18:45 UTC
I can confirm this bug and it's been like this for quite long time. I'm on a dual monitor setup with both at 100% scaling. Changing font family won't help; changing font size to >=12 can partially solve the problem for me, but the line numbers and code are still slightly misaligned.

Operating System: openSUSE Tumbleweed 20241018
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10850H CPU @ 2.70GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Quadro T2000/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 20SQSQ2200
System Version: ThinkPad P17 Gen 1
Comment 6 Arek Guzinski 2024-10-29 13:36:56 UTC
I can confirm this on current neon.

It started after I reeinstalled my system (with the newly rebased on 24.04) and switched to a higher resolution screen. Since I did both at the same time, I can't really tell which is the cause.

I also tried starting it with QT_SCALE_FACTOR=1 but that didn't change anything.