jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/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-project/-/issues/714Conference: no more sound when conf is paused/unpaused2020-10-05T17:27:23ZGuillaume HellerConference: no more sound when conf is paused/unpausedHow to reproduce:
1. Launch a conference (audio or video) with at least 3 participants
2. Host: pause the conference
3. Host: unpause the conference
Issue: no more sound once the conference is unpaused.
For info, sound comes back wh...How to reproduce:
1. Launch a conference (audio or video) with at least 3 participants
2. Host: pause the conference
3. Host: unpause the conference
Issue: no more sound once the conference is unpaused.
For info, sound comes back when only 2 participants remain in the conversation.New release 1Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/718connectivity issues with file transfers2020-08-25T13:48:39ZGuillaume Hellerconnectivity issues with file transfersIn some cases (random), file transfer is stuck at _connecting_ step:
![image](/uploads/f15d6c98f5e77614e05277e3fd500bd5/image.png)
Logs returned:
`[1572286748.867|10231|account_manager.cpp:496 ] Found 1 devices for 1a901ac4fc4693a49...In some cases (random), file transfer is stuck at _connecting_ step:
![image](/uploads/f15d6c98f5e77614e05277e3fd500bd5/image.png)
Logs returned:
`[1572286748.867|10231|account_manager.cpp:496 ] Found 1 devices for 1a901ac4fc4693a49c88bac9b82fb78d96ceeb23`
When the app is closed, following error appears in the log:
`no response from DHT to E2E request. Cancel transfer`
In comparison, here are the logs of a success file transfer.
```
[1572286739.593|10231|account_manager.cpp:496 ] Found 1 devices for 1a901ac4fc4693a49c88bac9b82fb78d96ceeb23
[1572286739.593|10359|ice_transport.cpp :264 ] [ice] added turn server '192.252.140.235', port 3478
[1572286739.595|10360|sip_utils.cpp :203 ] Registered thread 0x7ff270ff6dd0 (0x27E9)
[1572286739.683|10360|ice_transport.cpp :481 ] [ice:0x7ff248000bd0] initialization success
[1572286739.683|10360|ice_transport.cpp :551 ] ICE as slave
[1572286739.684|10360|ice_transport.cpp :628 ] [ice:0x7ff248000bd0] (local) ufrag=4cfc75b0, pwd=10b66b5126d322e24836c87d
[1572286739.684|10359|jamiaccount.cpp :2483 ] [Account 27c3543ae405fbd0] using public IP: 2607:fad8:4:6:24e9:e683:f7cb:989c
[1572286739.684|10359|ice_transport.cpp :729 ] [ice:0x7ff248000bd0] succeed to add candidate for comp_id=1 : 2607:fad8:4:6:24e9:e683:f7cb:989c : 2607:fad8:4:6:24e9:e683:f7cb:989c
[1572286739.684|10359|sipaccountbase.cpp:416 ] [Account 27c3543ae405fbd0] Using public address 2607:fad8:4:6:24e9:e683:f7cb:989c
[1572286739.684|10359|jamiaccount.cpp :2483 ] [Account 27c3543ae405fbd0] using public IP: 208.88.110.46
[1572286739.684|10359|ice_transport.cpp :729 ] [ice:0x7ff248000bd0] succeed to add candidate for comp_id=1 : 192.168.48.189 : 208.88.110.46
[1572286739.684|10359|sipaccountbase.cpp:416 ] [Account 27c3543ae405fbd0] Using public address 208.88.110.46
[1572286739.684|10359|p2p.cpp :403 ] [Account 27c3543ae405fbd0] [CNX] request connection to b0485de8f597468c58a2b7edcf6552c76860a613
[1572286742.267|10226|p2p.cpp :868 ] [Account 27c3543ae405fbd0] [CNX] rx DHT reply from b0485de8f597468c58a2b7edcf6552c76860a613
[1572286742.267|10359|p2p.cpp :243 ] [Account:27c3543ae405fbd0] add remote ICE candidate: Hac1011e7 1 TCP 2130706431 172.16.17.231 50659 typ host tcptype passive
[1572286742.267|10359|p2p.cpp :243 ] [Account:27c3543ae405fbd0] add remote ICE candidate: Hac1011e7 1 TCP 2130706431 172.16.17.231 9 typ host tcptype active
[1572286742.267|10359|p2p.cpp :243 ] [Account:27c3543ae405fbd0] add remote ICE candidate: R9e45cb0b 1 TCP 16777215 158.69.203.11 18727 typ relay tcptype passive
[1572286742.267|10359|p2p.cpp :243 ] [Account:27c3543ae405fbd0] add remote ICE candidate: Sac1011e7 1 TCP 1694498815 208.88.110.43 50659 typ srflx tcptype passive
[1572286742.267|10359|ice_transport.cpp :889 ] [ice:0x7ff248000bc0] negotiation starting (4 remote candidates)
[1572286742.736|10360|ice_transport.cpp :481 ] [ice:0x7ff248000bd0] negotiation success
[1572286742.736|10360|ice_transport.cpp :521 ] [ice:0x7ff248000bd0] connection pairs (local <-> remote):
[0] 208.88.110.46:50953 <-> 158.69.203.11:18727
[1572286742.736|10359|p2p.cpp :445 ] [Account:27c3543ae405fbd0] ICE negotiation succeed. Starting file transfer
[1572286742.736|10359|ice_transport.cpp :534 ] ICE as master
[1572286742.736|10359|p2p.cpp :479 ] [Account 27c3543ae405fbd0] [CNX] start TLS session
[1572286742.737|10371|tls_session.cpp :759 ] [TLS] Start client session
[1572286742.769|10371|tls_session.cpp :456 ] [TLS] User identity loaded
[1572286742.769|10371|tls_session.cpp :854 ] [TLS] handshake
[1572286742.783|10371|sip_utils.cpp :203 ] Registered thread 0x7ff246ffadd0 (0x27E9)
[1572286743.176|10371|tls_session.cpp :891 ] [TLS] session established: (TLS1.3)-(DHE-FFDHE8192)-(RSA-PSS-RSAE-SHA384)-(AES-256-GCM)
[1572286743.176|10372|peer_connection.cpp:652 ] [CNX] Peer connection to b0485de8f597468c58a2b7edcf6552c76860a613 ready
[1572286743.177|10372|sip_utils.cpp :203 ] Registered thread 0x7ff2467f9dd0 (0x27E9)
[1572286746.676|10231|account_manager.cpp:496 ] Found 0 devices for b0485de8f597468c58a2b7edcf6552c76860a613
[1572286746.676|10231|p2p.cpp :1078 ] 27c3543ae405fbd0[CNX] aborted, no devices for b0485de8f597468c58a2b7edcf6552c76860a613
```New release 1https://git.jami.net/savoirfairelinux/jami-project/-/issues/708file transfer not using full bandwidth2020-06-29T20:22:49ZGuillaume Hellerfile transfer not using full bandwidthWe tested the transfer of files and detected that it does not take advantage of the full bandwidth.
example:
* Network download speed: around 90Mbps/s
* Jami file transfer speed: between 1 and 3 Mbps/s
In comparison, Skype reaches a ...We tested the transfer of files and detected that it does not take advantage of the full bandwidth.
example:
* Network download speed: around 90Mbps/s
* Jami file transfer speed: between 1 and 3 Mbps/s
In comparison, Skype reaches a speed of 12Mbps/sNew release 1https://git.jami.net/savoirfairelinux/jami-project/-/issues/711Voice conference UX is confusing2019-12-05T20:50:26ZDanyl StrypeVoice conference UX is confusingThree [experienced geeks tested group voice chat on Jami](https://write.as/c7fda5x13qzve.md) a few months ago. We found that the control for launching a one-to-one voice chat between two users is simple and obvious, but it's not clear ho...Three [experienced geeks tested group voice chat on Jami](https://write.as/c7fda5x13qzve.md) a few months ago. We found that the control for launching a one-to-one voice chat between two users is simple and obvious, but it's not clear how to start a voice conference with three or more users. It took us a lot of experimentation to figure out how to do it.
I'm guessing this is something that might improve if and when you add the capacity for group text chat? In Wire, the users who want to have a voice conference first join a group text chat, then launch a voice chat using the usual control. Will the Jami UI work something like that at some point in the future?
Some other ways the UI could work
* one user can select 2 or more other users, before launching a voice chat
* during an existing voice chat, a "+" control appears next to each participating user's other contacts. Clicking that control brings that user into the voice conference.New release 1https://git.jami.net/savoirfairelinux/jami-project/-/issues/726update version name on all clients2019-11-22T01:56:49ZGuillaume Hellerupdate version name on all clientsupdate version name from "Live Free or Die" to "Free as in Freedom"update version name from "Live Free or Die" to "Free as in Freedom"New release 12019-11-15https://git.jami.net/savoirfairelinux/jami-project/-/issues/709text font+background color clash with adwaita dark (since gnome 3.34 or 3.34.1?)2019-11-06T15:09:14ZIT wrxtext font+background color clash with adwaita dark (since gnome 3.34 or 3.34.1?)Arch linux
gnome 3.34.1
jami-gnome 20190813-1
incoming text messages and call status messages (ex: "Missed outgoing call") are now white on light grey background and almost completely unreadable since gnome 3.34 or so (IIRC). I'm using ...Arch linux
gnome 3.34.1
jami-gnome 20190813-1
incoming text messages and call status messages (ex: "Missed outgoing call") are now white on light grey background and almost completely unreadable since gnome 3.34 or so (IIRC). I'm using the dark adwaita theme. Works fine on default/light adwaita theme.
thanksNew release 1Sébastien BlinSébastien Blin