savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-08-17T14:31:41Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1337Can't make videocalls from TV2023-08-17T14:31:41ZRichard BranchesCan't make videocalls from TVPlease specify the following:
- Jami version: 20230714-01
- Device model: Homatics Box R 4K Plus, Realme 4K stick, Walmart Onn.
- Android version: Android 11 and Android 12.
- What build you are using: Play Store.
## Steps to r...Please specify the following:
- Jami version: 20230714-01
- Device model: Homatics Box R 4K Plus, Realme 4K stick, Walmart Onn.
- Android version: Android 11 and Android 12.
- What build you are using: Play Store.
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami app on any of the aforementioned devices.
2. Open any contact
3. Press button to make a videocall
4. A gray screen (which is the color used in the interface) appears and nothing else happens afterwards.
- Actual result: Gray screen appears.
- Expected result: The videocall screen UI.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1267avatars: incoherent avatar in conversation list and chat view2023-07-26T16:50:54ZCharles-Francis Damedeyavatars: incoherent avatar in conversation list and chat viewBug report form
---------------
## Describe your environment
- OS: Linux Mint
- Jami version: 202306200915
- What build you are using: jami-client-qt
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. change the ...Bug report form
---------------
## Describe your environment
- OS: Linux Mint
- Jami version: 202306200915
- What build you are using: jami-client-qt
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. change the avatar picture of a jami account (I changed it on my android device)
2. chat with this account on jami (with the work computer)
...
- Actual result: the avatar picture in the conversation list will be updated but not the one in the chat
- Expected result: both avatar pictures, in the conversation list and the chat view should be updated
## Additional information
Screenshots/videos/logs/etc
![different_avatar_bug](/uploads/264abac2db7803129947b7da8d61bd82/different_avatar_bug.png)Charles-Francis DamedeyCharles-Francis Damedeyhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/877Incompatible with fmt >= 102023-09-07T18:50:23ZDavid RungeIncompatible with fmt >= 10Hi! We're currently attempting rebuilds against fmt 10 on Arch Linux (https://archlinux.org/todo/fmt-1000/).
Unfortunately, jami-daemon is not yet compatible and building it I run into:
```
[22/157] Compiling C++ object src/libjami.so....Hi! We're currently attempting rebuilds against fmt 10 on Arch Linux (https://archlinux.org/todo/fmt-1000/).
Unfortunately, jami-daemon is not yet compatible and building it I run into:
```
[22/157] Compiling C++ object src/libjami.so.13.7.0.p/connectivity_security_tls_session.cpp.o
FAILED: src/libjami.so.13.7.0.p/connectivity_security_tls_session.cpp.o
c++ -Isrc/libjami.so.13.7.0.p -Isrc -I../jami-daemon/src -I. -I../jami-daemon -I../jami-daemon/src/jami -I../jami-daemon/src/media -I../jami-daemon/src/jamidht/eth -I/usr/include/p11-kit-1 -I/build/jami-daemon/src/jami-daemon/contrib/x86_64-pc-linux-gnu/include -I/usr/include/upnp -I/usr/include/webrtc_audio_processin
g -flto=auto -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu++17 -DHAVE_CONFIG_H -DLIBJAMI_BUILD -Djami_EXPORTS -DASIO_STANDALONE -DMSGPACK_NO_BOOST -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protect
ion -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g -ffile-prefix-map=/build/jami-daemon/src=/usr/src/debug/jami-daemon -flto=auto -fpermissive -fPIC -DWEBRTC_AUDIO_PROCESSING_ONLY_BUILD -DWEBRTC_POSIX -D_REENTRANT -DPJ_AUTOCONF=1 -DPJ_IS_BIG_ENDIAN=0 -DPJ_IS_LITTLE_ENDIAN=1 -pthread -MD -MQ src/libjami.so.13.7.0.p/conne
ctivity_security_tls_session.cpp.o -MF src/libjami.so.13.7.0.p/connectivity_security_tls_session.cpp.o.d -o src/libjami.so.13.7.0.p/connectivity_security_tls_session.cpp.o -c ../jami-daemon/src/connectivity/security/tls_session.cpp
In file included from ../jami-daemon/src/manager.h:38,
from ../jami-daemon/src/connectivity/security/tls_session.cpp:32:
../jami-daemon/src/scheduled_executor.h:108: warning: ignoring ‘#pragma GCC pop’ [-Wunknown-pragmas]
108 | #pragma GCC pop
|
../jami-daemon/src/scheduled_executor.h:158: warning: ignoring ‘#pragma GCC pop’ [-Wunknown-pragmas]
158 | #pragma GCC pop
|
In file included from ../jami-daemon/src/logger.h:27,
from ../jami-daemon/src/connectivity/security/tls_session.cpp:29:
/usr/include/fmt/core.h: In instantiation of ‘constexpr decltype (ctx.begin()) fmt::v10::detail::parse_format_specs(ParseContext&) [with T = gnutls_credentials_type_t; ParseContext = compile_parse_context<char>; decltype (ctx.begin()) = const char*]’:
/usr/include/fmt/core.h:2620:22: required from ‘constexpr fmt::v10::detail::format_string_checker<Char, Args>::format_string_checker(fmt::v10::basic_string_view<Char>) [with Char = char; Args = {gnutls_credentials_type_t}]’
/usr/include/fmt/core.h:2670:56: required from ‘void fmt::v10::detail::check_format_string(S) [with Args = {gnutls_credentials_type_t&}; S = jami::tls::TlsSession::TlsSessionImpl::handleStateHandshake(jami::tls::TlsSessionState)::<lambda()>::FMT_COMPILE_STRING; typename std::enable_if<is_compile_string<S>::value, in
t>::type <anonymous> = 0]’
/usr/include/fmt/core.h:2772:41: required from ‘fmt::v10::basic_format_string<Char, Args>::basic_format_string(const S&) [with S = jami::tls::TlsSession::TlsSessionImpl::handleStateHandshake(jami::tls::TlsSessionState)::<lambda()>::FMT_COMPILE_STRING; typename std::enable_if<std::is_convertible<const S&, fmt::v10::b
asic_string_view<Char> >::value, int>::type <anonymous> = 0; Char = char; Args = {gnutls_credentials_type_t&}]’
../jami-daemon/src/logger.h:173:51: required from ‘void jami::log::error(const char*, int, S&&, Args&& ...) [with S = jami::tls::TlsSession::TlsSessionImpl::handleStateHandshake(jami::tls::TlsSessionState)::<lambda()>::FMT_COMPILE_STRING; Args = {gnutls_credentials_type_t&}]’
../jami-daemon/src/connectivity/security/tls_session.cpp:1226:9: required from here
/usr/include/fmt/core.h:2561:10: error: use of deleted function ‘fmt::v10::formatter<T, Char, Enable>::formatter() [with T = gnutls_credentials_type_t; Char = char; Enable = void]’
2561 | return formatter<mapped_type, char_type>().parse(ctx);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/fmt/core.h:792:3: note: declared here
792 | formatter() = delete;
| ^~~~~~~~~
/usr/include/fmt/core.h: In instantiation of ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_value(T&&) [with Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; T = gnutls_credentials_type_t&]’:
/usr/include/fmt/core.h:1711:29: required from ‘constexpr fmt::v10::detail::value<Context> fmt::v10::detail::make_arg(T&&) [with bool IS_PACKED = true; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; type <anonymous> = fmt::v10::detail::type::custom_type; T = gnutls_credentials_type_t&; typename
std::enable_if<IS_PACKED, int>::type <anonymous> = 0]’
/usr/include/fmt/core.h:1827:77: required from ‘constexpr fmt::v10::format_arg_store<Context, Args>::format_arg_store(T&& ...) [with T = {gnutls_credentials_type_t&}; Context = fmt::v10::basic_format_context<fmt::v10::appender, char>; Args = {gnutls_credentials_type_t}]’
/usr/include/fmt/core.h:1844:31: required from ‘constexpr fmt::v10::format_arg_store<Context, typename std::remove_cv<typename std::remove_reference<T>::type>::type ...> fmt::v10::make_format_args(T&& ...) [with Context = basic_format_context<appender, char>; T = {gnutls_credentials_type_t&}]’
/usr/include/fmt/core.h:2817:44: required from ‘std::string fmt::v10::format(format_string<T ...>, T&& ...) [with T = {gnutls_credentials_type_t&}; std::string = std::__cxx11::basic_string<char>; format_string<T ...> = basic_format_string<char, gnutls_credentials_type_t&>]’
../jami-daemon/src/logger.h:173:51: required from ‘void jami::log::error(const char*, int, S&&, Args&& ...) [with S = jami::tls::TlsSession::TlsSessionImpl::handleStateHandshake(jami::tls::TlsSessionState)::<lambda()>::FMT_COMPILE_STRING; Args = {gnutls_credentials_type_t&}]’
../jami-daemon/src/connectivity/security/tls_session.cpp:1226:9: required from here
/usr/include/fmt/core.h:1691:7: error: static assertion failed: Cannot format an argument. To make type T formattable provide a formatter<T> specialization: https://fmt.dev/latest/api.html#udt
1691 | formattable,
| ^~~~~~~~~~~
/usr/include/fmt/core.h:1691:7: note: ‘formattable’ evaluates to false
```
An update to current fmt would be much appreciated. Thanks!https://git.jami.net/savoirfairelinux/jami-project/-/issues/1583Feature: End all calls if the client crashes or is uninstalled?2023-08-05T21:08:22ZElysFeature: End all calls if the client crashes or is uninstalled?If you exit Jami without stopping the call manually it will automatically be ended.
However if the client (on one device) crashes the call will still proceed if other peers with other devices are involved. Not sure what will happen if y...If you exit Jami without stopping the call manually it will automatically be ended.
However if the client (on one device) crashes the call will still proceed if other peers with other devices are involved. Not sure what will happen if you host a conference and your client crashes?
When it comes to Android: I think you would be able to uninstall Jami while you make a call?? If yes, what will happen if you are one peer or even the host?
Is it technically possible to end all calls if the client crashes or is it a won't-fix?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/876Incompatible with libgit2 1.7.02023-07-21T14:26:03ZDavid RungeIncompatible with libgit2 1.7.0Hi! I'm currently trying to rebuild this project against libgit2 1.7.0 on Arch Linux.
I'm building from https://git.jami.net/savoirfairelinux/jami-daemon/-/commit/0ec1d2e35301d5d420606288f804b376d1fd6be5 since [there are no releases](ht...Hi! I'm currently trying to rebuild this project against libgit2 1.7.0 on Arch Linux.
I'm building from https://git.jami.net/savoirfairelinux/jami-daemon/-/commit/0ec1d2e35301d5d420606288f804b376d1fd6be5 since [there are no releases](https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/124) (:sob:) and some time after that this project fails to build against opendht 2.5.5 (which we package), due to [updating the vendored opendht to a prerelease version](https://git.jami.net/savoirfairelinux/jami-daemon/-/commit/12288b33c7f6f360892bff0a5cc6aaedc4721103) (:sob:).
I see many instances of:
```
/usr/include/git2/sys/transport.h:116:17: error: ‘git_oidarray’ has not been declared
116 | git_oidarray *out,
| ^~~~~~~~~~~~
```
Full build log:
[jami-daemon-20230620-1-x86_64-build.log](/uploads/4432f30e6342f4a7229db6706b6d5222/jami-daemon-20230620-1-x86_64-build.log)
FWIW: You are currently vendoring [libgit2 1.1.0](https://github.com/libgit2/libgit2/releases/tag/v1.1.0) in [jami-20230619.1](https://dl.jami.net/release/tarballs/jami-20230619.1.tar.gz) which is from 2020. I am not really sure if this version is affected by [CVE-2023-22742](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22742), but either way it would be very good to see an update to this library, as it currently blocks our rebuild of libgit2https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1266Please allow translation of "Screen sharing" [Settings > Audio & Video]2023-07-28T18:42:42ZElysPlease allow translation of "Screen sharing" [Settings > Audio & Video]using Jami Version (Beta): 202307171543
I think the strings "Screen sharing" can't be translated (using Transifex?).
I've tried different languages like French, German and you always get "Screen sharing".
Can you please make it possib...using Jami Version (Beta): 202307171543
I think the strings "Screen sharing" can't be translated (using Transifex?).
I've tried different languages like French, German and you always get "Screen sharing".
Can you please make it possible to translate these strings?
![Screensharing](/uploads/d7f976244e69bdb0fb5cf8585d6a911f/Screensharing.png)Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1265missing property placeholderText in SwarmDetailsPanel.qml2023-07-28T07:03:33ZFuchtelJockelmissing property placeholderText in SwarmDetailsPanel.qmlThis issue is plaguing jami-qt master for a while already and I got annoyed enough to debug it.
Building jami-qt from master leads to a broken ChatView. The error says along the lines of: `could not build ChatView.qml`.
After scratching ...This issue is plaguing jami-qt master for a while already and I got annoyed enough to debug it.
Building jami-qt from master leads to a broken ChatView. The error says along the lines of: `could not build ChatView.qml`.
After scratching my head for I while I came up with the attached patch.
Hooray I can see the chat again
[jami-client-qt_fix.patch](/uploads/5eb9d4ec483592c071a82d7f110a9a61/jami-client-qt_fix.patch)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1328New message notification text is not corresponding the received message2023-11-01T18:07:03ZPierre NicolasNew message notification text is not corresponding the received message## Describe your environment
- Device model: Samsung-T720
- Android version: Android 11 API 30
- What build you are using: own client:b8d7425a04db165fbab5109ab832eb5a4ee4f8d7 daemon:7670be4ca58a19d9d3f381097ef1c6ee9716e20c
## Add...## Describe your environment
- Device model: Samsung-T720
- Android version: Android 11 API 30
- What build you are using: own client:b8d7425a04db165fbab5109ab832eb5a4ee4f8d7 daemon:7670be4ca58a19d9d3f381097ef1c6ee9716e20c
## Additional information
fruitdudragon send "jami" to abricot. We can see a notification saying "ABCD" from a swarm group. Which is another unread message but received sooner.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1582[Feature request] Opt-in to DISABLE Multi-Stream (own video(s))2023-10-20T17:10:21ZElys[Feature request] Opt-in to DISABLE Multi-Stream (own video(s))Since Multi-Stream should be now possible - at least on desktop:
https://docs.jami.net/user/all-features-by-client.html
https://jami.net/improving-call-experience-in-jami/
AS mentioned (https://docs.jami.net/developer/calls.html#multi...Since Multi-Stream should be now possible - at least on desktop:
https://docs.jami.net/user/all-features-by-client.html
https://jami.net/improving-call-experience-in-jami/
AS mentioned (https://docs.jami.net/developer/calls.html#multi-stream):
> Since daemon’s version 13.3.0, multi-stream is fully supported. This feature allows users to share multiple videos during a call at the same time.
But for all supported OS:
I would like to have an option to disable Multi-Stream. Sometimes - for example if you are already using a virtual camera - you don't need that option and if you want to switch your camera it's actually not very useful.
So maybe you can add an option
- to generally disable Multi-Stream (Opt-In in the settings for example)
- or disable that option for a few selected cameras (like "OBS-Virtual Camera" or "ManyCam Virtual Webcam": Jami won't add a second video - if that's technically possible (desktop))https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/875Video starts automatically when creating a conference by adding a participant2023-07-31T12:51:48ZAlexander Lussier-CullenVideo starts automatically when creating a conference by adding a participantPlease specify the following:
- Jami version: jami-client-android@8c707034cf7dfaba5eb788f9d5b45c06888e0d96
- Device model: Emulator (Android1) & Samsung A14 (Android2)
- Android version: 9 (Android1) & 13 (Android2)
## Steps to r...Please specify the following:
- Jami version: jami-client-android@8c707034cf7dfaba5eb788f9d5b45c06888e0d96
- Device model: Emulator (Android1) & Samsung A14 (Android2)
- Android version: 9 (Android1) & 13 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start an audio call from Android1 -> QT
2. Add a participant of Android2
3. Android2 starts their camera
- Actual result: Android1 now has their camera started and shared
- Expected result: Android1 doesn't have their camera started and sharedAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1263Remove SRTP fallback as it is not wanted anymore2023-07-25T08:31:05ZPierre NicolasRemove SRTP fallback as it is not wanted anymoreIt is not wanted anymore and it doesnt work either.
"Se rabattre sur RTP"
![image](/uploads/74d69e0497b43d2b8277f35d5c2ebe29/image.png)It is not wanted anymore and it doesnt work either.
"Se rabattre sur RTP"
![image](/uploads/74d69e0497b43d2b8277f35d5c2ebe29/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1327Video starts automatically when a multi-person call is elevated to video2023-07-18T19:15:41ZAlexander Lussier-CullenVideo starts automatically when a multi-person call is elevated to videoPlease specify the following:
- Jami version: 8c707034cf7dfaba5eb788f9d5b45c06888e0d96
- Device model: Emulator (Android1) & Samsung A14 (Android2)
- Android version: 9 (Android1) & 13 (Android2)
## Steps to reproduce
- Can yo...Please specify the following:
- Jami version: 8c707034cf7dfaba5eb788f9d5b45c06888e0d96
- Device model: Emulator (Android1) & Samsung A14 (Android2)
- Android version: 9 (Android1) & 13 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start an audio call from Android1 -> QT
2. Add a participant of Android2
3. Android2 starts their camera
- Actual result: Android1 now has their camera started and shared
- Expected result: Android1 doesn't have their camera started and sharedAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/873Starting video doesn't work2023-07-31T12:49:11ZAlexander Lussier-CullenStarting video doesn't work- Jami version: jami-client-android@48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast
- Android version: 11
## Steps to reproduce
- Steps:
1. Start video call from QT -> Android
2. Answer call with au...- Jami version: jami-client-android@48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast
- Android version: 11
## Steps to reproduce
- Steps:
1. Start video call from QT -> Android
2. Answer call with audio only on Android
3. Turn on the camera on Android
- Actual result: The QT client receives no video and the Android client preview is blacked out.
- Expected result: The QT client receives video and the Android client preview shows the camera feed.
## Additional information
* Even with my fixes made for screensharing, this can be reproduce by doing the same with a screenshare instead of the camera.
* Simply cycling the camera after the first time fails makes it workAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1324Impossible to share an account2023-07-14T15:22:51ZPierre NicolasImpossible to share an account## Describe your environment
- Device model: NVIDIA SHIELD Android TV
- Android version: Android 11, API 30
- What build you are using: own, client a8fbe8cfadd2e5dd9364ef318861a214e7af4f44; daemon bb8e1a805247c2d306061e0d0be265457...## Describe your environment
- Device model: NVIDIA SHIELD Android TV
- Android version: Android 11, API 30
- What build you are using: own, client a8fbe8cfadd2e5dd9364ef318861a214e7af4f44; daemon bb8e1a805247c2d306061e0d0be26545792ff338
## Steps to reproduce
- Can you reproduce the bug: at willPierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/42Certficate Chain and customize certificate2023-08-24T15:02:34ZXavier Jouslin de NorayCertficate Chain and customize certificateadd certificate chain inside certificate and customize certificateadd certificate chain inside certificate and customize certificateXavier Jouslin de NorayXavier Jouslin de Norayhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1323Impossible to create an account2023-07-14T15:22:53ZPierre NicolasImpossible to create an account## Describe your environment
- Device model: NVIDIA SHIELD Android TV
- Android version: Android 11, API 30
- What build you are using: own, client a8fbe8cfadd2e5dd9364ef318861a214e7af4f44; daemon bb8e1a805247c2d306061e0d0be265457...## Describe your environment
- Device model: NVIDIA SHIELD Android TV
- Android version: Android 11, API 30
- What build you are using: own, client a8fbe8cfadd2e5dd9364ef318861a214e7af4f44; daemon bb8e1a805247c2d306061e0d0be26545792ff338
## Steps to reproduce
- Can you reproduce the bug: at will
## Additional information
![image](/uploads/b442b331ff11b6af84173799fc8bb90b/image.png)
Logs: [crash_tv.log](/uploads/efeeda8566d808df027d440f658acb7d/crash_tv.log)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1259[SIP-Account] (Audio-)Call recording doesn't work2023-12-04T21:26:45ZElys[SIP-Account] (Audio-)Call recording doesn't workusing Jami Version (Beta): 202311221253 on Windows
- Make a call (SIM-call -\> SIP-Account (Jami))
- Now record the call
- After the call you view the recordings: However if you want to listen to the audio recording - even if the file s...using Jami Version (Beta): 202311221253 on Windows
- Make a call (SIM-call -\> SIP-Account (Jami))
- Now record the call
- After the call you view the recordings: However if you want to listen to the audio recording - even if the file should have a duration of 20 seconds - every music player can only "play" the file 0:00 seconds.
Note:
- NO Issues if I recorded a Jami call (Jami account 1 (Android) -\> Jami account 2(Windows 10)) - and it does NOT matter if I record an audio call or a video call
EDIT: Can't try if SIP-video call recording works.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1321Jami can't be opened anymore (only if you open Jami on Windows too)2023-07-15T09:06:02ZElysJami can't be opened anymore (only if you open Jami on Windows too)I am using the newest beta version of Jami(20230710-01) on EMUI 11
EDIT: I think I just reproduced: (Seee also https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1321#note_44328)
- Make a call Windows 10 (Jami Version (...I am using the newest beta version of Jami(20230710-01) on EMUI 11
EDIT: I think I just reproduced: (Seee also https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1321#note_44328)
- Make a call Windows 10 (Jami Version (Beta): 202306191617) (account1) -> Android (Jami Version (Beta): 20230710-01) (account 2)
- Now exit both apps
- After a few seconds / a minute try to open the Jami app on Android
- Jami can't be opened anymore (even if you reboot your phone)
The only solution is to open the desktop app too - After like 30 seconds you can open the Android app againPierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/871Lock on long merge commits2023-10-26T17:52:03ZSébastien BlinLock on long merge commitsOn Jami:Core, sometimes, we can't send messages. A thread seems to be blocked on git_merge_commits (with a lot of merge_annotated_commit)
The reason is still unclear.On Jami:Core, sometimes, we can't send messages. A thread seems to be blocked on git_merge_commits (with a lot of merge_annotated_commit)
The reason is still unclear.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1258SIP account - No audio when calling, RTP error2023-08-03T13:20:22ZRoberto ResoliSIP account - No audio when calling, RTP error- OS: Ubuntu Linux 22.04
- Jami version:
```
$ jami -v
Using Qt runtime version: 6.4.3
Jami 202306272010
```
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Call a POTS number from SIP account
1. The caller...- OS: Ubuntu Linux 22.04
- Jami version:
```
$ jami -v
Using Qt runtime version: 6.4.3
Jami 202306272010
```
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Call a POTS number from SIP account
1. The caller answers
1. No audio from the called
The problem is intermittent (sometimes the call works, sometimes not)
## Additional information
Executing with debug information (`jami -d`), when the problems happens there are multiple lines such:
```
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
[sdp @ 0x7f7988001340] RTP: dropping old packet received too late
```