savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-09-07T19:23:24Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/665[JAMS] Revoke device on manager should inform clients2023-09-07T19:23:24ZSébastien Blin[JAMS] Revoke device on manager should inform clientsNew release 1Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/150[JAMS] Revoke device doesn't work2021-04-19T14:29:51ZSébastien Blin[JAMS] Revoke device doesn't workNew release 1Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/616Press and hold icon menu2021-09-26T08:49:20ZovariPress and hold icon menuThe menu which shows when the Jami icon is pressed and held (shown in the image below) is only the default `App info`
![Jami](/uploads/0491100c2e6602d4c2940ce879a9d049/Jami.png)
The menu which shows when the Skype icon is pressed and h...The menu which shows when the Jami icon is pressed and held (shown in the image below) is only the default `App info`
![Jami](/uploads/0491100c2e6602d4c2940ce879a9d049/Jami.png)
The menu which shows when the Skype icon is pressed and held (shown in the image below) has the default `App info` (in the top right) and:
* Open dialpad
* Recent chats
* New chat
* New call
![Skype](/uploads/dd5e600f9c3bf98e343030f1d260935c/Skype.png)
Should the Jami press and hold icon menu contain some options like Skype?
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/662Using Jami in LAN without Internet2019-12-05T20:58:44ZAvinash SonawaneUsing Jami in LAN without InternetHello!
Is it possible to use Jami in local area network (LAN) withuot Internet?
If yes then what are the Jami config changes the LAN nodes need to do?
Thanks!Hello!
Is it possible to use Jami in local area network (LAN) withuot Internet?
If yes then what are the Jami config changes the LAN nodes need to do?
Thanks!Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/613Wrong microphone used for audio and video call2021-12-29T21:27:04Zring userWrong microphone used for audio and video call- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the m...- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the microphone at the top of my smartphone. I didn't even notice there is a second microphone at that place before.
I would expect to be able to use the mike at the button of my phone.
In a normal call without Jami I can use the "normal" microphone at the button.
Another problem is, that during an video call I have to speak directly into that micro. If I'm looking at the video stream, I'm too far away from the mike so the other user can't hear me.
Settings:
- Mobile Data: enabled (but not used for the tests)
- HD-Video: enabled
- Hardware-Acceleration: enabled
- Use system contacts: disabled
- Normal phone calls via Jami: disabled
- Start Jami while booting: enabled
- Run Jami in background: enabledBackloghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/603Share multiple files at the time from sharing menu in other apps2024-03-05T13:49:25ZFrançois Naggar-TremblayShare multiple files at the time from sharing menu in other appsCurrently, Jami only appears as an option for sharing when there is a single file selected.Currently, Jami only appears as an option for sharing when there is a single file selected.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1052Improve conference creation2019-11-20T08:44:30ZSébastien BlinImprove conference creationActually to add a call to the conference, the user has to drag and drop the other call. This is bad, because the feature is hidden and can be improved a lot. Also, this behaviour make it impossible to merge a SIP call with a Jami call (w...Actually to add a call to the conference, the user has to drag and drop the other call. This is bad, because the feature is hidden and can be improved a lot. Also, this behaviour make it impossible to merge a SIP call with a Jami call (which is possible to do in the daemon).
# Idea
Use the same widget as the SIP transfer call (the dropdown), showing current calls on all enabled accounts + present contacts (because calling a non present contact is a non sense in our case). And just click on the wanted item to add it to the conference.
# TODO
- [ ] UI: create the dropdown showing active calls/conferences and present contacts (a treeview should be created for the user)
- [ ] LRC: refacto, and readd a collectionInterface to be able to create custom models like this one
- [ ] UI: The interface should be updated when new presence/calls
- [ ] Daemon: avoid automatic call holding when creating a new call
- [ ] LRC: modify joinCalls to be able to merge with calls from other accounts
- [ ] UI: add filter
- [ ] tests, tests, tests, tests.
# POC
https://review.jami.net/c/ring-client-gnome/+/12140
https://review.jami.net/c/ring-lrc/+/12141
![07-26-19-11_18_55](/uploads/98b56a26482fb8d74dc0401a3b011673/07-26-19-11_18_55.png)New release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/129[Bug] Cannot refuse trust request when account was a contact in the past2019-10-10T14:45:07ZMoritz Brunner[Bug] Cannot refuse trust request when account was a contact in the past**Platform:** x86_64
**OS:** Fedora 29
**Build:** based on eff973bd
**Prerequisites:** Jami client A having client B as contact, client B for sending test messages
**Steps to reproduce:**
1. In client A: Delete client B from ...**Platform:** x86_64
**OS:** Fedora 29
**Build:** based on eff973bd
**Prerequisites:** Jami client A having client B as contact, client B for sending test messages
**Steps to reproduce:**
1. In client A: Delete client B from contacts
2. In client B: Delete client A and restart Jami (necessary to avoid #130)
3. In client B: Send a trust request to client A
4. In client A: Try to refuse the contact request
**Expected behaviour:** Client A refuses the trust request
**Actual behaviour:** Nothing happensMoritz BrunnerMoritz Brunnerhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/128Multi device regression: file transfer doesn't work for all devices2019-08-29T14:44:19ZSébastien BlinMulti device regression: file transfer doesn't work for all devicesOnly file transfer seems a bit broken. Calls and text messages are ok.
# Reproduce step
Device A with account X, Device B,C with account Y
X send a file to Y, sometimes only one device (eg B) is receiving the file, the second can star...Only file transfer seems a bit broken. Calls and text messages are ok.
# Reproduce step
Device A with account X, Device B,C with account Y
X send a file to Y, sometimes only one device (eg B) is receiving the file, the second can start a ICE negotiation, but never receives the headers of the file.Iteration 14Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1051[bug] Account selector text not getting updated when opening conversation via...2020-10-05T17:17:50ZMoritz Brunner[bug] Account selector text not getting updated when opening conversation via desktop notification on GNOME client**Platform:** x86_64
**OS:** Fedora 29
**Build:** GNOME client based on commit 76b9e8f937c32c3b55aec026ab70c824d8bb308c in master branch
**Prerequisites:** A Jami client with two accounts and desktop notifications enabled, another ...**Platform:** x86_64
**OS:** Fedora 29
**Build:** GNOME client based on commit 76b9e8f937c32c3b55aec026ab70c824d8bb308c in master branch
**Prerequisites:** A Jami client with two accounts and desktop notifications enabled, another client to send test messages
**Steps to reproduce:**
1. Switch to account B
2. Send a test message to account A
3. Click on the "Open conversation" button that is part of the desktop notification
**Expected behaviour:** The message gets loaded in the chatview and the text in the account selector gets updated to account A.
**Actual behaviour:** The message gets loaded but the account selector still shows account B.
**I don't know whether this bug exists on other clients.**Moritz BrunnerMoritz Brunnerhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/646[bug] Account selector text not getting updated when opening conversation via...2019-07-22T17:15:11ZMoritz Brunner[bug] Account selector text not getting updated when opening conversation via desktop notification on GNOME client**Platform:** x86_64
**OS:** Fedora 29
**Build:** GNOME client based on commit 76b9e8f937c32c3b55aec026ab70c824d8bb308c in master branch
**Prerequisites:** A Jami client with two accounts and desktop notifications enabled, another ...**Platform:** x86_64
**OS:** Fedora 29
**Build:** GNOME client based on commit 76b9e8f937c32c3b55aec026ab70c824d8bb308c in master branch
**Prerequisites:** A Jami client with two accounts and desktop notifications enabled, another client to send test messages
**Steps to reproduce:**
1. Switch to account B
2. Send a test message to account A
3. Click on the "Open conversation" button that is part of the desktop notification
**Expected behaviour:** The message gets loaded in the chatview and the text in the account selector gets updated to account A.
**Actual behaviour:** The message gets loaded but the account selector still shows account B.
**I don't know whether this bug exists on other clients.**https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/602When the Jami android app uses a "DHT proxy" host-name different than the def...2020-10-28T18:39:26ZCarloWhen the Jami android app uses a "DHT proxy" host-name different than the default one it does not connect.Bug report
---------------
## Test environment
Android mobile setup:
- Ring version: 20190706-01
- Device model:
- Android version: 7.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the...Bug report
---------------
## Test environment
Android mobile setup:
- Ring version: 20190706-01
- Device model:
- Android version: 7.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: yes at will.
The Jami app default/preset proxy server connection string is "dhtproxy.jami.net:[80-100]", with [80-100] being a range of possible service ports .
- Steps:
1. The current IP address of of dhtproxy.jami.net resolved with nslookup is 54.36.178.20 .
2. Enabling the use of "dhtproxy.jami.net:[80-100]" the jami account goes online correctly.
3. Making a traceroute --resolve-hostnames dhtproxy.jami.net, on a Linux host, I get at the end of the trace list a name alias of the same ip (54.36.178.20) "ns3102173.ip-54-36-178.eu". I can make the same using an app ("Ping & Net") directly on the mobile and I obtain the same results.
4. Using nslookup I verify that the two host names dhtproxy.jami.net and ns3102173.ip-54-36-178.eu resolve to the same ip : 54.36.178.20 . Also on the Android mobile I obtain the same results using the app "Ping & Net".
5. If on the android mobile I point Firefox to the url http://dhtproxy.jami.net or to http://ns3102173.ip-54-36-178.eu I get the same dhtproxy report JSON text: this means that the two host names can be used to open at least the same port 80 \`web page\`.
6. In the Jami application I substituted the dafault/preset host namedhtproxy.jami.net with it's alias ns3102173.ip-54-36-178.eu, I obtain the connection string "ns3102173.ip-54-36-178.eu:[80-100]"; doing so the Jami account no more connects. It seems quite that "the application" is not resolving the IP address for the new host name or it cuts out any other server name to use/resolve different than dhtproxy.jami.net.
7. Using directly the ip address in the connection string makes Jami to connect : "54.36.178.20:[80-100]" .
- Actual result: the Jami Android OS app does not connect to a "DHT proxy" string that has a literal hostname different than "dhtproxy.jami.net". It does connect if the "DHT proxy" is identified using its IP address .
- Expected result: the the Jami Android OS app should connect with any "DHT proxy" using in the connection string its DNS name to be resolved.
## Additional information
I encountered this bug verifying the connection to an OpenDHT (dhtnode) instance I setup; using this setup the Jami app connects to the "DHT proxy" from the Internet only when using the the IP host number in the connection string.
OpenDHT instance, compiled from source baseline version 1.10.0 (https://github.com/savoirfairelinux/opendht.git), running on Linux OS.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1048unable to open account settings2020-11-20T00:14:55ZEdmund Laugassonunable to open account settingsUsing 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Jami built on 2019-06-29 05:14:54 UTC.
When opening *Settings* then *Account* part is not opening. Also cannot see the PIN needed to log in at smartphone (Android). Also canno...Using 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Jami built on 2019-06-29 05:14:54 UTC.
When opening *Settings* then *Account* part is not opening. Also cannot see the PIN needed to log in at smartphone (Android). Also cannot export settings. When trying to open then nothing happens. If any other choice is active then clicking on *Account* does show that previous one but not *Account* part.https://git.jami.net/savoirfairelinux/jami-project/-/issues/643import in smartphone2019-07-12T20:44:40ZEdmund Laugassonimport in smartphoneCannot find a way to get appropriate PIN in desktop client in order to log into Android app. As mentioned also at #642 - there cannot be opened account settings. Using 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Android 9 wit...Cannot find a way to get appropriate PIN in desktop client in order to log into Android app. As mentioned also at #642 - there cannot be opened account settings. Using 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Android 9 with [Jami app](https://play.google.com/store/apps/details?id=cx.ring&hl=en_US). Installed Jami first in computer and now would like to use it also in smartphone.
Same issue [seems to be here](https://privsecurity.wordpress.com/2019/01/11/jami-net/).https://git.jami.net/savoirfairelinux/jami-project/-/issues/642unable to open account settings2019-07-17T22:52:40ZEdmund Laugassonunable to open account settingsUsing 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Jami built on 2019-06-29 05:14:54 UTC.
When opening *Settings* then *Account* part is not opening. Also cannot see the PIN needed to log in at smartphone (Android). Also canno...Using 64-bit Linux Mint 19.1 MATE (based on Ubuntu 18.04) and Jami built on 2019-06-29 05:14:54 UTC.
When opening *Settings* then *Account* part is not opening. Also cannot see the PIN needed to log in at smartphone (Android). Also cannot export settings. When trying to open then nothing happens. If any other choice is active then clicking on *Account* does show that previous one but not *Account* part.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/597unify adding/searching contact ui2020-11-10T19:56:10ZMohamed Fenjirounify adding/searching contact uiThe bottom right button on Jami main page do the same function as the searching scope at the top right corner. I think this should be unified to one circle bottom right corner '+' button. This would reduce confusion in the user experienc...The bottom right button on Jami main page do the same function as the searching scope at the top right corner. I think this should be unified to one circle bottom right corner '+' button. This would reduce confusion in the user experience of jami.Rayan OsseiranRayan Osseiranhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/593Feature Request: Update VCard Occasionally2020-10-27T19:41:42ZvindicatorrFeature Request: Update VCard OccasionallyBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190629-01
- Device model: LG-Volt LS740
- Android version: 6.0 LineageOS 13
- What build you are using: Play St...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20190629-01
- Device model: LG-Volt LS740
- Android version: 6.0 LineageOS 13
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Create an account in Gnome
2. Create an account on Android
3. Add contact on Android (used QR code)
4. Accept request in Gnome
- Actual result: For my peer contact's identity, all I get is "ring:XXXXX..."
- Expected result: I see my peer contact's username instead of "ring:XXXXX..."
## Additional information
I figured I'd just bring this back up since it hasn't been addressed/dealt-with in quite some time. Something I had brought up in IRC and the ML.
*I know it currently is only sent with calls* That's why I'm calling this a feature request since it's currently behaving as it was programmed to, hence "not a bug".
My suggestion: When the application is started for any client, it initially seeks out the peers by sending a timestamp for sender's vcard as well as the timestamp for each peer's vcard.
Each peer compares the timestamp they have for the sender's vcard with what the sender just sent. If it's older, the peer responds back with the timestamp for THEIR OWN vcard as well as a request for the sender's updated vcard.
If the vcard they have for the sender is already up to date, they just return their vcard if it's newer than the timestamp the sender sent to them regarding the peer's vcard timestamp, otherwise they just send an ack (EDIT0).
That's only for when the application is started.
If a client makes a change to their vcard, they automatically send out the update to each peer.
It's my belief that with this methodology, the vcard will always remain up to date.
Again, it's the only thing that's been keeping me from getting my F&F to use this as their IM. Other than that, even though I haven't taken the testing much further, it's getting nicer and nicer and the latest test resulted in NO lost messages, which used to be another huge issue.
The easier option to implement before going with a vcard revamp is adding a superseding field like nickname that a client can set for each peer.
That way, the vcard will still be viewable, yet the history will always show the nickname if it's set.
EDIT0: Correct my thought.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-project/-/issues/636Option to toggle automatic volume control2020-11-10T19:54:00ZNoNameOption to toggle automatic volume controlHello! I've noticed that in Linux Mint 19.1 the microphone volume level keeps adjusting on its own. The problem is, it sets itself to a low level and it becomes difficult for the other person to hear. I keep trying to readjust it during ...Hello! I've noticed that in Linux Mint 19.1 the microphone volume level keeps adjusting on its own. The problem is, it sets itself to a low level and it becomes difficult for the other person to hear. I keep trying to readjust it during video calls but after a few seconds it sets itself back to about 20%. The computer this was tested on has a AMD Ryzen processor and the OS is running on kernel 5.0.19.
Thank you for your time. https://git.jami.net/savoirfairelinux/jami-project/-/issues/634Missing voice message feature2019-12-05T21:01:46ZAnth0rxMissing voice message featureCurrently, I am missing a voice message feature similar to those in other IMs like Telegram.Currently, I am missing a voice message feature similar to those in other IMs like Telegram.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/207Notifications for new messages don't always arrive2023-05-05T19:44:17ZDimitar DobrevNotifications for new messages don't always arriveIn addition, there's no badge above the application in the dock with the number of unread messages.In addition, there's no badge above the application in the dock with the number of unread messages.