“grabber_client connect_failed: No such file or directory” on macOS 15.3.1 (24D70) with Parsec

[beramodes]

Description

I am experiencing an issue while using Parsec to remotely access my Mac mini M2 Pro chip, running macOS 15.3.1 (24D70), from a Windows PC. The following error messages repeatedly appear in the logs:

[2025-02-14 14:25:50.747] [error] [console_user_server] grabber_client connect_failed: No such file or directory
[2025-02-14 14:25:51.818] [error] [console_user_server] grabber_client connect_failed: No such file or directory
[2025-02-14 14:25:52.885] [error] [console_user_server] grabber_client connect_failed: No such file or directory

This issue occurs consistently and seems to prevent proper functionality.

System Details
• Host Machine (Local):
• OS: Windows (Exact version can be provided if needed)
• Keyboard: Logitech Craft
• Remote Machine (Target):
• Model: Mac mini M2 Pro
• macOS Version: 15.3.1 (24D70)
• Parsec Version: [Specify your Parsec version]

Steps to Reproduce
1. Install Parsec on both the Windows PC (host) and macOS (remote).
2. Use Parsec to connect from the Windows machine to the Mac mini.
3. Observe the logs on the Mac for repeated “grabber_client connect_failed: No such file or directory” errors.

Expected Behavior

Parsec should successfully establish a remote connection without errors, and input devices (keyboard, mouse) should function properly.

Actual Behavior

The connection fails or experiences issues due to repeated “grabber_client connect_failed” errors.

Additional Notes
• This issue may be related to input handling, screen capturing, or macOS permissions.
• The Logitech Craft keyboard is used on the Windows host, which might be affecting input recognition.
• Any additional logs or debug information can be provided if needed.

Could you please provide guidance on resolving this issue? Thank you

[tekezo]

I'm not familiar with Parsec's behavior, but it seems that macOS may recognize the user as not being logged in.
Regardless, Karabiner-Elements can only modify physically connected devices on macOS, meaning virtual keyboards and similar devices are not supported. So, in this case, I don't think it will work.