[Geany-Users] Failed to bind IPC socket

[Enrico Tröger]

Hi,

On 27.08.20 15:24, Doug Henderson wrote:
> This message occurs on a Win 10 pro machine:
> 
> OS Name    Microsoft Windows 10 Pro
> Version    10.0.18363 Build 18363
> 
> Here are the first few lines from Help->Debug Messages
> 
> 06:24:15: Geany WARNING    : Failed to bind IPC socket
> (127.0.0.1:49876): 10013: An attempt was made to access a socket in a
> way forbidden by its access permissions.
> 06:24:15: Geany INFO        : Geany 1.36, English_Canada.1252
> 06:24:15: Geany INFO        : GTK 2.24.32, GLib 2.60.6
> 06:24:15: Geany INFO        : System data dir: C:\Program Files (x86)\Geany\data
> 06:24:15: Geany INFO        : User config dir:
> C:\Users\Doug\AppData\Roaming\geany
> 06:24:15: Geany INFO        : System plugin path: C:\Program Files
> (x86)\Geany\lib\geany
> 06:24:15: Geany INFO        : Added filetype Arduino (61).
> 06:24:15: Geany INFO        : Added filetype Clojure (62).
> 
> The warning does not seem to affect the normal functioning of Geany,
> as far as I know.
> 
> I would however like to discover further information about this
> warning, and resolve it, if possible.

This reminds of https://github.com/geany/geany/issues/2101.
In short, check your firewall settings and/or whether some other
application might be using TCP port 49876.

The IPC socket is used for communication between two Geany instances,
e.g. when you have Geany running and use "Open with Geany" menu item in
Explorer or similar. The communication is done via TCP port 49876 on
which the first started Geany instance binds to.
The above message tells that either the port is already in use by
another process or that a firewall might be blocking the port.


Regards,
Enrico

-- 
Get my GPG key from https://www.uvena.de/pub.asc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.geany.org/pipermail/users/attachments/20200827/6d039f72/attachment.sig>