For future reference, the short version of this issue is that it is almost
always caused by running geany via [`sudo`](https://kb.iu.edu/d/amyi) on
systems which have configured `sudo` not to change `$HOME`, and that it can be
resolved by closing geany and then running this in a terminal:
rm ~/.config/geany/geany_socket*
Previously reported in #294 and #1411
Long discussion of the issue at #1150
Request for more user-friendly recovery from the issue at #2102
--
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/1615#issuecomment-471110711
