savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-05-12T13:55:13Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1243when making a SIP call several times does not connect to the client2021-05-12T13:55:13Zda_adminwhen making a SIP call several times does not connect to the clienthello, Linux mint 20.1 snap package jami (20210105)
when making a SIP call several times does not connect to the client
the image below is a trace and a log
![1dbf3464-1124-47d2-a0a1-9e4185d5a457](/uploads/74077f0e725b1fa24f28b475e56bd...hello, Linux mint 20.1 snap package jami (20210105)
when making a SIP call several times does not connect to the client
the image below is a trace and a log
![1dbf3464-1124-47d2-a0a1-9e4185d5a457](/uploads/74077f0e725b1fa24f28b475e56bd64e/1dbf3464-1124-47d2-a0a1-9e4185d5a457.PNG)https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/95Enable white labeling in Jami2023-05-30T17:41:32ZMaxim CournoyerEnable white labeling in JamiSome customers have the requirement to use their own branding (white label).
This task is about to allow customizing the name (Jami) and icon logo.Some customers have the requirement to use their own branding (white label).
This task is about to allow customizing the name (Jami) and icon logo.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/295Swarm: add a test for sending a message to multiple participants at once2021-06-12T11:37:27ZSébastien BlinSwarm: add a test for sending a message to multiple participants at onceScenario:
Alice creates a conversation with 8 members
Then sends a messages
All devices should receives the whole conversationScenario:
Alice creates a conversation with 8 members
Then sends a messages
All devices should receives the whole conversationSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/409Add Mosaic button and stop sharing option2021-05-28T13:08:23ZGuillaume HellerAdd Mosaic button and stop sharing optionRefer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/af226f6a-2d7c-4410-ac8e-e4e3a92b2a37Refer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/af226f6a-2d7c-4410-ac8e-e4e3a92b2a37Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/411New action button design with support for camera/microphone/speaker selection2021-06-08T17:54:49ZGuillaume HellerNew action button design with support for camera/microphone/speaker selectionRefer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/e298064f-af76-4626-9d22-bb35bae68483Refer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/e298064f-af76-4626-9d22-bb35bae68483Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/420in-call overlay can't be activated when hovering over participants or partici...2021-05-28T20:55:51ZAndreas Traczykin-call overlay can't be activated when hovering over participants or participant menus- **OS:** all
- **Jami version:** master
- **Can you reproduce the bug:** at will
- **Steps to reproduce:** engage in a conference call and hover over a participant/participant menu
- **Actual result:** the main overlay is not visible
- ...- **OS:** all
- **Jami version:** master
- **Can you reproduce the bug:** at will
- **Steps to reproduce:** engage in a conference call and hover over a participant/participant menu
- **Actual result:** the main overlay is not visible
- **Expected result:** the main overlay should appearAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/421in-call overlay tool buttons fade when hovered over but remain clickable2021-05-28T20:55:55ZAndreas Traczykin-call overlay tool buttons fade when hovered over but remain clickable- **OS:** all
- **Jami version:** master
- **Can you reproduce the bug:** at will
- **Steps to reproduce:** engage in a call and hover over any main toolbar button and wait for the overlay to fade out
- **Actual result:** the main overla...- **OS:** all
- **Jami version:** master
- **Can you reproduce the bug:** at will
- **Steps to reproduce:** engage in a call and hover over any main toolbar button and wait for the overlay to fade out
- **Actual result:** the main overlay is not visible but the tooltip shows and the button can be activated
- **Expected result:** the main overlay should not fade outAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/410Add call status indicator when adding new participant to a conf2021-05-28T13:08:09ZGuillaume HellerAdd call status indicator when adding new participant to a confRefer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/5a8874fe-ec8e-4274-a67d-5c23093e05a5Refer to https://www.sketch.com/s/f15c7123-d06a-4e8f-96ab-3c0f58ad99c6/p/5a8874fe-ec8e-4274-a67d-5c23093e05a5Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/533SIP transport without channel, should not happen2021-05-25T14:06:51ZSébastien BlinSIP transport without channel, should not happen```
[1619619984.706|54688|call_factory.cpp :89 ] Removing call 2767615663813669
[1619619984.706|54688|call_factory.cpp :92 ] Remaining 0 call
[1619619984.706|54688|call.cpp :253 ] [call:2767615663813669] state change 1/6,...```
[1619619984.706|54688|call_factory.cpp :89 ] Removing call 2767615663813669
[1619619984.706|54688|call_factory.cpp :92 ] Remaining 0 call
[1619619984.706|54688|call.cpp :253 ] [call:2767615663813669] state change 1/6, cnx 0/0, code 0
[1619619984.706|54688|ice_transport.cpp :453 ] [ice:0x7fff98301880] destroying
[1619619987.775|54505|manager.cpp :1006 ] try outgoing call to 'ring:fc9ba875cdbbd2b213986491078851965655260a' with account 'fa4c689ca4cc3cfe'
[1619619987.775|54505|audio_rtp_session.cpp:56 ] Created Audio RTP session: 0x55555764dfc0 - call Id 8305342024106593
[1619619987.775|54505|ringbuffer.cpp :55 ] Create new RingBuffer 8305342024106593
[1619619987.775|54505|sipcall.cpp :1381 ] [call:8305342024106593] Added media @0: [0x555556f06750] type [AUDIO] muted [NO] label [main audio] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619619987.775|54505|sipcall.cpp :1381 ] [call:8305342024106593] Added media @1: [0x555556e77670] type [VIDEO] muted [NO] label [main video] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619619987.775|54505|sipcall.cpp :1389 ] [call:8305342024106593] Created 2 Media streams
[1619619987.775|54505|jamiaccount.cpp :465 ] [Account fa4c689ca4cc3cfe] Calling DHT peer fc9ba875cdbbd2b213986491078851965655260a
[1619619987.775|54505|contact_list.cpp :68 ] Can't set certificate status for existing contacts fc9ba875cdbbd2b213986491078851965655260a
[1619619987.775|54505|call.cpp :253 ] [call:8305342024106593] state change 0/0, cnx 0/1, code 0
[1619619987.775|54505|audio_rtp_session.cpp:56 ] Created Audio RTP session: 0x5555577052f0 - call Id 8541308648035115
[1619619987.775|54505|ringbuffer.cpp :55 ] Create new RingBuffer 8541308648035115
[1619619987.775|54505|sipcall.cpp :1381 ] [call:8541308648035115] Added media @0: [0x555556f9ccb0] type [AUDIO] muted [NO] label [main audio] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619619987.775|54505|sipcall.cpp :1381 ] [call:8541308648035115] Added media @1: [0x555556f256b0] type [VIDEO] muted [NO] label [main video] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619619987.775|54505|sipcall.cpp :1389 ] [call:8541308648035115] Created 2 Media streams
[1619619987.775|54505|call.cpp :474 ] [call:8305342024106593] add subcall 8541308648035115
[1619619987.775|54505|jamiaccount.cpp :638 ] A SIP transport exists without Channel, this is a bug. Please report
[1619619987.776|54505|manager.cpp :594 ] ----- Switch current call id to '8305342024106593' -----
[1619620117.839|54505|manager.cpp :1006 ] try outgoing call to 'ring:fc9ba875cdbbd2b213986491078851965655260a' with account 'fa4c689ca4cc3cfe'
[1619620117.839|54505|audio_rtp_session.cpp:56 ] Created Audio RTP session: 0x5555577052f0 - call Id 624900446566263
[1619620117.839|54505|ringbuffer.cpp :55 ] Create new RingBuffer 624900446566263
[1619620117.839|54505|sipcall.cpp :1381 ] [call:624900446566263] Added media @0: [0x7fff94817880] type [AUDIO] muted [NO] label [main audio] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.839|54505|sipcall.cpp :1381 ] [call:624900446566263] Added media @1: [0x5555571b05f0] type [VIDEO] muted [NO] label [main video] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.839|54505|sipcall.cpp :1389 ] [call:624900446566263] Created 2 Media streams
[1619620117.839|54505|jamiaccount.cpp :465 ] [Account fa4c689ca4cc3cfe] Calling DHT peer fc9ba875cdbbd2b213986491078851965655260a
[1619620117.839|54505|contact_list.cpp :68 ] Can't set certificate status for existing contacts fc9ba875cdbbd2b213986491078851965655260a
[1619620117.839|54505|call.cpp :253 ] [call:624900446566263] state change 0/0, cnx 0/1, code 0
[1619620117.839|54505|audio_rtp_session.cpp:56 ] Created Audio RTP session: 0x5555574132d0 - call Id 7505786282921218
[1619620117.839|54505|ringbuffer.cpp :55 ] Create new RingBuffer 7505786282921218
[1619620117.839|54505|sipcall.cpp :1381 ] [call:7505786282921218] Added media @0: [0x55555705df80] type [AUDIO] muted [NO] label [main audio] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.839|54505|sipcall.cpp :1381 ] [call:7505786282921218] Added media @1: [0x55555724c500] type [VIDEO] muted [NO] label [main video] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.839|54505|sipcall.cpp :1389 ] [call:7505786282921218] Created 2 Media streams
[1619620117.839|54505|call.cpp :474 ] [call:624900446566263] add subcall 7505786282921218
[1619620117.839|54505|jamiaccount.cpp :638 ] A SIP transport exists without Channel, this is a bug. Please report
[1619620117.840|54505|manager.cpp :594 ] ----- Switch current call id to '624900446566263' -----
[1619620117.842|54533|audio_rtp_session.cpp:56 ] Created Audio RTP session: 0x7fff94decb90 - call Id 7874120690412536
[1619620117.842|54533|ringbuffer.cpp :55 ] Create new RingBuffer 7874120690412536
[1619620117.842|54533|sipcall.cpp :1381 ] [call:7874120690412536] Added media @0: [0x7fff94ad6120] type [AUDIO] muted [NO] label [main audio] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.842|54533|sipcall.cpp :1381 ] [call:7874120690412536] Added media @1: [0x7fff94516e00] type [VIDEO] muted [NO] label [main video] source [camera://046d_Logitech_Webcam_C925e_AF4CDB5F] secure [YES]
[1619620117.842|54533|sipcall.cpp :1389 ] [call:7874120690412536] Created 2 Media streams
[1619620117.842|54533|call.cpp :253 ] [call:7874120690412536] state change 0/0, cnx 0/1, code 0
[1619620117.844|54533|call.cpp :474 ] [call:624900446566263] add subcall 7874120690412536
[1619620117.844|54533|jamiaccount.cpp :622 ] [call 624900446566263] No channeled socket with this peer. Send request
[1619620117.844|54533|jamiaccount.cpp :4726 ] [Account fa4c689ca4cc3cfe] A SIP connection with b6c5f94080357963a564f4f423e5be487d5f04bb already exists
[1619620117.844|54533|account_manager.cpp:587 ] Found 1 devices for fc9ba875cdbbd2b213986491078851965655260a
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/294Conference: add participants split2021-12-29T17:14:06ZAline Gondim SantosConference: add participants splitBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/529SIP: refactor SIPCall and related classes and routines2023-09-29T10:00:20ZMohamed ChibaniSIP: refactor SIPCall and related classes and routinesThe goal of the refactor is to improve stability (prevent crashes and deadlocks), clarify interactions between SIPCall class with other classes/routines. Three main changes will be introduced in this activity:
**1- Add an interface to r...The goal of the refactor is to improve stability (prevent crashes and deadlocks), clarify interactions between SIPCall class with other classes/routines. Three main changes will be introduced in this activity:
**1- Add an interface to report PJSIP events**\
The use of this interface is to give limited access to SIPCall from SipVoipLink class and related routines.
All processing involving SIPCall properties (such as SDP and RTP sessions) should be done as much as possible within SIPCall class to enhance encapsulation.
**2- Use the same thread (SIP thread) for SipVoIPLink events hander and SIP Transport**\
All events (hopefully) reported by PSIP lib will be reported on the same thread, which will help reduce data race on SIPCall class in particular.
**3- Run most of the task involving SIPCall on the same thread**
Dispatch tasks (when possible) on the SIP thread. Note that some calls still need to access SIPCall synchronously (getters in particular).BacklogMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/880Swarm: redo process with TrustRequest2021-06-12T11:39:18ZSébastien BlinSwarm: redo process with TrustRequestFor now, lot of duplicate/some crashesFor now, lot of duplicate/some crashesSwarm-chatAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/98Modernize CI via Jenkinsfiles (part 1)2021-06-29T20:50:50ZMaxim CournoyerModernize CI via Jenkinsfiles (part 1)The Jenkins-based CI currently relies on old-fashioned scripts that must be edited in the Jenkins web UI or copy pasted back and forth from an editor. This is unwieldy and changes to the scripts are not traceable.
This task is about mi...The Jenkins-based CI currently relies on old-fashioned scripts that must be edited in the Jenkins web UI or copy pasted back and forth from an editor. This is unwieldy and changes to the scripts are not traceable.
This task is about migrating the scripts used to Jenkinsfile so that they can be versioned along the code. This also has the benefit that testing modified jobs can be more easily done from the CLI via the `jenkinscli` tool.Maxim CournoyerMaxim Cournoyerhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/451swarm chat2021-06-12T11:39:24ZKateryna Kostiukswarm chatDONE:
- load conversations
- add conversation
- send messages
- load messages
- receive message
- accept conversation
- start conversation with first interaction (send message/file/place call)
- sort interactions by time
- confi...DONE:
- load conversations
- add conversation
- send messages
- load messages
- receive message
- accept conversation
- start conversation with first interaction (send message/file/place call)
- sort interactions by time
- configure call interactions
- configure data transfer interactions
- configure contact interactions
- remove interaction
- remove conversation
TODO:
- save last read interaction
CHANGES ON CLIENT SIDE:
- use string for interaction id instead of int
- connect and handle signal newInteractionsAvailable(accountId, conversationId)
- implement lazy loading (may be not for first version)Swarm-chatKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/412UI fluidity is coupled with the load of the daemon2021-12-29T17:15:09ZMaxim CournoyerUI fluidity is coupled with the load of the daemon## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we wil...## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Disable video acceleration to ensure high load in the daemon.
2. Join a video conference (rendezvous point)
- Actual result:
The UI elements are very slow to refresh. Having the overlay display, for example to make the mute button appear, may take several seconds. Opening the chat view may show a blank square for a long time before its content appear.
- Expected result:
The UI should remain fluid, running asynchronously from the daemon, like the GNOME client, which doesn't suffer from this problem.
## Additional information
Here's a screenshot of the chat view failing to refresh (it took several minutes for it to display its content!):
![chat](/uploads/0652a89288a7050627aa483c38c1a9dc/chat.png)Backloghttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/19UI fluidity is coupled with the load of the daemon2022-02-16T21:42:40ZMaxim CournoyerUI fluidity is coupled with the load of the daemon## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we wil...## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Disable video acceleration to ensure high load in the daemon.
2. Join a video conference (rendezvous point)
- Actual result:
The UI elements are very slow to refresh. Having the overlay display, for example to make the mute button appear, may take several seconds. Opening the chat view may show a blank square for a long time before its content appear.
- Expected result:
The UI should remain fluid, running asynchronously from the daemon, like the GNOME client, which doesn't suffer from this problem.
## Additional information
Here's a screenshot of the chat view failing to refresh (it took several minutes for it to display its content!):
![chat](/uploads/30892459b3f96ee850577878c3ea850e/chat.png)Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/136[API ready]Swarm: support request for resending a file transfer2021-06-12T11:37:55ZSébastien Blin[API ready]Swarm: support request for resending a file transfer+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/100Improve packaging2021-06-10T11:46:05ZSébastien BlinImprove packaging
the jami-daemon package incuding both libring.so and dring
the jami-qt package using libring.so
or
the libjami package including libring.so (maybe renamed to libjami.so)
the jami-dbus package including dring (maybe ren...
the jami-daemon package incuding both libring.so and dring
the jami-qt package using libring.so
or
the libjami package including libring.so (maybe renamed to libjami.so)
the jami-dbus package including dring (maybe renamed to jamid or something)
the jami-qt package depending on libjamihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/681sipvoiplink, crash on exit2021-12-28T20:54:37ZSébastien Blinsipvoiplink, crash on exit# Scenario
Quit jami
# trace (in rare case)
```
Thread 42 "jami-qt" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff1e7fc700 (LWP 1129330)]
__GI___pthread_mutex_lock (mutex=0x30) at ../nptl/pthread_mutex_lock.c...# Scenario
Quit jami
# trace (in rare case)
```
Thread 42 "jami-qt" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff1e7fc700 (LWP 1129330)]
__GI___pthread_mutex_lock (mutex=0x30) at ../nptl/pthread_mutex_lock.c:67
67 ../nptl/pthread_mutex_lock.c: No such file or directory.
(gdb) bt
#0 __GI___pthread_mutex_lock (mutex=0x30) at ../nptl/pthread_mutex_lock.c:67
#1 0x00007fffe8674c5d in __gthread_mutex_lock(__gthread_mutex_t*) (__mutex=0x30) at /usr/include/x86_64-linux-gnu/c++/9/bits/gthr-default.h:749
#2 0x00007fffe8683b1e in std::mutex::lock() (this=0x30) at /usr/include/c++/9/bits/std_mutex.h:100
#3 0x00007fffe8687466 in std::lock_guard<std::mutex>::lock_guard(std::mutex&) (this=0x7fff1e7f8380, __m=...) at /usr/include/c++/9/bits/std_mutex.h:159
#4 0x00007fffe89a089c in jami::SipTransportBroker::addTransport(pjsip_transport*) (this=0x0, t=0x555556184de8) at ./sip/siptransport.cpp:248
#5 0x00007fffe8987fa3 in jami::transaction_request_cb(pjsip_rx_data*) (rdata=0x7ffea8001bc8) at ./sip/sipvoiplink.cpp:274
#6 0x00007fffe8c7b3cb in pjsip_endpt_process_rx_data () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#7 0x00007fffe8c7b606 in endpt_on_rx_msg () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#8 0x00007fffe8c82633 in pjsip_tpmgr_receive_packet () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#9 0x00007fffe8c85136 in udp_on_read_complete () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#10 0x00007fffe8cc94d7 in ioqueue_dispatch_read_event () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#11 0x00007fffe8ccaf3b in pj_ioqueue_poll () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#12 0x00007fffe8c7b118 in pjsip_endpt_handle_events2 () at /home/sblin/ring-project/daemon/src/.libs/libring.so.0
#13 0x00007fffe898b644 in jami::SIPVoIPLink::handleEvents() (this=0x555555b86bc0) at ./sip/sipvoiplink.cpp:813
#14 0x00007fffe8989ce4 in jami::SIPVoIPLink::<lambda()>::operator()(void) const (__closure=0x555556153848) at ./sip/sipvoiplink.cpp:739
#15 0x00007fffe8991e0a in std::__invoke_impl<void, jami::SIPVoIPLink::SIPVoIPLink()::<lambda()> >(std::__invoke_other, jami::SIPVoIPLink::<lambda()> &&) (__f=...)
at /usr/include/c++/9/bits/invoke.h:60
#16 0x00007fffe8991dbf in std::__invoke<jami::SIPVoIPLink::SIPVoIPLink()::<lambda()> >(jami::SIPVoIPLink::<lambda()> &&) (__fn=...) at /usr/include/c++/9/bits/invoke.h:95
#17 0x00007fffe8991d6c in std::thread::_Invoker<std::tuple<jami::SIPVoIPLink::SIPVoIPLink()::<lambda()> > >::_M_invoke<0>(std::_Index_tuple<0>) (this=0x555556153848)
at /usr/include/c++/9/thread:244
#18 0x00007fffe8991d42 in std::thread::_Invoker<std::tuple<jami::SIPVoIPLink::SIPVoIPLink()::<lambda()> > >::operator()(void) (this=0x555556153848) at /usr/include/c++/9/thread:251
#19 0x00007fffe8991d26 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::SIPVoIPLink::SIPVoIPLink()::<lambda()> > > >::_M_run(void) (this=0x555556153840)
at /usr/include/c++/9/thread:195
#20 0x00007fffea6a3de4 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#21 0x00007fffea449609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#22 0x00007fffea36e293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)
```https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/111Packaging: prepare for Qt 6.2 (client-qt)2022-01-14T16:52:59ZSébastien BlinPackaging: prepare for Qt 6.2 (client-qt)Finish https://review.jami.net/c/jami-project/+/19673
**Testing:** (install & upgrade)
+ [x] debian 10
+ [x] debian 11
+ [x] debian testing
+ [x] debian unstable
+ [x] ubuntu 18.04
+ [x] ubuntu 20.04
+ [x] ubuntu 21.10
+ [x] fedora 33
...Finish https://review.jami.net/c/jami-project/+/19673
**Testing:** (install & upgrade)
+ [x] debian 10
+ [x] debian 11
+ [x] debian testing
+ [x] debian unstable
+ [x] ubuntu 18.04
+ [x] ubuntu 20.04
+ [x] ubuntu 21.10
+ [x] fedora 33
+ [x] fedora 34
+ [x] fedora 35
+ [x] opensuse leap 15.3
+ [x] ubuntu 21.04
+ [x] snap
**Removed:**
+ opensuse 15.2 to remove, EOL
+ tumbleweedSébastien BlinMing Rui ZhangSébastien Blin