Closed ChitranshuV closed 1 year ago
FSearch itself doesn't control the font rendering, this is all done by GTK, so there's nothing I can do about that. To me it seems like the GTK-portal implementation (which is forced to be used with GTK_USE_PORTAL=1
) fails to talk to the desktop portal of your system and hence doesn't know which theme, font and font settings it's supposed to use. So maybe your desktop portal isn't installed or configured properly. Do you have xdg-desktop-portal-kde
installed?
Yes. I do have xdg-desktop-portal-kde
, but I was still not able to use KDE file picker in VS Code and Firefox. The blogs and forums suggested to export GTK_USE_PORTAL=1
to force this behavior. But now it breaks font rendering in all the GTK application; they are very few. The workaround I found is to launch fsearch and similar GTK GUI application with GTK_USE_PORTAL=0
argument. Like this
Describe the bug
The UI of fsearch and all the settings have jagged fonts.
To Reproduce Launch fsearch from terminal using
fsearch
Expected behavior The fonts should be sharp and clear.
Screenshots
System informatiion Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: Victus by HP Laptop 16-e0xxx
How you installed FSearch - AUR FSearch 0.2.2 (AUR-stable)
localectl status
Additional context Launching fsearch with GTK_USE_PORTAL=0 fixes this somehow.
GTK_USE_PORTAL=0 fsearch
Can there be a fix that can be pushed so that users don't resort to this kind of hack to get fonts perfect in the application.
UPDATE
I discovered that I had set
export GTK_USE_PORTAL=1
in my.bash_profile
to force all applications to use the KDE file picker instead of the GTK one. I believe this is what was actually messing with fsearch.