jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2024-03-28T00:05:08Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/959Call-Swarm/Rdv: wrong audio is attached2024-03-28T00:05:08ZSébastien BlinCall-Swarm/Rdv: wrong audio is attached# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alice# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alicehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/958Call-swarm: Joining in audio make the host join2024-03-25T18:36:16ZSébastien BlinCall-swarm: Joining in audio make the host join# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attached# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attachedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/957Call-swarm: join in audio fails2024-02-26T20:30:19ZSébastien BlinCall-swarm: join in audio fails# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No sound# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No soundhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/953Call Swarm: full pass2024-03-28T00:05:08ZSébastien BlinCall Swarm: full pass# TODO
+ Check performance
+ Check call ending announcement
+ Check support on all platforms
+ Fallback
+ ask for hosts
+ audio binding
+ test with 8 devices
+ Performance# TODO
+ Check performance
+ Check call ending announcement
+ Check support on all platforms
+ Fallback
+ ask for hosts
+ audio binding
+ test with 8 devices
+ PerformanceSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/948Improve AccountStatusMessage synchronization2024-02-23T13:52:34ZSébastien BlinImprove AccountStatusMessage synchronization# Problems
On current master:
+ when you send a message, the message is marked as SENT as soon as one device got the messages
+ state is not kept after a reboot
+ if we say that a message is sent as soon as one other member get the mess...# Problems
On current master:
+ when you send a message, the message is marked as SENT as soon as one device got the messages
+ state is not kept after a reboot
+ if we say that a message is sent as soon as one other member get the message, this must take into account the fact that Jami is distributed and the contact may fetch the message from another device, so this information MUST be synced
+ status wasn't designed for swarm until nowSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/937Windows: kicking failed, invalid path2024-01-09T16:53:26ZSébastien BlinWindows: kicking failed, invalid path# Scenario
+ Alice admin (windows) ban a member from a conversation
# Current result
+ Member not banned
# Expected result
+ Member banned
# Logs
```
[1704486353.315|1280|conversation.cpp :958 ] Kicking ad2a7baf15ee3957bea...# Scenario
+ Alice admin (windows) ban a member from a conversation
# Current result
+ Member not banned
# Expected result
+ Member banned
# Logs
```
[1704486353.315|1280|conversation.cpp :958 ] Kicking ad2a7baf15ee3957beaef2271a7bb8e08c63cca5 failed
[1704486367.260|6552|conversationrepository.cpp:886 ] Error when adding file: invalid path: 'votes/ban/members/ad2a7baf15ee3957beaef2271a7bb8e08c63cca5\bda3200d605f7ff2b08e1c2a7eaa84c0a8a5f13e'
[1704486367.262|6552|conversation.cpp :958 ] Kicking ad2a7baf15ee3957beaef2271a7bb8e08c63cca5 failed
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/946Profile update cause invalid messages to be generated2024-01-24T13:12:27ZSébastien BlinProfile update cause invalid messages to be generated# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows g...# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows get an invalid commit detectedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/924Double conversation on bad presence sync2023-12-05T21:02:29ZSébastien BlinDouble conversation on bad presence sync# Scenario
+ Disable the presence in AccountManager::startSync
+ Alice adds Bob, Bob adds Alice => 1 conversation both side
+ Re-enable presence
+ Alice sends a message
# Current result
Bob receives a new trust request and doesn't acc...# Scenario
+ Disable the presence in AccountManager::startSync
+ Alice adds Bob, Bob adds Alice => 1 conversation both side
+ Re-enable presence
+ Alice sends a message
# Current result
Bob receives a new trust request and doesn't accept it automatically
# Expected
Alice and Bob should uses only 1 conversationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/922Accepting stuck in syncing for a long time2023-11-23T19:59:28ZSébastien BlinAccepting stuck in syncing for a long time# Scenario
+ Alice adds Bob
+ Bob receives the request
+ Alice goes offline
+ Bob accepts (syncing)
+ After 1 min Alice goes online
# Current result
Stuck in syncing
# Expected
Conversation must sync# Scenario
+ Alice adds Bob
+ Bob receives the request
+ Alice goes offline
+ Bob accepts (syncing)
+ After 1 min Alice goes online
# Current result
Stuck in syncing
# Expected
Conversation must syncSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/917Swarm-call: bugguy state if join call in audio-only2023-11-17T16:28:47ZSébastien BlinSwarm-call: bugguy state if join call in audio-only# Scenario
+ Host a video call in a swarm
+ With another device join in audio
# Current result
+ Stuck in calling, media not negotiated
# Expected
+ Call should work with muted video# Scenario
+ Host a video call in a swarm
+ With another device join in audio
# Current result
+ Stuck in calling, media not negotiated
# Expected
+ Call should work with muted videoSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/916Swarm-call: sometimes doesn't answer2023-11-17T16:28:52ZSébastien BlinSwarm-call: sometimes doesn't answer# Scenario
none identified
# Current result
Sometimes, caller stays in calling (but a swarm-call should be automatically answered by the host)# Scenario
none identified
# Current result
Sometimes, caller stays in calling (but a swarm-call should be automatically answered by the host)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/931Message cannot be sent2024-03-23T15:49:25Zsession 21Message cannot be sentI have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mo...I have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mobile version: 379 (376)
Equipment model: Samsung s20+5g
Android 12
Computer version: 202307111203
Win 10 (22H2)
I think I have reproduced this error. On September 16th, when I was in version 376, I encountered this error and it reappeared tonight. I give these two examples because I have the Jami logs on my phone during these two errors.
In the previous time, I encountered this error at least ten times, but it was all between computers, and the computer's records were not complete. I hoped to - d start, but this error will not reappear after restarting.
**The important thing is that this error may not occur until the computer's client is started for an hour (if that happens, the log will be large, so I did not attempt to record the log on the computer)**
**Actual result: My computer cannot receive any messages.**
**Expected results: Message transmission should be normal.**
**Public network dynamic ipv6 is working normally.**
Yesterday, I thought it might be an issue with the Android version being too low, so I didn't provide any feedback on this issue because I heard from a friend that Jami seemed to have fixed an error that could cause abnormal messages.
However, today I encountered this problem again.
And I have two days of logs, so I decided to upload it.
[log0.log](/uploads/2d1ef596bfeabf76eaaabb538c4a15a5/log0.log)
[log1.log](/uploads/240c35be47e58df87db612c0930256a2/log1.log)
In the two logs, there is a description of "message sent successfully", but in reality it is not.
In the second log paragraph, it was not until my account received a message from the computer that both parties' information reception and transmission resumed normal.
The reason for returning to normal is that I performed the "close account and then re enable account" operation on my computer.
During this period, the abnormal state of the message lasted for 20 minutes.
**I can't find how to upload the file, so if there is any sensitive information, could you please help me cover it up.**
**Thank you. I admire your hard work.**Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/890Call-Swarm fix audio binding2023-09-14T17:39:14ZSébastien BlinCall-Swarm fix audio binding# Scenario
+ Alice hosts a call-swarm between Alice/Bob/Carla
# Expected result
+ Bob should hear carla
# Current result
+ Carla and Bob can't communicate by audio, but Alice got all audio# Scenario
+ Alice hosts a call-swarm between Alice/Bob/Carla
# Expected result
+ Bob should hear carla
# Current result
+ Carla and Bob can't communicate by audio, but Alice got all audioCapucine BerthetSébastien BlinCapucine Berthethttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/831Add abstraction layer around conversation2024-01-19T13:25:49ZPierre NicolasAdd abstraction layer around conversationConversation are very complex partly because we keep history (git system).
Deamon should manage the data to give a simplified version to clients.
Then it will be cleaner and reduce bugs in the client conversation implementation.Conversation are very complex partly because we keep history (git system).
Deamon should manage the data to give a simplified version to clients.
Then it will be cleaner and reduce bugs in the client conversation implementation.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/817[call-swarm] duplicates/triplicate and ghost participants in the layout2023-03-03T20:52:53Zovari[call-swarm] duplicates/triplicate and ghost participants in the layoutDuplicate/triplicate participants in the layout.
Not sure how to reproduce the scenario; however, it is thought that all participants are connected as audio-only.
Following images show duplicate participants in the layout exists:
1. A ...Duplicate/triplicate participants in the layout.
Not sure how to reproduce the scenario; however, it is thought that all participants are connected as audio-only.
Following images show duplicate participants in the layout exists:
1. A duplicate and a ghost participant<br>
![1 duplicate and 1 ghost participant](/uploads/2a4fc8891d9f13388228f1a6a8a31cf2/image.png)
2. A triplicate and a ghost participant<br>
![1 triplicate and 1 ghost participant](/uploads/17ec7073b98bb31ac18c53a91d25eab3/image.png)
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/816Jami incorrectly states a call-swarm is in progress2023-09-05T12:48:45ZovariJami incorrectly states a call-swarm is in progress
1. ![A call is in progress. Do you want to join?](/uploads/fc6697a465eb54f006f4fe366fb57e2c/image.png)
2. Click on the telephone button to join as audio-only participant<br>
![Current host for this swarm seems unreachable. Do you want t...
1. ![A call is in progress. Do you want to join?](/uploads/fc6697a465eb54f006f4fe366fb57e2c/image.png)
2. Click on the telephone button to join as audio-only participant<br>
![Current host for this swarm seems unreachable. Do you want to host the call?](/uploads/d0215cafd8a4db4962ada7d8c4334cea/image.png)
Perhaps the host was the person Jami for Flatpak. If so, their Jami client crashed, i.e. they could not press any buttons; however, they was still able to talk and hear what we were saying.
```
[1676002144.162|1649|manager.cpp :938 ] ############## START MONITORING ##############
[1676002144.162|1649|manager.cpp :939 ] Using PJSIP version 2.12.1 for x86_64-pc-linux-gnu
[1676002144.162|1649|manager.cpp :940 ] Using GnuTLS version 3.7.6
[1676002144.162|1649|manager.cpp :941 ] Using OpenDHT version 2.4.11
[1676002144.163|1649|manager.cpp :947 ] Opened files: 246
[1676002144.163|1649|connectionmanager.cpp :1196] ConnectionManager for account REDACTED (jami:REDACTED), current status:
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:2348 [prflx] <-> REDACTED:26877 [relay]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:10360 [relay] <-> REDACTED:49868 [prflx]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:2370 [prflx] <-> REDACTED:25591 [relay]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:37740 [prflx] <-> REDACTED:48483 [host]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:2312 [prflx] <-> 192.252.140.235:10914 [relay]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:2464 [prflx] <-> REDACTED:13118 [srflx]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:27133 [relay] <-> REDACTED:64264 [prflx]
[1676002144.163|1649|peer_connection.cpp :426 ] - Ice connection: [2] REDACTED:2502 [prflx] <-> REDACTED:15031 [relay]
[1676002144.164|1649|connectionmanager.cpp :1203] ConnectionManager for account REDACTED (jami:REDACTED), end status.
[1676002144.164|1649|manager.cpp :956 ] ############## END MONITORING ##############
[1676002147.438|3715|data_transfer.cpp :222 ] Invalid sha3sum detected, unfinished file: /home/REDACTED/.local/share/jami/REDACTED/conversation_data/REDACTED/REDACTED.pdf
[1676002168.707|2044|jamiaccount.cpp :1889] [Account REDACTED] Dht status: IPv4 connected; IPv6 disconnected
[1676002187.762|2044|jamiaccount.cpp :1889] [Account REDACTED] Dht status: IPv4 connected; IPv6 connecting
```
Please advise if you need the `REDACTED` text.
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/798Swarm: add API to promote someone to an administrator2023-04-13T20:11:10ZSébastien BlinSwarm: add API to promote someone to an administrator# Goal
Because an administrator can leave, the swarm will have no administrator at the end. Make it possible for an administrator to promote someone else.
# TODO
+ Implement promotion/demotion (NOTE: no demotion if 1 admin) in the dae...# Goal
Because an administrator can leave, the swarm will have no administrator at the end. Make it possible for an administrator to promote someone else.
# TODO
+ Implement promotion/demotion (NOTE: no demotion if 1 admin) in the daemon
+ Validate an API
+ Add feature in clients
+ Check demotion2023-09-30https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/797Swarm: add support for multiple roles2023-11-20T14:38:31ZSébastien BlinSwarm: add support for multiple roles# Goal
In a swarm, pretty every action should be an action that needs to be permitted for a role and administrators should be able to add new roles.
# TODO
analyze what needs to change in the daemon# Goal
In a swarm, pretty every action should be an action that needs to be permitted for a role and administrators should be able to add new roles.
# TODO
analyze what needs to change in the daemon2023-12-31https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/796Edited: re-design contentType2022-12-16T22:26:22ZSébastien BlinEdited: re-design contentTypeFor now it uses `application/edited` but this should uses the current type we edit `plain/text` + `edit` or file.
docs.jami.net must also be updated (same for clients). The final design must be discussed first.For now it uses `application/edited` but this should uses the current type we edit `plain/text` + `edit` or file.
docs.jami.net must also be updated (same for clients). The final design must be discussed first.Sébastien BlinSébastien Blin2023-05-31https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/795Call in large groups - multi-host?2023-01-07T14:02:03ZSébastien BlinCall in large groups - multi-host?If we remove the limit for swarm, creating a call may have issue for the hosts as they will be able to receive and host thousands of calls.If we remove the limit for swarm, creating a call may have issue for the hosts as they will be able to receive and host thousands of calls.2023-12-31