savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-12-23T21:28:46Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/223Swarm: Conversations disappears2020-12-23T21:28:46ZSébastien BlinSwarm: Conversations disappears# Scenario
+ Create a one to one conversation between 2 accounts on same client
+ Switch from one account to another and send messages
# Current result
+ Sometimes the whole conversation disappears
# Expected
The conversation should...# Scenario
+ Create a one to one conversation between 2 accounts on same client
+ Switch from one account to another and send messages
# Current result
+ Sometimes the whole conversation disappears
# Expected
The conversation should be shownSwarm-chatAlbert Babí OllerKateryna KostiukAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/225Swarm: removeContact should remove related swarm2020-12-23T21:43:37ZSébastien BlinSwarm: removeContact should remove related swarm# Reproduce steps
+ Right click on contact, remove contact
# Expected
+ daemon will launch conversationremoved() for swarm, swarm must be removed
# Current
+ Swarm seems to stay there# Reproduce steps
+ Right click on contact, remove contact
# Expected
+ daemon will launch conversationremoved() for swarm, swarm must be removed
# Current
+ Swarm seems to stay thereSwarm-chatKateryna KostiukAlbert Babí OllerKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/84[Request] 32-bit Debian i386 package2020-12-24T13:27:35Z[Request] 32-bit Debian i386 packageAny chance to provide a *jami-all_i386.deb* for 32-bit Debian which can be used by
both Debian and Debian-based distros (like MX Linux, LMDE, SparkyLinux)
Debian 32bit users want to use jami too!
*P.S Ubuntu favors and Ubuntu will s...Any chance to provide a *jami-all_i386.deb* for 32-bit Debian which can be used by
both Debian and Debian-based distros (like MX Linux, LMDE, SparkyLinux)
Debian 32bit users want to use jami too!
*P.S Ubuntu favors and Ubuntu will stop official support in 2021 and 2023 respectively
while Debian, one of the most popular distros, and Debian-based distros still provide
official support for 32bit computer. Therefore users for Debian and Debian-based
distros will increase in the foreseeable future.*https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/12Debian: official distribution repository package2020-12-24T13:27:55ZFredy PulidoDebian: official distribution repository package* Analize Jami and Debian Versions and releases
* Define strategy
* Contact developer to work together
Related: https://git.jami.net/savoirfairelinux/jami-packaging/issues/8* Analize Jami and Debian Versions and releases
* Define strategy
* Contact developer to work together
Related: https://git.jami.net/savoirfairelinux/jami-packaging/issues/8Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1067Jami seems to be preventing Linux to shutdown or reboot.2020-12-24T14:27:03ZAndy HiscockJami seems to be preventing Linux to shutdown or reboot.Has anyone else noticed how Jami is preventing a reboot or power off of laptops?
I've tried a Lenovo, Acer and Dell. Keeping in with the Libre spirit, all running Trisquel 8. All shut down but "pause" at the point of power down or reb...Has anyone else noticed how Jami is preventing a reboot or power off of laptops?
I've tried a Lenovo, Acer and Dell. Keeping in with the Libre spirit, all running Trisquel 8. All shut down but "pause" at the point of power down or reboot. Either doing a soft reboot though the keyboard or pressing the power button to continue. The Pause can last 30 seconds, I have also left the machine overnight and it was still paused.
If I manually Quit Jami before trying to Shut Down / Reboot I never get the problem - this is why I suspect it is the jami-daemon.
Is this a known bug?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/231Swarm: Incorrect call duration shown2020-12-24T16:43:02ZSébastien BlinSwarm: Incorrect call duration shown# Scenario
In a swarm start a call
# Expected result
+ When finished, we should see Outgoing call - Duration
# Current result
+ Duration is incorrect
+ When relaunching client, the message totally disappears
# Note
Call messages a...# Scenario
In a swarm start a call
# Expected result
+ When finished, we should see Outgoing call - Duration
# Current result
+ Duration is incorrect
+ When relaunching client, the message totally disappears
# Note
Call messages are now synced, with the type "application/call-history+json" with a map<str, str> with the "duration" key (in ms)Swarm-chatAlbert Babí OllerKateryna KostiukAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/209Distribution 'void' not supported.2020-12-24T18:57:20ZFabio KrapohlDistribution 'void' not supported.I wanted to follow the build instructions, but already the first step (./make-ring.py --init) didn't work, because void linux is not supported.
Why do you have specific install rules for every system instead of just using some default ru...I wanted to follow the build instructions, but already the first step (./make-ring.py --init) didn't work, because void linux is not supported.
Why do you have specific install rules for every system instead of just using some default rules, and maybe add some special cases, where necessary, like basically every other project does?
You could just use some fallback, which uses the most common stuff.
I could also try to add some void installadion method myself, but I'm not sure, where to start.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/205Hyperlink in dark theme is unreadable2020-12-24T19:12:14ZlinsuiHyperlink in dark theme is unreadable![sshot-028](/uploads/e4dc7c6eaf14331e91974727420edf92/sshot-028.png)![sshot-028](/uploads/e4dc7c6eaf14331e91974727420edf92/sshot-028.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/119Resend failed files when peer is online2020-12-24T21:22:33ZSébastien BlinResend failed files when peer is onlineLike messagesLike messagesSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/215AudioInput segfault at the end of a call2020-12-24T21:24:27ZSébastien BlinAudioInput segfault at the end of a callFrom someone via IRC:
```
#0 0x0000000000000000 in ?? ()
#1 0x0000561a07b786c7 in jami::Observable<std::shared_ptr<DRing::MediaFrame> >::~Observable (this=0x7f8008036130, __in_chrg=<optimized out>) at ./daemon/src/observer.h:5...From someone via IRC:
```
#0 0x0000000000000000 in ?? ()
#1 0x0000561a07b786c7 in jami::Observable<std::shared_ptr<DRing::MediaFrame> >::~Observable (this=0x7f8008036130, __in_chrg=<optimized out>) at ./daemon/src/observer.h:50
#2 jami::AudioInput::~AudioInput (this=0x7f8008036130, __in_chrg=<optimized out>)
at audio_input.cpp:57
#3 0x0000561a07b7905a in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release (
this=0x7f8008036120) at /usr/include/c++/6/bits/shared_ptr_base.h:150
#4 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count (
this=0x561a0b097318, __in_chrg=<optimized out>)
at /usr/include/c++/6/bits/shared_ptr_base.h:662
#5 std::__shared_ptr<jami::AudioInput, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr (
this=0x561a0b097310, __in_chrg=<optimized out>)
at /usr/include/c++/6/bits/shared_ptr_base.h:928
#6 std::shared_ptr<jami::AudioInput>::~shared_ptr (this=0x561a0b097310,
__in_chrg=<optimized out>) at /usr/include/c++/6/bits/shared_ptr.h:93
#7 jami::AudioRtpSession::~AudioRtpSession (this=0x561a0b096f90,
__in_chrg=<optimized out>) at audio_rtp_session.cpp:58
#8 0x0000561a07b790b9 in jami::AudioRtpSession::~AudioRtpSession (this=0x561a0b096f90,
__in_chrg=<optimized out>) at audio_rtp_session.cpp:61
#9 0x0000561a07b4ee2e in std::default_delete<jami::AudioRtpSession>::operator() (
this=<optimized out>, __ptr=<optimized out>)
at /usr/include/c++/6/bits/unique_ptr.h:76
#10 std::unique_ptr<jami::AudioRtpSession, std::default_delete<jami::AudioRtpSession> >::~unique_ptr (this=0x561a0b098388, __in_chrg=<optimized out>)
at /usr/include/c++/6/bits/unique_ptr.h:239
#11 jami::SIPCall::~SIPCall (this=0x561a0b0981a0, __in_chrg=<optimized out>)
at sipcall.cpp:103
#12 0x0000561a07b4ada5 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release (
this=0x561a0b098190) at /usr/include/c++/6/bits/shared_ptr_base.h:150
#13 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count (
this=<synthetic pointer>, __in_chrg=<optimized out>)
at /usr/include/c++/6/bits/shared_ptr_base.h:662
#14 std::__shared_ptr<jami::SIPCall, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr (
this=<synthetic pointer>, __in_chrg=<optimized out>)
at /usr/include/c++/6/bits/shared_ptr_base.h:928
#15 std::shared_ptr<jami::SIPCall>::~shared_ptr (this=<synthetic pointer>,
__in_chrg=<optimized out>) at /usr/include/c++/6/bits/shared_ptr.h:93
#16 jami::SIPCall::<lambda()>::operator() (__closure=<optimized out>) at sipcall.cpp:396
#17 std::_Function_handler<void(), jami::SIPCall::hangup(int)::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/6/functional:1731
#18 0x0000561a07da1f5e in std::function<void ()>::operator()() const (
this=0x7f80077fc790) at /usr/include/c++/6/functional:2127
#19 dht::ThreadPool::<lambda()>::operator() (__closure=0x7f7ff0000e08)
at thread_pool.cpp:97
#20 std::_Bind_simple<dht::ThreadPool::run(std::function<void()>&&)::<lambda()>()>::_M_invoke<> (this=0x7f7ff0000e08) at /usr/include/c++/6/functional:1391
#21 std::_Bind_simple<dht::ThreadPool::run(std::function<void()>&&)::<lambda()>()>::operator() (this=0x7f7ff0000e08) at /usr/include/c++/6/functional:1380
#22 std::thread::_State_impl<std::_Bind_simple<dht::ThreadPool::run(std::function<void()>&&)::<lambda()>()> >::_M_run(void) (this=0x7f7ff0000e00) at /usr/include/c++/6/thread:197
#23 0x00007f804a17cb2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#24 0x00007f804ab65fa3 in start_thread (arg=<optimized out>) at pthread_create.c:486
#25 0x00007f8049e5c4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/216No audio input in Android 72020-12-24T21:25:23ZNo audio input in Android 7Hi, I posted this issue in the `jami-android` repo, but I think it is related to the daemon. The related issue is: https://git.jami.net/savoirfairelinux/ring-client-android/issues/725
I attach the Android log file here too.[logjami.txt]...Hi, I posted this issue in the `jami-android` repo, but I think it is related to the daemon. The related issue is: https://git.jami.net/savoirfairelinux/ring-client-android/issues/725
I attach the Android log file here too.[logjami.txt](/uploads/7720a53635d1cb6d0fa34ae1e30036dd/logjami.txt)Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/72Which layer owns the auto-answer flag???? Daemon or lrc?2020-12-24T21:25:55ZSébastien BlinWhich layer owns the auto-answer flag???? Daemon or lrc?For now, the auto-answer flag is in the account's config. The `--auto-answer` flag is also available for `dring`. Nice.
So, we can conclude that the code for auto answering a call is in the daemon. But it's not the case for the clients....For now, the auto-answer flag is in the account's config. The `--auto-answer` flag is also available for `dring`. Nice.
So, we can conclude that the code for auto answering a call is in the daemon. But it's not the case for the clients. We should re-implement this flag into the client part.
I think it's bad. We should implement this feature only once, and the flag should be managed by the layer which implems this behavior.
Also, in the future, I think we want to improve this flag by contact and by account.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/306jams contact synchro - retrieve and display avatar + contact first name/last ...2020-12-24T21:26:58ZGuillaume Hellerjams contact synchro - retrieve and display avatar + contact first name/last nameWhen the contact list is retrieved, only the username is displayed. vcard is exchanged after first interaction with the contact
![image](/uploads/0db02a44e73c4c580256fa1e624f63c0/image.png)
Aim is to retrieve the avatar and contact fir...When the contact list is retrieved, only the username is displayed. vcard is exchanged after first interaction with the contact
![image](/uploads/0db02a44e73c4c580256fa1e624f63c0/image.png)
Aim is to retrieve the avatar and contact first/name so info can be displayed directly when the user connects or the contact list is synchronized, without having to wait for an interaction between each contact to retrieve the vcard
even more important when we are in LDAP/AD config as we have no username
![image](/uploads/44c0ea92833eb9ac4da4008a2452eb6e/image.png)Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/364jami2020-12-24T21:30:40Zjamijami is not sharing location. but when you start sharing location, if you want share is saying stop sharing .help please.jami is not sharing location. but when you start sharing location, if you want share is saying stop sharing .help please.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1229Chatview: record video message - preview is missing2020-12-24T21:36:05ZSébastien BlinChatview: record video message - preview is missingIteration 25Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/222Swarm: Lazy loading support2020-12-24T21:38:03ZSébastien BlinSwarm: Lazy loading supportCurrently all the conversations messages are loaded, but lrc supports lazy loading.
Should be implementedCurrently all the conversations messages are loaded, but lrc supports lazy loading.
Should be implementedSwarm-chatKateryna KostiukAlbert Babí OllerKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1210preview frozen after accessing media settings during a call2020-12-24T21:40:28ZGuillaume Hellerpreview frozen after accessing media settings during a call* During a video call, Open Settings
* Go to Media
* Go back to video call
--> preview is frozen* During a video call, Open Settings
* Go to Media
* Go back to video call
--> preview is frozenhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/889Fedora stable repository serves nightly builds2020-12-24T21:44:03ZFedora stable repository serves nightly buildsThe stable repository for Fedora serves nightly builds instead of stable release builds.
https://dl.jami.net/stable/fedora_31/The stable repository for Fedora serves nightly builds instead of stable release builds.
https://dl.jami.net/stable/fedora_31/https://git.jami.net/savoirfairelinux/jami-project/-/issues/995Arabic layout in windows app not usable!2020-12-24T21:45:46ZaimaArabic layout in windows app not usable!First! the app is awesome thank you for your hard work,
as the title the arabic layout is bad please fix it
and here screenshot
![6651](/uploads/20c1dd17cb3d77b791f9e6f930f34a78/6651.PNG)
![46354](/uploads/565216b98ab795347bf6a3d6abcc...First! the app is awesome thank you for your hard work,
as the title the arabic layout is bad please fix it
and here screenshot
![6651](/uploads/20c1dd17cb3d77b791f9e6f930f34a78/6651.PNG)
![46354](/uploads/565216b98ab795347bf6a3d6abcc2223/46354.PNG)
and i have experience many crashes on the android app during video call please fix thanksItération 21Ming Rui ZhangYang WangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1063[Android] Constantly seeing "Syncing data" on lock screen2020-12-27T00:40:26ZDick Johnson[Android] Constantly seeing "Syncing data" on lock screenLately when looking at my cell phones lock screen I'll see "Jami Syncing data" that seems to stay for a long time and is curious as I thought jami was "server-less" and did not need a central server.
What could be causing Jami to alert t...Lately when looking at my cell phones lock screen I'll see "Jami Syncing data" that seems to stay for a long time and is curious as I thought jami was "server-less" and did not need a central server.
What could be causing Jami to alert the user of this and why does it take so long?