Hide Forgot
Description of problem: Starting mediawriter on a 4K laptop screen using the Compiz/Mate desktop is unusable as the App is not using the system font size selections. Version-Release number of selected component (if applicable): mediawriter-4.0.7-0.fc24.x86_64 Linux nohost.somedomain 4.8.11-200.fc24.x86_64 #1 SMP Mon Nov 28 19:36:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Using latest Mate/Compiz F24 desktop start mediawriter See that app is not using system font size selections but seems to be defaulting to circa 8 point font which is pretty much unreadable on a 4K screen using 16 point size fonts for all system font settings. Steps to Reproduce: 1. As above 2. 3. Actual results: App text is unreadable as it's too small Expected results: App text to use system font size settings and therefore be readable. Additional info:
Thanks for the report. I have a similar one upstream and I'm planning to do something about it in near future. In the meantime, please consult [0] to see what options are there to work around the problem before I fix it properly. Sorry about the issues. [0] http://doc.qt.io/qt-5/highdpi.html#high-dpi-support-in-qt
Thanks for the info Martin...my workaround was to do it on a different, lower resolution, machine!! :)
Hi, Same problem here in Africa with hidpi laptop and no other screen. The only workaround is to use a magnifiying glass over the screen! Fedora 25.
I'm setting this to ASSIGNED. I'll fix this either in mediawriter, in Qt itself or in QGnomePlatform...
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.