savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-08-20T21:09:03Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/614No option to resend pictures on Android2021-08-20T21:09:03Zring userNo option to resend pictures on Android- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build ...- Ring version: Live Free or Die - 20190602-01
- Device model: Samsung Galaxy S5 to Manjaro Linux (Arch based)
- Android version: Android 9/LineageOS 16 (no GApps) to "Live Free or Die" build 2019-07-01 19:46:10 UTC
- What build you are using: F-Droid to Manjaro/Arch build
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Requirements: Two accounts, one on Linux, one on Android, are already connected
2. Open the conversation on Android
3. Send a picture while Linux is offline
4. Wait. You will get the error message "Unjoinable peer" below the picture
5. Switching Linux online
6. Wait
7. Picture is not resend automatically
8. Try to resend manually (Click on picture, long click on picture to open menu etc.
- Actual result:
1. No option for resending available on Android (Linux has such an option in a poorly noticeable three-point-menu beside a not send picture)
- Expected result:
2. Automatically retry when other peer is online or at least an easy accessable option for retrying for Android. IMHO best solution would be a resend/retry-button directly below the picture.Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/136[API ready]Swarm: support request for resending a file transfer2021-06-12T11:37:55ZSébastien Blin[API ready]Swarm: support request for resending a file transfer+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.+ The daemon should store a link or the file in private datas to retrieve it
+ A peer in a conversation is able to re-ask for a file transfer
+ when downloaded sha3sum must be checked.Swarm-chatSé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-client-android/-/issues/1378Message cannot be sent2024-02-14T15:43:53Zsession 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/1b5a914986eedff40e514fd962dab3aa/log0.log)
[log1.log](/uploads/7059a3a393a8998e853a1066d07b73d3/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.**https://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-client-android/-/issues/1149Add support for call-swarm2023-09-07T13:52:12ZSébastien BlinAdd support for call-swarm+ Don't know if a design exists yet for android+ Don't know if a design exists yet for androidPierre NicolasPierre Nicolashttps://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-ios/-/issues/124iOS: add swarm support2021-10-07T19:29:33ZSébastien BliniOS: add swarm supportKateryna KostiukKateryna Kostiukhttps://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/815Synced messages appear as new on synced devices (notification spam)2023-03-02T19:06:10ZMaxim CournoyerSynced messages appear as new on synced devices (notification spam)Hi,
At least on Android and GNU/Linux, messages received via the SWARM sync feature *that already have been read* on one device appear as new, i.e. they trigger notifications.
This is especially annoying when not using a device for som...Hi,
At least on Android and GNU/Linux, messages received via the SWARM sync feature *that already have been read* on one device appear as new, i.e. they trigger notifications.
This is especially annoying when not using a device for some time (offline); when reconnecting to the Jami network all the past messages stored on other devices will be synced and cause a massive amount of notifications.
I'm opening the issue here since it seems to affect all the clients (at least Android and GNU/Linux).
Thanks.2023-02-28https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/971SwarmDetailsPanel: context menu opens to wrong position2023-03-02T14:22:45ZNicolas VengeonSwarmDetailsPanel: context menu opens to wrong positionScenario:
- Right click on a member in the swarmdetailsPanel opens a contextmenu on the top of the element
- Background doesn't change when the name of a member is hovered
Expected result:
- ContextMenu shoud open on mouse position
- Ba...Scenario:
- Right click on a member in the swarmdetailsPanel opens a contextmenu on the top of the element
- Background doesn't change when the name of a member is hovered
Expected result:
- ContextMenu shoud open on mouse position
- Background should change when the name of a member is hoveredNicolas VengeonNicolas Vengeonhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/902Swarm: Keep state of details panel2023-03-23T15:24:04ZSébastien BlinSwarm: Keep state of details panel# Scenario
+ Open the details panel in a swarm.
+ Close and re-open the conversation OR go to another conversation
# Expected
+ Details Panel kept opened at the same place)
# Current
+ Details Panel is resetted
# Goal
If the user ...# Scenario
+ Open the details panel in a swarm.
+ Close and re-open the conversation OR go to another conversation
# Expected
+ Details Panel kept opened at the same place)
# Current
+ Details Panel is resetted
# Goal
If the user prefers to always see members by default it's possible.Andreas TraczykAndreas Traczyk2023-02-28https://git.jami.net/savoirfairelinux/jami-project/-/issues/1508Synced messages appear as new on synced devices (notification spam)2023-02-07T20:19:57ZMaxim CournoyerSynced messages appear as new on synced devices (notification spam)Hi,
At least on Android and GNU/Linux, messages received via the SWARM sync feature *that already have been read* on one device appear as new, i.e. they trigger notifications.
This is especially annoying when not using a device for som...Hi,
At least on Android and GNU/Linux, messages received via the SWARM sync feature *that already have been read* on one device appear as new, i.e. they trigger notifications.
This is especially annoying when not using a device for some time (offline); when reconnecting to the Jami network all the past messages stored on other devices will be synced and cause a massive amount of notifications.
I'm opening the issue here since it seems to affect all the clients (at least Android and GNU/Linux).
Thanks.2023-02-28https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1128Continue swarm support with multiple participants - Missing features2023-12-18T14:41:38ZSébastien BlinContinue swarm support with multiple participants - Missing features1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other members1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other membersAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/768[swarm] conversation cannot be sync'd: Abort fetching repository, the fetch i...2023-01-10T15:25:14ZMaxim Cournoyer[swarm] conversation cannot be sync'd: Abort fetching repository, the fetch is too bigHi,
After updating Jami to 20220825.0828.c10f01f, there's a conversation info banner mentioning "An error occurred while fetching this repository".
Looking at the logs, the more exact error seems to be: "Abort fetching repository, the ...Hi,
After updating Jami to 20220825.0828.c10f01f, there's a conversation info banner mentioning "An error occurred while fetching this repository".
Looking at the logs, the more exact error seems to be: "Abort fetching repository, the fetch is too big":
```
Sep 19 10:45:23 localhost jami: Could not fetch remote repository for conversation b7ca6ad7bbf02d554160da6382f3f17b30082dc8: indexer progress callback returned -1
Sep 19 10:45:23 localhost jami: [Account 80852682ccb25a32] Could not fetch new commit from 536ba4cf048057f6fa01d8eafa7b65d7bdde470320af6e5c026cf2dc59a0355f for b7ca6ad7bbf02d554160da6382f3f17b30082dc8, other peer may be disconnected
Sep 19 10:45:23 localhost jami: [Account 80852682ccb25a32] Relaunch sync with 536ba4cf048057f6fa01d8eafa7b65d7bdde470320af6e5c026cf2dc59a0355f for b7ca6ad7bbf02d554160da6382f3f17b30082dc8
```
`grep jami /var/log/messages | tail -n200 > jami.log` attached.
[jami.log](/uploads/83aa19a73cefe19744742aa614172189/jami.log)Sébastien BlinSébastien Blin2023-01-18https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/685Swarm: add swarm details page2022-03-23T22:01:50ZSébastien BlinSwarm: add swarm details page![group-settings](/uploads/5a0642c5098a06514a5737ec40589a10/group-settings.png)![group-settings](/uploads/5a0642c5098a06514a5737ec40589a10/group-settings.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/670Swarm: Add swarm creation into the UI2022-05-13T14:55:46ZSébastien BlinSwarm: Add swarm creation into the UI![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/7Swarm: add swarm details page2022-02-16T21:38:58ZSébastien BlinSwarm: add swarm details page![group-settings](/uploads/8477a573fdac485ff55f6e8e5867cbdb/group-settings.png)![group-settings](/uploads/8477a573fdac485ff55f6e8e5867cbdb/group-settings.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/6Swarm: Add swarm creation into the UI2022-02-03T20:51:06ZSébastien BlinSwarm: Add swarm creation into the UI![create-group0](/uploads/9e79baa3db81a308d0fd30e5d7b8a326/create-group0.png)
![create-group1](/uploads/f559bff40640f05281aae4c74b23c490/create-group1.png)![create-group0](/uploads/9e79baa3db81a308d0fd30e5d7b8a326/create-group0.png)
![create-group1](/uploads/f559bff40640f05281aae4c74b23c490/create-group1.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1319(Feature request) Group picture2021-10-12T16:52:22ZhardBSDk(Feature request) Group pictureAdd an option to set an image as group picture.Add an option to set an image as group picture.