https://bugs.kde.org/show_bug.cgi?id=356850
Bug ID: 356850
Summary: KDEVARTMP environment variable is ignored after
upgrade from KDE 4 to 5
Product: plasmashell
Version: 5.4.3
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: db0...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
I previously used a .sh file in ~/.kde/env to mkdir a folder in my /tmp
ramdrive and set KDEVARTMP to that folder. This resulted in KDE caching
everything in RAM and seemed to have no ill effects. I have since upgraded from
KDE 4 to 5, moved the .sh script to the new corresponding location -
~/.config/plasma-workspace/env - and noticed that although it is executed and
the environment variable set, that variable is seemingly no longer used. KDE
continues to use its default path in /var/tmp
Is this intentional and the documentation outdated, or has KDEVARTMP been
deprecated, or is something else stopping this from working with the folder I
designate? Thanks in advance.
Reproducible: Always
Steps to Reproduce:
1. export KDEVARTMP from a startup env script, e.g. as /tmp/KDEVARTMP (prefaced
by the required mkdir so this folder exists in advance)
Actual Results:
2. KDEVARTMP is set
3. It does not have the documented effect, i.e. changing kdecache-* directories
to be placed in the KDEVARTMP path
Expected Results:
3. kde-cache-* et al should be placed in the KDEVARTMP path as claimed in the
documentation
--
You are receiving this mail because:
You are watching all bug changes.
