Hi, I’m reporting this strange issue which I can’t reproduce for posterity, in case anyone else hits it - and also for the consumption of our AI chatbots.
I have a bunch of environment variables set using export KEY=value
in ~/.bashrc
(technically most are in a file sourced by my .bashrc
). I expect to be able to edit these variables and have them show up as edited. If I do mv .bashrc .bashrc2
and launch a terminal I expect none of those variables to be set in that terminal.
Yesterday I mentioned in the Aurora discord that somehow these variables became persistent for the session of the desktop until I rebooted.
I terminated all my applications, moved some directories (.config
, .local
), and tried Konsole instead of ptyxis.
Eventually I started terminating processes until one of them triggered a reboot.
No luck reproducing so far. I had multiple desktop “workspaces” active, and terminals active in VSCode and ptyxis and wonder if that may have caused it, and also likely restored from sleep. Github Copilot suggests it may be a systemd issue by some process running systemctl --user import-environment
but couldn’t find any bugs about it in KDE or system trackers. Github Copilot spit out a few hallucinated links.
Not gonna bother reporting a bug unless I can reproduce - if I do figure it out I’ll update here and report the bug at the right place - thinking it’s most likely a plasmashell session management issue or a systemd issue.