You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated a Fedora 39 system with a 4K monitor to Fedora 40 and the megasync user interface is now at something like 4 x normal scale (with massive fonts also).
Other QT5 applications (VirtualBox, KeepassXC, BCompare and others) are all scaling correctly. I have qt5ct installed and set to a font size of 10. Importantly, while the screen is 4K it is so massive you don't need to scale things up for it. Maybe megasync is trying to be too clever and compensating for a small 4K laptop screen? In any event it is ignoring QT5 settings.
I've tried deleting the ~/.local/share/data/Mega Limited/ directory and staring again but same results.
Where is it getting it's information from? I cannot swear this issue didn't happen before the f39 to f40 upgrade because I cannot recall the last time I opened megasync. It is possible the megasync update to v5.2 did it.
The text was updated successfully, but these errors were encountered:
I updated a Fedora 39 system with a 4K monitor to Fedora 40 and the megasync user interface is now at something like 4 x normal scale (with massive fonts also).
Other QT5 applications (VirtualBox, KeepassXC, BCompare and others) are all scaling correctly. I have qt5ct installed and set to a font size of 10. Importantly, while the screen is 4K it is so massive you don't need to scale things up for it. Maybe megasync is trying to be too clever and compensating for a small 4K laptop screen? In any event it is ignoring QT5 settings.
I've tried deleting the ~/.local/share/data/Mega Limited/ directory and staring again but same results.
Where is it getting it's information from? I cannot swear this issue didn't happen before the f39 to f40 upgrade because I cannot recall the last time I opened megasync. It is possible the megasync update to v5.2 did it.
The text was updated successfully, but these errors were encountered: