On Parabola, Jami crashes upon startup

Support in English
1

With Parabola, Jami crashes on startup:

$ jami
Using Qt runtime version: 6.3.0
“notify server name: Notification Daemon, vendor: MATE, version: 1.26.0, spec: 1.1”
“Using locale: fr_FR”
“Error : jamid is not available, make sure it is running”
terminate called after throwing an instance of ‘char const*’
Abandon (core dumped)

I don’t know what “jamid is not available” means.

I have configured Jami when it was recently added to Parabola about two weeks ago and it was starting successfully at the time, but I haven’t used it so much on Parabola so much.

2

Hi

jamid is the jami-daemon. Here you built client-qt without libwrap, so it will use the DBUS API

You have two solutions:

  • Launch jamid then client-qt
    • jamid is the binary built by jami-daemon and depends where you installed it.
  • Use libwrap to only have one binary (what we do for our releases)
3

Ok but I have this:

$ /usr/lib/jamid
Jami Daemon 13.0.0, by Savoir-faire Linux 2004-2020

[Video support enabled]
[Plugins support enabled]

14:14:07.180 os_core_unix.c !pjlib 2.11 for POSIX initialized
[AVHWDeviceContext @ 0x7fb5ac01f280] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7fb5ac01f280] Could not dynamically load CUDA
[AVHWDeviceContext @ 0x7fb5ac01ee40] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7fb5ac01ee40] Could not dynamically load CUDA
[AVHWDeviceContext @ 0x7fb5ac01f680] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7fb5ac01f680] Could not dynamically load CUDA
[AVHWDeviceContext @ 0x7fb5ac01f680] Failed to initialise VAAPI connection: -1 (unknown libva error).
[AVHWDeviceContext @ 0x7fb5ac01ee40] Failed to initialise VAAPI connection: -1 (unknown libva error).
[AVHWDeviceContext @ 0x7fb5ac01f640] No VA display found for device /dev/dri/renderD129.
[AVHWDeviceContext @ 0x7fb5ac022440] Failed to initialise VAAPI connection: -1 (unknown libva error).
malloc(): invalid size (unsorted)
Abandon (core dumped)

I am not sure why this libcuda is needed, I suspect it may not be free software. I don’t know whether Jami is supposed to work without this.

4

probably a bad video driver. you can disable hardware acceleration in the dring.yml. The full backtrace may help