[bug report] [jami-qt] jami launches, but nothing shows up after update

[regivanx]

Hi,

Jami launches (exists in process list), but nothing shows up after yesterday’s update.

It is possible that the problem comes again from a library incompatibility, after the update of qt for example.

Jami-qt’s version: 20220722-4.2

[Strit]

I would assume that the Arch maintainer would have made a rebuild too if that was the case.

But again, without more info, we can guess until new years eve.

[regivanx]

Hi!

The error message come long after the program start, so I did not see it.

So here it is:

(jami-qt:1397753): libnotify-WARNING **: 14:35:05.604: Failed to connect to proxy
qt.webenginecontext:

GL Type: desktop
Surface Type: OpenGL
Surface Profile: NoProfile
Surface Version: 3.1
QSG RHI Backend: OpenGL
Using Supported QSG Backend: yes
Using Software Dynamic GL: no
Using Multithreaded OpenGL: yes

Init Parameters:
  *  application-name Jami
  *  browser-subprocess-path /usr/lib/qt6/QtWebEngineProcess
  *  disable-features ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture
  *  disable-setuid-sandbox
  *  disable-speech-api
  *  enable-features NetworkServiceInProcess,TracingServiceInProcess
  *  enable-threaded-compositing
  *  in-process-gpu
  *  use-gl desktop

"Using locale: fr_FR"
14:35:07.494         os_core_unix.c !pjlib 2.11 for POSIX initialized
[AVHWDeviceContext @ 0xfffef4003150] Failed to initialise VAAPI connection: -1 (unknown libva error).
[AVHWDeviceContext @ 0xfffef4003c10] Failed to initialise VAAPI connection: -1 (unknown libva error).
[AVHWDeviceContext @ 0xfffef4003150] No VA display found for device /dev/dri/renderD129.
[AVHWDeviceContext @ 0xfffef4003c10] Failed to initialise VAAPI connection: -1 (unknown libva error).
Daemon is running
No migration required
could not update message status for not existing conversation
Syncing lrc accounts list with the daemon
Cannot find dbus interface for screen saver
QQmlApplicationEngine failed to load component
qrc:/src/app/MainApplicationWindow.qml:108:5: Type DaemonReconnectPopup unavailable
qrc:/src/app/commoncomponents/DaemonReconnectPopup.qml:26:1: Type BaseModalDialog unavailable
qrc:/src/app/commoncomponents/BaseModalDialog.qml:109:5: Type DropShadow unavailable
qrc:/qt-project.org/imports/Qt5Compat/GraphicalEffects/DropShadow.qml:6:1: Impossible de charger la bibliothèque /usr/lib/qt6/qml/Qt5Compat/GraphicalEffects/private/libqtgraphicaleffectsprivateplugin.so : (libQt6ShaderTools.so.6: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type)
Main window loaded using OpenGLRhi
NetworkManager client initialized, version:  1.40.0 , daemon running: yes , networking enabled: yes
primary network connection: 84cc056c-1b8b-4eea-a4a2-c57404d6f112 default:  yes

[regivanx]

Hello,

Bug report filed on archlinuxarm on January 2, 2023.

The latest Manjaro update did not fix the issue (January 2023).

According to Jami’s developer, this is definitely a packaging issue, not a problem on their end.

With no response from archlinuxarm or Manjaro, I feel helpless, as I don’t know how to package software.

[Strit]

If you are really relying on Jami, maybe you can try the flatpak version:

Jami | Flathub