I believe that I am in the right repository for the code that creates the file /usr/sbin/lightdm-session. That file has, inter alia, this content:
# temporary storage of error messages
ERR=$(mktemp --tmpdir config-err-XXXXXX)
It seems to me - and web searches provide some suppport for this view - that users who stumble upon the /tmp file will presume that its existence indicates that something has gone wrong somewhere. Yet, does it? Does it even the file is empty?
I suggest the following. If possible, the file shall be created (or left undeleted) only if there is an actual error, and in that case the error shall indeed by described within the file. If for some reason the file must exist even when it contains no error message, then the file could contain some text to that effect (# Any error messages from lightdm will appear here) and/or the file could be given a new, more innocuous name (such as lightdm.log).
I believe that I am in the right repository for the code that creates the file /usr/sbin/lightdm-session. That file has, inter alia, this content:
It seems to me - and web searches provide some suppport for this view - that users who stumble upon the /tmp file will presume that its existence indicates that something has gone wrong somewhere. Yet, does it? Does it even the file is empty?
I suggest the following. If possible, the file shall be created (or left undeleted) only if there is an actual error, and in that case the error shall indeed by described within the file. If for some reason the file must exist even when it contains no error message, then the file could contain some text to that effect (
# Any error messages from lightdm will appear here) and/or the file could be given a new, more innocuous name (such aslightdm.log).