savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-07-18T19:15:41Zhttps://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
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1320Soft break in messages are ignored2023-07-14T15:22:59ZPierre NicolasSoft break in messages are ignored## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![soft-break](/upload...## Describe your environment
- Jami version:
- Device model: Samsung-T720
- Android version: 20230710-01
- What build you are using: own 575fc884dfb95e46ae9a8bad5e7bf15f7c5b6b2f
## Additional information
![soft-break](/uploads/8f8206343be1ec4f5ad98e7483f359a8/soft-break.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1318No video is received when adding a participant2023-07-19T19:48:16ZAlexander Lussier-CullenNo video is received when adding a participant- Jami version: 48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast (Android1) & Emulator (Android2)
- Android version: 11 (Android1) & 9 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- ...- Jami version: 48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast (Android1) & Emulator (Android2)
- Android version: 11 (Android1) & 9 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start an audio call from QT -> Android1
2. Answer call on Android1
3. Start camera on QT
4. Add participant Android2
5. Answer call on Android2 with audio only
- Actual result: Android2 receives no video from QT
- Expected result: Android2 receives video from QTAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1317Adding participant to a video call causes preview to erroneously appear2023-07-31T12:55:43ZAlexander Lussier-CullenAdding participant to a video call causes preview to erroneously appear- Jami version: 48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast (Android1) & Emulator (Android2)
- Android version: 11 (Android1) & 9 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- ...- Jami version: 48be2a8b11273c84dff7e858148c2b197b51f615
- Device model: Moto G Fast (Android1) & Emulator (Android2)
- Android version: 11 (Android1) & 9 (Android2)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start an audio call from QT -> Android1
2. Answer call on Android1
3. Start camera on QT
4. Add participant Android2
5. Answer call on Android2 with video
- Actual result: Android1 has a blacked out preview window suggesting they have video active, but they do not
- Expected result: Android1 has no preview windowAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1315Starting video doesn't work2023-07-14T15:04:40ZAlexander Lussier-CullenStarting video doesn't work- Jami version: 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
...- Jami version: 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-daemon/-/issues/870pupnp avoid select() for sockets2024-03-06T16:25:35ZSébastien Blinpupnp avoid select() for sockets`select()` uses FD_SET() that can lead to random crashes unrelated to the number of files authorized per process.
This is used by `pupnp`, this may result in some backtraces like:
```
*** buffer overflow detected ***: terminated
Threa...`select()` uses FD_SET() that can lead to random crashes unrelated to the number of files authorized per process.
This is used by `pupnp`, this may result in some backtraces like:
```
*** buffer overflow detected ***: terminated
Thread 242 "jami" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffe6cf81640 (LWP 246791)]
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140730726618688) at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140730726618688)
at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=140730726618688) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=140730726618688, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff2442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff24287f3 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff24896f6 in __libc_message
(action=action@entry=do_abort, fmt=fmt@entry=0x7ffff25db943 "*** %s ***: terminated\n")
at ../sysdeps/posix/libc_fatal.c:155
#6 0x00007ffff253676a in __GI___fortify_fail
(msg=msg@entry=0x7ffff25db8e9 "buffer overflow detected") at ./debug/fortify_fail.c:26
#7 0x00007ffff25350c6 in __GI___chk_fail () at ./debug/chk_fail.c:28
#8 0x00007ffff25366ab in __fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:25
#9 0x00007ffff3961625 in sock_read_write
(info=info@entry=0x7ffe6cf7aa00, buffer=0x7fff854dc120 "GET /dyndev/uuid:2d27b940-da93-441d-b519-acf1fbd1d460 HTTP/1.1\r\nHOST: 192.168.1.1:5431\r\nDATE: Tue, 11 Jul 2023 16:38:42 GMT\r\nCONNECTION: close\r\nUSER-AGENT: Linux/5.19.0-46-generic, UPnP/1.0, Portable "..., bufsize=bufsize@entry=232, timeoutSecs=timeoutSecs@entry=0x7ffe6cf7a9ec, bRead=bRead@entry=0) at src/genlib/net/sock.c:187
#10 0x00007ffff396183c in sock_write
(info=info@entry=0x7ffe6cf7aa00, buffer=<optimized out>, bufsize=bufsize@entry=232, timeoutSecs=timeoutSecs@entry=0x7ffe6cf7a9ec) at src/genlib/net/sock.c:292
#11 0x00007ffff396480c in http_SendMessage
(info=info@entry=0x7ffe6cf7aa00, TimeOut=TimeOut@entry=0x7ffe6cf7a9ec, fmt=0x7ffff44dda77 "",
fmt@entry=0x7ffff44dda76 "b") at src/genlib/net/http/httpreadwrite.c:698
#12 0x00007ffff3964913 in http_RequestAndResponse
(destination=destination@entry=0x7ffe6cf7ab10, request=0x7fff854dc120 "GET /dyndev/uuid:2d27b940-da93-441d-b519-acf1fbd1d460 HTTP/1.1\r\nHOST: 192.168.1.1:5431\r\nDATE: Tue, 11 Jul 2023 16:38:42 GMT\r\nCONNECTION: close\r\nUSER-AGENT: Linux/5.19.0-46-generic, UPnP/1.0, Portable "..., request_length=232, req_method=req_method@entry=HTTPMETHOD_GET, timeout_secs=<optimized out>,
timeout_secs@entry=30, response=response@entry=0x7ffe6cf7abe0)
at src/genlib/net/http/httpreadwrite.c:788
#13 0x00007ffff3965eb0 in http_Download
(url_str=<optimized out>, timeout_secs=timeout_secs@entry=30, document=document@entry=0x7ffe6cf7ae48, doc_length=doc_length@entry=0x7ffe6cf7ae20, content_type=content_type@entry=0x7ffe6cf7ae50 "\006") at src/genlib/net/http/httpreadwrite.c:897
#14 0x00007ffff39574d0 in UpnpDownloadUrlItem
(url=<optimized out>, outBuf=outBuf@entry=0x7ffe6cf7ae48, contentType=contentType@entry=0x7ffe6cf7ae50 "\006") at src/api/upnpapi.c:3500
#15 0x00007ffff3957545 in UpnpDownloadXmlDoc (url=<optimized out>, xmlDoc=0x7ffe6cf7af48)
at src/api/upnpapi.c:3519
#16 0x00007ffff327342e in jami::upnp::PUPnP::downLoadIgdDescription(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
(this=0x7fff9c001f00, locationUrl="http://192.168.1.1:5431/dyndev/uuid:2d27b940-da93-441d-b519-acf1fbd1d460") at connectivity/upnp/protocol/pupnp/pupnp.cpp:840
#17 0x00007ffff3272ce3 in operator()() const (__closure=0x7fff9c015f50)
at connectivity/upnp/protocol/pupnp/pupnp.cpp:831
#18 0x00007ffff327cf16 in std::__invoke_impl<void, jami::upnp::PUPnP::processDiscoverySearchResult(const string&, const string&, const jami::IpAddr&)::<lambda()>&>(std::__invoke_other, struct {...} &)
(__f=...) at /usr/include/c++/11/bits/invoke.h:61
#19 0x00007ffff327b883 in std::__invoke_r<void, jami::upnp::PUPnP::processDiscoverySearchResult(const string&, const string&, const jami::IpAddr&)::<lambda()>&>(struct {...} &) (__fn=...)
at /usr/include/c++/11/bits/invoke.h:111
--Type <RET> for more, q to quit, c to continue without paging--
#20 0x00007ffff327a739 in std::_Function_handler<void(), jami::upnp::PUPnP::processDiscoverySearchResult(const string&, const string&, const jami::IpAddr&)::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/11/bits/std_function.h:290
#21 0x00007ffff38118a7 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dht::ThreadPool::run(std::function<void ()>&&)::{lambda()#1}> > >::_M_run() ()
at /home/sblin/Projects/jami-project/client-qt/daemon/src/.libs/libjami.so.0
#22 0x00007ffff28dc2b3 in () at /lib/x86_64-linux-gnu/libstdc++.so.6
#23 0x00007ffff2494b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#24 0x00007ffff2526a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)
```
Instead of this, it should use `poll()` to avoid this kind of limitation.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1257call: crash during a video conference2024-02-19T22:37:34ZThomas Ballasicall: crash during a video conference## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04.6
- Jami version: self-built
- What build you are using: @ commit `f903c635a790db966bf426d644050b24cab748c7`
## Steps to reproduce
There's isn't an actual ...## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04.6
- Jami version: self-built
- What build you are using: @ commit `f903c635a790db966bf426d644050b24cab748c7`
## Steps to reproduce
There's isn't an actual reproducible way yet.
The crash happened during a video conference with screen share after 2 hours and 20 minutes.
```
[New Thread 0x7ffbf6961700 (LWP 3467820)]
[New Thread 0x7ffbf6160700 (LWP 3467821)]
[New Thread 0x7ffbf595f700 (LWP 3467822)]
Added sink: 0x555559a58fe0 to subscribers for id: 1054419315475731_video_0
free(): invalid pointer
--Type <RET> for more, q to quit, c to continue without paging--
Thread 190 "QSGRenderThread" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffd6e7fc700 (LWP 3461292)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007ffff3320859 in __GI_abort () at abort.c:79
#2 0x00007ffff338b26e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff34b5298 "%s\n")
at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007ffff33932fc in malloc_printerr (str=str@entry=0x7ffff34b34c1 "free(): invalid pointer") at malloc.c:5347
#4 0x00007ffff3394b2c in _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:4173
#5 0x00007ffff7817660 in QVideoFrame::operator=(QVideoFrame const&) ()
at /usr/lib/libqt-jami/lib/libQt6Multimedia.so.6
#6 0x00007fff5011952e in () at /usr/lib/libqt-jami/qml/QtMultimedia/../../lib/libQt6MultimediaQuick.so.6
#7 0x00007ffff7415a36 in QSGBatchRenderer::Renderer::updateMaterialDynamicData(QSGBatchRenderer::ShaderManagerShader*, QSGMaterialShader::RenderState&, QSGMaterial*, QSGBatchRenderer::Batch const*, QSGBatchRenderer::Element*, int, int)
() at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007ffff7417e8e in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#9 0x00007ffff741a74d in QSGBatchRenderer::Renderer::prepareRenderPass(QSGBatchRenderer::Renderer::RenderPassContext*) () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#10 0x00007ffff741c247 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#11 0x00007ffff73e4a46 in QSGRenderer::renderScene() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#12 0x00007ffff7440c82 in QSGRhiLayer::grab() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#13 0x00007ffff7440de5 in QSGRhiLayer::updateTexture() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#14 0x00007ffff72c2a76 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#15 0x00007ffff7410175 in QSGRenderer::preprocess() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#16 0x00007ffff73e4a3a in QSGRenderer::renderScene() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#17 0x00007ffff7440c82 in QSGRhiLayer::grab() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#18 0x00007ffff7440de5 in QSGRhiLayer::updateTexture() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#19 0x00007ffff72c2a76 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#20 0x00007ffff7410175 in QSGRenderer::preprocess() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#21 0x00007ffff73e4a3a in QSGRenderer::renderScene() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#22 0x00007ffff7440c82 in QSGRhiLayer::grab() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#23 0x00007ffff7440de5 in QSGRhiLayer::updateTexture() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#24 0x00007ffff72c2a76 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#25 0x00007ffff7410175 in QSGRenderer::preprocess() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#26 0x00007ffff73e4a3a in QSGRenderer::renderScene() () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#27 0x00007ffff73e5594 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#28 0x00007ffff750f207 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#29 0x00007ffff57cfad3 in () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#30 0x00007ffff3846609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#31 0x00007ffff341d133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)
```https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1252Remove an account leads to crash2023-09-14T13:11:30ZPierre NicolasRemove an account leads to crash## Describe your environment
- OS: ubuntu 22.04
- Jami version: 202306261331
- What build you are using: apt
## Steps to reproduce
Remove an account that is imported multiple times.
## Additional information
![Kazam_screencast_00004]...## Describe your environment
- OS: ubuntu 22.04
- Jami version: 202306261331
- What build you are using: apt
## Steps to reproduce
Remove an account that is imported multiple times.
## Additional information
![Kazam_screencast_00004](/uploads/02e97d97b5dcb39ac79cc49571781ff9/Kazam_screencast_00004.webm)
[crash5.log](/uploads/ee46c5fc610f1a0dac2b3e37e56707fb/crash5.log)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1313Use device DHT proxy parameter when importing an account2023-07-07T17:11:00ZPierre NicolasUse device DHT proxy parameter when importing an accountAndroid client: c6985a8c175e1390a81a24ae995232a6c0cc3cb2
Daemon: 417447a167c52512e8c81250cc08bb5b24c6b667
Define the scope of the bug if it happens when importing an account from:
- [ ] archive
- [ ] link a new deviceAndroid client: c6985a8c175e1390a81a24ae995232a6c0cc3cb2
Daemon: 417447a167c52512e8c81250cc08bb5b24c6b667
Define the scope of the bug if it happens when importing an account from:
- [ ] archive
- [ ] link a new devicePierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/869JAMS account: Blocked users can still communicate2023-10-26T17:51:49ZLéo Banno-CloutierJAMS account: Blocked users can still communicate1. User A blocks user B
2. User B sends a message to user A
Actual: User A receives a notification and a red dot of the icon in the system tray, but there isn't any new messages in the conversation list
Expected: User A blocked user B,...1. User A blocks user B
2. User B sends a message to user A
Actual: User A receives a notification and a red dot of the icon in the system tray, but there isn't any new messages in the conversation list
Expected: User A blocked user B, so it shouldn't get notified about itSébastien BlinLéo Banno-CloutierSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1251Blocked users still send a notification and a red dot on the system tray2023-07-06T20:10:33ZLéo Banno-CloutierBlocked users still send a notification and a red dot on the system tray1. User A blocks user B
2. User B sends a message to user A
Actual: User A receives a notification and a red dot of the icon in the system tray, but there isn't any new messages in the conversation list
Expected: User A blocked user B,...1. User A blocks user B
2. User B sends a message to user A
Actual: User A receives a notification and a red dot of the icon in the system tray, but there isn't any new messages in the conversation list
Expected: User A blocked user B, so it shouldn't get notified about ithttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1249Clicking twice on the emoji button opens a second window.2023-07-06T15:49:36ZLiam CoursodonClicking twice on the emoji button opens a second window.Clicking twice on the emoji button in the text editor opens a second window.
It would be better if clicking a second time closed the first window.Clicking twice on the emoji button in the text editor opens a second window.
It would be better if clicking a second time closed the first window.Liam CoursodonLiam Coursodon