savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-01-31T13:11:29Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/844about dialog: needs some styling work2021-01-31T13:11:29ZHugo Lefeuvreabout dialog: needs some styling workThe about dialog is ugly.
![screenshot-2018-07-04-11-19-36](/uploads/3dcd1c1fe6788ae0ae1bb5f0ac53a80a/screenshot-2018-07-04-11-19-36.png)
At least, the Ring icon is way too big. Or we should use the simple logo, without 'Ring, a GNU pa...The about dialog is ugly.
![screenshot-2018-07-04-11-19-36](/uploads/3dcd1c1fe6788ae0ae1bb5f0ac53a80a/screenshot-2018-07-04-11-19-36.png)
At least, the Ring icon is way too big. Or we should use the simple logo, without 'Ring, a GNU package'. That should be mentioned elsewhere.
This is an easy issue. Hint: take a look at `src/dialogs.c`.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/843(TBD) Avatar receiving issue2021-01-31T15:06:56ZMing Rui Zhang(TBD) Avatar receiving issueMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1219Impossible to delete old conversations2021-01-31T16:42:49ZJLImpossible to delete old conversationsI have tried repeatedly to delete an old conversation that appears in the Gnome client (but not on my F-droid client of the same account). I right-click the converesation and click "Delete conversation" - nothing happens.
This version: ...I have tried repeatedly to delete an old conversation that appears in the Gnome client (but not on my F-droid client of the same account). I right-click the converesation and click "Delete conversation" - nothing happens.
This version: "Together"
compiled 2020-11-10 21:02:06 UTC
from Synaptic Package Managerhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/309Known connectivity issues2021-01-31T21:27:08ZSébastien BlinKnown connectivity issuesThis is more a note than a real issue, but used to group what's known, in progress and missing
# Connecting status
Maybe still there. But for now, the scenarios I see are not related (last week was due to TURN changes). So for now, **w...This is more a note than a real issue, but used to group what's known, in progress and missing
# Connecting status
Maybe still there. But for now, the scenarios I see are not related (last week was due to TURN changes). So for now, **wontfix** til no new precise scenario. Too much time lost for non reproducible scenarios
# UPnP
## UPnP candidate selection
Generally not chosen. The current question is to determine why it's not the case
Observation: Lot of timeout when adding candidates
## Improve the current code
https://git.jami.net/savoirfairelinux/ring-client-android/issues/740
## Add libpcp?
Unanswered for now
# IPv6
## TURN not added in IPv6
cf https://git.jami.net/savoirfairelinux/ring-daemon/issues/301#note_21918
This patch solves current state for daemon + pjsip: https://review.jami.net/c/ring-daemon/+/15606
However still a TODO: update our TURN configuration to allow both IPv6 + IPv4 selection as specified in the issue
## IPv6 only to IPv4
All is there: https://git.jami.net/savoirfairelinux/ring-client-ios/issues/46
# iOS
## IPv4 addresses are not always resolved
Solved by https://review.jami.net/c/ring-daemon/+/15655 but still in discussion with pjsip
# Android
## Wake up after a night
Some devices are not correctly awoken. First lead was a lock solved by https://github.com/savoirfairelinux/opendht/commit/23a75a3f504938771649a5791451207b366fa351
However still some tests to know if there is more than one issue, cause the OS can be pretty aggressive with Doze Mode and constructors (cf https://dontkillmyapp.com/).
# Ice possible evolutions
+ Implement latest RFCs
+ Get candidates as soon as available to avoid any delay in TURN resolution for example
+ Follow a connectivity change to update sockets when going from wifi to 3g for example
+ https://git.jami.net/savoirfairelinux/ring-daemon/issues/288
# Misc
+ Merge current stack into pjsip master to avoid to manage patches
+ Investigate: https://git.jami.net/savoirfairelinux/ring-daemon/issues/274 but it's been a while I don't see this, so for now, I think I will closehttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/46Communication between IPv6-only to IPv4-only networks2021-01-31T21:27:09ZSébastien BlinCommunication between IPv6-only to IPv4-only networksTo perform that, we need to have a ipv6<->ipv4 mechanism somewhere. Because the first peer is only able to listen on ipv6 addresses and the second one on ipv4 addresses, something between those peers need to do that job.
And the good ne...To perform that, we need to have a ipv6<->ipv4 mechanism somewhere. Because the first peer is only able to listen on ipv6 addresses and the second one on ipv4 addresses, something between those peers need to do that job.
And the good news is that TURN is here for that and this behavior is described by [RFC6156](https://tools.ietf.org/html/rfc6156).
So, for coturn, the config needs two relay-addr entries. One for ipv6, one for ipv4 (cf https://github.com/coturn/coturn/issues/154). This is ok for turn.jami.net, so nothing to do there.
For Jami, this needs to be handled by pjproject but this is not the case for now:
https://github.com/pjsip/pjproject/commit/4b6835c9b818eb8a434d35beccd5faa1b684533b
This needs to be able to set "IPV4_AF_TYPE" for PJ_STUN_ATTR_REQ_ADDR_TYPE to be able to allocate an IPv4 candidate for an IPv6 address. However, the rest is not supported because the session will fail. So, the code needs to be done.
Depends on: https://github.com/pjsip/pjproject/issues/2520Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/274pjsip crash in pj_sockaddr_cmp2021-02-01T15:13:20ZSébastien Blinpjsip crash in pj_sockaddr_cmpSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1248Outgoing audio and video calls often fail2021-02-01T19:29:56ZLuis FelipeOutgoing audio and video calls often fail**Jami**: (GTK) 20200710.1.6bd18d2 (from official OS repository)
**Daemon**: Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
**OS**: Guix System 681af17
-----
## Steps to reproduce bug
Assuming Jami has been already started:
1...**Jami**: (GTK) 20200710.1.6bd18d2 (from official OS repository)
**Daemon**: Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
**OS**: Guix System 681af17
-----
## Steps to reproduce bug
Assuming Jami has been already started:
1. Click on a contact in the left pane
2. Click on the video camera icon to place a video call **or**
click the phone icon to place and audio call
## What you expect to happen:
+ I see a visual indicator that Jami is making the call
+ The person I'm calling notices I'm calling and answers the call
+ We can talk to each other
## What happens instead:
+ A new pane opens, telling me the following information about the call, which seems fine to me:
```
CONTACT_AVATAR
CONTACT_NAME
CONTACT_USER_NAME
Spinner spinning
Searching
Hang up icon
```
But this is unexpected:
+ The pane disappears after a minute of displaying the same state: spinner spinning and the state "Searching".
+ The messages history displays a new entry that says: Missed outgoing call
+ My contact never notices I'm calling
+ So we can't talk to each other
## Logs
There is no `journalctl --since "24h ago" | grep dring` in my system. It doesn't use `systemd` and `dring` runs at user-level.
I'd be happy to provide additional information with some additional guidance.
## Additional information
I tried the same steps indicated above several times with two different contacts, both using Android clients:
**OS**: Android 5.1 and Android 9
**Jami**: 20201222-01 (from F-Droid)
Note that we can text to each other, although not without problems (see #1243).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/394Plugin System: add "always"preference2021-02-01T19:51:38ZAline Gondim SantosPlugin System: add "always"preferenceAdd a preference that will automatically toggle a plug-in at call/conversation startAdd a preference that will automatically toggle a plug-in at call/conversation startIteration 27Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/10Change png logo by svg file2021-02-01T19:52:29ZAline Gondim SantosChange png logo by svg fileIteration 27Aline Gondim SantosAline Gondim Santoshttps://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/1240Improve Jami's description in AppStream metadata2021-02-03T03:44:46ZBruno KleinertImprove Jami's description in AppStream metadataHi,
the current AppStream description is weak and does not clearly describe Jami.
[0001-Improve-AppStream-description.patch](/uploads/7962a59ac2c9a35e3419ff4fb9bfe6c1/0001-Improve-AppStream-description.patch) is a patch to improve Jami...Hi,
the current AppStream description is weak and does not clearly describe Jami.
[0001-Improve-AppStream-description.patch](/uploads/7962a59ac2c9a35e3419ff4fb9bfe6c1/0001-Improve-AppStream-description.patch) is a patch to improve Jami's AppStream description to give users a better idea of the package and list Jami's key features.
Cheers,
BrunoIteration 27Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/885Plugins: reload after changing preference2021-02-03T15:15:06ZAline Gondim SantosPlugins: reload after changing preferenceIteration 27Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/7AutoAnswer: automatic build2021-02-03T15:51:17ZAline Gondim SantosAutoAnswer: automatic buildAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/390audio: use Opus PLC and FEC2021-02-03T16:29:41ZAdrien Béraudaudio: use Opus PLC and FECAudio glitches are noticed in case of packet drop. Use Opus PLC and FEC to improve audio qualityAudio glitches are noticed in case of packet drop. Use Opus PLC and FEC to improve audio qualityIteration 27Pierre LespagnolPierre Lespagnol2021-04-01https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/423Packaging: check for statically build qt 5.14 for out .deb2021-02-03T16:42:14ZSébastien BlinPackaging: check for statically build qt 5.14 for out .debAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/267Plugins: split "always" preference by handler2021-02-03T19:05:47ZAline Gondim SantosPlugins: split "always" preference by handlerIteration 27Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/265Plugins: add EditText preference option2021-02-03T19:06:22ZAline Gondim SantosPlugins: add EditText preference optionIteration 27Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/266Plugins: add "always" preference2021-02-03T19:07:05ZAline Gondim SantosPlugins: add "always" preferenceIteration 27Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/52Plugin settings: parameters settings should be linked to the plugin line2021-02-03T19:07:37ZSébastien BlinPlugin settings: parameters settings should be linked to the plugin lineActually if there is multiple plugins, the settings are in a panel at the bottom of the page. It should be just after the selected pluginActually if there is multiple plugins, the settings are in a panel at the bottom of the page. It should be just after the selected pluginAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/230Code smell, packaging: do not include $${LRC}/src2021-02-03T19:09:54ZSébastien BlinCode smell, packaging: do not include $${LRC}/srcIf somebody install libringclient, it will be /usr/include/libringclient/ not /usr/include/libringclient/src so the build will fails. $${LRC} will link to the installed lrc anyway
Same for /build, as it will be /usr/libIf somebody install libringclient, it will be /usr/include/libringclient/ not /usr/include/libringclient/src so the build will fails. $${LRC} will link to the installed lrc anyway
Same for /build, as it will be /usr/libIteration 27Albert Babí OllerAlbert Babí Oller