Bug 25665 - mageiawelcome.py is not resistant against QT_SCALE_FACTOR
Summary: mageiawelcome.py is not resistant against QT_SCALE_FACTOR
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: papoteur
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-07 00:17 CET by Elmar Stellnberger
Modified: 2021-09-07 14:08 CEST (History)
0 users

See Also:
Source RPM: mageiawelcome-2.01-1.mga7.src.rpm
CVE:
Status comment:


Attachments
mageia welcome started without and with scaling factor (413.06 KB, image/png)
2019-11-08 11:15 CET, Elmar Stellnberger
Details

Description Elmar Stellnberger 2019-11-07 00:17:23 CET
/usr/share/mageiawelcome/mageiawelcome.py assumes QT_SCALE_FACTOR=1. If I want to adjust this setting for icewm to adapt QT apps to HiDPI fonts and graphics get scaled differently so that you can no more read the output of mageiawelcome.py
Comment 1 Lewis Smith 2019-11-07 20:44:43 CET
This may be an enhancement request: that the user should be able to alter the scale factor; but I cannot judge.
Assigning to Yves for MageiaWelcome. If you think it is an enhancement rather than a fault, please set Severity accordingly.

Assignee: bugsquad => yves.brungard_mageia

Comment 2 papoteur 2019-11-08 08:44:30 CET
Hi Elmar,
Which factor did you use?
What are the size of the screen, in pixel?
Can you provide a screenshot?
Comment 3 Elmar Stellnberger 2019-11-08 11:03:28 CET
3840x2160, scaling factor of 1.33
Comment 4 Elmar Stellnberger 2019-11-08 11:15:01 CET
Created attachment 11343 [details]
mageia welcome started without and with scaling factor
Comment 5 papoteur 2019-11-14 12:06:53 CET
Hi Elmar,
What is reported in console when launching:
QT_LOGGING_RULES=qml=true mageiawelcome

I tried that mageiawelcome detects itself that the display is HDI, but it seems to fail. 
Note that QT_SCALE_FACTOR=2 is working fine, for what I see.
Comment 6 Elmar Stellnberger 2019-11-14 13:03:46 CET
qml: Screen:  1.33 4.705708322117859
Comment 7 Elmar Stellnberger 2019-11-14 13:08:07 CET
  Interestingly when I set a QT_SCALE_FACTOR in /etc/X11/Xsession then overriding it later on on the console is ineffective for mageiawelcome:
$ QT_SCLAE_FACTOR=2 QT_LOGGING_RULES=qml=true mageiawelcome
qml: Screen:  1.33 4.705708322117859
$ QT_SCLAE_FACTOR=1 QT_LOGGING_RULES=qml=true mageiawelcome
qml: Screen:  1.33 4.705708322117859

  Nonetheless as far as I remember the distortions also appear with a QT_SCALE_FACTOR of 1.33 when not setting it in Xsession.
Comment 8 papoteur 2019-11-14 15:42:05 CET
(In reply to Elmar Stellnberger from comment #7)
> $ QT_SCLAE_FACTOR=2 QT_LOGGING_RULES=qml=true mageiawelcome
> qml: Screen:  1.33 4.705708322117859
> $ QT_SCLAE_FACTOR=1 QT_LOGGING_RULES=qml=true mageiawelcome
> qml: Screen:  1.33 4.705708322117859

Hello,
You used SCLAE instead of SCALE, which can explain what this has no effect ;)
Comment 9 papoteur 2019-11-14 15:43:43 CET
And, yes, I confirm the distorsion with factor 1.33
Comment 10 Aurelien Oudelet 2021-07-06 13:17:43 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 11 Marja Van Waes 2021-09-07 14:08:59 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.