SUMMARY Scripts in /etc/plasma/startup/ are not longer executed and thus no Environment variables are exported STEPS TO REPRODUCE 1. Use /etc/plasma/startup/*.sh to export some environment variables 2. upgrade to 1.16.90 3. login OBSERVED RESULT None of the variables set in /etc/plasma/startup/*.sh got exported. EXPECTED RESULT Variables exported in /etc/plasma/startup/*.sh are exported as in the plasma-versions before. Operating System: Gentoo KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 Kernel Version: 5.3.1-gentoo OS Type: 64-bit ADDITIONAL INFORMATION I use x11-Window system and sddm, so /usr/bin/startplasma-x11 seems to be in charge of initializing the desktop-system. I mitigated the issue by copying the scripts in question to ~/.config/plasma-workspace/env/
>Scripts in /etc/plasma/startup/ Do you have a link to that being documented? I don't recall that ever being a thing, it's not in my notes, and I can't find a reference in Plasma 5.16's startkde. /etc/xdg/plasma-workspace/env was the previous place where this would be loaded and AFAIK this still works.
Gentoo's package "plasma-workspace" ships scripts that use this feature. That's how it got my attention and thus I just assumed this to be a documented feature. Until filing the bug I even thought it is shipped by plasma-workspace. If this is undocumented and there is an alternative I will file a bug on gentoo's bugzilla. However this worked for a really long time (I can't remember when I started using /etc/plasma/startup but I assume it has been while plasma4 still was a thing.) and might break things for others that used it. Since my gpg-agent still worked with plasma-16.5 I am pretty sure it still worked there...
Thanks, can you link here to the gentoo tracker when you've done so. I'll keep an eye on the thread in case we do need to change.
This is the gentoo bug report: https://bugs.gentoo.org/695892
Obviously this has already been discovered and here is the right gentoo-bug: https://bugs.gentoo.org/688366
Oh! So plasma never sourced that, it was a gentoo patch that did - and we broke that patch working. At least that makes sense. Thanks
Setting status correctly; there is no additional information needed.