savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-08-18T19:49:25Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1288Initial audio mode2021-08-18T19:49:25ZovariInitial audio modePlease watch https://youtu.be/gGr-O3jEbLk?t=103 related to LiveWebinar
Initial audio mode
1. **Q&A – Participant questions**<br>
Only presenters can talk and participants can ask for permission to speak
2. **Meeting – Discussion mode**<...Please watch https://youtu.be/gGr-O3jEbLk?t=103 related to LiveWebinar
Initial audio mode
1. **Q&A – Participant questions**<br>
Only presenters can talk and participants can ask for permission to speak
2. **Meeting – Discussion mode**<br>
All participants can talk and are able to activate their audio and video by themselves
3. **Webinar – Presentation mode**<br>
Only presenters can talk and participants can listen
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/496Linked Devices: Unable to delete linked accounts. Solution: Please add a hori...2021-11-04T20:16:56ZovariLinked Devices: Unable to delete linked accounts. Solution: Please add a horizontal scroll barUnable to delete a linked account. The buttons to the far right can not be reached.
1. Should there be a horizontal scroll bar?
2. Should right-click on a device bring up the option to delete a linked device?
3. Should the delete button...Unable to delete a linked account. The buttons to the far right can not be reached.
1. Should there be a horizontal scroll bar?
2. Should right-click on a device bring up the option to delete a linked device?
3. Should the delete buttons be moved to the front or underneath the string?
![image](/uploads/224d0cd0ec26c2b17b689080fa3b9407/image.png)
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/495Settings: button label cut and string extends outside of container2021-10-29T09:17:36ZovariSettings: button label cut and string extends outside of container1. Open Settings
2. Advanced Account Settings
3. `Add default moderator` **Bug**: Should this button be wider as the button label has an ellipsis?
4. `Find a user or search for a conversation` **Bug**: string extends out of the box. Shou...1. Open Settings
2. Advanced Account Settings
3. `Add default moderator` **Bug**: Should this button be wider as the button label has an ellipsis?
4. `Find a user or search for a conversation` **Bug**: string extends out of the box. Should the dialog be made wider?
What do you think?
Thank you
![image](/uploads/84326fe956fc99348e23ba5e9adc3d7b/image.png)
cf. https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/301https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/494Change button label from `Delete account` to `Remove account` and add toolTip...2023-06-26T21:55:00ZovariChange button label from `Delete account` to `Remove account` and add toolTipText `Remove account from only this device`Should a toolTipText be added to the `Delete account` button?
This might help screen readers?
![image](/uploads/098f718ab73c2983b27afa22993d0a4b/image.png)
What do you think?
Thank youShould a toolTipText be added to the `Delete account` button?
This might help screen readers?
![image](/uploads/098f718ab73c2983b27afa22993d0a4b/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/493toolTipText `Display or hide advanced settings` → `Show advanced account sett...2021-12-16T20:56:19ZovaritoolTipText `Display or hide advanced settings` → `Show advanced account settings` and `Hide advanced account settings`Depending on whether `Advanced Account Settings` is shown or hidden, should the string be changed from `Display or hide advanced settings` and made into 2 strings being:
* `Hide advanced account settings`
* `Show advanced account setting...Depending on whether `Advanced Account Settings` is shown or hidden, should the string be changed from `Display or hide advanced settings` and made into 2 strings being:
* `Hide advanced account settings`
* `Show advanced account settings`
![image](/uploads/1cdf012b469357eb6b0f613d7b55b40c/image.png)
What do you think?
Thank you
Linux Mint 20.2 Cinnamon<br>
Jami-qt Version: 202108132052
cf. https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/459https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/492Issues on Beta2021-09-13T16:58:16ZMing Rui ZhangIssues on Betachatview:
- [x] Picture Preview on FilesToSendContainer (Ming)
- [x] TextArea text insert not replace (Ming)
- [x] sometimes missing avatars (Andreas)
- [x] chat plugins available in header for read-only convs
contact management
- [x] B...chatview:
- [x] Picture Preview on FilesToSendContainer (Ming)
- [x] TextArea text insert not replace (Ming)
- [x] sometimes missing avatars (Andreas)
- [x] chat plugins available in header for read-only convs
contact management
- [x] Banned contact list and ban contact functionalities (Ming)Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/105Guix packaging: allow jami-qt to run on non-Mesa systems2024-01-10T22:53:46ZMaxim CournoyerGuix packaging: allow jami-qt to run on non-Mesa systemsGuix applications cannot currently run on drivers not part of Mesa, such as the nvidia proprietary drivers or AMD ones.
To be truly universal, Guix applications should be able to run on such systems as well.
This basically requires fix...Guix applications cannot currently run on drivers not part of Mesa, such as the nvidia proprietary drivers or AMD ones.
To be truly universal, Guix applications should be able to run on such systems as well.
This basically requires fixing Mesa in Guix to use glvnd (see the upstream issue here: https://issues.guix.gnu.org/49847).https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/104Guix packaging: fix fonts issue2021-08-13T17:48:50ZMaxim CournoyerGuix packaging: fix fonts issueExplore if something can be done to improve the look and feel of jami-qt when packaged as a Guix pack (software bundle). Perhaps adding a font to the pack could be enough.Explore if something can be done to improve the look and feel of jami-qt when packaged as a Guix pack (software bundle). Perhaps adding a font to the pack could be enough.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/491AltGr (programmer's keyboard) does not work; possible Qt issue though2023-05-29T17:03:30ZbriestAltGr (programmer's keyboard) does not work; possible Qt issue though- OS: Windows 10 Home, version 21H1, build 19043.1165, Polish version, Polish programmer's keyboard (AltGr+letter)
EDIT: ah, I see there's separate project for Windows client, sorry for misplacement; I know no way though to move the bug...- OS: Windows 10 Home, version 21H1, build 19043.1165, Polish version, Polish programmer's keyboard (AltGr+letter)
EDIT: ah, I see there's separate project for Windows client, sorry for misplacement; I know no way though to move the bugreport between projects.
- Jami version: Maloya, 202106031831
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. In chat, press AltGr+[acelnoszx] (standard way to obtain Polish characters ąćęłńóśżź)
- Actual result: no reaction
- Expected result: a Polish character should be written
## Additional information
Writing the text elsewhere and pasting into chat works without problems. While I'm not entirely sure (we use Jami mostly for video calls, in addition it's my son's machine I rarely use), it was working OK before Qt version.
It MAY be related to [QTBUG-69317](https://bugreports.qt.io/browse/QTBUG-69317), but:
- it works OK in user search (that is, Polish chars can be written there)
- two other Qt apps installed on the machine (VLC and Stellarium) do not expose the problem.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/490QR code/share feature is not valid for the current account2022-03-23T22:12:20ZAndreas TraczykQR code/share feature is not valid for the current account## Steps to reproduce
1. change accounts
1. click the share button on the account selection combo box
2. the qr code shown will be the identity of the previously selected account## Steps to reproduce
1. change accounts
1. click the share button on the account selection combo box
2. the qr code shown will be the identity of the previously selected accounthttps://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 Santos