<p>The problem at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="210318488" data-permission-text="Issue title is private" data-url="https://github.com/geany/geany/issues/1411" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/1411/hovercard" href="https://github.com/geany/geany/issues/1411">#1411</a> is more than just the root problem since its involving a foreign filesystem as well, and since few people seem to have that setup to care or develop or test it, nothing has happened for several years.</p>
<p>Best to keep this separate for the best chance of someone doing something, and in the process it can solve part of <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="210318488" data-permission-text="Issue title is private" data-url="https://github.com/geany/geany/issues/1411" data-hovercard-type="issue" data-hovercard-url="/geany/geany/issues/1411/hovercard" href="https://github.com/geany/geany/issues/1411">#1411</a>.</p>
<p>Adding the effective UID to the link name and testing the ownership of the socket, not the link seems fairly simple and somebody might contribute it test it and accept it.</p>
<p>All other "recovery" methods are more complex and less likely to happen.</p>
<p>In fact most of the regular contributors seem to be of the opinion that there are more useful things to spend time on than occasional problems caused by someone else's misconfiguration.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/2102#issuecomment-472662292">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ-RwqcVPjMnzD1tXaqeVZWmMx2dsks5vWZ2bgaJpZM4bmS_c">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ2_n3Lg_zd1itiHiGfyQu8O1UoKVks5vWZ2bgaJpZM4bmS_c.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #2102: The problem at #1411 is more than just the root problem since its involving a foreign filesystem as well, and since few people seem to have that setup to care or develop or test it, nothing has happened for several years.  \r\n\r\nBest to keep this separate for the best chance of someone doing something, and in the process it can solve part of #1411.\r\n\r\nAdding the effective UID to the link name and testing the ownership of the socket, not the link seems fairly simple and somebody might contribute it test it and accept it.\r\n\r\nAll other \"recovery\" methods are more complex and less likely to happen.\r\n\r\nIn fact most of the regular contributors seem to be of the opinion that there are more useful things to spend time on than occasional problems caused by someone else's misconfiguration.\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2102#issuecomment-472662292"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2102#issuecomment-472662292",
"url": "https://github.com/geany/geany/issues/2102#issuecomment-472662292",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>