Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#49495 - [nautilus] restarting nautilus doesn't respect environment set with $HOME/.profile
Attached to Project:
Arch Linux
Opened by Amit Mendapara (cristatus) - Saturday, 28 May 2016, 10:24 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 31 July 2016, 13:07 GMT
Opened by Amit Mendapara (cristatus) - Saturday, 28 May 2016, 10:24 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 31 July 2016, 13:07 GMT
|
DetailsDescription:
When we restart Nautilus with "Icons on Desktop" enabled, the environment variables set from "$HOME/.profile" are not respected. Additional info: * gnome-shell 3.20.1-1 * nautilus 3.20.1-1 Steps to reproduce: * enable "Icons on Desktop" from tweak-tools * logout and login again * make the attached script executable * run the script by double click (need to configure nautilus to allow run script with double click) * check /tmp/env-test.txt * restart nautilus with "nautilis -q" (or disable/enable "Icons on Desktop" from tweak-tools) * run the script again by double click * check /tmp/env-test.txt |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 31 July 2016, 13:07 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#49194
Sunday, 31 July 2016, 13:07 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Amit Mendapara (cristatus) -
Sunday, 31 July 2016, 05:43 GMT
Probably, duplicate of #49194
Comment by Amit Mendapara (cristatus) -
Sunday, 31 July 2016, 05:47 GMT
Yes, that's the case. Setting variables with .pam_environment solved the issue.
test.sh