1. Click Jami in Application menu -> Internet -> Jami 2. Nothing happens 3. When started from konsole: $ jami Using Qt runtime version: 6.4.1 qt.webenginecontext: GL Type: desktop Surface Type: OpenGL Surface Profile: CompatibilityProfile Surface Version: 4.6 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/lib64/qt6/libexec/QtWebEngineProcess * create-default-gl-context * 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 terminate called after throwing an instance of 'char const*' Aborted (core dumped)
Thank you for the report. $ urpmf bin/jami jami-client-qt:/usr/bin/jami Installed it to try (78 pkgs!). On this Cauldron system, with a working WiFi connection: $ jami [same O/P as above until...] * use-gl desktop Can't update current account info data for "" Main window loaded using OpenGLRhi QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.91' no primary network connection detected, check network settings --------------------- with a correct-looking GUI, functional as far as I could try it: "Share freely and privately with Jami ... Join Jami ... I already have an account ... About Jami" So we need to find the difference. Can you check the pkg version: jami-client-qt-0.0-0.git20221221.2.mga9
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0CC: (none) => lewyssmithSource RPM: (none) => jami-client-qt-0.0-0.git20221221.2.mga9.src.rpm
It seems to be that the older configuration files were the culprit. Deleted all Jami related files&directories from .cache; .config and .local/share and Jami started to initial setup window. As I have an account then tried to link it from another device and to restore the backup - both just showed the message that "creating account" or something similar, but actually nothing was created. Did not try to create a new account.
jami-client-qt-0.0-0.git20230118.stable.1.mga9 and jami-daemon-13.7.0-0.git20230118.1.mga9 did not have any progress - still endless message "Generating account" at account linking or restoring from backup.
Tested also new account generation: "Could not re-connect to the jami-daemon (jamid). Jami will now quit."
Summary: Jami does not start => Jami does not start when old configuration files exist and at fresh start account generation, linking and restoring fails.
Thanks for your further tests. I am not geared up to testing this more extensively, know nothing about it; so cannot comment constructively. Assigning to wally who deals with Jani.
Assignee: bugsquad => jani.valimaaCC: lewyssmith => (none)
Status: UNCONFIRMED => NEWEver confirmed: 0 => 1
jami-client-qt-0.0-0.git20230118.stable.2.mga9 and jami-daemon-13.7.0-0.git20230119.1.mga9 update fixed the situation - account linking and restoration from backup now works. Could not test non-starting situation when older configuration files exist and did not test new account generation. Should we mark it fixed?
Closing as FIXED.
Status: NEW => RESOLVEDResolution: (none) => FIXED