Non-blocking errors in the Wireguard log

Using /e/OS Applications
1

Hello,
I’m contacting you not because of a blocking error, but rather because of errors displayed in the “Wireguard” application log that seem strange to me.
Could you please tell me if the errors logged are dangerous or not?
Thank you in advance for your cooperation.
Ricardo.
Phone : Samsung Galaxy A5 2017 SM-A520F
Android : 11
e/os : e_a5y17lte-user 11 RQ3A.211001.001 eng.antec.20250206.072441 dev-keys
Wireguard : v1.0.20250531

10-15 09:40:31.035  8436  8470 W libEGL  : EGLNativeWindowType 0x7385e76ad0 disconnect failed
10-15 09:40:31.047  8436  8436 I wm_on_stop_called: [232901057,com.wireguard.android.activity.SettingsActivity,STOP_ACTIVITY_ITEM]
10-15 09:40:31.387  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:33.388  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:35.389  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:37.389  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:39.390  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:40.463  8436  8477 D WireGuard/GoBackend/GalaxyA5: peer(0qp2…BMQo) - Receiving keepalive packet
10-15 09:40:41.391  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:43.392  8436  8448 E reguard.androi: failed to connect to jdwp control socket: Connection refused
10-15 09:40:43.707  8436  8436 I menu_item_selected: [0,Exporter le fichier journal]
2

dangerous - no.

do you look at this through an on-device logger or log export to file? I’d expect you didn’t see this through adb logcat.

somewhere a wireguard import checks for ro.debuggable in the system config and tries to connect to the jdwp socket to ship debug logs. Imo if adbd would run system side those lines wouldn’t be spewn.

Here’s a bit of lineage discussion it.

3

Hello,
Thank you for your reassuring reply.
I did some research online and found a solution that fixed my problem: you need to enable Developer Options and USB Debugging.
I no longer see these worrying lines in the Wireguard log.

4

to explain, these two are the same thing:

enable Developer Options and USB Debugging

if adbd would run system side

adbd - android debug bridge daemon → “USB Debugging”