You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is support via the external listener fd feature introduced in 0.9.0 (but not the specific sd_listen_fds(3) protocol). With your set of units you would use ExecStart=wayvnc [...] -x 3 to treat the address argument (3) as an fd which is where systemd's socket would be accessible from. You should also have Requires=wayvnc.socket in the [Unit] section of wayvnc.service in case you ever start wayvnc.service manually without it being triggered by socket activation, otherwise wayvnc would start with fd 3 being unusable.
Useful information:
Please, try to gather as much of useful information as possible and follow
these instructions:
wayvnc -V
0.8.0-2
Try to reproduce while capturing a trace log:
wayvnc -Ltrace | tee wayvnc-crash.log
Get the stack trace:
coredumpctl
, you can gather the stack trace after a crash usingcoredumpctl gdb wayvnc
and then runbt full
to obtain the stack trace.wayvnc in gdb like so:
gdb --args wayvnc -Ltrace
??
, please compilewayvnc and those other projects from source with debug symbols and try
again.
wayvnc.socket
wayvnc.service
config
The text was updated successfully, but these errors were encountered: