| Summary: | Visiting Fonts KCM changes antialliasing settings without warning | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Matej Mrenica <matejm98mthw> |
| Component: | kcm_fonts | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | arojas, bhush94, bugseforuns, c.roux_atmos, fabian, filipfila.kde, finoderi, freefreeno81, gianluca.pettinello, gszymaszek, matejm98mthw, mayavi.nair, nate, parag.lkml, pepko94, postix, slartibart70, unassigned-bugs |
| Priority: | VHI | ||
| Version: | 5.16.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=409374 | ||
| Latest Commit: | https://commits.kde.org/plasma-desktop/b0f1d6620d78235e5b85defab880d68129f7a4e9 | Version Fixed In: | 5.16.4 |
| Sentry Crash Report: | |||
| Attachments: | fonts.conf; | ||
|
Description
Matej Mrenica
2019-07-05 09:44:25 UTC
Same for me Can you provide ~/.config/kdeglobals and ~/.config/kcmfontrc files? can you also pastebin ~/.config/fontconfig/fonts.conf? (In reply to Bhushan Shah from comment #4) > can you also pastebin ~/.config/fontconfig/fonts.conf? I don't have this one. Also happens to me randomly, this is annoying, I hope it will get fixed soon (・ω・｀) Happens to me even without opening `Font Settings`. (In reply to shscs911 from comment #7) > Happens to me even without opening `Font Settings`. How does it happen for you then? (In reply to mthw0 from comment #8) > How does it happen for you then? It happened when I was changing Splash Screens and re-logined. All the fonts were non anti-aliased including the notifications. After unchecking `Exclude range 0-99` and re-login, it was back to normal. After a shutdown and fresh start, everything was normal including notification fonts, but in the middle of browsing in Firefox it changed. One tab was normal, but the next tab onwards, fonts were non anti-aliased. I had recently installed and removed Deepin DE and found some leftover config in `~/.config/fontconfig/conf.d/`. Is it somehow related? Sorry for the rant. Created attachment 121483 [details]
fonts.conf;
There are several <match target="font"> with different antialiasing settings. I suspect that the font config file generating got broken.
I can fully confirm mthw0's and shscs911's descriptions. #### System Operating System: Manjaro Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 5.1.16-1-MANJARO Since nobody mentioned this, this issue doesn't seem to exist on Wayland. *** Bug 409793 has been marked as a duplicate of this bug. *** I'm affected unfortunately. Happens when switching to and from "font management". There's also some other trigger because I had to look at awful kana when I opened Audacious this morning. "Skip antialiasing for range" 0-99 toggles itself. *** Bug 409374 has been marked as a duplicate of this bug. *** I suspect this broke with https://cgit.kde.org/plasma-desktop.git/commit/?id=08ec9a036bf5b3ee102938ad332f624adc1060b9 Bhushan, could you take a look? *** Bug 410072 has been marked as a duplicate of this bug. *** I still cannot reproduce this bug on openSUSE TW, and I'm trying quite hard. I noticed that all reports about this bug seem to come from users of Arch or derivatives, so maybe it's something with compile options or other library versions. Can someone build it with -fsanitize=address and/or run with valgrind? I think that we're chasing some uninitialized variables. I (OP) have checked and I don't seem to have this problem anymore. I remember deleting "~/.config/kcmfonts" but I am not sure if it is what fixed this. I can reproduce, investigating - it's unrelated to 08ec9a036bf5b3ee102938ad332f624adc1060b9 [Manjaro] I also experienced this. It was triggered by changing the font and then it wouldn't stop happening. I deleted fonts.conf in the home dir and generated it with qt5ct. Haven't touched the Fonts kcm since and have been left alone by the bug. Alright, found the issue. This is indeed a (very tricky) case of uninitialized variables. The problem is in PreviewImageProvider::requestImage, which saves the (In reply to Antonio Rojas from comment #23) Alright, found the issue. This is indeed a (very tricky) case of uninitialized variables. The problem is in PreviewImageProvider::requestImage, which saves the xft exclude range to temporary variables oldStart, oldEnd which are not initialized, then sets the exclude range to (0,0) to perform some computations, and finally restores the old exclude range from the oldStart, oldEnd variables. The issue comes up when the original exclude range is (0,0), in which case xft.getExcludeRange does not assign any value to the variables. So, at the end, the exclude range was set to whatever random values these variables were storing. Fixed in https://phabricator.kde.org/D22707 by properly initializing the variables. I have still got this problem as of today. It has done several times today already. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 Kernel Version: 5.2.2-arch1-1-ARCH OS Type: 64-bit Thanks so much Antonio! Git commit b0f1d6620d78235e5b85defab880d68129f7a4e9 by Antonio Rojas. Committed on 24/07/2019 at 06:03. Pushed by arojas into branch 'Plasma/5.16'. Properly initialize oldStart and oldEnd in PreviewImageProvider::requestImage Otherwise they may not get assigned any value if the xft exclude range is (0,0), which will make them write random values to the xft exclude range later. Differential Revision: https://phabricator.kde.org/D22707 M +1 -1 kcms/fonts/previewimageprovider.cpp https://commits.kde.org/plasma-desktop/b0f1d6620d78235e5b85defab880d68129f7a4e9 I can confirm, the issue is fixed for me (Plasma 5.16.3, Frameworks 5.60.0, Qt 5.13.0, 5.2.2-arch1-1). Thank you. |