Running PopOS which is based on Ubuntu 19.04 and using Gnome.
I have 4k display and Cryptomator UI is tiny!
Any way to fix it?
Which version of Cryptomator are you using? We had an issue regarding the small size of cryptomator with high DPI displays a year ago. You may found a solution there:
Running latest appimage version so 1.4.14
yes saw that but proposed solution was to change gnome scaling which breaks other apps
cryptomator only app I am having issues with
anyone able to help?
I set the scaling factor through Gnome setting tool, and most applications display correct size except Cryptomator.
I have no idea why, but
gsettings set org.gnome.desktop.interface scaling-factor 2
works for Cryptomator.
Same here, the scaling for Cryptomator (AppImage) is at 100 %, although in Gnome Settings the scaling is at 200 %. All other Apps follow Gnome Settings and show with 200 % scaling.
The workaround from @zhouer seems to change the global scaling factor and I prefer not to touch this setting as I do not know how it differs from the Gnome Settings (i.e. the GUI).
Is it possible to change the AppImage in a way that it follows the scaling factor from Gnome Settings?
System: Fedora 32 Workstation with Gnome
Hardware: Dell XPS 13 with HiDPI
AppImage Cryptomator 1.5.5
Below you can see my current setting:
$ gsettings get org.gnome.desktop.interface scaling-factor uint32 0
@wurstsemmel You can also start the cryptomator with
GDK_SCALE environment variable, for example:
@zhouer Thank you for the quick reply. I can confirm that
opens Cryptomator with 200 % scaling.
Next step is to make the AppImage follow the scaling settings in Gnome Settings out-of-the-box, to make this workaround unnecessary.
I will file a new bug for Cryptomator and ask whether this is something what can be changed during the build process of the AppImage or whether a bug needs to be filed upstream at OpenJFX (?).
Edit 11 Jun 2020: Link to the bug report: https://github.com/cryptomator/cryptomator/issues/1242
For the record:
I filed a bug with the number JDK-8248126 at OpenJFX project. http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8248126
Dear @nekromantik and other affected users, please use the following URL to comment, describe your issue and raise awareness for the bug. http://bugreport.java.com/bugreport/bug_info.do?bug_id=641DA2D31D74996CB43293BC9CA313E4
Thank you very much!
For those stepping by this old topic:
With Cryptomator 1.6.0 an update to JDK 17 was done which resolves the issue.
This topic may be closed.