https://bugs.kde.org/show_bug.cgi?id=226344
--- Comment #5 from rbing...@acm.org --- This is a side note. I am responding only because I was apparently added as a CC to this bug in Jan 2017 (as reporter of a related bug 375717). Alas, I cannot help with the Linux environment NEEDSINFO. However, I note that Mr. Feck's last post of 2010-02-11 "...so you might check if you have that variable defined to /tmp" presumptively also setting NEEDSINFO status, does *not* actually request an action on the part of the reporter nor a request to report back. "...you might check..." conveys a meaning of purely optional activity. There is no "call to action" language requesting an update of the bug report. The reporter "might" have checked his env vars and even fiddled them based on the bug updates but was under no call to action compulsion to report anything. I suggest that as https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging has guidelines for reporting bugs, there also needs to be a guideline for triage and developers in how to word NEEDSINFO requests to give reporters specific guidance motivation on what is needed and sample call to action language to actually update the bug report. R -- You are receiving this mail because: You are watching all bug changes.
