savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-12-06T21:21:34Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/573Jami recivies SIGABRT while connecting to network2021-12-06T21:21:34ZИльдар АхметгалеевJami recivies SIGABRT while connecting to network## Describe your environment
Please specify the following:
- OS: Manjaro Linux x86_64
- Jami version: 202110150847
- What build you are using: flathub beta
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Star...## Describe your environment
Please specify the following:
- OS: Manjaro Linux x86_64
- Jami version: 202110150847
- What build you are using: flathub beta
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start jami-qt.
2. Log in to existing account.
3. Wait about 10 seconds while jami connects to network.
4. Crash.
- Actual result: jami-qt crashes.
- Expected result: it should not crash.
## Additional information
Console log:
```
[1634310322.509| 132|connectionmanager.cpp:767 ] [Account 02f00663f1ee75e7] [CNX] connection accepted, DHT reply to 4933c5ea1771c0b432a38c751833856c2fdcee61dd4d281f652badb9bc915227
[1634310322.509| 132|ice_transport.cpp :1255 ] [ice:0x7ffedc1b7700] negotiation starting (7 remote candidates)
[1634310322.603| 101|account_manager.cpp:211 ] device announced at 31b900c6be8cebabbcfe33d96750cb1e7b06b600
[1634310323.017| 142|ice_transport.cpp :686 ] [ice:0x7ffedc1b7700] TCP negotiation success
[1634310323.017| 142|ice_transport.cpp :712 ] [ice:0x7ffedc1b7700] TCP connection pairs ([comp id] local [type] <-> remote [type]):
[1] 192.168.16.178:55192 [prflx] <-> 192.168.16.182:14206 [host]
[1634310323.017| 104|connectionmanager.cpp:831 ] [Account 02f00663f1ee75e7] Start TLS session - Initied by DHT request. Device:afc6dfe77c7af829b4f88dc21f68601012ff69e5 - vid: 2548209633465894
[New Thread 0x7ffeaffff700 (LWP 143)]
[1634310323.017| 143|tls_session.cpp :1057 ] [TLS] Start client session
[1634310323.030| 143|tls_session.cpp :528 ] [TLS] User identity loaded
[1634310323.030| 143|tls_session.cpp :1153 ] [TLS] handshake
/usr/include/c++/10.2.0/bits/stl_vector.h:1063: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = jami::IpAddr; _Alloc = std::allocator<jami::IpAddr>; std::vector<_Tp, _Alloc>::const_reference = const jami::IpAddr&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
--Type <RET> for more, q to quit, c to continue without paging--c
```
Backtrace:
```gdb
(gdb) bt
#0 0x00007ffff54b97f5 in raise () at /usr/lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff54a2855 in abort () at /usr/lib/x86_64-linux-gnu/libc.so.6
#2 0x00007fffec56af98 in std::__replacement_assert(char const*, int, char const*, char const*)
(__file=__file@entry=0x7fffecfab8d8 "/usr/include/c++/10.2.0/bits/stl_vector.h", __line=__line@entry=1063, __function=__function@entry=0x7fffecfb4d28 "std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = jami::IpAddr; _Alloc = std::allocator<jami::IpAddr>; std::vector<_"..., __condition=__condition@entry=0x7fffecfb0b70 "__builtin_expect(__n < this->size(), true)")
at /usr/include/c++/10.2.0/x86_64-unknown-linux-gnu/bits/c++config.h:457
#3 0x00007fffec5cc7a7 in std::vector<jami::IpAddr, std::allocator<jami::IpAddr> >::operator[](unsigned long) const
(this=<optimized out>, __n=<optimized out>) at /usr/include/c++/10.2.0/bits/stl_vector.h:1061
#4 std::vector<jami::IpAddr, std::allocator<jami::IpAddr> >::operator[](unsigned long) const
(this=<optimized out>, this=<optimized out>, __n=<optimized out>) at /usr/include/c++/10.2.0/bits/stl_vector.h:1061
#5 jami::IceTransport::Impl::getDefaultRemoteAddress(unsigned int) const (this=<optimized out>, compId=<optimized out>) at ice_transport.cpp:1094
#6 0x00007fffec5cc7e2 in jami::IceTransport::getRemoteAddress(unsigned int) const (this=0x7ffedc0bd6d0, comp_id=1)
at /usr/include/c++/10.2.0/bits/unique_ptr.h:421
#7 0x00007fffec5cc9f0 in jami::IceTransport::send(unsigned int, unsigned char const*, unsigned long)
(this=0x7ffedc0bd6d0, compId=1, buf=buf@entry=0x7ffee404ad7b "\026\003\001\001.\001", len=len@entry=307) at ice_transport.cpp:1681
#8 0x00007fffec5e2d23 in jami::IceSocketEndpoint::write(unsigned char const*, unsigned long, std::error_code&)
(ec=..., len=307, buf=0x7ffee404ad7b "\026\003\001\001.\001", this=0x7ffef0002db0) at /usr/include/c++/10.2.0/bits/shared_ptr_base.h:1324
#9 jami::IceSocketEndpoint::write(unsigned char const*, unsigned long, std::error_code&)
(this=0x7ffef0002db0, buf=0x7ffee404ad7b "\026\003\001\001.\001", len=307, ec=...) at peer_connection.cpp:145
#10 0x00007fffec76a32d in jami::tls::TlsSession::TlsSessionImpl::sendRaw(void const*, unsigned long)
(this=0x7ffed00038e0, buf=0x7ffee404ad7b, size=307) at ./security/tls_session.cpp:898
#11 0x00007fffec76a6eb in jami::tls::TlsSession::TlsSessionImpl::sendRawVec(iovec const*, int)
(iovcnt=<optimized out>, iov=<optimized out>, this=0x7ffed00038e0) at ./security/tls_session.cpp:909
#12 operator() (iovcnt=<optimized out>, iov=<optimized out>, t=0x7ffed00038e0, __closure=0x0) at ./security/tls_session.cpp:605
#13 _FUN(gnutls_transport_ptr_t, giovec_t const*, int) () at ./security/tls_session.cpp:606
#14 0x00007fffe836a309 in _gnutls_io_write_flush () at /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#15 0x00007fffe836b598 in _gnutls_handshake_io_write_flush () at /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#16 0x00007fffe836d6f8 in _gnutls_send_handshake2 () at /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#17 0x00007fffe83712ff in send_client_hello () at /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#18 0x00007fffe83718f8 in gnutls_handshake () at /usr/lib/x86_64-linux-gnu/libgnutls.so.30
#19 0x00007fffec768388 in jami::tls::TlsSession::TlsSessionImpl::handleStateHandshake(jami::tls::TlsSessionState)
(this=0x7ffed00038e0, state=jami::tls::TlsSessionState::HANDSHAKE) at ./security/tls_session.cpp:1154
#20 0x00007fffec76d488 in std::function<jami::tls::TlsSessionState (jami::tls::TlsSessionState)>::operator()(jami::tls::TlsSessionState) const
(__args#0=jami::tls::TlsSessionState::HANDSHAKE, this=0x7ffee400a398) at /usr/include/c++/10.2.0/bits/std_function.h:617
--Type <RET> for more, q to quit, c to continue without paging--c
#21 jami::tls::TlsSession::TlsSessionImpl::process() (this=0x7ffed00038e0) at ./security/tls_session.cpp:1554
#22 0x00007fffec5c61ad in std::function<void ()>::operator()() const (this=0x7ffeafffbfe0) at /usr/include/c++/10.2.0/bits/std_function.h:617
#23 jami::ThreadLoop::mainloop(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>) (this=0x7ffed0003c50, tid=..., setup=..., process=..., cleanup=...) at threadloop.cpp:38
#24 0x00007fffec5c6a2a in std::__invoke_impl<void, void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> >(std::__invoke_memfun_deref, void (jami::ThreadLoop::*&&)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*&&, std::reference_wrapper<std::thread::id>&&, std::function<bool ()>&&, std::function<void ()>&&, std::function<void ()>&&) (__f=<optimized out>, __t=<optimized out>, __f=<optimized out>, __t=<optimized out>) at /usr/include/c++/10.2.0/bits/refwrap.h:337
#25 std::__invoke<void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> >(void (jami::ThreadLoop::*&&)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*&&, std::reference_wrapper<std::thread::id>&&, std::function<bool ()>&&, std::function<void ()>&&, std::function<void ()>&&) (__fn=<optimized out>) at /usr/include/c++/10.2.0/bits/invoke.h:95
#26 std::thread::_Invoker<std::tuple<void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> > >::_M_invoke<0ul, 1ul, 2ul, 3ul, 4ul, 5ul>(std::_Index_tuple<0ul, 1ul, 2ul, 3ul, 4ul, 5ul>) (this=<optimized out>) at /usr/include/c++/10.2.0/thread:264
#27 std::thread::_Invoker<std::tuple<void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> > >::operator()() (this=<optimized out>) at /usr/include/c++/10.2.0/thread:271
#28 std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> > > >::_M_run() (this=<optimized out>) at /usr/include/c++/10.2.0/thread:215
#29 0x00007ffff5895a74 in execute_native_thread_routine () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#30 0x00007ffff54664d2 in start_thread () at /usr/lib/x86_64-linux-gnu/libpthread.so.0
#31 0x00007ffff557e323 in clone () at /usr/lib/x86_64-linux-gnu/libc.so.6
```
Flathub's bug report https://github.com/flathub/net.jami.Jami/issues/37Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/572Very high CPU when idle on the main window only - Jami 202110011958 on Xubunt...2022-05-13T15:18:04Zgilles gaidoVery high CPU when idle on the main window only - Jami 202110011958 on Xubuntu 20.04Report a bug
-------------------
Very HIGH CPU consumption on main screen when idle.
## Environment
- OS: Ubuntu 20.04.3 LTS x86_64 ( Kernel: 5.4.0-88-generic ) DE: Xfce , WM: Xfwm4
- Jami version: 202110011958
- What build you are usi...Report a bug
-------------------
Very HIGH CPU consumption on main screen when idle.
## Environment
- OS: Ubuntu 20.04.3 LTS x86_64 ( Kernel: 5.4.0-88-generic ) DE: Xfce , WM: Xfwm4
- Jami version: 202110011958
- What build you are using: 202110011958 / jami_20210930.1.835f5ae~dfsg1-1_amd64 installed thru "apt install" (includes libqt-jami_5.15.2-1_amd64)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1.stop all applications and open a task manager to monitor CPU
2.open JAMI's client (configured with at least 1 contact)
3.keep the JAMI window opened : more than 80% CPU consumption (CPU: Intel i5-4690T (3) @ 2.494GHz)
4.minimize the JAMI window : no CPU consumption (less than 2%)
5.open the JAMI window opened : more than 80% CPU consumption again
6.go to the JAMI settings : no CPU consumption (less than 2%)
- Actual result: when opened and idle, JAMI uses more than 80% of CPU
- Expected result:when opened and idle, a very little CPU consumption
## Additional information
I faced the same issue when I used Ubuntu 18.04 on my laptop, that is why I left JAMI (my laptop's CPU is only an Intel Core i3)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/571Chatview column layout in call2022-02-19T06:22:36ZovariChatview column layout in callWhen in a call, the chatview shows as a row at the bottom of the screen.
When writing short responses, the information in the chatview quickly can't be seen unless one scrolls.
As screens are wider than taller, better use of screen rea...When in a call, the chatview shows as a row at the bottom of the screen.
When writing short responses, the information in the chatview quickly can't be seen unless one scrolls.
As screens are wider than taller, better use of screen real estate could be found by having the chatview as a column; hence, can the chatview layout please be shown as a column (or have an option to do so if the current view is required)?
Other programs have the chatview as a column and it seems to provide for a better UX.
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/109Ubuntu 21.102021-10-19T18:21:40ZovariUbuntu 21.10Does [Ubuntu 21.10](https://releases.ubuntu.com/impish/) need to be added to [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
Thank youDoes [Ubuntu 21.10](https://releases.ubuntu.com/impish/) need to be added to [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
Thank youAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/570"Accept transfer limit": value is gone if you restart Jami2021-11-04T19:40:48ZElys"Accept transfer limit": value is gone if you restart Jamiusing Jami Windows 10, 202109211812
By default the Accept transfer limit is 20 MB. You can change to value to zero if it should be unlimited.
As long as Jami is running you now have "Accept transfer limit =0".
But
As soon as you exit ...using Jami Windows 10, 202109211812
By default the Accept transfer limit is 20 MB. You can change to value to zero if it should be unlimited.
As long as Jami is running you now have "Accept transfer limit =0".
But
As soon as you exit and open Jami again. the transfer limited is 20 MB again.
Expected result:
The Accept transfer limit should stay zero - unlimitedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1328Move the docs from this repo's wiki to docs.jami.net2023-03-30T20:19:41ZAmin BandaliMove the docs from this repo's wiki to docs.jami.netAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/569Can't start two instances of Jami on one system2021-12-22T20:37:28ZvstoykovbgCan't start two instances of Jami on one systemI am trying to open two instances of Jami under different users on my Ubuntu 18 system.
I am using Jami installed via snap.
If I try to run a second instance of Jami at the same time I get these error message:
$ jami
Testing...I am trying to open two instances of Jami under different users on my Ubuntu 18 system.
I am using Jami installed via snap.
If I try to run a second instance of Jami at the same time I get these error message:
$ jami
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Qt: Session management error: Could not open network socket
"notify server name: gnome-shell, vendor: GNOME, version: 3.28.4, spec: 1.2"
Destroying connectivity monitor
Version: 202109292221
On a multi-user operating system there should not be such a problem. I do not encounter similar problem when I run browsers for example.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/568Jami forgot accounts2022-04-20T20:44:05ZvstoykovbgJami forgot accountsI starter Jami today and the accounts are gone.
I see the welcome screen instead of my accounts:
![welcome](/uploads/fbc2d7b81f0d53ecd7f05c136fe56775/welcome.png)
```
$ jami --version
Testing for explicit PulseAudio choice...
Testing ...I starter Jami today and the accounts are gone.
I see the welcome screen instead of my accounts:
![welcome](/uploads/fbc2d7b81f0d53ecd7f05c136fe56775/welcome.png)
```
$ jami --version
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Qt: Session management error: Could not open network socket
"notify server name: gnome-shell, vendor: GNOME, version: 3.28.4, spec: 1.2"
Jami 202109302149
```
I am using Ubuntu 18 with Jami installed via snap.
Maybe it's related with my experiments with running Jami as another user.
The problem appeared after reboot.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/646Video settings - disable video in account settings must be handled2022-01-17T17:13:55ZAdrien BéraudVideo settings - disable video in account settings must be handledWhen video is disabled in the account settings, video should never be used or enabled, including video mixer.When video is disabled in the account settings, video should never be used or enabled, including video mixer.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/298add support for qt-client on macOS2021-10-27T14:23:08ZKateryna Kostiukadd support for qt-client on macOSKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1017CALL: UI v.22021-11-10T15:37:59ZMaxime CalletCALL: UI v.2Preview:
![299c9d6f-5125-4988-b738-f7097a0ab964](/uploads/cd543b9c2cb4ee6266f060dc915bba44/299c9d6f-5125-4988-b738-f7097a0ab964.png)
**FEATURES:**
Must have:
- [x] bottomSheet: Implement a bottomsheet with 3 states (collapsed/half/ex...Preview:
![299c9d6f-5125-4988-b738-f7097a0ab964](/uploads/cd543b9c2cb4ee6266f060dc915bba44/299c9d6f-5125-4988-b738-f7097a0ab964.png)
**FEATURES:**
Must have:
- [x] bottomSheet: Implement a bottomsheet with 3 states (collapsed/half/extended)
- [x] bottomSheet: size scaling based on display size/density
- [x] bottomSheet: Implement the new ui logic for conference participants
- [x] UI: Handle Insets for system elements (navigation bar / status bar)
- [x] UI: Reduce size of preview
- [x] UI: Implement new android API for fullscreen
Good to have:
_if not ready will be part of an update later_
- [ ] bottomSheet: Implement the new ui logic for plugins
- [ ] Fix screen sharing issuesMaxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/645SDP - Set media direction attribute (a=sendrecv/sendonly/...) according to me...2021-12-17T16:26:12ZAdrien BéraudSDP - Set media direction attribute (a=sendrecv/sendonly/...) according to media stateThe media direction attribute in the SDP should be set according to actual state of the media.The media direction attribute in the SDP should be set according to actual state of the media.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/644audio call: could not unpause audio only call2022-03-10T18:19:36ZKateryna Kostiukaudio call: could not unpause audio only callthe scenario on iOS:
- start audio-only call
- pause call
- unpause. The call stays in the paused state.
the scenario on the desktop client:
- start audio-only call
- start another audio-only call. The first call will be paused.
-...the scenario on iOS:
- start audio-only call
- pause call
- unpause. The call stays in the paused state.
the scenario on the desktop client:
- start audio-only call
- start another audio-only call. The first call will be paused.
- stop the second call, the first call stays in the paused state.
When a call is paused an exception is thrown: "Exception running job: Stream index is out-of-range"Kateryna KostiukMohamed ChibaniKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/297Unable to send DTMF2023-05-05T19:44:02ZruivappsUnable to send DTMFOS: MacOS 11.6
Jami: Version 2.06 (2021100122)
Jami is set to use the Profile without username, password, sip server, proxy or voice mail.
on the "Advanced" setting
* Published Address was set with customer address (local IP) and por...OS: MacOS 11.6
Jami: Version 2.06 (2021100122)
Jami is set to use the Profile without username, password, sip server, proxy or voice mail.
on the "Advanced" setting
* Published Address was set with customer address (local IP) and port (5060)
* Audio codecs only has opus enabled
* video codecs disabled
* UPnP off, TURN off
try to make the call with the format: +123456789@target_server_ip, both SIP and RTP works without any issue.
When trying to send some DTMF via keyboard, didn't see any DTMF event on wireshark capture. (sip/rtp shows correctly). Do not see any "keypad" UI that allows user to "click" DTMF.
the invite (SDP) shows DTMF is supported
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/643SIPCall/PJSIP - Deadlock between main thread and MultiplexedSocket thread2022-07-22T15:26:12ZMohamed ChibaniSIPCall/PJSIP - Deadlock between main thread and MultiplexedSocket threadA deadlock may occur the main thread (or any thread that calls the Call/SIPCall methods that try to access an existing invite session) and the MultiplexedSocket (event loop) thread. The deadlock involves callMutex_ and pjsip_dialog group...A deadlock may occur the main thread (or any thread that calls the Call/SIPCall methods that try to access an existing invite session) and the MultiplexedSocket (event loop) thread. The deadlock involves callMutex_ and pjsip_dialog group lock. See bt in the comment.BacklogMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1327ArchLinux snap not starting (2022-02-23T04:12:46Ztr37ionArchLinux snap not starting (Tryig to run the latest Jami beta version on Arch via snapd seem not to work. I get the following error:
```
$ snap run jami
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Gt...Tryig to run the latest Jami beta version on Arch via snapd seem not to work. I get the following error:
```
$ snap run jami
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Gtk-Message: 16:17:25.496: Failed to load module "colorreload-gtk-module"
Gtk-Message: 16:17:25.496: Failed to load module "window-decorations-gtk-module"
(jami-qt:85803): dbind-WARNING **: 16:17:25.498: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-71TA93pJS9: No such file or directory
(jami-qt:85803): libnotify-WARNING **: 16:18:15.694: Failed to connect to proxy
```
I installed the snap edge channel version yesterday:
```
$ sudo snap install jami --channel=edge
$ snap list
Name Version Rev Tracking Publisher Notes
bare 1.0 5 latest/stable canonical✓ base
core18 20210722 2128 latest/stable canonical✓ base
gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓ -
gtk-common-themes 0.1-59-g7bca6ae 1519 latest/stable canonical✓ -
jami 20210930.1.835f5ae 214 latest/edge sfljami -
snapd 2.52 13270 latest/stable canonical✓ snapd
```
Any ideas how to fix this?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/567client not connecting fast enough with daemon2023-06-05T15:14:30ZJavierclient not connecting fast enough with daemonHi, I've experienced on gnu+linux (artix) that one can't really use jami without having to pause. It seems the client and the daemon it starts lose connection, and to reestablish it, the jami client stops and attempts the connection, an...Hi, I've experienced on gnu+linux (artix) that one can't really use jami without having to pause. It seems the client and the daemon it starts lose connection, and to reestablish it, the jami client stops and attempts the connection, and then comes back, but the time spent connecting back to its daemon, is often way high (minutes some times), or high enough (seconds) for the user to feel it like really slow...
![image](/uploads/1905bc1f8b7a725faa5bbb35701a2726/image.png)
Just in case, I'm using artix gnu+linux, with jami-daemon, libjamiclient and jami-client-qt built and install from their respective AUR packages, which grab the sources from github, top of head.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/148crash when video conference started2021-10-29T12:40:29ZKateryna Kostiukcrash when video conference startedWhen the video conference started and the first frame for the conference arrived app crashed. Happens when iOS is host or participant.When the video conference started and the first frame for the conference arrived app crashed. Happens when iOS is host or participant.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/642Video scaler : crash when answering to a new participant2022-03-10T18:17:08ZMaxime CalletVideo scaler : crash when answering to a new participantHow to reproduce
Answer to a new participant, then the tablet will crashHow to reproduce
Answer to a new participant, then the tablet will crashhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/641Crash - sigsev when starting a new call2022-03-10T18:17:13ZMaxime CalletCrash - sigsev when starting a new call**How to reproduce **
Answer a call with the galaxy tab s2 (Android 7.0)**How to reproduce **
Answer a call with the galaxy tab s2 (Android 7.0)