savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-12-12T23:20:59Zhttps://git.jami.net/savoirfairelinux/jami-web/-/issues/4Set up server API (WebSocket + REST)2022-12-12T23:20:59ZCharlie DuquetteSet up server API (WebSocket + REST)- REST API
- WebSocket API- REST API
- WebSocket APIMisha Krieger-RaynauldMisha Krieger-Raynauld2022-10-20https://git.jami.net/savoirfairelinux/jami-web/-/issues/3Set up formatter2022-09-28T19:04:08ZCharlie DuquetteSet up formatterSimon TranSimon Tranhttps://git.jami.net/savoirfairelinux/jami-web/-/issues/2Set up linter2022-12-12T23:21:01ZCharlie DuquetteSet up linterSimon TranSimon Tranhttps://git.jami.net/savoirfairelinux/jami-web/-/issues/1Add Typescript Support2022-12-12T23:20:57ZCharlie DuquetteAdd Typescript SupportSimon TranSimon Tranhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/832Can't choose JPG as image (.JPG capital letters)2022-09-15T21:03:26ZsbaduxCan't choose JPG as image (.JPG capital letters)## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: 202208251306
- Snap package
## Steps to reproduce
- Can you reproduce the bug: [yes]
- Steps:
1. Save a JPG file image. NOTE: the extension must ...## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: 202208251306
- Snap package
## Steps to reproduce
- Can you reproduce the bug: [yes]
- Steps:
1. Save a JPG file image. NOTE: the extension must be .JPG (capital letters) and not .jpg
2. Change profile image
3. The .JPG file is not shown.
4. If you change extension as .jpg it's correctly shown and usable
- Expected result: capital letters extensions should be usable as wellhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1477[Feature request] Please show a notification if one peer disables/disabled video2023-06-16T19:46:35ZElys[Feature request] Please show a notification if one peer disables/disabled videoScenario:
Alice makes a video call and calls Bob. However Bob generally disabled video (calls).
If one peer has video disabled generally or disables video while you're on a call (in a conference) it would be better if the other peer ge...Scenario:
Alice makes a video call and calls Bob. However Bob generally disabled video (calls).
If one peer has video disabled generally or disables video while you're on a call (in a conference) it would be better if the other peer gets a message like:
"Bob (or every other Jami username) disabled video".
As soon as (Multi-)Swarm-Calls (also group video calls?) will be available or if you're in a conference it should be discussed if all peers get this message or just the host for example.
Or maybe the host can choose if other members get a notification if one peer disables/(generally) disabled video.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1476Issue if you disable video while you're on a (1:1) video call [Windows 10/And...2022-09-15T18:04:22ZElysIssue if you disable video while you're on a (1:1) video call [Windows 10/Android]using newest beta version of Jami
also related: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1475
steps to reproduce:
Issue 1:
Android & Windows 10 both enabled video
1. Make a video call Windows 10 -> Android
1. Just...using newest beta version of Jami
also related: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1475
steps to reproduce:
Issue 1:
Android & Windows 10 both enabled video
1. Make a video call Windows 10 -> Android
1. Just Windows 10 while you're on a video call: Go to settings -> Account -> Media -> and disable video
1. Windows 10: Now return to the video
1. The video of the Windows 10 webcam still keeps running (and both persons can view all video streams)
1. Now just the Android user changes the camera
1. The Windows 10 user and the Android user can now see the camera preview of their own camera but the Android user can't see the Windows 10 user and the Windows 10 user can't see the Android user (The Android user will just see the profile picture of the Windows 10 user; the Windows 10 user just gets a black video)
1. Now exit the call
Issue 2:
Android & Windows 10 both enabled video
1. Make a video call Windows 10 -> Android
1. Android: While you're on a video call: Go to settings and disable the video -> the video still keeps running
1. Android: If you switch the camera the Windows 10 user will still see the video of the Android user, but the video of Windows 10 user will freeze (although the Windows 10 user never switched the camera or turned it on or off)
1. the Android user can even switch the camera and/or shares his screen
1. After the Android user stops to share his phone screen he can see the Windows 10 user again
Maybe you can also check scenarios like group call (conferences) if just one peer disables video while he is on the call.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1475Disabling video: some issues?2023-05-12T15:46:46ZElysDisabling video: some issues?using the newest beta version of Jami
I read the following information: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1316#note_31286
> Disabling video fully disables video in Jami. No video can be sent or received, and s...using the newest beta version of Jami
I read the following information: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1316#note_31286
> Disabling video fully disables video in Jami. No video can be sent or received, and screen sharing would not be possible. It's mostly for embedded systems with no screen or limited hardware capabilities, or for people who just want audio for various reasons (gamers, some business use cases..?)
> So if video is disabled, the video call and screen share options should not be displayed. File streaming would only allow to stream audio files.
Steps to reproduce: (Calls Windows 10 <-> Android, using different Jami accounts)
1)
Just disable video on the Android device:
- You still view the video call button on your Android screen
2)
Make a video call Android (Video) -> Windows 10: Video calls still work
3)
Now make a video call Windows 10 -> Android
-(Android:) You can only answer in audio
However the Windows 10 user will view his own preview (but not the Android user)
- during the call the Android user will be still able to tap the camera on/off button or the Share screen button - but the Android user will never get a video
other direction:
Just the Windows 10 user disables video
- he will have no video call button anymore
Now the Android user makes a video call: Android -> Windows 10
Windows: only allows to answer in audio
However the android user is still able to tap the camera icon and share the screen (although the video won't work)
And after you exit a call you get a notification of an incoming call? Is this also a bug?
Maybe you can also test these scenarios using conferences and in the future swarm-calls.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/829[Feature Request] Ability to minimize to tray on launch2023-05-12T15:15:51ZDilly O[Feature Request] Ability to minimize to tray on launchI like to launch Jami on startup so it's ready to accept calls, but I don't necessarily want to interact with it right away after each boot. It would be great to have an option to keep it minimized to the tray when launching.I like to launch Jami on startup so it's ready to accept calls, but I don't necessarily want to interact with it right away after each boot. It would be great to have an option to keep it minimized to the tray when launching.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/828[Windows 10 1:1 video call] using VP8 won't show the video of the Android cal...2022-09-16T20:36:12ZElys[Windows 10 1:1 video call] using VP8 won't show the video of the Android caller if the Android user enabled hardware accelerationusing newest beta version of Jami
Make a call Windows 10 -> Android
If you just choose the VP8 video codec during a call:
* The video of the webcamera of the Windows 10 user can be viewed by the Android user
* The Android user will vie...using newest beta version of Jami
Make a call Windows 10 -> Android
If you just choose the VP8 video codec during a call:
* The video of the webcamera of the Windows 10 user can be viewed by the Android user
* The Android user will view his own video preview
* The Windows 10 user will view his own video preview
BUT:
The Windows 10 user won't see the video of the Android user (or sometimes just a black & white video that will freeze (just the Windows 10 user will see the frozen video of the Android user) if the **Android user enables hardware acceleration** and **just uses VP8**
No issues if just the Windows 10 user enables or disables hardware acceleration
If the developers can reproduce, can you also try to reproduce this issue in conferences (and/or Multistream)?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/764Sporadic crash in ConnectionManager2022-10-01T10:12:41ZSébastien BlinSporadic crash in ConnectionManager```
[New Thread 0x7fffa67fc640 (LWP 2962014)]
Thread 74 "ut_conversation" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff527fc640 (LWP 2960732)]
0x0000000000ad98cb in pj_grp_lock_acquire ()
(gdb) bt
#0 0x000000...```
[New Thread 0x7fffa67fc640 (LWP 2962014)]
Thread 74 "ut_conversation" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff527fc640 (LWP 2960732)]
0x0000000000ad98cb in pj_grp_lock_acquire ()
(gdb) bt
#0 0x0000000000ad98cb in pj_grp_lock_acquire ()
#1 0x000000000059edfd in jami::IceLock::lock (this=0x7fff527f8c58) at ice_transport.cpp:92
#2 0x000000000059edc3 in jami::IceLock::IceLock (this=0x7fff527f8c58, strans=0x0) at ice_transport.cpp:87
#3 0x00000000005975ff in jami::IceTransport::isStarted (this=0x7fff4c16c180) at ice_transport.cpp:1173
#4 0x0000000000598370 in jami::IceTransport::stop (this=0x7fff4c16c180) at ice_transport.cpp:1354
#5 0x0000000000a0f0c2 in jami::ConnectionManager::Impl::removeUnusedConnections (this=0x7fffd81108d0, deviceId=...) at jamidht/connectionmanager.cpp:83
#6 0x0000000000a0f442 in jami::ConnectionManager::Impl::shutdown (this=0x7fffd81108d0) at jamidht/connectionmanager.cpp:109
#7 0x00000000009ff484 in jami::ConnectionManager::~ConnectionManager (this=0x7fffd80c90e0, __in_chrg=<optimized out>) at jamidht/connectionmanager.cpp:1038
#8 0x00000000007c9060 in std::default_delete<jami::ConnectionManager>::operator() (this=0x1d2fcd0, __ptr=0x7fffd80c90e0) at /usr/include/c++/12/bits/unique_ptr.h:95
#9 0x00000000007bce44 in std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> >::~unique_ptr (this=0x1d2fcd0, __in_chrg=<optimized out>) at /usr/include/c++/12/bits/unique_ptr.h:396
#10 0x00000000007fd1be in std::_Destroy<std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> > > (__pointer=0x1d2fcd0) at /usr/include/c++/12/bits/stl_construct.h:151
#11 0x00000000007fceac in std::allocator_traits<std::allocator<void> >::destroy<std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> > > (__p=0x1d2fcd0) at /usr/include/c++/12/bits/alloc_traits.h:648
#12 0x00000000007fc641 in std::_Sp_counted_ptr_inplace<std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> >, std::allocator<void>, (__gnu_cxx::_Lock_policy)2>::_M_dispose (this=0x1d2fcc0)
at /usr/include/c++/12/bits/shared_ptr_base.h:613
#13 0x0000000000484521 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release (this=0x1d2fcc0) at /usr/include/c++/12/bits/shared_ptr_base.h:346
#14 0x000000000048544b in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count (this=0x1d2ac48, __in_chrg=<optimized out>) at /usr/include/c++/12/bits/shared_ptr_base.h:1071
#15 0x00000000007b8cfe in std::__shared_ptr<std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> >, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr (this=0x1d2ac40, __in_chrg=<optimized out>)
at /usr/include/c++/12/bits/shared_ptr_base.h:1524
#16 0x00000000007b8d1a in std::shared_ptr<std::unique_ptr<jami::ConnectionManager, std::default_delete<jami::ConnectionManager> > >::~shared_ptr (this=0x1d2ac40, __in_chrg=<optimized out>) at /usr/include/c++/12/bits/shared_ptr.h:175
#17 0x0000000000771096 in ~<lambda>(void) (this=0x1d2ac40, __in_chrg=<optimized out>) at jamidht/jamiaccount.cpp:359
#18 0x00000000007a8185 in std::_Function_base::_Base_manager<jami::JamiAccount::shutdownConnections()::<lambda()> >::_M_destroy(std::_Any_data &, std::false_type) (__victim=...) at /usr/include/c++/12/bits/std_function.h:175
#19 0x000000000079e5a3 in std::_Function_base::_Base_manager<jami::JamiAccount::shutdownConnections()::<lambda()> >::_M_manager(std::_Any_data &, const std::_Any_data &, std::_Manager_operation) (__dest=..., __source=...,
__op=std::__destroy_functor) at /usr/include/c++/12/bits/std_function.h:203
#20 0x0000000000798712 in std::_Function_handler<void(), jami::JamiAccount::shutdownConnections()::<lambda()> >::_M_manager(std::_Any_data &, const std::_Any_data &, std::_Manager_operation) (__dest=..., __source=...,
__op=std::__destroy_functor) at /usr/include/c++/12/bits/std_function.h:282
#21 0x0000000000b17766 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dht::ThreadPool::run(std::function<void ()>&&)::{lambda()#1}> > >::_M_run() ()
#22 0x00007ffff6adbb03 in execute_native_thread_routine () from /lib64/libstdc++.so.6
#23 0x00007ffff668ce2d in start_thread () from /lib64/libc.so.6
#24 0x00007ffff67121b0 in clone3 () from /lib64/libc.so.6
(gdb)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1474Save Conversation History2022-09-09T15:31:02ZthoranSave Conversation HistoryThis request is prompted by the need to destroy a conversation in order to initiate a swarm-based convo. I'd like to download a conversation first before doing that. I could have the participant create a new account, but it shouldn't be ...This request is prompted by the need to destroy a conversation in order to initiate a swarm-based convo. I'd like to download a conversation first before doing that. I could have the participant create a new account, but it shouldn't be as hard as it is to copy that conversation. Select-all just selects one message and not the contents of all messages. Perhaps that's a security feature, but I suspect it is an incidental rather than a deliberate one. Correct me if I'm wrong. Is there a way to decrypt the conversation and dump it from the command line, since I don't need a means of doing that from the GUI, but don't mind if you did provide that, even if your efforts should be put elsewhere if the ability to do it from the CLI is easier to implement or already exists. Also, the phrase "Migrate conversation" on the button to switch to swarm-based convo's is very misleading as the conversation is DELETED not migrated.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/827Improve timestamp display in the chatview2022-10-31T16:10:02ZSébastien BlinImprove timestamp display in the chatviewDesign reference
![Screenshot_2022-09-08_at_15-42-59_Adobe_XD](/uploads/178d61786259473acee77c8c50ab5bbb/Screenshot_2022-09-08_at_15-42-59_Adobe_XD.png)Design reference
![Screenshot_2022-09-08_at_15-42-59_Adobe_XD](/uploads/178d61786259473acee77c8c50ab5bbb/Screenshot_2022-09-08_at_15-42-59_Adobe_XD.png)Nicolas VengeonNicolas Vengeonhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/763Crash in peer_connection2022-12-29T16:39:16ZSébastien BlinCrash in peer_connection# Scenario
none
# Backtrace
```
2022-09-07 12:22:02.789 15614-27109 libc pid-15614 A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1 in tid 27109 (Thread-18027), pid 15614 (cx.ring)
2022-09-07 ...# Scenario
none
# Backtrace
```
2022-09-07 12:22:02.789 15614-27109 libc pid-15614 A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1 in tid 27109 (Thread-18027), pid 15614 (cx.ring)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A Cmdline: cx.ring
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A pid: 15614, tid: 27109, name: Thread-18027 >>> cx.ring <<<
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #00 pc 0000000000d22e0c /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (jami::IceTransport::cancelOperations()+24)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #01 pc 0000000001315500 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (jami::TlsSocketEndpoint::shutdown()+248)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #02 pc 0000000001362f04 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (jami::MultiplexedSocket::Impl::shutdown()+224)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #03 pc 0000000001355d6c /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (jami::MultiplexedSocket::Impl::eventLoop()+424)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #04 pc 000000000136f354 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()::operator()() const+32)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #05 pc 000000000136f2e8 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (decltype(std::__ndk1::forward<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(fp)()) std::__ndk1::__invoke<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()&&)+24)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #06 pc 000000000136f288 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (void std::__ndk1::__thread_execute<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>&, std::__ndk1::__tuple_indices<>)+32)
2022-09-07 12:22:05.876 28069-28069 DEBUG pid-28069 A #07 pc 000000000136efe4 /data/app/~~9yX6U37i7cjLkuy_wJtYDA==/cx.ring-wsPGQcNLaDnoFvMbixm3GQ==/base.apk (void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()> >(void*)+108)
2022-09-07 14:03:44.847 24432-25046 libc pid-24432 A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1 in tid 25046 (Thread-1785), pid 24432 (cx.ring)
2022-09-07 14:03:46.509 3653-3653 DEBUG pid-3653 A Cmdline: cx.ring
2022-09-07 14:03:46.509 3653-3653 DEBUG pid-3653 A pid: 24432, tid: 25046, name: Thread-1785 >>> cx.ring <<<
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #00 pc 0000000000d22e0c /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::IceTransport::cancelOperations()+24)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #01 pc 0000000001315500 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::TlsSocketEndpoint::shutdown()+248)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #02 pc 0000000001362f04 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::shutdown()+224)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #03 pc 0000000001355d6c /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::eventLoop()+424)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #04 pc 000000000136f354 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()::operator()() const+32)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #05 pc 000000000136f2e8 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (decltype(std::__ndk1::forward<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(fp)()) std::__ndk1::__invoke<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()&&)+24)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #06 pc 000000000136f288 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (void std::__ndk1::__thread_execute<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>&, std::__ndk1::__tuple_indices<>)+32)
2022-09-07 14:03:46.510 3653-3653 DEBUG pid-3653 A #07 pc 000000000136efe4 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()> >(void*)+108)
2022-09-07 15:32:11.382 15670-16051 libc pid-15670 A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1 in tid 16051 (Thread-1842), pid 15670 (cx.ring)
2022-09-07 15:32:13.956 16804-16804 DEBUG pid-16804 A Cmdline: cx.ring
2022-09-07 15:32:13.956 16804-16804 DEBUG pid-16804 A pid: 15670, tid: 16051, name: Thread-1842 >>> cx.ring <<<
2022-09-07 15:32:13.956 16804-16804 DEBUG pid-16804 A #00 pc 0000000000d22e0c /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::IceTransport::cancelOperations()+24)
2022-09-07 15:32:13.956 16804-16804 DEBUG pid-16804 A #01 pc 0000000001315500 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::TlsSocketEndpoint::shutdown()+248)
2022-09-07 15:32:13.956 16804-16804 DEBUG pid-16804 A #02 pc 0000000001362f04 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::shutdown()+224)
2022-09-07 15:32:13.957 16804-16804 DEBUG pid-16804 A #03 pc 0000000001355d6c /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::eventLoop()+424)
2022-09-07 15:32:13.957 16804-16804 DEBUG pid-16804 A #04 pc 000000000136f354 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()::operator()() const+32)
2022-09-07 15:32:13.957 16804-16804 DEBUG pid-16804 A #05 pc 000000000136f2e8 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (decltype(std::__ndk1::forward<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(fp)()) std::__ndk1::__invoke<jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()&&)+24)
2022-09-07 15:32:13.957 16804-16804 DEBUG pid-16804 A #06 pc 000000000136f288 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (void std::__ndk1::__thread_execute<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>(std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()>&, std::__ndk1::__tuple_indices<>)+32)
2022-09-07 15:32:13.957 16804-16804 DEBUG pid-16804 A #07 pc 000000000136efe4 /data/app/~~Qzk32LlX3MAo9qvSgI4-MA==/cx.ring-SQuHwUPNcoDHjI4QX82a5A==/base.apk (void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, jami::MultiplexedSocket::Impl::Impl(jami::MultiplexedSocket&, dht::Hash<32ul> const&, std::__ndk1::unique_ptr<jami::TlsSocketEndpoint, std::__ndk1::default_delete<jami::TlsSocketEndpoint> >)::'lambda'()> >(void*)+108)
--------- beginning of system
2022-09-08 14:08:26.791 1909-2023 VerityUtils system_server E Failed to measure fs-verity, errno 1: /data/app/~~bKV2Ot0nhEgxaOviWOzvjg==/cx.ring-0sSYbhKeLYc2d7DZ__s6Ig==/base.apk
2022-09-08 14:08:28.106 1909-2023 VerityUtils system_server E Failed to measure fs-verity, errno 1: /data/app/~~bKV2Ot0nhEgxaOviWOzvjg==/cx.ring-0sSYbhKeLYc2d7DZ__s6Ig==/base.apk
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/762Recorder: auto record does not take video in video calls2023-03-23T15:26:50ZAline Gondim SantosRecorder: auto record does not take video in video callsCurrent behaviour:
* Enable automatic recording;
* Make a video call;
* Saved file contains audio only.
Expected:
* Saved file contains audio and video data.Current behaviour:
* Enable automatic recording;
* Make a video call;
* Saved file contains audio only.
Expected:
* Saved file contains audio and video data.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/180conversation: wrong aspect ratio for contact's avatar2022-10-20T15:38:08ZKateryna Kostiukconversation: wrong aspect ratio for contact's avatarBinal AhiyaBinal Ahiyahttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1116Conversations replace BottomNavigation with TabLayout2022-11-11T18:27:15ZAmirhossein NaghshzanConversations replace BottomNavigation with TabLayoutImplementing the new design for conversations and replacing the BottomNavigation with TabLayout.
https://xd.adobe.com/view/5ebda7e6-523a-488a-b7b7-befd79255ca3-0bee/Implementing the new design for conversations and replacing the BottomNavigation with TabLayout.
https://xd.adobe.com/view/5ebda7e6-523a-488a-b7b7-befd79255ca3-0bee/Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1473[Android] Can I stop incoming calls from ringing?2022-09-08T11:57:27Zcyorimer[Android] Can I stop incoming calls from ringing?When using the Android phone application, a ringtone is always made when an incoming call is received.
The smartphone is set to silent (& vibrate).
Incoming phone calls and other social networking apps will be silent and only vibrate.
JA...When using the Android phone application, a ringtone is always made when an incoming call is received.
The smartphone is set to silent (& vibrate).
Incoming phone calls and other social networking apps will be silent and only vibrate.
JAMI ignores the smartphone setting and the ringtone will ring and cannot be turned off.
Model used: Xiaomi Redmi note 9S / Xiaomi Mi 10Thttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/179notification: service stops before notification completed2023-06-07T19:11:44ZKateryna Kostiuknotification: service stops before notification completedSometimes notification service stops before conversation fetch completed or timeout for extension triggered. It is more noticible on Cellular data. Probably signal ConversationSyncFinished arrive earlier.Sometimes notification service stops before conversation fetch completed or timeout for extension triggered. It is more noticible on Cellular data. Probably signal ConversationSyncFinished arrive earlier.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/178notification: there is no notification for invitation2023-04-07T13:02:27ZKateryna Kostiuknotification: there is no notification for invitationKateryna KostiukKateryna Kostiuk