savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-07-16T18:41:52Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/428add participant to conference: search is case sensitive2021-07-16T18:41:52ZGuillaume Helleradd participant to conference: search is case sensitive![Capture_d_écran_du_2021-05-20_11-23-00](/uploads/0b9b4b6a438b3214e941029dc9099f7b/Capture_d_écran_du_2021-05-20_11-23-00.png)
![Capture_d_écran_du_2021-05-20_11-23-19](/uploads/7675a5a43a8650a04effd0ad28156945/Capture_d_écran_du_2021-0...![Capture_d_écran_du_2021-05-20_11-23-00](/uploads/0b9b4b6a438b3214e941029dc9099f7b/Capture_d_écran_du_2021-05-20_11-23-00.png)
![Capture_d_écran_du_2021-05-20_11-23-19](/uploads/7675a5a43a8650a04effd0ad28156945/Capture_d_écran_du_2021-05-20_11-23-19.png)
the filter should case insensitiveBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/412UI fluidity is coupled with the load of the daemon2021-12-29T17:15:09ZMaxim CournoyerUI fluidity is coupled with the load of the daemon## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we wil...## Describe your environment
Please specify the following:
- OS: Guix System
- Jami version: jami-qt 20210326.1.cfba013
- What build you are using: as packaged in Guix
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Disable video acceleration to ensure high load in the daemon.
2. Join a video conference (rendezvous point)
- Actual result:
The UI elements are very slow to refresh. Having the overlay display, for example to make the mute button appear, may take several seconds. Opening the chat view may show a blank square for a long time before its content appear.
- Expected result:
The UI should remain fluid, running asynchronously from the daemon, like the GNOME client, which doesn't suffer from this problem.
## Additional information
Here's a screenshot of the chat view failing to refresh (it took several minutes for it to display its content!):
![chat](/uploads/0652a89288a7050627aa483c38c1a9dc/chat.png)Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/540Analyze opened files2021-12-29T17:16:32ZSébastien BlinAnalyze opened filesWe need to check how many opened files and what files are opened
+ per account
+ per calls
+ per calls with 10 participants
+ per calls with 20 participants
+ per calls with 30 participants
+ per calls with 40 participantsWe need to check how many opened files and what files are opened
+ per account
+ per calls
+ per calls with 10 participants
+ per calls with 20 participants
+ per calls with 30 participants
+ per calls with 40 participantsBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/401Go over share screen area2021-11-26T22:14:28ZMing Rui ZhangGo over share screen areaBacklogMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/537Conference layout seems broken after 25+ participants2021-12-21T21:11:59ZSébastien BlinConference layout seems broken after 25+ participants# Scenario
+ Start a conference with 25 participants
+ Another participant join
# Expected
+ The layout should be updated
# Current result
Seems blocked to the previous view# Scenario
+ Start a conference with 25 participants
+ Another participant join
# Expected
+ The layout should be updated
# Current result
Seems blocked to the previous viewBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/396Could not re-add deleted contact from invites2021-08-20T21:04:36ZMing Rui ZhangCould not re-add deleted contact from invitesBacklogMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/287Conference: display avatar of audio participants2023-05-05T19:44:03ZGuillaume HellerConference: display avatar of audio participantsBacklogKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/135Conference: display avatar of audio participants2023-12-18T16:44:03ZGuillaume HellerConference: display avatar of audio participantsBacklogKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/530Medias: Big lag when a lot of person leave the conference2021-12-23T21:46:55ZSébastien BlinMedias: Big lag when a lot of person leave the conference# Scenario
+ Be in a rdv with 10 people
+ Every body leave except 2 people
# Current result
+ Big lag on video
# Expected
+ No lag# Scenario
+ Be in a rdv with 10 people
+ Every body leave except 2 people
# Current result
+ Big lag on video
# Expected
+ No lagBackloghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/92Add raspbian (armhf/arm64) packages2021-12-29T17:18:40ZAmin BandaliAdd raspbian (armhf/arm64) packagesWe do not provide a raspbian package anymore due to complications with cross-building our Qt package (`libqt-jami`), now used for building both the client library (`lrc`) and the Qt client (`jami-qt`). Since `lrc` is also built using `l...We do not provide a raspbian package anymore due to complications with cross-building our Qt package (`libqt-jami`), now used for building both the client library (`lrc`) and the Qt client (`jami-qt`). Since `lrc` is also built using `libqt-jami`, we cannot continue providing a `jami-gnome` raspbian package either.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/529SIP: refactor SIPCall and related classes and routines2023-09-29T10:00:20ZMohamed ChibaniSIP: refactor SIPCall and related classes and routinesThe goal of the refactor is to improve stability (prevent crashes and deadlocks), clarify interactions between SIPCall class with other classes/routines. Three main changes will be introduced in this activity:
**1- Add an interface to r...The goal of the refactor is to improve stability (prevent crashes and deadlocks), clarify interactions between SIPCall class with other classes/routines. Three main changes will be introduced in this activity:
**1- Add an interface to report PJSIP events**\
The use of this interface is to give limited access to SIPCall from SipVoipLink class and related routines.
All processing involving SIPCall properties (such as SDP and RTP sessions) should be done as much as possible within SIPCall class to enhance encapsulation.
**2- Use the same thread (SIP thread) for SipVoIPLink events hander and SIP Transport**\
All events (hopefully) reported by PSIP lib will be reported on the same thread, which will help reduce data race on SIPCall class in particular.
**3- Run most of the task involving SIPCall on the same thread**
Dispatch tasks (when possible) on the SIP thread. Note that some calls still need to access SIPCall synchronously (getters in particular).BacklogMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/524Swarm: redo file transfer logic [Wait for android implem]2022-11-18T20:22:36ZSébastien BlinSwarm: redo file transfer logic [Wait for android implem]+ sendFile() only adds a message to the conversation, but don't send any request
+ other peers download files or not
+ logic is the same as askForTransfer
+ URI should supports parameters like from/to to download a block
+ If a socket ...+ sendFile() only adds a message to the conversation, but don't send any request
+ other peers download files or not
+ logic is the same as askForTransfer
+ URI should supports parameters like from/to to download a block
+ If a socket is cut, it should retry to download
+ Add ratio infos (peers transfer in progress)
# TODO
~~+ rebase unit tests~~
~~+ Download file return TID file~~
~~+ relink cancelTransfer~~
~~+ shutdown channel avoid write both sides.~~
~~+ start offset support~~
~~+ remove istringstream~~
~~+ cache waiting transfers~~
~~+ add re-ask mechanism~~
~~+ Prepare patch to delete all deprecated code~~
~~+ Relink infos()~~
~~+ Check that all test builds~~
~~+ Move transferManager in conversation and logic from jamiaccount~~
~~+ rebase re-ask~~
~~+ sendProfile()~~
~~+ patch to remove all old logic~~
~~+ fileInfo (conv, interactionId, info)~~
~~+ cleanup code~~
~~+ add tests (info out/in ; retry ; info ; bytesProgress)~~
~~+ Update API~~Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/375video lag during screen sharing (and call)2021-12-29T18:50:22ZGuillaume Hellervideo lag during screen sharing (and call)Scenario:
- do call between 2 participants
- participant A on linux qt, other participant B shares his screen
- after few minutes, there is a delay in the video seen by A (no audio delay)Scenario:
- do call between 2 participants
- participant A on linux qt, other participant B shares his screen
- after few minutes, there is a delay in the video seen by A (no audio delay)Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/517Remove hacky underlyingIce()2021-12-29T18:52:33ZSébastien BlinRemove hacky underlyingIce()underlyingIce() is hacky. This method should not exists and the chain should be clean.
However this issue is quite complex, because the socket can be cut pretty everywhere in the chain and it should correctly close all the layer.
The m...underlyingIce() is hacky. This method should not exists and the chain should be clean.
However this issue is quite complex, because the socket can be cut pretty everywhere in the chain and it should correctly close all the layer.
The most hacky part is in TlsSocketEndpoint::ImplBackloghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1225Remove hacky underlyingIce()2021-04-14T19:57:20ZSébastien BlinRemove hacky underlyingIce()underlyingIce() is hacky. This method should not exists and the chain should be clean.
However this issue is quite complex, because the socket can be cut pretty everywhere in the chain and it should correctly close all the layer.
The m...underlyingIce() is hacky. This method should not exists and the chain should be clean.
However this issue is quite complex, because the socket can be cut pretty everywhere in the chain and it should correctly close all the layer.
The most hacky part is in TlsSocketEndpoint::ImplBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/368Remove unnecessary c++ singleton classes2021-07-16T19:42:21ZAndreas TraczykRemove unnecessary c++ singleton classesBacklogMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/365plugins: setting in handler activation popup2023-04-07T18:38:18ZAline Gondim Santosplugins: setting in handler activation popupFollow directives from: https://www.sketch.com/s/164f7656-95fd-48d0-9d19-c2aaf211b5c3Follow directives from: https://www.sketch.com/s/164f7656-95fd-48d0-9d19-c2aaf211b5c3BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/358plugins: create handlers activation order UI2023-09-15T19:40:39ZAline Gondim Santosplugins: create handlers activation order UIBacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/465plugins: set handlers activation order api2023-05-05T19:37:23ZAline Gondim Santosplugins: set handlers activation order apiThere may be API changes allowing UI to change handlers activation order.There may be API changes allowing UI to change handlers activation order.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/506plugins: set handlers activation order2021-04-01T12:53:01ZAline Gondim Santosplugins: set handlers activation orderUser should be able to change the order each handler is called from the observable notify.User should be able to change the order each handler is called from the observable notify.BacklogAline Gondim SantosAline Gondim Santos