Correct folder, file placement and Environment Variable for disabling QML cache in Plasma 6?
Hi, Tumbleweed Plasma 6 here. Wondering if you know of the correct location for holding QT Plasma 6 QML Environment Variables? There has been a suggestion of '~/.config/environment.d/envvars.conf`. The directory does not exist by default. '/etc/environment' directory does not exist by default either so this very well could be the case. Suggested to me is "QML_DISABLE_DISK_CACHE=1" though I do not see that on the documentation page. Interested in variable to disable QML disk cache (bottom of page). Documentation reference:> https://doc.qt.io/qt-6/qmldiskcache.html QML_DISABLE_DISK_CACHE No '=1' is shown in examples. Quote from page, "The primary way of fine tuning the behavior regarding ahead of time compiled code and caching is via the environment variable QML_DISK_CACHE. This variable takes a comma-separated list of options, for example:" 🫥
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing: INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1 rpm on TW reports /etc/environment is not owned by any package, so optional according to admin desire. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 08-19-2024 01:43AM, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
Please explain more about the contents you add to "/etc/environment" if possible. I'm going to have to look them up because I do not know what they do at all as you may have already guessed.
rpm on TW reports /etc/environment is not owned by any package, so optional according to admin desire. Ok this is good to know.
Update on Disable of QML cache: Adding QML_FORCE_DISK_CACHE to /home/user/environment.d//envars.conf Appears to be a very, very bad decision at least on this machine. Resulting in *horrible* and a unusable desktop experience (application tabs unusable), I think maybe segfaulting. TTY1 even unable to open nano to modify file. In fact it was necessary to open a completely separate ICEWM session from SDDM and use nano to comment the entry out Even after commenting out the entry then powercycling and loading an X11 session desktop unusable...Added QML_FORCE_DISK_CACHE , powercycled.. machine still seizing up.....going to have to find default setting on this.... Found this to clear QML cache > https://github.com/NixOS/nixpkgs/issues/177720 # substitute -delete for -print if you want to see what happens instead of actually deleting the files find ${XDG_CACHE_HOME:-$HOME/.cache}/**/qmlcache -type f -delete Possibly turning off the Disk cache and not clearing QML cache caused prior problem. More investigation needed. Desktop appears to be stable for now with QML_FORCE_DISK_CACHE and QML cache cleared. -Greatest Hopes
-pj composed on 2024-08-19 03:10 (UTC-0500):
On 08-19-2024 01:43AM, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
The first prevents multiple building of one single kernel's initrd during a zypper up or dup, deferring build until all transactions affecting initrd building and/or content have been applied. The second causes automatic initrd regeneration to be applied to one specific kernel, instead of all installed kernels, preventing inclusion of some possibly failing component to initrds that may have been usable when last generated. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 08-19-2024 05:26AM, Felix Miata wrote:
-pj composed on 2024-08-19 03:10 (UTC-0500):
On 08-19-2024 01:43AM, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
The first prevents multiple building of one single kernel's initrd during a zypper up or dup, deferring build until all transactions affecting initrd building and/or content have been applied.
"multiple building of one single kernel's initrd" I thought 1 initrd for each kernel no more? It rebuilds again with each installed kernel? Does this help prevent the machine from becoming non-bootable and requiring a chroot? Something going wrong with building initrd can cause grub_ blank.. and require chroot? Machine here line 579 and 580 in /etc/zypp/zypp.conf set to > ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set multiversion.kernels = latest,latest-1,latest-2,latest-3,latest-4,latest-5,latest-6,latest-7,latest-8,latest-9,running,6.6.11-1
The second causes automatic initrd regeneration to be applied to one specific kernel, instead of all installed kernels, preventing inclusion of some possibly failing component to initrds that may have been usable when last generated.
"failing component" meaning part of initrd software included in snapshot? "applied to one specific kernel" < you mean the new kernel (included in the dup)? What can you tell me about the us of > 'dracut --regenerate-all --force' what I do think to know, is that it causes a regeneration of all the installed kernels' initrd's is that correct? Possible problem maker of sorts? Patrick Shanahan, says further in threads > subject file, environment, on tumbleweed is at /usr/etc/environment What do you think to place these variables in /usr/etc/environment and *not* in /etc/environment? Both of these directories are read during the boot process when created? -Regards
On Tue, Aug 20, 2024 at 8:45 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Patrick Shanahan, says further in threads > subject file, environment, on tumbleweed is at /usr/etc/environment
What do you think to place these variables in /usr/etc/environment and *not* in /etc/environment?
You should never edit anything in /usr. It is reserved for the distribution packages.
On 08-20-2024 01:23AM, Andrei Borzenkov wrote:
On Tue, Aug 20, 2024 at 8:45 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Patrick Shanahan, says further in threads > subject file, environment, on tumbleweed is at /usr/etc/environment
What do you think to place these variables in /usr/etc/environment and *not* in /etc/environment?
You should never edit anything in /usr. It is reserved for the distribution packages.
I have placed two systemD script files in > /usr/local/sbin> ls -lah total 8.0K drwxr-xr-x. 1 root root 88 Apr 20 23:20 . drwxr-xr-x. 1 root root 80 Jun 9 2021 .. -rwxr-xr-x. 1 root root 206 Apr 20 23:20 cpupower-ondemand-governor.sh -rwxr-xr-x. 1 root root 182 Feb 14 2024 PS2-Keyboard.sh Where is a better placement for these?
On Tue, Aug 20, 2024 at 9:46 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 08-20-2024 01:23AM, Andrei Borzenkov wrote:
On Tue, Aug 20, 2024 at 8:45 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Patrick Shanahan, says further in threads > subject file, environment, on tumbleweed is at /usr/etc/environment
What do you think to place these variables in /usr/etc/environment and *not* in /etc/environment?
You should never edit anything in /usr. It is reserved for the distribution packages.
I have placed two systemD script files in >
/usr/local/sbin
OK, /usr/local is explicitly for local stuff and packages should never place anything there. This is the exception that proves the rule.
ls -lah total 8.0K drwxr-xr-x. 1 root root 88 Apr 20 23:20 . drwxr-xr-x. 1 root root 80 Jun 9 2021 .. -rwxr-xr-x. 1 root root 206 Apr 20 23:20 cpupower-ondemand-governor.sh -rwxr-xr-x. 1 root root 182 Feb 14 2024 PS2-Keyboard.sh
Where is a better placement for these?
On 2024-08-19 08:43, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
rpm on TW reports /etc/environment is not owned by any package, so optional according to admin desire.
cer@Telcontar:~> cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on seperate lines # ALSA_CONFIG_PATH=/etc/alsa-pulse.conf SDL_AUDIODRIVER=pulse cer@Telcontar:~> cer@Telcontar:~> rpm -qf /etc/environment pam-1.3.0-150000.6.66.1.x86_64 cer@Telcontar:~> cer@Telcontar:~> l /etc/environment -rw-r--r-- 1 root root 157 Sep 24 2010 /etc/environment cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 08-19-2024 06:15AM, Carlos E. R. wrote:
On 2024-08-19 08:43, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
'/etc/environment' directory does not exist by default either so this very well could be the case.
All my openSUSE installations, regardless of primary DE, or whether Leap or TW or Slowroll, have a file named /etc/environment, currently containing:
INITRD_IN_POSTTRANS=1 SKIP_REGENERATE_INITRD_ALL=1
rpm on TW reports /etc/environment is not owned by any package, so optional according to admin desire.
cer@Telcontar:~> cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on seperate lines # ALSA_CONFIG_PATH=/etc/alsa-pulse.conf SDL_AUDIODRIVER=pulse cer@Telcontar:~>
Looks like /etc/environment is default with LEAP due to the commented out messages?
cer@Telcontar:~> rpm -qf /etc/environment pam-1.3.0-150000.6.66.1.x86_64 cer@Telcontar:~>
This above rpm -qf (--query format) shows "pam env module" is parsing the environment? Can you explain a bit more about this please? Why did you not follow with 'QUERYFMT' format string?
cer@Telcontar:~> l /etc/environment -rw-r--r-- 1 root root 157 Sep 24 2010 /etc/environment cer@Telcontar:~>
On 2024-08-20 09:17, -pj via openSUSE Users wrote:
On 08-19-2024 06:15AM, Carlos E. R. wrote:
On 2024-08-19 08:43, Felix Miata wrote:
-pj composed on 2024-08-19 01:08 (UTC-0500):
rpm on TW reports /etc/environment is not owned by any package, so optional according to admin desire.
cer@Telcontar:~> cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on seperate lines # ALSA_CONFIG_PATH=/etc/alsa-pulse.conf SDL_AUDIODRIVER=pulse cer@Telcontar:~>
Looks like /etc/environment is default with LEAP due to the commented out messages?
/etc/environment file exists and is used in Leap. On TW it has a different location, "/usr/etc/environment", but will also use "/etc/environment" if it exists.
cer@Telcontar:~> rpm -qf /etc/environment pam-1.3.0-150000.6.66.1.x86_64 cer@Telcontar:~>
This above rpm -qf (--query format) shows "pam env module" is parsing the environment? Can you explain a bit more about this please? Why did you not follow with 'QUERYFMT' format string?
It is not "query format", but "query file" man rpm: -f, --file FILE Query package owning FILE. Ie, query the rpm that owns the given file and path. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Mon, 19 Aug 2024 01:08:47 -0500 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, Tumbleweed Plasma 6 here. Wondering if you know of the correct location for holding QT Plasma 6 QML Environment Variables? There has been a suggestion of '~/.config/environment.d/envvars.conf`. The directory does not exist by default.
'/etc/environment' directory does not exist by default either so this very well could be the case.
/etc/environment is a file not a directory. Historically it has been used by pam to set environment variables in environments when starting them up. See man 7 environ for more info. Now it has been 'embraced and extended' by systemd, which also uses such things as ~/.config/environment.d/*.conf See https://www.freedesktop.org/software/systemd/man/latest/environment.d.html for more info. I know nothing about specific plasma variables.
participants (5)
-
-pj -
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
Felix Miata