savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-02-17T22:13:34Zhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/456swarm: [to check]old conversation compatibility2021-02-17T22:13:34ZKateryna Kostiukswarm: [to check]old conversation compatibilitywhen continue not swarm conversation next features are broken:
- message status
- calls messages
- file transferwhen continue not swarm conversation next features are broken:
- message status
- calls messages
- file transferSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/410android: rotation doesn't work the first time2021-02-19T23:09:24ZSébastien Blinandroid: rotation doesn't work the first timeWhen a video call is made from an Android phone, the orientation of the video sent by the Android phone is not properly set at the receiver side. This typically happens after a media restart of the receiver (after a hold/resume for examp...When a video call is made from an Android phone, the orientation of the video sent by the Android phone is not properly set at the receiver side. This typically happens after a media restart of the receiver (after a hold/resume for example).
One possible scenario to reproduce:
- Make a call (A) from an Android phone to a desktop computer
- Rotate the Android phone such that the orientation angle is other than "0". Note that the physical orientation (portrait/landscape) matching angle "0" depends on the device type. You can check the rotation in the logs.
- On the desktop, make another video call: this would put the call A on-hold
- Get back to call A.
**Current behavior:** the video orientation might be lost
**Expected:** the video should be correct (the one used before the hold)Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/409Continuous participant info payloads sent between connected conference hosts2021-03-08T15:17:41ZAndreas TraczykContinuous participant info payloads sent between connected conference hostsStart a conference with someone in a conference and you should see something like:
```
...
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
New conference layout rece...Start a conference with someone in a conference and you should see something like:
```
...
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
New conference layout received for call "3944008630436379"
...
```Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/408Jami not longer installable in Debian testing/bullseye2021-01-29T18:23:20ZJürgen LütersJami not longer installable in Debian testing/bullseyeHi,
I will let you know, that jami is not longer installable in debian testing.
apt-get install jami
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed....Hi,
I will let you know, that jami is not longer installable in debian testing.
apt-get install jami
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jami : Depends: libappindicator3-1 (>= 0.4.90) but it is not installable
Depends: jami-daemon (= 20210125.1.8b9138c~dfsg1-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@nuc:~# apt-get install libappindicator3-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libappindicator3-1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libappindicator3-1' has no installation candidate
root@nuc:~#
root@nuc:~# apt-get install jami-daemon
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jami-daemon : Depends: libjsoncpp1 (>= 1.7.4) but it is not installable
E: Unable to correct problems, you have held broken packages.
root@nuc:~#https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/407basic_ios::clear: iostream error every 493 seconds2021-03-19T17:46:44ZJürgen Lütersbasic_ios::clear: iostream error every 493 secondsHi, happy new Year.
I have just noticed that jami and dring are producing the following write errors, which are occuring in a regular interval. 8 minutes and 13 seconds or 493 seconds.
uname -a:
5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2...Hi, happy new Year.
I have just noticed that jami and dring are producing the following write errors, which are occuring in a regular interval. 8 minutes and 13 seconds or 493 seconds.
uname -a:
5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17) x86_64 GNU/Linux
Jami Version : "Together" 2021-01-04 18:01:04 UTC
Jan 12 00:26:54 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:26:54 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:35:07 nuc dring: [Account ] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:35:07 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:35:07 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:43:20 nuc dring: [Account xxx] Couldn't save messages to /home/xx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:43:20 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:43:20 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc dring: [Account xxxx] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:51:33 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:59:46 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:59:46 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:59:46 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:07:59 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:07:59 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:07:59 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:16:12 nuc dring: [Account xx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:16:12 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:16:12 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc dring: Keep alive registration callback for account 6eec02b60ae98264
Jan 12 00:51:33 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 00:51:33 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:51:33 nuc dring: Creating transport
Jan 12 00:51:33 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 00:59:46 nuc dring: Keep alive registration callback for account xxx
Jan 12 00:59:46 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 00:59:46 nuc dring: [Account xxx] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:59:46 nuc dring: Creating transport
Jan 12 00:59:46 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 01:07:59 nuc dring: Keep alive registration callback for account xxx
Jan 12 01:07:59 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 01:07:59 nuc dring: [Account ] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:07:59 nuc dring: Creating transport
Jan 12 01:07:59 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 01:16:12 nuc dring: Keep alive registration callback for account 6eec02b60ae98264
Jan 12 01:16:12 nuc dring: [Account ] SIP port changed to 5060: reregistering SIP account
Jan 12 01:16:12 nuc dring: [Account ] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:16:12 nuc dring: Creating transport
Jan 12 01:16:12 nuc dring: Recycling transport 0.0.0.0:5060https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/270use new design for conference layout2021-02-04T13:52:31ZKateryna Kostiukuse new design for conference layoutIteration 27Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/272GNU/Linux: inhibit screen saver while in a call2021-02-15T15:22:45ZSébastien BlinGNU/Linux: inhibit screen saver while in a call# Scenario
+ Do a call
+ Stay X minutes while the screensaver come
# Expected
Because we are in a call, the screen should stay on
# Current
The screensaver is coming
https://stackoverflow.com/questions/31498114/how-to-programmatica...# Scenario
+ Do a call
+ Stay X minutes while the screensaver come
# Expected
Because we are in a call, the screen should stay on
# Current
The screensaver is coming
https://stackoverflow.com/questions/31498114/how-to-programmatically-prevent-linux-computer-from-sleeping-or-turning-on-screeAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/271High CPU consuption when Jami window is open2021-07-16T19:41:33ZCyrille BéraudHigh CPU consuption when Jami window is openWhen the Jami window is opened on Windows, the CPU usage is observed to be around 5-7% at all time on a modern CPU.
When the window is closed (Jami in the systray), the CPU consumption drops to 0%. It goes back to 5-7% when the Jami win...When the Jami window is opened on Windows, the CPU usage is observed to be around 5-7% at all time on a modern CPU.
When the window is closed (Jami in the systray), the CPU consumption drops to 0%. It goes back to 5-7% when the Jami window is opened again.Ming Rui ZhangAndreas TraczykMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/270Swarm: [TO TEST Seb]Can't add SIP contacts anymore2021-02-22T21:09:34ZSébastien BlinSwarm: [TO TEST Seb]Can't add SIP contacts anymoreSwarm-chatKateryna KostiukAlbert Babí OllerKateryna Kostiuk2021-03-03https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/406SIP: cannot call zoom room anymore2021-02-02T21:25:43ZSébastien BlinSIP: cannot call zoom room anymoreRegression from https://review.jami.net/c/ring-daemon/+/16369
# Scenario
+ Call contact with @ip inside
# Current result
+ Call fails immediately
# Expected
Call must workRegression from https://review.jami.net/c/ring-daemon/+/16369
# Scenario
+ Call contact with @ip inside
# Current result
+ Call fails immediately
# Expected
Call must workhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1245Lazy-loading of smartview2021-05-13T18:47:33ZSébastien BlinLazy-loading of smartviewrender_contact_photo & set_tree_model should be async as it takes quite some times when a lot of contacts are there
cf https://blogs.gnome.org/ebassi/documentation/lazy-loading/comment-page-1/render_contact_photo & set_tree_model should be async as it takes quite some times when a lot of contacts are there
cf https://blogs.gnome.org/ebassi/documentation/lazy-loading/comment-page-1/https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/269A frame from previous call is shown when starting a new call2021-04-07T19:48:34ZPierre LespagnolA frame from previous call is shown when starting a new callSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/269add more actions to conference management2021-02-04T13:52:29ZKateryna Kostiukadd more actions to conference managementAdd next actions:
- mute participant
- stop participant call
- set moderatorAdd next actions:
- mute participant
- stop participant call
- set moderatorIteration 27Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1171[Feature request] Choose definition and quality before sending pictures2021-01-22T10:12:09ZChristophe Laurent[Feature request] Choose definition and quality before sending picturesSometimes it is not necessary to send à large definition and max quality pic, could be interetsing to choose before sending it.Sometimes it is not necessary to send à large definition and max quality pic, could be interetsing to choose before sending it.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/405Swarm: add displayName/size/hash to application/data-transfer+json2021-01-27T16:04:32ZSébastien BlinSwarm: add displayName/size/hash to application/data-transfer+json+ add displayName/size/hash to application/data-transfer+json
+ update doc+ add displayName/size/hash to application/data-transfer+json
+ update docIteration 27Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/404Plugins: can't enable video plugin when hosting a conference2021-03-19T17:44:08ZSébastien BlinPlugins: can't enable video plugin when hosting a conference# Scenario
+ Start a video conference
+ Enable greenscreen
# Current result
+ Greenscreen don't start
# Expected
+ GreenScreen should be started# Scenario
+ Start a video conference
+ Enable greenscreen
# Current result
+ Greenscreen don't start
# Expected
+ GreenScreen should be startedAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/268Packaging: evaluate downgrade of minimum qt version (linux)2021-02-16T18:39:21ZAlbert Babí OllerPackaging: evaluate downgrade of minimum qt version (linux)Albert Babí OllerMing Rui ZhangAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/403ASAN crash in enterConference2021-02-15T20:05:59ZSébastien BlinASAN crash in enterConference```
Thread 2 "dring" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff24ff640 (LWP 229429)]
0x00007ffff76160c7 in __asan::QuickCheckForUnpoisonedRegion(unsigned long, unsigned long) () from /lib64/libasan.so.6
(gd...```
Thread 2 "dring" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff24ff640 (LWP 229429)]
0x00007ffff76160c7 in __asan::QuickCheckForUnpoisonedRegion(unsigned long, unsigned long) () from /lib64/libasan.so.6
(gdb) bt
#0 0x00007ffff76160c7 in __asan::QuickCheckForUnpoisonedRegion(unsigned long, unsigned long) () from /lib64/libasan.so.6
#1 0x00007ffff7616c74 in memcpy () from /lib64/libasan.so.6
#2 0x00007ffff6781d68 in std::basic_streambuf<char, std::char_traits<char> >::xsputn(char const*, long) () from /lib64/libstdc++.so.6
#3 0x00007ffff677467c in std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) () from /lib64/libstdc++.so.6
#4 0x000000000091041b in operator() (__closure=0x21ee0a0 <jami::video::ShmHolder::ShmHolder(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::shmFailedWithErrno>, what="shm_open") at sinkclient.cpp:125
#5 0x0000000000910bee in jami::video::ShmHolder::ShmHolder (this=0x607000202b40, name="") at sinkclient.cpp:141
#6 0x000000000091b03f in __gnu_cxx::new_allocator<jami::video::ShmHolder>::construct<jami::video::ShmHolder> (this=0x7ffff24fb440, __p=0x607000202b40) at /usr/include/c++/10/ext/new_allocator.h:150
#7 0x000000000091ab89 in std::allocator_traits<std::allocator<jami::video::ShmHolder> >::construct<jami::video::ShmHolder> (__a=..., __p=0x607000202b40) at /usr/include/c++/10/bits/alloc_traits.h:512
#8 0x000000000091a450 in std::_Sp_counted_ptr_inplace<jami::video::ShmHolder, std::allocator<jami::video::ShmHolder>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<>(std::allocator<jami::video::ShmHolder>) (this=0x607000202b30, __a=...) at /usr/include/c++/10/bits/shared_ptr_base.h:551
#9 0x0000000000919aee in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<jami::video::ShmHolder, std::allocator<jami::video::ShmHolder>>(jami::video::ShmHolder*&, std::_Sp_alloc_shared_tag<std::allocator<jami::video::ShmHolder> >) (this=0x7ffff24fb6b8, __p=@0x7ffff24fb6b0: 0x0, __a=...)
at /usr/include/c++/10/bits/shared_ptr_base.h:682
#10 0x0000000000919121 in std::__shared_ptr<jami::video::ShmHolder, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<jami::video::ShmHolder>>(std::_Sp_alloc_shared_tag<std::allocator<jami::video::ShmHolder> >) (this=0x7ffff24fb6b0,
__tag=<error reading variable: Cannot access memory at address 0xffffffffffffffe5>) at /usr/include/c++/10/bits/shared_ptr_base.h:1371
#11 0x00000000009180d3 in std::shared_ptr<jami::video::ShmHolder>::shared_ptr<std::allocator<jami::video::ShmHolder>>(std::_Sp_alloc_shared_tag<std::allocator<jami::video::ShmHolder> >) (this=0x7ffff24fb6b0, __tag=<error reading variable: Cannot access memory at address 0xffffffffffffffe5>)
at /usr/include/c++/10/bits/shared_ptr.h:408
#12 0x0000000000916f3e in std::allocate_shared<jami::video::ShmHolder, std::allocator<jami::video::ShmHolder>>(std::allocator<jami::video::ShmHolder> const&) (__a=...) at /usr/include/c++/10/bits/shared_ptr.h:860
#13 0x0000000000915f57 in std::make_shared<jami::video::ShmHolder> () at /usr/include/c++/10/bits/shared_ptr.h:876
#14 0x00000000009120cb in jami::video::SinkClient::start (this=0x611000504510) at sinkclient.cpp:277
#15 0x0000000000e17e9c in jami::video::VideoMixer::start_sink (this=0x6170003e6d80) at video_mixer.cpp:451
#16 0x0000000000e17cba in jami::video::VideoMixer::setParameters (this=0x6170003e6d80, width=1280, height=720, format=AV_PIX_FMT_YUV422P) at video_mixer.cpp:436
#17 0x0000000000e2318b in jami::video::VideoRtpSession::enterConference (this=0x61c0005bf880, conference=0x61600151d790) at video_rtp_session.cpp:362
#18 0x0000000000970301 in jami::Conference::add (this=0x61600151d790, participant_id="3426407002363824") at conference.cpp:199
#19 0x00000000009b3d22 in jami::Manager::ManagerPimpl::bindCallToConference (this=0x620000000080, call=warning: RTTI symbol not found for class 'jami::CallFactory::newCall<jami::SIPCall, jami::JamiAccount>(std::shared_ptr<jami::JamiAccount>, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, jami::Call::CallType, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > const&)::ConcreteCall'
..., conf=...) at manager.cpp:677
#20 0x00000000009c2fe0 in operator() (__closure=0x6040004f5b50) at manager.cpp:1928
#21 0x00000000009d8c62 in operator() (this=0x6040004f5b50) at manager.h:974
#22 0x00000000009dde88 in std::__invoke_impl<void, jami::runOnMainThread<jami::Manager::incomingCall(jami::Call&, const string&)::<lambda()> >::<lambda()>&>(std::__invoke_other, struct {...} &) (__f=...) at /usr/include/c++/10/bits/invoke.h:60
#23 0x00000000009dd2bd in std::__invoke_r<void, jami::runOnMainThread<jami::Manager::incomingCall(jami::Call&, const string&)::<lambda()> >::<lambda()>&>(struct {...} &) (__fn=...) at /usr/include/c++/10/bits/invoke.h:110
#24 0x00000000009dc198 in std::_Function_handler<void(), jami::runOnMainThread<jami::Manager::incomingCall(jami::Call&, const string&)::<lambda()> >::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/10/bits/std_function.h:291
#25 0x0000000000575ff4 in std::function<void ()>::operator()() const (this=0x6030004b5590) at /usr/include/c++/10/bits/std_function.h:622
#26 0x0000000000abcc43 in jami::ScheduledExecutor::loop (this=0x6200000000a0) at scheduled_executor.cpp:124
#27 0x0000000000abb3b3 in operator() (__closure=0x60200002d7b8) at scheduled_executor.cpp:28
#28 0x0000000000abf390 in std::__invoke_impl<void, jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> >(std::__invoke_other, struct {...} &&) (__f=...) at /usr/include/c++/10/bits/invoke.h:60
#29 0x0000000000abf345 in std::__invoke<jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> >(struct {...} &&) (__fn=...) at /usr/include/c++/10/bits/invoke.h:95
#30 0x0000000000abf2f2 in std::thread::_Invoker<std::tuple<jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> > >::_M_invoke<0>(std::_Index_tuple<0>) (this=0x60200002d7b8) at /usr/include/c++/10/thread:264
#31 0x0000000000abf2c6 in std::thread::_Invoker<std::tuple<jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> > >::operator()(void) (this=0x60200002d7b8) at /usr/include/c++/10/thread:271
#32 0x0000000000abf2aa in std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> > > >::_M_run(void) (this=0x60200002d7b0) at /usr/include/c++/10/thread:215
#33 0x00007ffff67185f4 in execute_native_thread_routine () from /lib64/libstdc++.so.6
#34 0x00007ffff70f83f9 in start_thread () from /lib64/libpthread.so.0
#35 0x00007ffff6417903 in clone () from /lib64/libc.so.6
(gdb)
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/402Alsa: crash ASAN on master2021-04-16T14:55:23ZSébastien BlinAlsa: crash ASAN on master[crash-alsa-master.log](/uploads/aa38ced88ff74f3e61835494928419a1/crash-alsa-master.log)
The patch I did to fix this : https://review.jami.net/c/ring-daemon/+/16215[crash-alsa-master.log](/uploads/aa38ced88ff74f3e61835494928419a1/crash-alsa-master.log)
The patch I did to fix this : https://review.jami.net/c/ring-daemon/+/16215Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/401Conference: Add parameter to set everybody as a moderator2021-03-10T15:22:02ZSébastien BlinConference: Add parameter to set everybody as a moderator+ Add in dring.yml (default true)
+ Add in client-qt+ Add in dring.yml (default true)
+ Add in client-qtPierre LespagnolAlbert Babí OllerPierre Lespagnol