savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-01-24T16:44:22Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/609Device info isCurrent issue2022-01-24T16:44:22ZMing Rui ZhangDevice info isCurrent issueWhen an account is created initially, the device info from the only device (current device) has the isCurrent set to false.When an account is created initially, the device info from the only device (current device) has the isCurrent set to false.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/489Camera occupied without active conversation2021-08-12T15:07:58Zm.eikCamera occupied without active conversation## Environment
- OS: Kubuntu 20.04
- Jami version: 202106061341
- What build you are using: dl.jami.net/nightly/ubuntu_20.04
## Steps to reproduce
I've noticed that as soon as I plug in my USB webcam, it is automatically occupied by J...## Environment
- OS: Kubuntu 20.04
- Jami version: 202106061341
- What build you are using: dl.jami.net/nightly/ubuntu_20.04
## Steps to reproduce
I've noticed that as soon as I plug in my USB webcam, it is automatically occupied by Jami (if it is already running) and can't be used with other applications. I have to quit Jami to be able to use the webcam otherwise. By occupied I mean it is active in the sense of recording video.
- Can you reproduce the bug: at will
- Steps:
1. Start Jami
2. Plug in USB webcam
- Actual result: Webcam becomes active and is blocked for other applications, it does not shut down on its own
- Expected result: Webcam should only be used when a video call is being started
## Additional information
Apart from this not being very useful, it is kind of creepy that Jami immediately starts "recording" video when it can. It does not happen if Jami is being started after the webcam is already plugged in, so i guess you won't see this on laptops but rather with pluggable USB cameras.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1286jami.net pages to update and enable translation2021-09-26T07:55:41Zovarijami.net pages to update and enable translation- [X] Homepage
- [X] Contribute
- [X] Blog
- [ ] Help
# Homepage
On the [Jami homepage](https://jami.net/) the string `Latency is reduced and transfer speeds are greatly increased thanks to the direct peer-to-peer connection.` is not s...- [X] Homepage
- [X] Contribute
- [X] Blog
- [ ] Help
# Homepage
On the [Jami homepage](https://jami.net/) the string `Latency is reduced and transfer speeds are greatly increased thanks to the direct peer-to-peer connection.` is not showing in Hungarian nor French. The string doesn't seem to be in Transifex either. Can this string please be added to Transifex and once translated be available on the Jami website?
Thank you
![image](/uploads/9ea117706dccabe2135c7920604654d1/image.png)
# Contribute
On the [Jami Contribute page](https://jami.net/contribute/), the following strings are not translated:
1. `Join the Jami discussion forum to discuss with other Jami users and developers, share your requests and ideas for Jami features, or get help about Jami.`
2. `Jami forum`
3. `Subscribe to the Jami mailing list, where you can report bugs, get help, or just follow the progress of the project.`
4. `Mailing list`
5. `Participate in IRC discussions on the #jami channel on Libera.Chat.`
6. `Libra.Chat webchat`
7. `Follow our Twitter feed @Jami_social or our Mastodon @jami@mstdn.io to learn about the important new features of the project.`
8. `Follow Us`
Thank you
![image](/uploads/0b073e580e8cc59a0a40f5c7f14fd389/image.png)
# Blog
On the [Jami Blog page](https://jami.net/tag/blog/), the following strings are not translated:
1. `A collection of 26 posts`
2. `7 min read`
Thank you
![image](/uploads/0a2b2f1b9771c312d1bf1e8bd9aafb54/image.png)
# Help
On the [Jami Help page](https://jami.net/help/), the following strings are not translated:
1. `During a call, right-click on the video call screen.`
Perhaps this section can be removed/updated as there is a button to share screen.
Thank you
![image](/uploads/5300ff197d72323335ee30da939b38a5/image.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/608ICE - add generic srflx candidates only if UPNP candidates are not available2021-08-17T20:05:30ZMohamed ChibaniICE - add generic srflx candidates only if UPNP candidates are not availableCurrently, (generic) srflx candidates generated using the account public address are always added regardless if UPNP candidates are available or not. Having duplicate srflx candidates is not useful, and even worse, it may reduce the chan...Currently, (generic) srflx candidates generated using the account public address are always added regardless if UPNP candidates are available or not. Having duplicate srflx candidates is not useful, and even worse, it may reduce the chance of UPNP candidates to succeed.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/607ICE - missing srflx candidates in answer2021-08-17T20:05:31ZMohamed ChibaniICE - missing srflx candidates in answerServer reflexive candidates are not added in call answer if UPNP is disabled. This can cause ICE media negotiation failure if the peer is behind a NAT with TURN enabled, and UPNP disabled/unavailable.
Setup:
Endpoint A
TURN enabled
UPNP...Server reflexive candidates are not added in call answer if UPNP is disabled. This can cause ICE media negotiation failure if the peer is behind a NAT with TURN enabled, and UPNP disabled/unavailable.
Setup:
Endpoint A
TURN enabled
UPNP disabled
Endpoint B
TURN disabled
UPNP disabled
A calls B.
Results: failed (notice the absence of srflx cand in B's SDP answer)
Expected: success (connection pair A:relay <-> B:prflx
ICE fails because the TURN server does not authorize connection from prflx candidates because they are unknown to it (they be authorized if the B add the address as a srflx canddiate).
Note that the call is successful if B calls A (because the srflx are included in the offer).Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1284Allow activation of camera in audio only mode.2021-08-08T19:58:51ZCross NastasiAllow activation of camera in audio only mode.I realize this sounds counterproductive, but the ability to switch to a video call from a voice only call would be greatly beneficial. This way, the call doesn't have to be restarted to switch to video/screen sharing mode.
Please let me...I realize this sounds counterproductive, but the ability to switch to a video call from a voice only call would be greatly beneficial. This way, the call doesn't have to be restarted to switch to video/screen sharing mode.
Please let me know how this suggestion is.
-Crosshttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/487addSwarmConversation incorrect mode2021-12-29T17:12:40ZSébastien BlinaddSwarmConversation incorrect mode`conversation::to_mode(details["mode"].toInt());` does an assumption from the daemon which is not true.
A mode is unknown when syncing, it will be ok after conversationReady`conversation::to_mode(details["mode"].toInt());` does an assumption from the daemon which is not true.
A mode is unknown when syncing, it will be ok after conversationReadyBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/605ICE/PJNATH - use different Ta timer for TCP candidates2021-09-08T14:05:59ZMohamed ChibaniICE/PJNATH - use different Ta timer for TCP candidatesThe current Ta timer (interval between two connectivity checks, see RFC-5245 for details) is set to 20ms and used for UDP and TCP candidates alike. RFC-5245 (section recommends using a less a higher value for non-real-time application (T...The current Ta timer (interval between two connectivity checks, see RFC-5245 for details) is set to 20ms and used for UDP and TCP candidates alike. RFC-5245 (section recommends using a less a higher value for non-real-time application (TCP/TLS connections in our case). Furthermore, newer ICE spec (RFC-8445), recommends a min value of 50ms for real-time applications.
The advantage of using a low Ta value (20ms) is to start the connectivity checks, but the drawback is a abrupt increase in bandwidth (as described in RFC-5245 and RFC-8445). The peak in bandwidth usage may be significant if the candidate list is large. The goal is to find a better trade-off between connection speed and bandwidth usage.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/488jami-qt does not start on Arch/GNOME2021-08-05T17:15:28ZIvan Shapovalovjami-qt does not start on Arch/GNOME### Versions
* jami-daemon 4.0.0.r2333.g3212ddf46-1
* libjamiclient (libringclient) 1.0.0.r1038.g110c8d8b-1
* jami-client-qt r582.a3aea50-1
* qt5 5.15.2
### Environment
Arch Linux, GNOME 40.3, Wayland session.
### Problem
`jami-qt` ...### Versions
* jami-daemon 4.0.0.r2333.g3212ddf46-1
* libjamiclient (libringclient) 1.0.0.r1038.g110c8d8b-1
* jami-client-qt r582.a3aea50-1
* qt5 5.15.2
### Environment
Arch Linux, GNOME 40.3, Wayland session.
### Problem
`jami-qt` immediately exits with exit code 0 and no error logging:
```
$ jami-qt; echo "rc=$?"
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
"notify server name: gnome-shell, vendor: GNOME, version: 40.3, spec: 1.2"
Destroying connectivity monitor
rc=0
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/604Video conf: bad mute status2021-08-05T19:41:06ZSébastien BlinVideo conf: bad mute status+ Alice is a rendez-vous
+ Bob joins
+ Carla joins
+ Bob is muted by a moderator
+ Bob leaves
+ Bob joins
# Expected result
+ Bob should not be shown as muted because it's not anymore
# Current
Bob is shown as muted+ Alice is a rendez-vous
+ Bob joins
+ Carla joins
+ Bob is muted by a moderator
+ Bob leaves
+ Bob joins
# Expected result
+ Bob should not be shown as muted because it's not anymore
# Current
Bob is shown as mutedAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/487Video conf: bad mute status2021-08-04T19:07:20ZSébastien BlinVideo conf: bad mute status+ Alice is a rendez-vous
+ Bob joins
+ Carla joins
+ Bob is muted by a moderator
+ Bob leaves
+ Bob joins
# Expected result
+ Bob should not be shown as muted because it's not anymore
# Current
Bob is shown as muted+ Alice is a rendez-vous
+ Bob joins
+ Carla joins
+ Bob is muted by a moderator
+ Bob leaves
+ Bob joins
# Expected result
+ Bob should not be shown as muted because it's not anymore
# Current
Bob is shown as mutedhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/486Profile picture: small improvments2021-08-16T20:56:04ZAndreas TraczykProfile picture: small improvments* Remove the "Select file" button during the camera picture-taking process
* Add missing cancel (x) button during the first step of the camera picture-taking process* Remove the "Select file" button during the camera picture-taking process
* Add missing cancel (x) button during the first step of the camera picture-taking processMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/485Drag and drop files from chatview and send to other contacts2023-05-19T14:50:07ZAndreas TraczykDrag and drop files from chatview and send to other contacts1. Direct send
2. No conversation selection1. Direct send
2. No conversation selectionhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/602Deadlock with sendBeacon2021-08-17T20:19:30ZSébastien BlinDeadlock with sendBeacon[gdb.txt](/uploads/e9900d59f519af011c3af4eec22deb0c/gdb.txt)[gdb.txt](/uploads/e9900d59f519af011c3af4eec22deb0c/gdb.txt)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1283Do not add [nightly] repos to sources.list.d2021-08-03T15:22:22ZIaroslav GridinDo not add [nightly] repos to sources.list.dCurrently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely...Currently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely to cause issues to me and adding repo and key is not necessarily wanted by repository uses.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/601ICE - disable aggressive nomination2021-09-02T15:00:33ZMohamed ChibaniICE - disable aggressive nominationMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/484Superposition of 2 contacts2021-12-22T20:38:31ZovariSuperposition of 2 contacts1. Call yourself, then end the conversation.
2. `Find a user or search for a conversation` and type a contact in your list, say `amarok` (but not yourself)<br>
![image](/uploads/3491ac8542ef2c695c658a23cad7ac61/image.png)
3. Click on the...1. Call yourself, then end the conversation.
2. `Find a user or search for a conversation` and type a contact in your list, say `amarok` (but not yourself)<br>
![image](/uploads/3491ac8542ef2c695c658a23cad7ac61/image.png)
3. Click on the contact<br>
![image](/uploads/d0574ea281da42fb8303ecbd905d4d6a/image.png)
4. Press the `×` which has the tooltip `Clear Text`<br>
![image](/uploads/dc6d045b25d8ac344076e9c1081b5186/image.png)
5. Bug: the first item in the list is an overlap of 2 contacts, i.e. yourself and amarok.<br>
a) Light theme<br>
![Light theme](/uploads/8e5a17b3ac3cd778b6d8fbb0dee0fd0f/image.png)<br>
b) Dark theme<br>
![Dark theme](/uploads/c86eb11dd94fd00a4d5b636d38c048ca/image.png)
Are you able to reproduce and fix?
Thank you
Jami-client-qt Version: 202106061341 deb edition<br>
Linux Mint 20.2 Cinnamonhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/600TrustRequest: add signal for conversationRequest removed, and ensure it's cor...2021-08-09T14:35:49ZSébastien BlinTrustRequest: add signal for conversationRequest removed, and ensure it's correctly syncedRelated to https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282Related to https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/599Account preferences: add preferences to send or not displayed status2021-08-09T13:30:43ZSébastien BlinAccount preferences: add preferences to send or not displayed statusFor now clients are doing their own logic. This should be moved into the daemon. This allow us to group code from differnt clients.For now clients are doing their own logic. This should be moved into the daemon. This allow us to group code from differnt clients.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/486Links surrounded by <> (e.g. "<https://git.jami.net>") are not linkified prop...2023-05-05T19:37:15ZMaxime DevosLinks surrounded by <> (e.g. "<https://git.jami.net>") are not linkified properly.I type "text \<https://git.jami.net> text" in the chat.
The following appears in the area above the input field:
text \<https://git.jami.net>; text
where "\<https://git.jami.net>;" is a hyperlink pointing to "\<https://git.jami.net>;...I type "text \<https://git.jami.net> text" in the chat.
The following appears in the area above the input field:
text \<https://git.jami.net>; text
where "\<https://git.jami.net>;" is a hyperlink pointing to "\<https://git.jami.net>;" (without the " quotes).
There are two problems here:
- the ";" should not be present
- the ">" should not be part of the link
I noticed "linkify" is used, and typing the same input in https://soapbox.github.io/linkifyjs/ results in properly linkified text. So maybe the bundled copy of linkify needs to be updated? Looking at this git repo, the copy of 'linkify' appears to be from 2016 and there has been a release of linkify in 2020 (v2.1.9).
I'm using "jami-gnome" (version 20210606.1.e2f9490 as packaged in Guix).
(Edit: apparently \<http://...> is Markdown mark-up, so I added a few \\, and now this text is formatted properly (including the <>).)