savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-08-20T21:09:03Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/614No option to resend pictures on Android2021-08-20T21:09:03Zring userNo option to resend pictures on Android- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build ...- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build you are using: F-Droid to Manjaro/Arch build
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Requirements: Two accounts, one on Linux, one on Android, are already connected
2. Open the conversation on Android
3. Send a picture while Linux is offline
4. Wait. You will get the error message "Unjoinable peer" below the picture
5. Switching Linux online
6. Wait
7. Picture is not resend automatically
8. Try to resend manually (Click on picture, long click on picture to open menu etc.
- Actual result:
1. No option for resending available on Android (Linux has such an option in a poorly noticeable three-point-menu beside a not send picture)
- Expected result:
2. Automatically retry when other peer is online or at least an easy accessable option for retrying for Android. IMHO best solution would be a resend/retry-button directly below the picture.Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/396Could not re-add deleted contact from invites2021-08-20T21:04:36ZMing Rui ZhangCould not re-add deleted contact from invitesBacklogMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/908Jami protocols, please2021-08-20T21:03:43ZZulJami protocols, pleaseI am now using Jami, but it's not perfect yet. I am not sure Jami is yet easy-use and easy-maintenance enough for me to ask some of my friends to install it, though I hope it will get there. I also, oddly, feel that it is too centralized...I am now using Jami, but it's not perfect yet. I am not sure Jami is yet easy-use and easy-maintenance enough for me to ask some of my friends to install it, though I hope it will get there. I also, oddly, feel that it is too centralized!
In order to use Jami, [I had to](https://git.jami.net/savoirfairelinux/ring-project/issues/844#note_18790) add the Savoir-faire repository, and download the latest version directly from there. All my friends will have to do the same to keep their versions in sync.
In some ways, this is more centralized than Mumble, which is not peer-to-peer, but has [multiple third-party applications](https://wiki.mumble.info/wiki/3rd_Party_Applications) for both server and client *(Mumble also has [no end-to-end encryption](https://github.com/mumble-voip/mumble/issues/1813); the server operator is a de-facto party to all group calls, so you have to run your own server)*.
A Jami protocol would fix, allowing different versions and implementations to interoperate. It's hard to write a protocol without first writing a prototype implementation. I very much hope that Jami will, like Mediagoblin, eventually spawn a protocol.
Then Jami will be like a peer-to-peer Mumble; we can use different versions, and if a Jami becomes not quite what we want we can seamlessly switch to another program, keeping our contact list and histories. Free as in freedom.
A protocol just for account data storage/import/export would be a good first step; a protocol for the actual messages could come later.https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/275swarm: 1:1 beta2021-08-20T21:01:36ZKateryna Kostiukswarm: 1:1 betaSwarm-chatKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/946Resend2021-08-20T20:56:30ZShawn DunResendInvitation keeps being resentInvitation keeps being resenthttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/316The client seems extremely slow in conference2021-08-20T20:56:23ZPierre LespagnolThe client seems extremely slow in conferenceReproducible on linux platform, sometimes during a conference the client become extremely slow: participant overlay, hangup/muteAudio/muteVideo buttons take extra time to be shown.
Restart the client (not the daemon) fix the problemReproducible on linux platform, sometimes during a conference the client become extremely slow: participant overlay, hangup/muteAudio/muteVideo buttons take extra time to be shown.
Restart the client (not the daemon) fix the problemhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/931Chat with myself trouble2021-08-20T20:54:44ZChat with myself troubleIn fdroid jami version 20210421-01
https://paste.debian.net/hidden/c8414c4a
i made an account, copied my address to add as a contact, sent request, clicked back once, clicked on contact, sent a thumbs up, result on pic
![Screenshot_202...In fdroid jami version 20210421-01
https://paste.debian.net/hidden/c8414c4a
i made an account, copied my address to add as a contact, sent request, clicked back once, clicked on contact, sent a thumbs up, result on pic
![Screenshot_2021-05-01-15-28-23-402_cx.ring](/uploads/a3e7938751b5eb67fdc9b4367b955565/Screenshot_2021-05-01-15-28-23-402_cx.ring.jpg)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1109crasing app in debian 102021-08-20T20:54:01Znoxcrasing app in debian 10is happening that when trying to use the app , the jami app crash many time since the new update done todayis happening that when trying to use the app , the jami app crash many time since the new update done todayhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/384Context menu code smells2021-08-20T20:40:46ZAndreas TraczykContext menu code smells- excessive logic required outside the class
https://review.jami.net/c/jami-client-qt/+/17428/3/src/mainview/components/ConversationSmartListViewItemDelegate.qml#37
- js may be simplified with loader/repeater
- menu should be functionall...- excessive logic required outside the class
https://review.jami.net/c/jami-client-qt/+/17428/3/src/mainview/components/ConversationSmartListViewItemDelegate.qml#37
- js may be simplified with loader/repeater
- menu should be functionally modalhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/839My android client (from F-droid) are not recieving incoming messages2021-08-20T20:39:12ZJLMy android client (from F-droid) are not recieving incoming messagesBug report form
---------------
## Describe your environment
- Jami version: 20200810-01
- Device model: Samsung S8
- Android version: 9
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug...Bug report form
---------------
## Describe your environment
- Jami version: 20200810-01
- Device model: Samsung S8
- Android version: 9
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. I send someone a message from the Android client
2. They receive it and reply
3. It is not received on Android, it is only received when I start the desktop client
...
- Actual result: It is received in only one of my two clients
- Expected result: It is received in both clients
## Additional information
I have promoted Jami to many people as I love the idea of a P2P messenger, but not managed to have one solid call or longer conversation with anyone yet. With bug after bug, crash after crash, it is getting difficult. I still have faith in Jami but I don't think anyone I have convinced to download it is going to use it again, sadly. Maybe wait with release until it is a bit more stable?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/923Group contacts2021-08-20T20:15:32ZGUEST.itGroup contactsLet's assume an account synced on multiple devices. In example, a customerservice account used by 3 employee
There are multiple contacts to handle, but the company is divided in geographic zone, so user1 is for zone1, user2 is for zone2 ...Let's assume an account synced on multiple devices. In example, a customerservice account used by 3 employee
There are multiple contacts to handle, but the company is divided in geographic zone, so user1 is for zone1, user2 is for zone2 and so on.
Grouping contacs in groups (but all users should be able to see all groups), would be useful to make things easier: if you have to follow the zone2, you just check for zone2 messages.
without the grouping, when you receive a message from a customer you have to check if that customer is under your zone or not.
In this way, you can also shut up notifications coming from a different group than yours.
Something similiar to a Telegram group
I'm not sure if this is clear. I hope so.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/919Can send text and emoticons, but can't send pictures.2021-08-20T20:00:52ZFrederikSchackCan send text and emoticons, but can't send pictures.I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly...I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly unstable. One issue I have is that we share one public IP, which means we can't redirect a port to more than one subscriber inside the network.
It's the same issue with several phones.
We don't have problems with Bittorrent or any other program accessing the Internet, except for losing Internet connection once in a while.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/421Investigate "no response from DHT" [To check]2021-08-20T20:00:27ZSébastien BlinInvestigate "no response from DHT" [To check]Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/278Conférence : ajouter l'avatar d'un utilisateur présent en audio2021-08-20T20:00:16ZCharlotte HoffmannConférence : ajouter l'avatar d'un utilisateur présent en audio![07_JAMI_Moderation_Tous2](/uploads/4006de3a923993dbf35e99935796d50b/07_JAMI_Moderation_Tous2.jpg)![07_JAMI_Moderation_Tous2](/uploads/4006de3a923993dbf35e99935796d50b/07_JAMI_Moderation_Tous2.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/913Video conferences are broken2021-08-20T20:00:07ZSébastien BlinVideo conferences are brokenhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/307Smartlist: wrong cursor for resize mode2021-08-20T19:56:24ZSébastien BlinSmartlist: wrong cursor for resize modeall is in the titleall is in the titlehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/785[Feature Request] Link Previews2021-08-20T19:56:20Ztrymeout[Feature Request] Link PreviewsNot an important feature. But to get the webapge details such as image and a short description for any links sent from certain websites. This is only needed for popular websites such as YouTube, Twitter, Facebook, maybe news articles. Th...Not an important feature. But to get the webapge details such as image and a short description for any links sent from certain websites. This is only needed for popular websites such as YouTube, Twitter, Facebook, maybe news articles. This is a feature in WhatsApp and Signal.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/332Crash in media2021-08-20T19:53:07ZSébastien BlinCrash in media```
[Switching to Thread 0x7ffef4ff9700 (LWP 1076141)]
0x00000000012925aa in ff_yuv_420_rgb32_ssse3 ()
(gdb) bt
#0 0x00000000012925aa in ff_yuv_420_rgb32_ssse3 ()
#1 0x00000000012914d3 in yuv420_rgb32_ssse3 (c=0x7ffedc3142c0, src=0x7ff...```
[Switching to Thread 0x7ffef4ff9700 (LWP 1076141)]
0x00000000012925aa in ff_yuv_420_rgb32_ssse3 ()
(gdb) bt
#0 0x00000000012925aa in ff_yuv_420_rgb32_ssse3 ()
#1 0x00000000012914d3 in yuv420_rgb32_ssse3 (c=0x7ffedc3142c0, src=0x7ffef4ff5960, srcStride=0x7ffef4ff5940, srcSliceY=0, srcSliceH=720, dst=0x7ffef4ff5980, dstStride=0x7ffef4ff5950) at libswscale/x86/yuv2rgb_template.c:119
#2 0x000000000122ebff in sws_scale (c=<optimized out>, srcSlice=<optimized out>, srcStride=<optimized out>, srcSliceY=<optimized out>, srcSliceH=<optimized out>, dst=<optimized out>, dstStride=<optimized out>)
at libswscale/swscale.c:969
#3 0x000000000063357c in jami::video::VideoScaler::scale(DRing::VideoFrame const&, DRing::VideoFrame&) () at libswscale/swscale.c:596
#4 0x00000000006111e0 in jami::video::ShmHolder::renderFrame(DRing::VideoFrame const&) () at libswscale/swscale.c:596
#5 0x0000000000612169 in jami::video::SinkClient::update(jami::Observable<std::shared_ptr<DRing::MediaFrame> >*, std::shared_ptr<DRing::MediaFrame> const&) () at libswscale/swscale.c:596
#6 0x000000000061a1d8 in jami::Observable<std::shared_ptr<DRing::MediaFrame> >::notify(std::shared_ptr<DRing::MediaFrame>) () at libswscale/swscale.c:596
#7 0x0000000000614a23 in jami::video::VideoGenerator::publishFrame(std::shared_ptr<DRing::VideoFrame>) () at libswscale/swscale.c:596
#8 0x00000000007e4bea in std::_Function_handler<void (std::shared_ptr<DRing::MediaFrame>&&), jami::video::VideoReceiveThread::setup()::{lambda(std::shared_ptr<DRing::MediaFrame> const&)#1}>::_M_invoke(std::_Any_data const&, std::shared_ptr<DRing::MediaFrame>&&) () at libswscale/swscale.c:596
#9 0x000000000071e30c in jami::MediaDecoder::decode(AVPacket&) () at libswscale/swscale.c:596
#10 0x000000000071c14a in jami::MediaDemuxer::decode() () at libswscale/swscale.c:596
#11 0x00000000007e62c4 in jami::video::VideoReceiveThread::decodeFrame() () at libswscale/swscale.c:596
#12 0x0000000000674bdd in jami::ThreadLoop::mainloop(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>) () at libswscale/swscale.c:596
#13 0x0000000000675308 in 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() () at libswscale/swscale.c:596
#14 0x00007ffff72f9b84 in execute_native_thread_routine () from /lib64/libstdc++.so.6
#15 0x00007ffff7950432 in start_thread () from /lib64/libpthread.so.0
#16 0x00007ffff6ff7913 in clone () from /lib64/libc.so.6
```
Also
```
i Daemon_shm_1088573_0>, mixer=0
[1603479935.280|40373|sinkclient.cpp :419 ] Start sink <5345364777673835 / Jami Daemon_shm_1088573_0>, size=1206x720, mixer=0
[1603479935.280|40373|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_1088573_0]: new sizes: f=3473280, a=6946663
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1088573==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x0000018ec52a bp 0x7fd6bd5a1b50 sp 0x7fd6bd5a1a38 T119)
==1088573==The signal is caused by a READ memory access.
==1088573==Hint: this fault was caused by a dereference of a high value address (see register values below). Dissassemble the provided pc to learn which register was used.
#0 0x18ec52a (/home/amarok/Projects/jami/daemon/bin/dring+0x18ec52a)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/home/amarok/Projects/jami/daemon/bin/dring+0x18ec52a)
Thread T119 created by T1 here:
#0 0x7fd705418be5 in __interceptor_pthread_create (/lib64/libasan.so.6+0x57be5)
[1603479935.371|40269|sipvoiplink.cpp :1218 ] [INVITE:0x6190002670a8] RX SIP method 6 (INFO)
[1603479935.371|40269|sipvoiplink.cpp :1086 ] Rotate video 0 deg.
#1 0x7fd704718e48 in std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (/lib64/libstdc++.so.6+0xd8e48)
#2 0xa13459 in jami::ThreadLoop::start() /home/amarok/Projects/jami/daemon/src/threadloop.cpp:86
#3 0xe3dd71 in jami::video::VideoReceiveThread::startLoop(std::function<void (jami::MediaType)> const&) /home/amarok/Projects/jami/daemon/src/media/video/video_receive_thread.cpp:71
#4 0xddc26f in jami::video::VideoRtpSession::startReceiver() /home/amarok/Projects/jami/daemon/src/media/video/video_rtp_session.cpp:196
#5 0xddcd2c in jami::video::VideoRtpSession::start(std::unique_ptr<jami::IceSocket, std::default_delete<jami::IceSocket> >, std::unique_ptr<jami::IceSocket, std::default_delete<jami::IceSocket> >) /home/amarok/Projects/jami/daemon/src/media/video/video_rtp_session.cpp:241
#6 0xb1174d in jami::SIPCall::startAllMedia() /home/amarok/Projects/jami/daemon/src/sip/sipcall.cpp:1170
#7 0xb13362 in operator() /home/amarok/Projects/jami/daemon/src/sip/sipcall.cpp:1375
#8 0xb2108b in __invoke_impl<bool, jami::SIPCall::waitForIceAndStartMedia()::<lambda()>::<lambda()>&> /usr/include/c++/10/bits/invoke.h:60
#9 0xb1e821 in __invoke_r<bool, jami::SIPCall::waitForIceAndStartMedia()::<lambda()>::<lambda()>&> /usr/include/c++/10/bits/invoke.h:113
#10 0xb1c31a in _M_invoke /usr/include/c++/10/bits/std_function.h:291
#11 0xa13b49 in std::function<bool ()>::operator()() const /usr/include/c++/10/bits/std_function.h:622
#12 0xa983c8 in jami::RepeatedTask::run() /home/amarok/Projects/jami/daemon/src/scheduled_executor.h:76
#13 0xa94dfb in operator() /home/amarok/Projects/jami/daemon/src/scheduled_executor.cpp:87
#14 0xa97e0d in __invoke_impl<void, jami::ScheduledExecutor::reschedule(std::shared_ptr<jami::RepeatedTask>, jami::ScheduledExecutor::time_point, jami::ScheduledExecutor::duration)::<lambda()>&> /usr/include/c++/10/bits/invoke.h:60
#15 0xa97cb9 in __invoke_r<void, jami::ScheduledExecutor::reschedule(std::shared_ptr<jami::RepeatedTask>, jami::ScheduledExecutor::time_point, jami::ScheduledExecutor::duration)::<lambda()>&> /usr/include/c++/10/bits/invoke.h:110
#16 0xa97b2b in _M_invoke /usr/include/c++/10/bits/std_function.h:291
#17 0x571dc7 in std::function<void ()>::operator()() const /usr/include/c++/10/bits/std_function.h:622
#18 0xa9829f in jami::Task::run() /home/amarok/Projects/jami/daemon/src/scheduled_executor.h:55
#19 0xa95281 in operator() /home/amarok/Projects/jami/daemon/src/scheduled_executor.cpp:98
#20 0xa9758d in __invoke_impl<void, jami::ScheduledExecutor::schedule(std::shared_ptr<jami::Task>, jami::ScheduledExecutor::time_point)::<lambda()>&> /usr/include/c++/10/bits/invoke.h:60
#21 0xa97400 in __invoke_r<void, jami::ScheduledExecutor::schedule(std::shared_ptr<jami::Task>, jami::ScheduledExecutor::time_point)::<lambda()>&> /usr/include/c++/10/bits/invoke.h:110
#22 0xa970c4 in _M_invoke /usr/include/c++/10/bits/std_function.h:291
#23 0x571dc7 in std::function<void ()>::operator()() const /usr/include/c++/10/bits/std_function.h:622
#24 0xa95a78 in jami::ScheduledExecutor::loop() /home/amarok/Projects/jami/daemon/src/scheduled_executor.cpp:124
#25 0xa941e8 in operator() /home/amarok/Projects/jami/daemon/src/scheduled_executor.cpp:28
#26 0xa981c5 in __invoke_impl<void, jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> > /usr/include/c++/10/bits/invoke.h:60
#27 0xa9817a in __invoke<jami::ScheduledExecutor::ScheduledExecutor()::<lambda()> > /usr/include/c++/10/bits/invoke.h:95
#28 0xa98127 in _M_invoke<0> /usr/include/c++/10/thread:264
#29 0xa980fb in operator() /usr/include/c++/10/thread:271
#30 0xa980df in _M_run /usr/include/c++/10/thread:215
#31 0x7fd704718b83 (/lib64/libstdc++.so.6+0xd8b83)
Thread T1 created by T0 here:
#0 0x7fd705418be5 in __interceptor_pthread_create (/lib64/libasan.so.6+0x57be5)
#1 0x7fd704718e48 in std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (/lib64/libstdc++.so.6+0xd8e48)
#2 0xa9441c in jami::ScheduledExecutor::ScheduledExecutor() /home/amarok/Projects/jami/daemon/src/scheduled_executor.cpp:29
#3 0x98502b in jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&) /home/amarok/Projects/jami/daemon/src/manager.cpp:447
#4 0x988503 in jami::Manager::Manager() /home/amarok/Projects/jami/daemon/src/manager.cpp:726
#5 0x9882e1 in jami::Manager::instance() /home/amarok/Projects/jami/daemon/src/manager.cpp:702
#6 0x59e675 in DRing::init(DRing::InitFlag) /home/amarok/Projects/jami/daemon/src/ring_api.cpp:57
#7 0x48e097 in DBusClient::initLibrary(int) /home/amarok/Projects/jami/daemon/bin/dbus/dbusclient.cpp:245
#8 0x482e34 in DBusClient::DBusClient(int, bool) /home/amarok/Projects/jami/daemon/bin/dbus/dbusclient.cpp:108
#9 0x482543 in void __gnu_cxx::new_allocator<DBusClient>::construct<DBusClient, int&, bool&>(DBusClient*, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x482543)
#10 0x48235f in void std::allocator_traits<std::allocator<DBusClient> >::construct<DBusClient, int&, bool&>(std::allocator<DBusClient>&, DBusClient*, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x48235f)
#11 0x482000 in std::_Sp_counted_ptr_inplace<DBusClient, std::allocator<DBusClient>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<int&, bool&>(std::allocator<DBusClient>, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x482000)
#12 0x481a25 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<DBusClient, std::allocator<DBusClient>, int&, bool&>(DBusClient*&, std::_Sp_alloc_shared_tag<std::allocator<DBusClient> >, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x481a25)
#13 0x48150d in std::__shared_ptr<DBusClient, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<DBusClient>, int&, bool&>(std::_Sp_alloc_shared_tag<std::allocator<DBusClient> >, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x48150d)
#14 0x480b7b in std::shared_ptr<DBusClient>::shared_ptr<std::allocator<DBusClient>, int&, bool&>(std::_Sp_alloc_shared_tag<std::allocator<DBusClient> >, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x480b7b)
#15 0x480224 in std::shared_ptr<DBusClient> std::allocate_shared<DBusClient, std::allocator<DBusClient>, int&, bool&>(std::allocator<DBusClient> const&, int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x480224)
#16 0x47f70a in std::shared_ptr<DBusClient> std::make_shared<DBusClient, int&, bool&>(int&, bool&) (/home/amarok/Projects/jami/daemon/bin/dring+0x47f70a)
#17 0x47e74b in main /home/amarok/Projects/jami/daemon/bin/main.cpp:218
#18 0x7fd70433c041 in __libc_start_main (/lib64/libc.so.6+0x27041)
==1088573==ABORTING
```Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/645file transfer cancellation & progress bar not available on Android2021-08-20T19:52:47ZGuillaume Hellerfile transfer cancellation & progress bar not available on Android1- it is currently impossible to cancel a file transfer on Android (before or during the transfer)
2- file transfer progress bar is not displayed (available on all other platforms)1- it is currently impossible to cancel a file transfer on Android (before or during the transfer)
2- file transfer progress bar is not displayed (available on all other platforms)New release 1Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/860Swarm: issues follow up (more than 2 participants)2021-08-20T19:07:29ZSébastien BlinSwarm: issues follow up (more than 2 participants)+ Conversation requests not shown
+ Can't make differences for join messages & authors for incoming messages (cf screenshot)
![Capture_2020-12-29-16-26-57](/uploads/7df1bec8561ccd0eaa5c1ef374133592/Capture_2020-12-29-16-26-57.png)
+ N...+ Conversation requests not shown
+ Can't make differences for join messages & authors for incoming messages (cf screenshot)
![Capture_2020-12-29-16-26-57](/uploads/7df1bec8561ccd0eaa5c1ef374133592/Capture_2020-12-29-16-26-57.png)
+ Not following ConversationMemberAdded (cf screenshot, it's the same conversation after reloading the daemon)
![Capture_2020-12-29-16-27-22](/uploads/f13b50efe923e895d1bf843f6c4cadfd/Capture_2020-12-29-16-27-22.png)Swarm-chat