[Bug 1204434] New: env exports in /etc/environment don't work anymore after snapshot update
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434 Bug ID: 1204434 Summary: env exports in /etc/environment don't work anymore after snapshot update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: c.j@tuta.io QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After today's update (to snapshot 20221016 or perhaps was it 20221015) "export QT_SCALE_FACTOR_ROUNDING_POLICY=PassThrough" in /etc/environment doesn't have any effect anymore (needed to fix QT5 apps scaling on hidpi displays, i.ex Yast and chessx are 2x too big on Gnome with 1.5x Gnome font scaling). It seems that the variables exported in /etc/environment aren't applied anymore, because starting an app with "QT_SCALE_FACTOR_ROUNDING_POLICY=PassThrough" in gnome-terminal WORKS. Does anyone know which update in snapshot 20221016 or 20221015 is responsible for breaking the env set in /etc/environment ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c1
--- Comment #1 from C J
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c2
--- Comment #2 from C J
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c3
Luciano Santos
$ man environment
They are supposed to be the first source of truth. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c4
--- Comment #4 from C J
That's why we have manpages for:
$ man environment
1. I worked before and stopped after an update. -> Who would think to look into the cli man? 2.The command "environment" doesn't exit. -> Who would think to look into the cli man? But thanks for the feedback. Glad I could learn something today. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c5
C J
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c6
--- Comment #6 from Luciano Santos
(In reply to Luciano Santos from comment #3)
That's why we have manpages for:
$ man environment
1. I worked before and stopped after an update. -> Who would think to look into the cli man?
2.The command "environment" doesn't exit. -> Who would think to look into the cli man?
But thanks for the feedback. Glad I could learn something today.
Yes. Usually, configuration files have their own manpage, under section 5 [1]. You were using a wrong syntax in the first place. Yes, it was working before, but at the risk of happening what you experienced. In Leap 15.4 we have:
$ rpm -q pam pam-1.3.0-150000.6.58.3.x86_64 $ cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on separate lines #
And, in Tumbleweed:
$ rpm -q pam pam-1.5.2-8.1.x86_64 $ cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on separate lines #
The syntax is still the same: "KEY=VAL". And, yes, the latest update to the PAM package brought a new patch that seems to be, enforcing the expected syntax now. [1] https://www.commandlinux.com/man-page/man5/ -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434
http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c7
C J
participants (1)
-
bugzilla_noreply@suse.com