Well, IMO again, it's really a distribution's `sudo` configuration issue. In no circumstances should applications be left to believe that a directory is the current user's home if it shouldn't be considered as such. The issue you describe can only happen with a badly configured `sudo`, or somebody willingly setting some specific environment variable to point in another user's directory, and still have write permission there. Meh.
This said, maybe altering the dialog to suggest where to look could be fine I guess. Offering to automatically recover seems useless and potentially dangerous to me, given what can actually lead to this situation -- e.g., no reasonable usage. > 2. if the socket is created by Geany running as root then Geany running > as user can't delete it. That's not necessarily true: if the user has write permission on the directory containing the file it can delete that file. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2102#issuecomment-471333663
