savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2019-06-20T12:15:44Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/880No ring item in appindicator on Ubuntu 18.042019-06-20T12:15:44ZRoberto ResoliNo ring item in appindicator on Ubuntu 18.04The appindicator item for ring is no more present after upgrading to latest Ubuntu LTS (18.04 "bionic"). I'm using ring repo:
`deb https://dl.ring.cx/ring-nightly/ubuntu_18.04/ ring main`The appindicator item for ring is no more present after upgrading to latest Ubuntu LTS (18.04 "bionic"). I'm using ring repo:
`deb https://dl.ring.cx/ring-nightly/ubuntu_18.04/ ring main`Next major releasehttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/372smartlist: contact list reordered when sending messages2018-08-06T18:35:06ZHugo Lefeuvresmartlist: contact list reordered when sending messages**Affects**: Latest LRC + GNU/Linux GNOME client
**How to reproduce**:
1. Set up a Ring account with several contacts where the conversation is empty (completely empty, clear history was called)
2. Open the topmost conversation and sen...**Affects**: Latest LRC + GNU/Linux GNOME client
**How to reproduce**:
1. Set up a Ring account with several contacts where the conversation is empty (completely empty, clear history was called)
2. Open the topmost conversation and send messages while looking at the conversations list: the order of empty conversations changes
This makes the smartlist blinky, we should really avoid that.Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/868Reworking notifications system2018-07-31T19:43:56ZSébastien BlinReworking notifications system`ringnotify` contains a lot of old code and don't use new LRC models for now. This needs some work to update this file.
For now, I see 3 types for notifications:
1. **Call notifications**, opened when an incoming call is here and close...`ringnotify` contains a lot of old code and don't use new LRC models for now. This needs some work to update this file.
For now, I see 3 types for notifications:
1. **Call notifications**, opened when an incoming call is here and closed at the end of the call.
2. **Request notifications**: opened when a new trust request arrives and closed when the user accepts/refuse/block or just open the conversation.
3. **Chat notifications**: arrives with new interactions and if the current conversation is different or the client not focused. Closed by Gnome or when the conversation is opened.
If the conversation is already activated but not used for x minutes, the notification should still popNext major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/21SIP register fails: No username on digest authentication2024-02-08T18:58:54ZAlba MendezSIP register fails: No username on digest authenticationThis bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register....This bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register.
My Asterisk server sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>;tag=as3f952c47
...
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0074f5d0"
And Ring then sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>
...
Authorization: Digest , realm="asterisk", nonce="0074f5d0", uri="sip:10.139.205.101", response="631415fcf3715907a48f11fec1e6a880", algorithm=MD5
i.e. notice the space and comma after `Digest`
ring-daemon version 2018-07-07. Bug could be on upstream, for some reason username is not set on `pjsip/src/pjsip/sip_auth_client.c` when adding the Authorization header, [header printed here](https://github.com/asterisk/pjproject/blob/106ec876a371b57bb3db8231a55cb5f368e6266b/pjsip/src/pjsip/sip_auth_msg.c#L73).Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/368Database: AccountID should be used to identify account instead URI2018-12-05T18:17:03ZSébastien BlinDatabase: AccountID should be used to identify account instead URIFor example if the device certificate is removed the account ID is the only thing accessible to identify an account. So we should use this.For example if the device certificate is removed the account ID is the only thing accessible to identify an account. So we should use this.Swarm-chatKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/511contacts can't be deleted2018-10-18T02:03:53ZRing Thingcontacts can't be deletedV 20180629 play
A 7.1.2
Installed, created an account without registering, and scanned a new contact, sent a message.
Deleting the conversation in the main view (long press) does not remove it.
After the attempt, the name of the conta...V 20180629 play
A 7.1.2
Installed, created an account without registering, and scanned a new contact, sent a message.
Deleting the conversation in the main view (long press) does not remove it.
After the attempt, the name of the contact is deleted, but the contact stays with only the ring:xyz... shown.
With the f-droid version, it even happens that contacts appear twice after attempting to delete.Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/9dtmf tones do not work2024-03-08T19:26:14ZJami Botdtmf tones do not workIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daem...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daemon since a while ago. Its also possible that SIP tones work, but are not accepted in all cases on the other end?</p>
<p>Also the gnome UI is not very nice for sending them, so could also be an input issue.</p>SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/813smartlist: improve support for Display names with emoji2023-05-26T13:59:33ZHugo Lefeuvresmartlist: improve support for Display names with emojiIf a display name contains Emojis, the default avatar contains a question mark '?'.
![Screenshot_from_2018-06-01_16-49-34](/uploads/97e89e4d785cbb9f29113a1382774195/Screenshot_from_2018-06-01_16-49-34.png)
**Expected behaviour:**
It s...If a display name contains Emojis, the default avatar contains a question mark '?'.
![Screenshot_from_2018-06-01_16-49-34](/uploads/97e89e4d785cbb9f29113a1382774195/Screenshot_from_2018-06-01_16-49-34.png)
**Expected behaviour:**
It should contain the default avatar, like this one:
![Screenshot_from_2018-06-01_16-55-43](/uploads/f80dc27208c84d79001a7fbcbd07757c/Screenshot_from_2018-06-01_16-55-43.png)Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/362SIP: relink to blind and save transfer2018-06-11T23:12:16ZSébastien BlinSIP: relink to blind and save transferWe need to be able to transfer SIP calls.We need to be able to transfer SIP calls.SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/803SIP: Add a transfer button in currentcallview2018-06-11T23:12:34ZSébastien BlinSIP: Add a transfer button in currentcallview+ [x] Add a transfer button in the callview linked to a context menu
+ [x] In this context menu, we should see current conversations and if we click on an item, perform a transfer (blind or not if a call id)
+ [x] Also in this context me...+ [x] Add a transfer button in the callview linked to a context menu
+ [x] In this context menu, we should see current conversations and if we click on an item, perform a transfer (blind or not if a call id)
+ [x] Also in this context menu, we should be able to search a new number and perform a blind transfer.SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/801Feature request: Display Emojis stand alone2022-02-18T16:48:07ZHugo LefeuvreFeature request: Display Emojis stand aloneIn the GNU/Linux GNOME client, Emojis are always displayed with background.
This is not the case on all clients, for example the Android app removes the background when a single Emoji is sent:
![samsung_s8_mockup](/uploads/c6a916ec91f9...In the GNU/Linux GNOME client, Emojis are always displayed with background.
This is not the case on all clients, for example the Android app removes the background when a single Emoji is sent:
![samsung_s8_mockup](/uploads/c6a916ec91f98217159061501725efea/samsung_s8_mockup.png)
It would be great to do that in the GNU/Linux GNOME client too.Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/800Feature request: Emoji picker2021-05-03T17:08:20ZHugo LefeuvreFeature request: Emoji pickerThe only way to insert emojis currently is to open a web browser, search for Emojis and copy&paste in the GNU/Linux GNOME client. This is way too long.
Please, provide an Emoji Picker.
![IEppg](/uploads/44a6c05b47cca2d9b1034ba791a29426...The only way to insert emojis currently is to open a web browser, search for Emojis and copy&paste in the GNU/Linux GNOME client. This is way too long.
Please, provide an Emoji Picker.
![IEppg](/uploads/44a6c05b47cca2d9b1034ba791a29426/IEppg.png)Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/799Emojis not displayed on systems not providing an Emoji font2021-07-09T17:48:42ZHugo LefeuvreEmojis not displayed on systems not providing an Emoji fontCurrently Emojis are only displayed correctly if an Emoji font is present on the system. Otherwise they look very crappy (black and white, barely readable, not what people usually call "Emoji").
It would be very nice if the GNU/Linux GN...Currently Emojis are only displayed correctly if an Emoji font is present on the system. Otherwise they look very crappy (black and white, barely readable, not what people usually call "Emoji").
It would be very nice if the GNU/Linux GNOME client was able to display Emojis regardless of the system.Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/798chatview: Unable to display some emojis2019-11-12T20:18:01ZHugo Lefeuvrechatview: Unable to display some emojisThe chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open...The chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open another client (macOS, Android), and send a fox 🦊 (U+1F98A) Emoji to the GNU/Linux GNOME client.
2. The GNU/Linux GNOME client fails to display received Emoji. Only the background is displayed.
This may be a bug in the dependency chain.Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/490Some emojis are not displayed stand-alone (emoji-only messages)2018-06-11T21:18:00ZHugo LefeuvreSome emojis are not displayed stand-alone (emoji-only messages)Emojis are supposed to be displayed stand-alone (without background), but this feature is broken with some specific emojis, e.g. 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
I suspect bad handling of Emoji 3.0 (Unico...Emojis are supposed to be displayed stand-alone (without background), but this feature is broken with some specific emojis, e.g. 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
I suspect bad handling of Emoji 3.0 (Unicode 9.0).Full Emoji support 🚩Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/360Load current calls from daemon2018-10-18T02:03:08ZSébastien BlinLoad current calls from daemonRing-daemon can be launched separately from clients.
So, a call can be received before launching a client. LRC should retrieve these calls from the daemon.
The major part of this patch is already done, see https://gerrit-ring.savoirfai...Ring-daemon can be launched separately from clients.
So, a call can be received before launching a client. LRC should retrieve these calls from the daemon.
The major part of this patch is already done, see https://gerrit-ring.savoirfairelinux.com/#/c/8188/
The idea is to take this patch and finish it.Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/780Dates in contact list do not respect locale settings2018-08-10T18:19:04ZJami BotDates in contact list do not respect locale settingsIssue generated from Tuleap's migration script.
**Originally submitted by: Denis (sciamano)**
\* Environment:
actual package from the debian repository + ru\_RU | de\_DE | etc locale settings (i.e. any not en\_US locale) in the deskto...Issue generated from Tuleap's migration script.
**Originally submitted by: Denis (sciamano)**
\* Environment:
actual package from the debian repository + ru\_RU | de\_DE | etc locale settings (i.e. any not en\_US locale) in the desktop environment
\* Reproduce steps:
chat with a contact to get some history
\* Expected result:
in the contact list, the date of the last conversation have to be formatted according to the locale settings.
\* Actual result:
the date of the last conversation does not follow the locale setting and is shown in a hardcoded "MM/DD/YY" format. (see the red mark on the attached picture)
at the same time, the date format in the chat window is already correct and follows the locale (see the green marks)
![ring](/uploads/f11587d96754861e10f8f0b38957dabd/ring.png)Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/452Linux Mint should be added to make-ring.py builder2018-07-16T18:56:07ZJami BotLinux Mint should be added to make-ring.py builderIssue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
Linux Mint is popular GNU/Linux distro based on Ubuntu and Debian, so you can build Ring easily on it, by modifying make-ring.py file like ...Issue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
Linux Mint is popular GNU/Linux distro based on Ubuntu and Debian, so you can build Ring easily on it, by modifying make-ring.py file like at attached picture. This should be default feature.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/442Encryption : having an alternative2023-11-20T14:24:00ZJami BotEncryption : having an alternativeIssue generated from Tuleap's migration script.
**Originally submitted by: (daoumilseitek)**
I suggest having an alternative way of encryption. While GnuTLS is good, you never know what can happen with cryptography. Wether it's implem...Issue generated from Tuleap's migration script.
**Originally submitted by: (daoumilseitek)**
I suggest having an alternative way of encryption. While GnuTLS is good, you never know what can happen with cryptography. Wether it's implementation, protocol or maths that are broken, it is generally hard to make a fix and might take a while.
I would recommend NaCl crypo lib, as it seems reliable (elliptic curves and all these fancy things) :
https://en.wikipedia.org/wiki/NaCl\_(software)
What about retro-compatibility though ? I think we can have some retro-compatible key sharing, such as :
gnutls\_key:nacl\_key
and one can choose to use either one or let the default be chosen depending on the security context, old versions of software can still use just
gnutls\_keySwarm-chathttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/708Gnome client UI resets to main screen when account connection is re-established2018-07-17T16:43:36ZJami BotGnome client UI resets to main screen when account connection is re-establishedIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (ver...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (version tested: built from sources as of 2018-02-08)
\* Reproduce steps:
1. Open the Gnome client.
2. Enter or create a new chat conversation.
3. Manually disconnect then connect again the network (use the Ethernet cable, the Wi-Fi killswitch, etc.)
4. Notice that when daemon notices about the disconnection, the client redraws its UI to show the main screen and the user is kicked out of its current conversation view.
\* Expected result:
The view should be maintained to the current conversation. If the network problem persists (after a threshold of say, 5 seconds), a visual hint should notify the user that there is currently no connectivity.
\* Actual result:
The user is disoriented/confused since the UI changes under their feet without any action on their part.Next major releaseHugo LefeuvreHugo Lefeuvre