savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-07-09T00:50:06Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/262Received pictures are not displayed - Android Beta 20200703-012020-07-09T00:50:06ZCyrille BéraudReceived pictures are not displayed - Android Beta 20200703-01Iteration 19Adrien BéraudPierre DucheminAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/259File transfer and multi device, "already accepted" + cancelled2020-07-17T14:25:42ZSébastien BlinFile transfer and multi device, "already accepted" + cancelled# Reproduce step
+ Account B got 2 devices connected to account A
+ A sends a file
+ B receives the file request on both devices, but A cancels the transfer# Reproduce step
+ Account B got 2 devices connected to account A
+ A sends a file
+ B receives the file request on both devices, but A cancels the transferIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/258No way to use a custom turn server port2020-07-16T18:48:33ZBrando TovarNo way to use a custom turn server port**Evironment details:**
* OS: Ubuntu 20.04
* Jami version: Jami from jami.net for ubuntu 20.04
**Steps to reproduce**
* Set your own turn server using these instructions: https://git.jami.net/savoirfairelinux/ring-project/wikis/technica...**Evironment details:**
* OS: Ubuntu 20.04
* Jami version: Jami from jami.net for ubuntu 20.04
**Steps to reproduce**
* Set your own turn server using these instructions: https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/3.6-Setup-your-own-TURN-server
* Update turn configuration on Jami advance settings with: IPOfTurnServer:customPort
* Then trying to make a call using turn only will not work and the logs will show this line: `[ice] added turn server 'IPOfTurnServer', port 3478`
The solution is to use 3478 as the listening port on the turnserver.conf than everything will work as intended.Iteration 19Brando TovarBrando Tovarhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/761Image preview no more displayed since last version 202007032024-01-30T14:52:25ZGuillaume HellerImage preview no more displayed since last version 20200703How to reproduce:
* send or receive an image on Android
* image preview is not displayed in the chatviewHow to reproduce:
* send or receive an image on Android
* image preview is not displayed in the chatviewIteration 19Adrien BéraudAmirhossein NaghshzanAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/256Stuck in Connecting: Some negotiations are blocked2020-07-16T18:48:37ZSébastien BlinStuck in Connecting: Some negotiations are blockedRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...ICE process complete, status=Success
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...Valid list
(called a second time after that when negotiation is done
# Reproduce steps
still unknownIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/760UX for creating a jams account is broken2020-07-13T14:08:50ZAdrien BéraudUX for creating a jams account is brokenAfter creating an account with management server, the wizard remains openAfter creating an account with management server, the wizard remains openIteration 19Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1003Wizard View with photobooth - QML Client-Windows2020-06-26T20:10:32ZYang WangWizard View with photobooth - QML Client-WindowsIteration 19Yang WangYang Wanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/249Stuck in Searching: Listen on Call ICE is not responding2020-07-09T20:19:50ZSébastien BlinStuck in Searching: Listen on Call ICE is not respondingRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
Unknown
# Observations
+ Device A calls device B with the bug
+ device B answer its ICE for the PeerConnection request, but not for the DHT ICE...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
Unknown
# Observations
+ Device A calls device B with the bug
+ device B answer its ICE for the PeerConnection request, but not for the DHT ICE candidates request
+ First call is failing. No fallback done because we are still in the SEARCHING state. Second call will succeed. Because the Peer negotiation is done without issue. However all first calls to device B will failIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/248Stuck in Connecting/Searching: timeout duration2020-07-02T20:06:29ZSébastien BlinStuck in Connecting/Searching: timeout durationRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
Actually ICE_NEGOTIATION_TIMEOUT is 60 seconds. This is pretty long and the user will close the window before thisRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
Actually ICE_NEGOTIATION_TIMEOUT is 60 seconds. This is pretty long and the user will close the window before thisIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/247Stuck in Searching/Connecting: Resolve the two requests mystery2020-07-02T20:06:32ZSébastien BlinStuck in Searching/Connecting: Resolve the two requests mysteryRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
1. device B cut its connectivity
2. device A calls device B (with the connecting lock, cf https://git.jami.net/savoirfairelinux/ring-daemon/issue...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
1. device B cut its connectivity
2. device A calls device B (with the connecting lock, cf https://git.jami.net/savoirfairelinux/ring-daemon/issues/243)
3. device A is blocked in "Searching"
4. after a while, device B is back online
5. device A receives 2 ICE response
# Expected results
Only one answer should be received (the one from the fallback request)Iteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/756jams - add support for user directory search2020-07-17T14:25:44ZGuillaume Hellerjams - add support for user directory searchShould be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results).
The list of results should al...Should be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results).
The list of results should also contains the avatar of the users (even for new users)Iteration 19Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/246Stuck in Searching/Connecting: Improve logs2020-07-07T17:49:52ZSébastien BlinStuck in Searching/Connecting: Improve logsEverything is in the title. The negotiation of a call can be quite complex to understand and logs should be understandable, moreover if the call fails.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227Everything is in the title. The negotiation of a call can be quite complex to understand and logs should be understandable, moreover if the call fails.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227Iteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/244Stuck in Connecting/Searching: Re-add timeouts2020-07-02T20:06:34ZSébastien BlinStuck in Connecting/Searching: Re-add timeoutsBecause we removed the eventloop to check pending calls, timeout are not checked and only done on successfully negotiated ICE. We should check re-add timeout to avoid any lock in SEARCHING or CONNECTING.
Related to https://git.jami.net/...Because we removed the eventloop to check pending calls, timeout are not checked and only done on successfully negotiated ICE. We should check re-add timeout to avoid any lock in SEARCHING or CONNECTING.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device B cut its connectivity
2. device A calls device B
5. device A is blocked in "Searching"
# Expected result
When ICE_NEGOTIATION_TIMEOUT is reached, the searching window should be closedIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/243Stuck in Connecting: Closed sockets are not detected all the time2020-07-02T20:06:36ZSébastien BlinStuck in Connecting: Closed sockets are not detected all the timeRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
# Expected result
Jami should detect that the socket is unusable and stop the call if fallback fails
+ icecb.on_destroy should be calledIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1180Integrate background modification plugin on Linux client2020-07-17T14:26:01ZGuillaume HellerIntegrate background modification plugin on Linux clientIteration 19Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/999Jami at rest randomly crashes - Ubuntu 20.042020-07-16T18:48:39ZCyrille BéraudJami at rest randomly crashes - Ubuntu 20.04```
/usr/lib/ring/dring -d -c
[Switching to Thread 0x7ffdd1ff3700 (LWP 147895)]
0x0000555555a429c6 in pj_turn_session_on_rx_pkt2 ()
(gdb) bt
#0 0x0000555555a429c6 in pj_turn_session_on_rx_pkt2 ()
#1 0x0000555555a42bf2 in pj_turn_sessi...```
/usr/lib/ring/dring -d -c
[Switching to Thread 0x7ffdd1ff3700 (LWP 147895)]
0x0000555555a429c6 in pj_turn_session_on_rx_pkt2 ()
(gdb) bt
#0 0x0000555555a429c6 in pj_turn_session_on_rx_pkt2 ()
#1 0x0000555555a42bf2 in pj_turn_session_on_rx_pkt ()
#2 0x0000555555a4430e in on_data_read_asock ()
#3 0x0000555555a575bd in ioqueue_on_read_complete ()
#4 0x0000555555a5282c in ioqueue_dispatch_read_event ()
#5 0x0000555555a541bb in pj_ioqueue_poll ()
#6 0x0000555555882060 in jami::IceTransport::Impl::handleEvents(unsigned int) ()
#7 0x00005555558822a6 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::IceTransport::Impl::Impl(char const*, int, bool, jami::IceTransportOptions const&)::{lambda()#6}> > >::_M_run() ()
#8 0x00007ffff795ccb4 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#9 0x00007ffff7c1d609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#10 0x00007ffff764a103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
```Iteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/747"Video Resolution" setting on Android TV doesn't work2020-10-03T17:07:50Z"Video Resolution" setting on Android TV doesn't workMy webcam supports up to 720p/16:9 resolution, but selecting that option inside "Video Resolution" setting on the Android TV app doesn't seem to affect the output video, it appears to be stuck on 480p/4:3 as you can see in the attached s...My webcam supports up to 720p/16:9 resolution, but selecting that option inside "Video Resolution" setting on the Android TV app doesn't seem to affect the output video, it appears to be stuck on 480p/4:3 as you can see in the attached screenshot.
The certified Android TV device I'm using is the Ematic Jetstream, with Android 9 and native UVC webcam support.
![Screenshot___1](/uploads/0d295ff45225b8fa434c41de08df8771/Screenshot___1.png)
![Screenshot___2](/uploads/1467ebe7083e8a7d9700edd0c04f9c63/Screenshot___2.png)Iteration 19Adrien BéraudAmirhossein NaghshzanPierre DucheminAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/74Messages should be grouped by tranches of more than 1 minute in conversations2020-08-19T16:06:47ZRaphaël BruléMessages should be grouped by tranches of more than 1 minute in conversationsWhen sending messages, the message time line will be shown for every first message of a given minute.
For exemple:
<pre>
--- THU 10:00PM ---
received1
sent1
sent2
--- THU 10:01PM ---
received2 ...When sending messages, the message time line will be shown for every first message of a given minute.
For exemple:
<pre>
--- THU 10:00PM ---
received1
sent1
sent2
--- THU 10:01PM ---
received2
sent3
--- THU 10:02PM ---
sent4
received3
</pre>
This makes conversations unnecessarily spaced out and heavy. Instead of every minute, messages could be grouped by tranches of 15 minutes (exemple). However, it would be important for the user to have a way to know at what time a was sent, thus we could have a single tap on a message show the time at which it was sent (or other user-friendly way to show it on demand).Iteration 19https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/744Auto-answer doesn't work some times2024-01-30T14:52:05ZCyrille BéraudAuto-answer doesn't work some timesOn Android-Tv : some times (very often) the device answers, but the ring tone continues.
On tablet/phone, if the device is wake-up, the device doesn't auto-answer.On Android-Tv : some times (very often) the device answers, but the ring tone continues.
On tablet/phone, if the device is wake-up, the device doesn't auto-answer.Iteration 19Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/225Add support for searching a JAMS user repository2020-07-13T14:11:56ZAdrien BéraudAdd support for searching a JAMS user repositoryShould be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results)
The list of results should als...Should be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results)
The list of results should also contains the avatar of the users (even for new users)
Example:
![contact_search](/uploads/09d4b6cbd56f62000422d7c925765438/contact_search.png)Iteration 19Adrien BéraudAdrien Béraud