Application block with xvfb

Support
1

Hello people,

I have a Salea 16 connected to a Linux Ubuntu 22.04.3 LTS that I use as a CI machine. I was able to use Salea in the headless mode with xvfb for quite long without any issues. I believe that at some point I downloaded a newer version of the Salea and I started to have problems.

When I execute the command xvfb-run /usr/local/bin/Logic --automation --automationPort 10430

The following error appears

/tmp/.mount_LogicuWpAi5 ~
~
Environment
Executable path: /tmp/.mount_LogicuWpAi5/Logic
Executable directory: /tmp/.mount_LogicuWpAi5
Original working directory: /home/eks_99th
Current working directory: /tmp/.mount_LogicuWpAi5
Process ID: 13069
Crash reporting enabled. Machine ID: a1cd288f-6668-4b7a-aed0-c23141c35581
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[13162:0121/203308.317670:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[13232:0121/203308.401436:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[13232:0121/203315.285412:ERROR:gl_utils.cc(319)] [.WebGL-0x557a5f0d4980]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[13232:0121/203315.333041:ERROR:gl_utils.cc(319)] [.WebGL-0x557a5f0d4980]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
HERE I PRESS ctrl+C to cancel the process
[13232:0121/204202.903759:ERROR:connection.cc(46)] X connection error received.
[13232:0121/204202.903719:ERROR:connection.cc(46)] X connection error received.

And the application hangs at this point forever.

On a older version of the software, which I cannot precise which one as I overwrote it, I have the following log in the same conditions:

/tmp/.mount_LogicQPdpia ~/actions-runner/_work/Omni/Omni
~/actions-runner/_work/Omni/Omni
Environment
Executable path: /tmp/.mount_LogicQPdpia/Logic
Executable directory: /tmp/.mount_LogicQPdpia
Original working directory: /home/eks_99th/actions-runner/_work/Omni/Omni
Current working directory: /tmp/.mount_LogicQPdpia
Process ID: 1970
Crash reporting enabled. Machine ID: a1cd288f-6668-4b7a-aed0-c23141c35581
[1970:1230/093736.409413:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are “tcp” and on UNIX “unix”)
[1970:1230/093736.409591:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are “tcp” and on UNIX “unix”)
[1970:1230/093738.004119:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are “tcp” and on UNIX “unix”)
[1970:1230/093738.109207:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are “tcp” and on UNIX “unix”)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[2047:1230/093738.807198:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[2092:1230/093739.628617:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2023-12-30 09:37:42.946684] [C] [tid 2122] [main] [saleae_log.cpp:294] Global logging level is set to: debug
from this point on it works normally

Could you please help me to solve the issue? During the week I will try with different versions to try to identify the last which worked.

1 Like
2

@ericksagaguara the issue appears to be with your GPU card. also the device may have loaded wrong.
Try re-installing the Libva goods.

PS there are many forums with this same issue and the respective fixes.

3

@ericksagaguara The vaGetDriverNameByIndex() failed with unknown libva error used to appear when the Logic 2 software crashed when it consumed over 4 GB of memory or over 2 GB at one time. We fixed this specific error in 2.4.13 (the current version of the software).

Although your error condition is different, the first thing I’d like to check is to see if you’re running 2.4.13 available below.
https://ideas.saleae.com/f/changelog/

You can also try some of the older versions above to test your theory. Feel free to let me know the results of that, and if none of the versions you try help, we can take a further look.

1 Like