Jami doesn't launch after install

I’ve installed Jami snap package on debian 11. However I can not launch the app.

:~$ jami
Testing for explicit PulseAudio choice…
Testing for ALSA permissions…
…and using ALSA.

(jami:19089): dbind-WARNING **: 18:26:24.811: Couldn’t connect to accessibility bus: Failed to connect to socket /tmp/dbus-fg3x6Hwbqc: No such file or directory
Qt: Session management error: None of the authentication protocols specified are supported
Using Qt runtime version: 6.2.3
“notify server name: cinnamon, vendor: GNOME, version: 5.6.7, spec: 1.2”

GLImplementation: desktop
Surface Type: OpenGL
Surface Profile: CompatibilityProfile
Surface Version: 4.6
Using Default SG Backend: yes
Using Software Dynamic GL: no
Using Angle: no

Init Parameters:

  • application-name Jami
  • browser-subprocess-path /snap/jami/270/usr/lib/libqt-jami/libexec/QtWebEngineProcess
  • create-default-gl-context
  • disable-features DnsOverHttpsUpgrade,ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture
  • disable-setuid-sandbox
  • disable-speech-api
  • disable-web-security
  • enable-features NetworkServiceInProcess,TracingServiceInProcess
  • enable-main-frame-before-activation
  • enable-threaded-compositing
  • in-process-gpu
  • lang en
  • num-raster-threads 4
  • single-process
  • use-gl desktop

“Using locale: en_US”
18:26:25.020 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
Daemon is running
No accounts to migrate
Screen saver dbus interface: “org.freedesktop.ScreenSaver”
nmea: No serial ports found
Can’t update current account info data for “”
Main window loaded using OpenGLRhi
NetworkManager client initialized, version: 1.30.6 , daemon running: yes , networking enabled: yes
primary network connection: 597f2e69-5666-4e85-9d3b-f8d9949627c1 default: yes

(jami:19089): GStreamer-CRITICAL **: 18:26:25.197: gst_element_link_many: assertion ‘GST_IS_ELEMENT (element_2)’ failed
Segmentation fault (core dumped)

Is it possible to resolve this problem? Thank you.

Maybe this is the issue?

Do you by any chance also have OBS-Studio also installed?

I am using WIndows 10 and I have OBS Studio installed.

In the past there had been an issue if you use OBS + Jami on Windows 10 but it has been fixed.

Not sure about the Linux distro.
Maybe you use Gitlab to post your issue: