savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-07-02T20:31:49Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/574ice: call fail if init is too fast2021-07-02T20:31:49ZSébastien Blinice: call fail if init is too fast[xxx_2_](/uploads/c18940ceaa87fb6176a6107df61ea368/xxx_2_)[xxx_2_](/uploads/c18940ceaa87fb6176a6107df61ea368/xxx_2_)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/573conference: no rdv and videomuted host should appear2021-11-18T16:19:15ZAline Gondim Santosconference: no rdv and videomuted host should appearBackloghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/974High Battery consumption in Android2023-04-07T20:26:22ZkrishnakHigh Battery consumption in Android
Bug #737 may be related to this
A phone dedicated to Jami testing left with Jami on as background service consumes very less battery.
However when the WiFi/mobile data is switched off on the phone and if the Jami background process t...
Bug #737 may be related to this
A phone dedicated to Jami testing left with Jami on as background service consumes very less battery.
However when the WiFi/mobile data is switched off on the phone and if the Jami background process tries to Sync without checking on network adapter status-this probably occurs once a day or so.
When this sync process starts and if there is NO network connectivity, it is draining the battery like anything.
The notification bar displays Jami Syncing for ever (no way to dismiss it), the sync process doesn't appear to complete even when the Wifi adapter is turned on again.
The main issue here is that it drains battery, in 6 hours it drained around 700mAh - I gathered this information from the battery consumption chart for the apps.
The only way to recover the app to correct status is by force killing it.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1271Add Lyra voice codec (3 kbit/s)2023-09-07T19:09:51Zring userAdd Lyra voice codec (3 kbit/s)Google has announced a low bitrate speech codec, lyra, which aims to encode speech with 3 kbit/s:
https://github.com/google/lyra/
With release 0.2, it seems to be fully open source (https://github.com/google/lyra/releases/tag/v0.0.2).
M...Google has announced a low bitrate speech codec, lyra, which aims to encode speech with 3 kbit/s:
https://github.com/google/lyra/
With release 0.2, it seems to be fully open source (https://github.com/google/lyra/releases/tag/v0.0.2).
Maybe it could be implemented int Jami to save bandwith and prevent connection issues with voice only calls?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/973Question: Frame rate of video call (Android)2021-09-30T09:58:40ZElysQuestion: Frame rate of video call (Android)Android:
What is the frame rate of a video call?
Does the frame rate depend on the video resolution or hardware?
For example 1080p HD 60fps or 720p HD 120 fps ?Android:
What is the frame rate of a video call?
Does the frame rate depend on the video resolution or hardware?
For example 1080p HD 60fps or 720p HD 120 fps ?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/972Audio choppy on Voice only call with Opus2021-10-02T07:05:21ZkrishnakAudio choppy on Voice only call with OpusI am on a 100Mbps fiber and a phone connects to the WiFi at 75Mbps, I have another fiber connection to the same ISP same 100Mbps link and a different phone connects to WiFi on that network as well at 75Mbps. Ping between the two networks...I am on a 100Mbps fiber and a phone connects to the WiFi at 75Mbps, I have another fiber connection to the same ISP same 100Mbps link and a different phone connects to WiFi on that network as well at 75Mbps. Ping between the two networks going via the ISP is <5ms
Using Android if I use Jami for audio call with Opus codec - the audio is choppy (metallic cracking sound in the middle of the conversation). Can you let me know what is the codec's sampling rate, is it 48K? Also the call volume is low when using this Codec. If all the codec's are enabled how does the software determine which codec to use?
I found that using Speex 8000 the audio is not choppy and the call volume is equal to normal mobile/landline calls.Even though it is narrow band - it gives the best experience.
I wonder whether the phone hardware is at fault with the opus codec considering that there is plenty of bandwidth or is it something else?
One phone is an Octa core running at 1.4GHz @ Android 7.1.2
Another is a much more newer hardware Octa-core (4x2.0 GHz Cortex-A55 & 4x2.0 GHz Cortex-A55) running Android 11https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/463Compile error: unable to deduce ‘auto*’2021-07-05T19:13:14ZJamesCompile error: unable to deduce ‘auto*’gcc --version
gcc (Gentoo 10.3.0 p1) 10.3.0
[ 67%] Building CXX object CMakeFiles/jami-qt.dir/src/rendermanager.cpp.o
[ 68%] Building CXX object CMakeFiles/jami-qt.dir/src/connectivitymonitor.cpp.o
[ 69%] Building CXX objec...gcc --version
gcc (Gentoo 10.3.0 p1) 10.3.0
[ 67%] Building CXX object CMakeFiles/jami-qt.dir/src/rendermanager.cpp.o
[ 68%] Building CXX object CMakeFiles/jami-qt.dir/src/connectivitymonitor.cpp.o
[ 69%] Building CXX object CMakeFiles/jami-qt.dir/src/mainapplication.cpp.o
[ 70%] Building CXX object CMakeFiles/jami-qt.dir/src/messagesadapter.cpp.o
[ 70%] Building CXX object CMakeFiles/jami-qt.dir/src/accountadapter.cpp.o
[ 71%] Building CXX object CMakeFiles/jami-qt.dir/src/calladapter.cpp.o
[ 72%] Building CXX object CMakeFiles/jami-qt.dir/src/conversationsadapter.cpp.o
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp: In lambda function:
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp:119:75: error: unable to deduce ‘auto*’ from ‘this->ConversationsAdapter::<anonymous>.QmlAdapterBase::lrcInstance_->LRCInstance::getAccountInfo((* & accountId)).lrc::api::account::Info::conversationModel’
119 | auto* convModel = lrcInstance_->getAccountInfo(accountId).conversationModel;
| ^~~~~~~~~~~~~~~~~
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp:119:75: note: mismatched types ‘auto*’ and ‘std::unique_ptr<lrc::api::ConversationModel>’
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp: In lambda function:
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp:128:75: error: unable to deduce ‘auto*’ from ‘this->ConversationsAdapter::<anonymous>.QmlAdapterBase::lrcInstance_->LRCInstance::getAccountInfo((* & accountId)).lrc::api::account::Info::conversationModel’
128 | auto* convModel = lrcInstance_->getAccountInfo(accountId).conversationModel;
| ^~~~~~~~~~~~~~~~~
/var/tmp/portage/net-voip/jami-client-qt-9999/work/jami-client-qt-9999/src/conversationsadapter.cpp:128:75: note: mismatched types ‘auto*’ and ‘std::unique_ptr<lrc::api::ConversationModel>’
make[2]: *** [CMakeFiles/jami-qt.dir/build.make:610: CMakeFiles/jami-qt.dir/src/conversationsadapter.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:181: CMakeFiles/jami-qt.dir/all] Error 2
make: *** [Makefile:149: all] Error 2https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/572Outgoing SIP calls drop after 32s2021-11-26T15:15:26ZDavid LecompteOutgoing SIP calls drop after 32sI am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:4...I am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:43:25 UTC . The network connection is via ethernet, my ISP is SFR in Paris France, fiber connection.
The attached log was obtained with
/usr/lib/ring/dring -d -c 2>&1 | tee dring5.log
The image is a screen capture taken immediately after the call drop (less than 1s after) in order to show what was visible in the log. The big seqence of consecutive "underrun occured" was during the call but it paused more than 10s before the call drop.
[dring5.log](/uploads/648d1b648fb16fc641573235420d2b37/dring5.log)
![right_after_drop](/uploads/6f53ee76e0969c94a429aac2589da7e8/right_after_drop.png)Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1270sip calls always drop after 32 seconds2021-06-25T20:25:42Zblerp deprsip calls always drop after 32 secondsI am using the latest version of jami on debian 10 linux. This error is not present on other SIP clients, I can make calls fine with linphone. This error also occurs regardless of what number I call to or from.
The call itself starts f...I am using the latest version of jami on debian 10 linux. This error is not present on other SIP clients, I can make calls fine with linphone. This error also occurs regardless of what number I call to or from.
The call itself starts fine, can chat with no issues, and the logs look normal, but after 32 seconds errors crop up in the logs and the call disconnects. The relenvet logs seem to be (with any unique numbers that I don't know about edited in case they break privacy)
```
[INVITE:"NUMBERS"] RX SIP method 5 (OPTIONS)
Processing in-dialog option request
Sent in-dialog response for option request
INVITE@NUMBERS state changed to 6 (DISCONNCTD): cause=408, tsx@NUMBERS status 408 (Request Timeout)
state change 1/5, cnx 4/0, code 408
emit client call state change FAILURE, code 408
Delete current invite session
Parent call failed
```https://git.jami.net/savoirfairelinux/jami-project/-/issues/1269Add a Jami icon on the Font Awesome website2021-07-16T18:19:31ZManoel NascimentoAdd a Jami icon on the Font Awesome websiteHi, I was building my own website and noticed that there is no Jami icon on the Font Awesome site. It would be nice to have it, as a simplified version of the Jami icon in SVG format (such as the one that appears in Android's top-of-scre...Hi, I was building my own website and noticed that there is no Jami icon on the Font Awesome site. It would be nice to have it, as a simplified version of the Jami icon in SVG format (such as the one that appears in Android's top-of-screen notifications, for example) could have many uses in visual design. If for some reason this is not in the developers' plans, a simplified SVG icon could be made available somewhere by Savoir Faire Linux for web designers to have an "official" version of this icon. Thanks!https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/971Incorrect contact status2023-06-01T14:37:39ZkrishnakIncorrect contact statusThis is on Android 7.1.2 and happens on other devices running Android 10 and 11 as well.
I have reopened this issue separately for clarity - this incorrect status is an Android UI issue, when the WiFi is switched off, the contacts cont...This is on Android 7.1.2 and happens on other devices running Android 10 and 11 as well.
I have reopened this issue separately for clarity - this incorrect status is an Android UI issue, when the WiFi is switched off, the contacts continues to appear ONLINE. Some service which is supposed to update the UI doesn't seem to update the UI. I tried looking in to the Android code, I am not able to easily find where the Green Circle is redrawn -
I tracked it up to here which goes to the [Native Code](https://github.com/savoirfairelinux/ring-client-android/blob/56cd3fa1175b69dceda88db31bf6fbafeac7e667/ring-android/libringclient/src/main/java/net/jami/services/AccountService.java#L777)
Can you let me know how the UI gets updated and point me to the Java code, so that I can debug and fix it if possible.
![IMG_20210624_203118](/uploads/2c856d6e2d1a5573229ac241efb366c5/IMG_20210624_203118.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/970Contact color doesn't update2022-08-14T20:12:11ZkrishnakContact color doesn't update![IMG_20210623_204318_1_](/uploads/fd1858b413cba64f19f33045080f8818/IMG_20210623_204318_1_.jpg)
When the contact color is changed by clicking on the (color palette) - the color of the text messages change, however the contact is still i...![IMG_20210623_204318_1_](/uploads/fd1858b413cba64f19f33045080f8818/IMG_20210623_204318_1_.jpg)
When the contact color is changed by clicking on the (color palette) - the color of the text messages change, however the contact is still in the old color (yellow)https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/478Video Split: create participantsmodel per call2022-09-26T17:35:44ZAline Gondim SantosVideo Split: create participantsmodel per callBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/571SIP Account - use account setting to enable/disable SRTP2021-09-02T15:12:32ZMohamed ChibaniSIP Account - use account setting to enable/disable SRTPMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/294Conference: add participants split2021-12-29T17:14:06ZAline Gondim SantosConference: add participants splitBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/462incoming call: set buttons order as "Refuse", "Audio Accept", "Camera accept"2021-06-22T20:19:00ZAline Gondim Santosincoming call: set buttons order as "Refuse", "Audio Accept", "Camera accept"Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/570Crash in PJSIP on SDP negotiation failure2021-07-21T18:13:20ZAdrien BéraudCrash in PJSIP on SDP negotiation failureThe crash happens if the SDP negotiation fail. The crash can be reproduced by answering to an incoming call with all media disabled. There is a test case (peer_disable_media) in the unit test sip_base_calls.cpp that reproduces the crash....The crash happens if the SDP negotiation fail. The crash can be reproduced by answering to an incoming call with all media disabled. There is a test case (peer_disable_media) in the unit test sip_base_calls.cpp that reproduces the crash.
[crash_pjsip.txt](/uploads/5267262ca4283ff78c6626c4b00c7845/crash_pjsip.txt)Olivier DionOlivier Dionhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/569Crash in jamiaccount cacheSIPConnection2021-06-22T16:27:35ZSébastien BlinCrash in jamiaccount cacheSIPConnection```
1623963179.676|45271|tls_session.cpp :1529 ] [TLS] shutdown
[LWP 176344 exited]
[LWP 176343 exited]
--Type <RET> for more, q to quit, c to continue without paging--
Thread 28 "dring" received signal SIGSEGV, Segmentation fault.
[S...```
1623963179.676|45271|tls_session.cpp :1529 ] [TLS] shutdown
[LWP 176344 exited]
[LWP 176343 exited]
--Type <RET> for more, q to quit, c to continue without paging--
Thread 28 "dring" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 169557]
0x0000555555837095 in std::weak_ptr<jami::SIPAccountBase, (gnu_cxx::_Lock_policy)2>::operator=<jami::SIPAccountBase> (this=0x78, r=...)
at /usr/include/c++/10/bits/shared_ptr_base.h:1690
1690 Mptr = r.Mptr;
(gdb) bt
#0 0x0000555555837095 in std::weak_ptr<jami::SIPAccountBase, (gnu_cxx::_Lock_policy)2>::operator=<jami::SIPAccountBase> (this=0x78, __r=...)
at /usr/include/c++/10/bits/shared_ptr_base.h:1690
#1 0x00005555558256ef in std::weak_ptr<jami::SIPAccountBase>::operator=<jami::SIPAccountBase> (this=0x78, __r=...) at /usr/include/c++/10/bits/shared_ptr.h:732
#2 0x000055555581c1d3 in jami::SipTransport::setAccount (this=0x0, account=...) at /home/cyrille/ring-daemon/src/sip/siptransport.h:118
#3 0x00005555557e2f1f in jami::JamiAccount::cacheSIPConnection (this=0x7fffd0000b70, socket=..., peerId=..., deviceId=...) at jamiaccount.cpp:4798
#4 0x00005555557cc9ca in operator() (__closure=0x7fffe40949c0, deviceId=..., name=..., channel=...) at jamiaccount.cpp:2361
#5 0x0000555555809bcd in std::invoke_impl<void, jami::JamiAccount::doRegister_()::<lambda(const DeviceId&, const string&, std::shared_ptr<jami::ChannelSocket>)>&, const dht::Hash<20>&, const std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, std::shared_ptr<jami::ChannelSocket> >(std::invoke_other, struct {...} &)
(f=...) at /usr/include/c++/10/bits/invoke.h:60
#6 0x00005555557fee94 in std::invoke_r<void, jami::JamiAccount::doRegister_()::<lambda(const DeviceId&, const string&, std::shared_ptr<jami::ChannelSocket>)>&, const dht::Hash<20>&, const std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, std::shared_ptr<jami::ChannelSocket> >(struct {...} &) (__fn=...)
at /usr/include/c++/10/bits/invoke.h:110
#7 0x00005555557f6029 in std::Function_handler<void(const dht::Hash<20>&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, std::shared_ptr<jami::ChannelSocket>), jami::JamiAccount::doRegister()::<lambda(const DeviceId&, const string&, std::shared_ptr<jami::ChannelSocket>)> >::Minvoke(const std::_Any_data &, const dht::Hash<20> &, const std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > &, std::shared_ptr<jami::ChannelSocket> &&) (functor=...,
args#0=..., args#1=..., __args#2=...) at /usr/include/c++/10/bits/std_function.h:291
#8 0x0000555555c42740 in std::function<void (dht::Hash<20ul> const&, std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::shared_ptr<jami::ChannelSocket>)>::operator()(dht::Hash<20ul> const&, std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::shared_ptr<jami::ChannelSocket>) const (this=0x7fffe40949c0, args#0=..., args#1=..., __args#2=...) at /usr/include/c++/10/bits/std_function.h:622
#9 0x0000555555c323da in operator() (__closure=0x7fff78114830, deviceId=..., socket=...) at connectionmanager.cpp:936
#10 0x0000555555c3c8f9 in std::invoke_impl<void, jami::ConnectionManager::Impl::addNewMultiplexedSocket(const DeviceId&, const Id&)::<lambda(const DeviceId&, const std::shared_ptr<jami::ChannelSocket>&)>&, const dht::Hash<20>&, const std::shared_ptr<jami::ChannelSocket>&>(std::invoke_other, struct {...} &) (__f=...)
at /usr/include/c++/10/bits/invoke.h:60
#11 0x0000555555c39b97 in std::invoke_r<void, jami::ConnectionManager::Impl::addNewMultiplexedSocket(const DeviceId&, const Id&)::<lambda(const DeviceId&, const std::shared_ptr<jami::ChannelSocket>&)>&, const dht::Hash<20>&, const std::shared_ptr<jami::ChannelSocket>&>(struct {...} &) (fn=...) at /usr/include/c++/10/bits/invoke.h:110
#12 0x0000555555c37184 in std::_Function_handler<void(const dht::Hash<20>&, const std::shared_ptr<jami::ChannelSocket>&), jami::ConnectionManager::Impl::addNewMultiplexedSocket(const DeviceId&, const Id&)::<lambda(const DeviceId&, const std::shared_ptr<jami::ChannelSocket>&)> >::Minvoke(const std::_Any_data &, const dht::Hash<20> &, const std::shared_ptr<jami::ChannelSocket> &) (functor=..., args#0=..., __args#1=...) at /usr/include/c++/10/bits/std_function.h:291
#13 0x00005555558d057f in std::function<void (dht::Hash<20ul> const&, std::shared_ptr<jami::ChannelSocket> const&)>::operator()(dht::Hash<20ul> const&, std::shared_ptr<jami::ChannelSocket> const&) const (this=0x7fff78122df0, args#0=..., args#1=...) at /usr/include/c++/10/bits/std_function.h:622
#14 0x00005555558c648d in jami::MultiplexedSocket::Impl::onRequest (this=0x7fff78122ce0, name=..., channel=44561) at multiplexed_socket.cpp:404
#15 0x00005555558c69e5 in operator() (__closure=0x7fff5805a840) at multiplexed_socket.cpp:444
--Type <RET> for more, q to quit, c to continue without paging--
#16 0x00005555558cbe72 in std::invoke_impl<void, jami::MultiplexedSocket::Impl::handleControlPacket(std::vector<unsigned char>&&)::<lambda()>&>(std::invoke_other, struct {...} &) (__f=...) at /usr/include/c++/10/bits/invoke.h:60
#17 0x00005555558cb80b in std::invoke_r<void, jami::MultiplexedSocket::Impl::handleControlPacket(std::vector<unsigned char>&&)::<lambda()>&>(struct {...} &) (fn=...)
at /usr/include/c++/10/bits/invoke.h:110
#18 0x00005555558caf93 in std::_Function_handler<void(), jami::MultiplexedSocket::Impl::handleControlPacket(std::vector<unsigned char>&&)::<lambda()> >::Minvoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/10/bits/std_function.h:291
#19 0x0000555555d910bd in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dht::ThreadPool::run(std::function<void ()>&&)::{lambda()#1}> > >::Mrun() ()
#20 0x00007ffff6e2cd84 in ?? ()
#21 0x0000000000000000 in ?? ()
(gdb)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/568Crash in conversationRepository2021-11-12T18:33:16ZSébastien BlinCrash in conversationRepository```
[1624127455.501|10853|jamiaccount.cpp :3833 ] Something went wrong when cloning conversation: Couldn't clone repository
[1624127455.506|15742|sip_utils.cpp :278 ] Registered thread 0x7ffe2f7fe428 (0x2A33)
[1624127455.510|10978...```
[1624127455.501|10853|jamiaccount.cpp :3833 ] Something went wrong when cloning conversation: Couldn't clone repository
[1624127455.506|15742|sip_utils.cpp :278 ] Registered thread 0x7ffe2f7fe428 (0x2A33)
[1624127455.510|10978|conversationrepository.cpp:1890 ] Start clone in /home/cyrille/.local/share/jami/fb33489037813e47/conversations/1bbe92a272e1207d6f1f37069bf3486110e7c166
--Type <RET> for more, q to quit, c to continue without paging--
Thread 1 "dring" received signal SIGSEGV, Segmentation fault.
0x0000555555feb844 in git_repository_workdir ()
(gdb) bt
#0 0x0000555555feb844 in git_repository_workdir ()
#1 0x0000555555ca350d in jami::ConversationRepository::infosabi:cxx11 const (this=0x7ffef801ae80) at conversationrepository.cpp:2972
#2 0x0000555555c7a0fb in jami::Conversation::infosabi:cxx11 const (
this=0x7fff640285d0) at conversation.cpp:943
#3 0x00005555557ef2f4 in jami::JamiAccount::conversationInfos (
this=0x7fffd0000b70,
conversationId="1bbe92a272e1207d6f1f37069bf3486110e7c166")
at jamiaccount.cpp:3987
#4 0x0000555555767dfa in DRing::conversationInfos (
accountId="fb33489037813e47",
conversationId="1bbe92a272e1207d6f1f37069bf3486110e7c166")
at conversation_interface.cpp:96
#5 0x000055555571ea62 in DBusConfigurationManager::conversationInfos(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&) ()
#6 0x0000555555731898 in cx::ring::Ring::ConfigurationManager_adaptor::_conversationInfos_stub(DBus::CallMessage const&) ()
#7 0x0000555555738172 in DBus::Callback<cx::ring::Ring::ConfigurationManager_adaptor, DBus::Message, DBus::CallMessage const&>::call(DBus::CallMessage const&) const ()
--Type <RET> for more, q to quit, c to continue without paging--
age const&) ()
#9 0x000055555574699a in DBus::ObjectAdaptor::handle_message(DBus::Message const&) ()
#10 0x0000555555743f06 in DBus::ObjectAdaptor::Private::message_function_stub(DBusConnection, DBusMessage, void*) ()
#11 0x00007ffff7f78270 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#12 0x00007ffff7f67f54 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#13 0x00005555557394b0 in DBus::Connection::Private::do_dispatch() ()
#14 0x000055555573b6d2 in DBus::Dispatcher::dispatch_pending(std::__cxx11::list<DBus::Connection::Private, std::allocator<DBus::Connection::Private> >&) ()
#15 0x000055555573b7cf in DBus::Dispatcher::dispatch_pending() ()
#16 0x000055555573cd2f in DBus::BusDispatcher::enter() ()
#17 0x00005555556ad40e in DBusClient::event_loop() ()
#18 0x00005555556a59b8 in main ()
(gdb)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1268Android - error when build iconv lib2021-07-16T20:02:50ZTan2NTAndroid - error when build iconv libhi, I face this error when build client-android
`libtool: link: rm -fr .libs/libiconv.a .libs/libiconv.la .libs/libiconv.lai
libtool: link: ar cru .libs/libiconv.a objects/iconv.o objects/localcharset.o objects/relocatable.o
ar: u mod...hi, I face this error when build client-android
`libtool: link: rm -fr .libs/libiconv.a .libs/libiconv.la .libs/libiconv.lai
libtool: link: ar cru .libs/libiconv.a objects/iconv.o objects/localcharset.o objects/relocatable.o
ar: u modifier ignored since D is the default (see U)
libtool: link: /home/tan111/devtools/android-ndk-r21e/toolchains/llvm/prebuilt/linux-x86_64/bin/llvm-ranlib .libs/libiconv.a
libtool: link: ( cd ".libs" && rm -f "libiconv.la" && ln -s "../libiconv.la" "libiconv.la" )
cp .libs/libiconv.so preloadable_libiconv.so
cp: cannot stat .libs/libiconv.so': No such file or directory
make[2]: *** [Makefile:52: preloadable_libiconv.so] Error 1
make[2]: Leaving directory /home/tan111/jami/ring-project/daemon/contrib/native-aarch64-linux-android/iconv/preload
make[1]: *** [Makefile:49: install] Error 2
make[1]: Leaving directory /home/tan111/jami/ring-project/daemon/contrib/native-aarch64-linux-android/iconv
make: *** [/home/tan111/jami/ring-project/daemon/contrib/src/iconv/rules.mak:41: .iconv] Error 2`
Does anyone facing it before? Please help me
Thank a lot!