Ingo Schwarze wrote: > The problem only occurs when the initialization file starts a background > process that prints to standard output, which is even more crazy.
The example given was a foreground process. > Normal output generated by the initialization file occurs before > the "echo ENV", so it won't prevent security(8) from finding ENV at > the end of the output. I disagree with this. Some testing showed that running neofetch with no command line arguments, it will generate ANSI escape codes to print colors to the terminal. This sufficiently corrupts the output stream that security(8) is trying to parse that it does break, and cannot find ENV. You can validate this is true by adding the --stdout switch to neofetch so it will print a plain-text summary to the console instead. security(8) does not misbehave if you do this. Running neofetch, fortune, etc. tools from .profile is not uncommon. > Then again, even though printing from the background is crazy, the > totally misleading error message "Failed to find ENV" is not good, > and for that reason, i think i should commit the patch appended > below. I agree the message is misleading.
