[GH-ISSUE #330] failed to bind lan-mouse socket #172

New issue

Open

opened 2026-05-05 22:12:33 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 22:12:33 -06:00

Owner

Originally created by @cben484 on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/330

My platform is Windows 10.
I initially used lan-mouse successfully.
However, after unplugging a USB device from another computer (it might have been a coincidence, not necessarily the cause), my computer froze.
So I restarted it (during the restart, an automatic update was installed, but it remained Windows 10).
After rebooting, when I started lan-mouse, it showed a warning.
First, it couldn’t find config.toml.
I manually created a config.toml with the following content:
port = 4243
auto_start = true
But there is still one error:
failed to bind lan-mouse socket
and
(lan-mouse.exe:4592): GLib-GIO-WARNING **: 17:31:00.224: win32 session dbus binary not found

(lan-mouse.exe:4592): GLib-GIO-CRITICAL **: 17:31:00.834: g_settings_schema_source_lookup: assertion 'source != NULL' failed

Originally created by @cben484 on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/330 My platform is Windows 10. I initially used lan-mouse successfully. However, after unplugging a USB device from another computer (it might have been a coincidence, not necessarily the cause), my computer froze. So I restarted it (during the restart, an automatic update was installed, but it remained Windows 10). After rebooting, when I started lan-mouse, it showed a warning. First, it couldn’t find config.toml. I manually created a config.toml with the following content: port = 4243 auto_start = true But there is still one error: failed to bind lan-mouse socket and (lan-mouse.exe:4592): GLib-GIO-WARNING **: 17:31:00.224: win32 session dbus binary not found (lan-mouse.exe:4592): GLib-GIO-CRITICAL **: 17:31:00.834: g_settings_schema_source_lookup: assertion 'source != NULL' failed

gitea-mirror added the

question

label 2026-05-05 22:12:34 -06:00

gitea-mirror commented

2026-05-05 22:12:35 -06:00

Author

Owner

@feschber commented on GitHub (Oct 29, 2025):

Did you fix this issue? On Windows, LanMouse uses TCP port 5252 to communicate between the frontend (the GTK Window) and the service, because windows does not have unix sockets.
This sounds like some other service is running on that port.

To find out, which application might be running on that port, you can use

Get-Process -Id (Get-NetTCPConnection -LocalPort 5252).OwningProcess

In my case this is showing lan-mouse:

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     28    10,06      33,32       0,83    2372   1 lan-mouse

@feschber commented on GitHub (Oct 29, 2025): Did you fix this issue? On Windows, LanMouse uses TCP port 5252 to communicate between the frontend (the GTK Window) and the service, because windows does not have unix sockets. This sounds like some other service is running on that port. To find out, which application might be running on that port, you can use ```sh Get-Process -Id (Get-NetTCPConnection -LocalPort 5252).OwningProcess ``` In my case this is showing lan-mouse: ``` NPM(K) PM(M) WS(M) CPU(s) Id SI ProcessName ------ ----- ----- ------ -- -- ----------- 28 10,06 33,32 0,83 2372 1 lan-mouse ```