WayVNC process kill itself after some reconnections

[drigoskalwalker]

Useful information:

Please, try to gather as much of useful information as possible and follow these instructions:

• Version:

  • Run this command: wayvnc -V wayvnc: 0.10-dev neatvnc: 0.10-dev aml: 1.0.0

• Provide context, including but not limited to

  • Command line arguments

  • anyone, just run waynvc.

  • Special environment variables, if any

  • Which wayland compositor are you using? Which version? labwc 0.8.4

  • What VNC client are you using? tigervnc 1.5.0 (windows)

  • Did you configure your VNC client in a specific manner? I think not.

  • Linux distro/operating system Slackware Current

• • Kernel version 6.12.33

  • Graphics drivers mesa-25.1.4 (RTX 3060)

• Try to reproduce the problem while capturing a trace log:

  • wayvnc -Ltrace | tee wayvnc-bug.log I can't do it by now

• Get the stack trace, in case of a crash:

  • If you have coredumpctl, you can gather the stack trace after a crash using coredumpctl gdb wayvnc and then run bt full to obtain the stack trace.
  • Otherwise, you can either locate the core file and load it into gdb or run wayvnc in gdb like so:
    • gdb --args wayvnc -Ltrace
  • If the lines mentioning wayvnc, neatvnc or aml have ??, please compile wayvnc and those other projects from source with debug symbols and try again.

• Describe how to reproduce the problem Connect to WayVNC with some client (I'm using TigerVNC) work normally, end the connection, connect again work normally, after some random connections the process ends with the message: bash-5.2# ERROR: ../src/main.c: 1176: Failed to start capture. Exiting...

  I worked two days using normally and suddenly this happened.

  I was using an old version of WayVNC and its libs, and the problem ocurred more often and earlier. Sometimes it happened on the second connection. After the upgrade it got more stable, and faster, but still have this problem

• Try to think about your problem beyond these instructions and include whatever information that you believe will help to resolve the issue This problem began after I upgraded my Slackware Current to new packages, before that WayVNC worked normally I was like six months outdated, and upgraded some packages, it was not a big thing, it was really some packages I think it could be something relationed with wlroots or mesa drivers (I think I'm using the NVK one)

[any1]

Did you also upgrade labwc and wlroots?

Does the debug log from labwc say why capture failed?

[drigoskalwalker]

Yes, I also upgraded those, but sorry my misunderstood, the labwc don't crash Did I have to debug it too? Even not crashing?

[any1]

Doesn't look like wayvnc is crashing either. It just exits because labws denies the capture, right?

[drigoskalwalker]

I only got this ERROR: ../src/main.c: 1176: Failed to start capture. Exiting... Do I have to upgrade labwc to the lastest version?

[any1]

I have no idea why labwc intermittently denies the capture. That's why I suggested that you checked the log output from labwc. A trace log from wayvnc could also be useful.

Do I have to upgrade labwc to the lastest version?

I don't have enough information to diagnose the problem, so I can't tell you that.