Bug 404444

Summary:	Damaged font in Sidebarview after scrolling
Product:	[Frameworks and Libraries] frameworks-qqc2-desktop-style	Reporter:	Lucia Mrenica <lucia.mrenica>
Component:	general	Assignee:	Marco Martin <notmart>
Status:	RESOLVED FIXED
Severity:	normal	CC:	imaginator, kde, lucia.mrenica, nate
Priority:	NOR
Version First Reported In:	5.55.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Lucia Mrenica 2019-02-16 13:09:36 UTC

SUMMARY

STEPS TO REPRODUCE
1. Open System Settings

OBSERVED RESULT
After few 'scrollings', font on labels gets corrupted like this: https://imgur.com/a/fcDDgjT

EXPECTED RESULT
This shouldn't happen

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.55
Qt Version: 5.12.1

ADDITIONAL INFORMATION
Intel HD 4400 GPU, 1366x768 screen resolution, no hidpi settings

Comment 1 Nate Graham 2019-02-18 22:31:30 UTC

Can reproduce with touchpad scrolling. I'd thought this was fixed with https://cgit.kde.org/qqc2-desktop-style.git/commit/?id=22a2f9eaae138d6fef510800d4333b88efbb8649.

it's certainly better than before, but I can still get it into a fractional pixel state with a very subtle two-finger scroll gesture.

Comment 2 Nate Graham 2019-05-09 21:40:55 UTC

*** Bug 407266 has been marked as a duplicate of this bug. ***

Comment 3 imaginator 2019-05-10 05:23:11 UTC

Interesting: the initial state of the sidepanel fonts is "corrupted". When I scroll *down* to the end they suddenly are OK. When I then scroll *up* to the end, they get corrupted again. Between the endpoints they stay either corrupted or OK. 
HTH.

Comment 4 imaginator 2019-05-10 14:38:23 UTC

Would it be enough then to apply the patch and rebuild/install systemsettings-5.12.8 in order to see whether it works?

--
QT-5.10.1
FW-5.46.0
Pl-5.12.8

Comment 5 imaginator 2019-05-10 16:48:18 UTC

OK, re-build systemsettings as described in Comment 4 but the problem was still there. So either my approach was wrong or the patch doesn't work.

Comment 6 Nate Graham 2019-05-10 16:50:05 UTC

The fix was made to the qqc2-desktop-style framework, so you would need to rebuild that from git master, or cherry-pick 22a2f9eaae138d6fef510800d4333b88efbb8649.

But yes, that fix evidently did not completely solve the problem, which is why this bug report is still open. :)

Comment 7 imaginator 2019-05-10 16:56:28 UTC

Thanks. Was a quick trial and error anyway. ;)

Comment 8 Lucia Mrenica 2020-05-23 11:59:55 UTC

Is anybody still able to reproduce this issue? I personally cannot, but I am not on the same hardware anymore. Could someone check? It's been a year since the last comment and if it's not present anymore I would like to close this.

Comment 9 Nate Graham 2020-05-23 13:20:06 UTC

I cannot either. Let's call it fixed for now. If someone sees it again, we can re-open.