Bug 420294 - Chrome drops Qt scaling environment variables
Summary: Chrome drops Qt scaling environment variables
Status: RESOLVED LATER
Alias: None
Product: plasma-browser-integration
Classification: Plasma
Component: Chrome (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-19 09:05 UTC by Andrew Udvare
Modified: 2020-04-19 18:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Udvare 2020-04-19 09:05:11 UTC
SUMMARY

This is related to https://bugs.kde.org/show_bug.cgi?id=415421

When I run a KDE application such as Ark via Chrome (by clicking on the file in the download manager), it shows up with the incorrect scale because it does not have the environment variables that would normally be set:

QT_AUTO_SCREEN_SCALE_FACTOR=0
QT_SCREEN_SCALE_FACTORS=DVI-I-0=1.5;DVI-I-1=1.5;HDMI-0=1.5;DP-0=1.5;DP-1=1.5;DP-2=1.5;DP-3=1.5;DP-4=1.5;DP-5=1.5;

Chrome/Chromium now runs with a minimum environment which causes applications to lose environment variables set by Plasma or in ~/.xprofile or similar. However since it seems to use xdg-open, I can edit the .desktop file for an app and add environment variables, but this is very inconvenient.

Even adding `export QT_AUTO_SCREEN_SCALE_FACTOR=0` to .xprofile (and logging in again) does not fix this.

STEPS TO REPRODUCE
1. Open Chrome, download a zip file.
2. Click on the file in the download bar or download manager to open it with Ark.

OBSERVED RESULT

Ark opens with incorrect scale.

EXPECTED RESULT

Ark should respect the QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS values when opened from anywhere.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo / 5.18.4
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2020-04-19 18:32:35 UTC
PBI cannot influence that.


If we make kde-open5 use ApplicationLaunchJob and we merge the patches that make ApplicationLaunchJob use the systemd launch env, that will resolve the issue