savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-03-11T10:05:10Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1182Long preview load time (for conversations not with yourself)2023-03-11T10:05:10ZAltonsLong preview load time (for conversations not with yourself)## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start ...## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start the app (cold start)
2. See that conversions preview for conversions not with yourself load slower
- Actual result: Conversions preview (profile picture+id/username) for conversions not with yourself load slower.
- Expected result: Should take the same speed then conversation with yourself (and load faster).
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1181Broken call screen (all black) when audio call to unavailable contact2023-03-11T09:54:11ZAltonsBroken call screen (all black) when audio call to unavailable contact## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Call (...## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Call (audio) an unavailable contact
- Actual result: A short black screen appears (no call screen) before closing.
- Expected result: This should more behave like when trying a video call, which fails too due to the contact beeing unavailable, but shows a call screen instead of black screen.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1180Quote message: deletion or modification of original message broken2023-05-11T18:54:48ZAltonsQuote message: deletion or modification of original message broken## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps (for an ori...## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps (for an original message):
1. Quote a message
2. Delete or modify it
3. See that the quote is still unchanged
- Steps (for an changed message):
1. Quote a message that has been changed
2. See that the quote still contains the original version of the message
- Actual result: Quote message: deletion or modification of original message broken
- Expected result: It should behave normally: replicate deletion or modification.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1179Quote message broken: unable to unselect quoted message2023-03-11T09:31:46ZAltonsQuote message broken: unable to unselect quoted message## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Quote...## Describe your environment
Please specify the following:
- Jami version: 20230227-01
- Android version: 13
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Quote your own message
2. Tap on the "quote" that selects the corresponding message
...
- Actual result: Quote message broken: unable to unselect quoted message
- Expected result: We should be able to unselect quoted message.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1178Fake linked devices appear2023-03-21T16:30:08ZWear GuxjFake linked devices appearWith the 20230227-01 version, create a new Jami account. When it's done, go to account settings. Note that the "identity" and "this device" fields are empty?
Go further on to account's advanced settings and uncheck UPnP. All other sett...With the 20230227-01 version, create a new Jami account. When it's done, go to account settings. Note that the "identity" and "this device" fields are empty?
Go further on to account's advanced settings and uncheck UPnP. All other settings remain default.
Go back one step. Because of unchecking UPnP, account status has now become offline, and it cannot easily become online again.
However, those empty fields are now filled in. Without unchecking UPnP, they would still have been empty.
Very soon, two alleged linked devices appear, one with the same name as "this device", the second with an 8 digit name. But I never tried to link any devices. What's wrong here?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1177(UI Bug) Blankscreen when rotating from landscape to portrait2023-03-08T18:51:02ZPierre Nicolas(UI Bug) Blankscreen when rotating from landscape to portrait## Describe your environment
- Jami version: Világfa 20230119-01
- Device model: Samsung Galaxy S20 5G (SM-G981B/DS)
- Android version: Android 13
- What build you are using: Play Store
## Steps to reproduce
- Can you repro...## Describe your environment
- Jami version: Világfa 20230119-01
- Device model: Samsung Galaxy S20 5G (SM-G981B/DS)
- Android version: Android 13
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. See the video. Don't forget to click on right panel before rotating back to portrait.
- Actual result: Blank screen.
- Expected result: Idk but not a blank screen.
## Additional information
![Screen_Recording_20230308_113556_Jami](/uploads/046d667d8e00ca0c41befdead8820171/Screen_Recording_20230308_113556_Jami.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1176Homogenize typeface and input field2023-03-07T22:06:15ZPierre NicolasHomogenize typeface and input field- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: Android version 11
- What build you are using: master branch commit b45b110de04c76dffe99c6209ff2c0789c78ebfa
As you can see, there is no homogeneity in input field ...- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: Android version 11
- What build you are using: master branch commit b45b110de04c76dffe99c6209ff2c0789c78ebfa
As you can see, there is no homogeneity in input field typeface and color :
![issue_1_typoface_2](/uploads/f4964c37af00fbdd948d1a56a050d133/issue_1_typoface_2.png)
![issue_1_typoface](/uploads/fb3a13736a179b9d2c150f382531bbe9/issue_1_typoface.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1023Convert recording call quality values to human-friendly labels2023-04-07T18:21:52ZBesnik BletaConvert recording call quality values to human-friendly labelsHello!
Under Settings > General > Call Recording > Quality one can choose different recoding quality for the recording of the call. I must confess that I don’t know the unit used to describe the quality (Mbps). I suspect most of the use...Hello!
Under Settings > General > Call Recording > Quality one can choose different recoding quality for the recording of the call. I must confess that I don’t know the unit used to describe the quality (Mbps). I suspect most of the users will fall in the same group. Couldn’t this be changed in something closer to everyday experience? Like, AM radio quality - FM radio quality - CD quality - … or, fair/medium/heavy on processing power, or something else understandable that could help making an informed decision about setting up that part.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/264location sharing: adapt to light mode2023-03-31T19:14:55ZKateryna Kostiuklocation sharing: adapt to light modeuse system background color for map view title and buttons.use system background color for map view title and buttons.Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-docs/-/issues/15Unable to build docs following the instructions2023-03-22T17:43:45ZRaphaël BruléUnable to build docs following the instructions# Steps to reproduce
1. Follow instructions to contribute to the documentation on the [Contribute to Jami](https://docs.jami.net/contribute.html#contributing-to-this-documentation) page until `make clean && make html`
# Expected result...# Steps to reproduce
1. Follow instructions to contribute to the documentation on the [Contribute to Jami](https://docs.jami.net/contribute.html#contributing-to-this-documentation) page until `make clean && make html`
# Expected result
Docs build successfully.
# Actual result
Docs do not build.
# Discussion
The docs do not build with versions of sphinx 6.0.0 or higher. As a workaround, it is possible to run `pip install --upgrade sphinx==5.3.0`.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1175Prohibit communication with blocked contact2024-01-29T21:48:51ZWear GuxjProhibit communication with blocked contactIf a contact is blocked, it is still possible to send another message, which will implicitly bring the contact back to unblocked state.
I would prefer if it worked like when a local account is disabled, so there would be a banner te...If a contact is blocked, it is still possible to send another message, which will implicitly bring the contact back to unblocked state.
I would prefer if it worked like when a local account is disabled, so there would be a banner telling that the contact is blocked, and it should not be possible to do anything that would affect the peer.
So no calls or reactions, and the text composer should not be available.
To best ensure this, the prohibition should preferably be enforced at daemon level.
It should though remain possible to read and copy text, search the conversation, share or remove attached files.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1174Display reason for call failure2023-02-28T20:38:35ZWear GuxjDisplay reason for call failureThis is on Android but may be same in other clients as well.
#
When trying to make a call but it does not succeed, it often appears as just a sub second flash before going back to the conversation view. Only a discrete "missed outgoing c...This is on Android but may be same in other clients as well.
#
When trying to make a call but it does not succeed, it often appears as just a sub second flash before going back to the conversation view. Only a discrete "missed outgoing call" entry was added. This is very confusing, so users need better information on what happened. The reason for call failure should be clearly presented to the user.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1009Call participants can be placed incorrectly within the layout2023-02-28T15:10:52ZAndreas TraczykCall participants can be placed incorrectly within the layout![image](/uploads/34917dd00a99261b6c3e5a7f7cb9f675/image.png)![image](/uploads/34917dd00a99261b6c3e5a7f7cb9f675/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1008Big lag when switching between 2 conversations with the same call2023-02-27T20:37:00ZSébastien BlinBig lag when switching between 2 conversations with the same call# Scenario
+ Alice starts a conference with Bob and Carla
+ Alice switch between Bob's conversation and Carla's conv
# Expected
+ No lag
# Current result
3 seconds delay# Scenario
+ Alice starts a conference with Bob and Carla
+ Alice switch between Bob's conversation and Carla's conv
# Expected
+ No lag
# Current result
3 seconds delayRaphaël BruléRaphaël Bruléhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/826problem connecting tio SIP account on startup2023-11-12T14:17:59Ztomo90problem connecting tio SIP account on startupI have configured a simple SIP account. The application does not automatically log in to the account when it starts. However, all I need to do to connect is go into the settings and click in the name settings field, for example, and then...I have configured a simple SIP account. The application does not automatically log in to the account when it starts. However, all I need to do to connect is go into the settings and click in the name settings field, for example, and then exit the settings and the application will connect to the account immediately. It doesn't make any sense to me.
Generally speaking, it will connect to the account after editing any unrelated settings.
Furthermore, the application does not seem to save some of the settings i make. After quitting, the switches and settings are at their original values. This is not a problem with, for example, write permissions to the configuration file, because some of the settings made are preserved and some are not when the application is restarted.
You can see for yourself that on the attached video.
![vid](/uploads/e0e18d538065a0cffa977629dbfcf594/vid.mp4)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-web/-/issues/205404: No routes matched location "/setup/login"2023-02-24T05:07:05ZJacob Trock404: No routes matched location "/setup/login"![image](/uploads/3ba40935333b802882a713b64539ca24/image.png)
I've attempted starting the project using both the docker image and manual build. I use ubuntu 22.10 and node v16.19.0 installed with nvm. I've installed all the dependencies ...![image](/uploads/3ba40935333b802882a713b64539ca24/image.png)
I've attempted starting the project using both the docker image and manual build. I use ubuntu 22.10 and node v16.19.0 installed with nvm. I've installed all the dependencies and followed the instructions to a tee, however, I can't yield a case where I'm not hit with the "No routes matched location "/setup/login"" error. Please let me know if I've omitted something or if there is a solution.
-Jacob
p.s. if it's worth noting, I've also attempted to run it using the special instructions on line 104. No dice.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/824test suite fails2024-01-08T00:45:49ZMaxim Cournoyertest suite failsHello,
The test suite is not currently usable:
1. Some tests fail non-deterministically (or always).
2. It takes about 1 h to run, which is too long.
Reproducer:
1. Run `make check`
Without the above patch applied:
```
make check-TE...Hello,
The test suite is not currently usable:
1. Some tests fail non-deterministically (or always).
2. It takes about 1 h to run, which is too long.
Reproducer:
1. Run `make check`
Without the above patch applied:
```
make check-TESTS
make[3]: Entering directory '/tmp/guix-build-libjami-20230221.0.drv-0/jami-20230221.0/daemon/test/unitTest.s ' re
make[4]: Entering directory '/tmp/guix-build-libjami-20230221.0.drv-0/jami-20230221.0/daemon/test/unitTest/g ' ag
RUNNING: ut_certstore
RUNNING: ut_account_factory
RUNNING: ut_account_archive mi
RUNNING: ut_migration
RUNNING: ut_string_utils fl
RUNNING: ut_scheduler
RUNNING: ut_map_utils
RUNNING: ut_fileutils .s
RUNNING: ut_base64 re
RUNNING: ut_video_input /g
RUNNING: ut_media_encoder xt
RUNNING: ut_media_filter
RUNNING: ut_utf8_utils
RUNNING: ut_media_decoder
RUNNING: ut_media_player
RUNNING: ut_resampler
RUNNING: ut_video_scaler -2
RUNNING: ut_media_frame
RUNNING: ut_audio_frame_resizer
RUNNING: ut_recorder
RUNNING: ut_conference
RUNNING: ut_connectionManager
RUNNING: ut_fileTransfer l:
RUNNING: ut_call
PASS: ut_utf8_utils
PASS: ut_map_utils
PASS: ut_audio_frame_resizer
PASS: ut_string_utils
PASS: ut_fileutils
PASS: ut_base64 i-
RUNNING: ut_conversationRepository
RUNNING: ut_media_negotiation fl
RUNNING: ut_conversation
RUNNING: ut_auto_answer
RUNNING: ut_hold_resume .s
RUNNING: ut_conversation_call re
PASS: ut_media_frame /g
PASS: ut_resampler xt
PASS: ut_video_scaler mi
PASS: ut_media_filter
PASS: ut_media_decoder
RUNNING: ut_conversationRequest
RUNNING: ut_conversationMembersEvent fl
RUNNING: ut_ice
RUNNING: ut_syncHistory
RUNNING: ut_revoke .s
PASS: ut_video_input re
RUNNING: ut_ice_sdp_parser /g
PASS: ut_media_player ag
RUNNING: ut_ice_media_cand_exchange sc
FAIL: ut_scheduler ):
FAIL: ut_ice_sdp_parser -2
RUNNING: ut_sip_srtp fl
RUNNING: ut_sip_basic_calls
FAIL: ut_sip_srtp
PASS: ut_media_encoder .s
RUNNING: ut_plugins re
PASS: ut_certstore /g
FAIL: ut_sip_basic_calls ag
FAIL: ut_ice
FAIL: ut_account_factory
FAIL: ut_hold_resume mi
FAIL: ut_ice_media_cand_exchange
FAIL: ut_auto_answer fl
FAIL: ut_revoke
FAIL: ut_migration
FAIL: ut_media_negotiation .s
FAIL: ut_recorder re
FAIL: ut_conversation_call /g
FAIL: ut_account_archive xt
FAIL: ut_call
FAIL: ut_plugins
FAIL: ut_fileTransfer
FAIL: ut_conversationRepository
[...] (takes a very long time)
```
The patch at https://review.jami.net/c/jami-daemon/+/22670 has the right idea: separating quick unit tests from more expensive integration tests, but its implementation should be improved, so that we have two distinct check targets (`make check` for unit tests, `make check-integration` for integration tests).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1171My Router(s) May Be a Problem - I'm Requesting Help Diagnosing This2023-02-17T20:54:12ZOkyDookyMy Router(s) May Be a Problem - I'm Requesting Help Diagnosing ThisSo, I really want to be able to use Jami full-time. But, after a couple years of hanging in there, it still hasn't become viable for me to do so. Currently, my contacts and I almost always have to manually Force Stop the app and, in the ...So, I really want to be able to use Jami full-time. But, after a couple years of hanging in there, it still hasn't become viable for me to do so. Currently, my contacts and I almost always have to manually Force Stop the app and, in the Android App settings, clear the cache, and restart Jami to have our messages go through. It is wildly inconsistent and sometimes requires several rounds of the above procedure, as well as sending a message or inputting random characters in the text box to "prompt" the other device (all have "display typing notifications" on). Sometimes, new messages will go through after clearing cache and force stopping, but older messages will still stay stuck until a future clearing. We primarily use text and images, rather than calls, to communicate, but I mainly see issues posted here about the calling (audio/video) features.
This would have just been a rant, but I recently found that one of my contacts and I were able to chat with perfect reliability when we were both out and about, using cellular connectivity (and one time, where he was on Wi-Fi and I was out and using cellular). I believe that my Wi-Fi routers may be a big part of what is confusing Jami and making it hard for our devices to sync. However...**_I have no experience in networking, let alone trouble-shooting in the area. So, I am unable to know where to even start in diagnosing this problem._**
Looking through "similar" issues, I found [this one](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/920), which has not been solved for me and my clients by Swarm (so far), and [this one](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/954), which is definitely an issue for me (minus the desktop client being involved - the Android devices are the ones that are still unclear). I have been contemplating making an issue titled "The Green Dot Means Nothing," because it does not give me or my contacts a reliable indication of if the other can be reached. [This issue](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/740) may also be related, but I don't have enough knowledge to know for sure, plus it is more related to SIP accounts and all my clients and I are using Jami accounts via Swarm.
This is, of course, made harder by [this issue](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1126) that I opened a while back. But, my main concern is that Jami (or the backend services) may not be able to navigate my connection setup for whatever reason and that may be affecting other users, as well. If this can be addressed effectively, it may allow other users to enjoy a functioning Jami app out of the box.
My two routers are: A Netgear for the main router/modem and a TP-Link to extend connectivity to the back of the house (it uses ethernet-over-power to connect to the Netgear). Both are Wi-Fi capable. I will update this once I find the exact model names for each.
And the devices are all Moto G7 Supra phones on the same cellular network (Cricket) and all running the latest F-Droid flavor of Jami. The only difference is my device hasn't been able to update from Android 9 to 10, for some reason, while my other two clients' devices have updated. So, two Android 10s and one Android 9.
Oh, and one final note: I have tried leaving the Diagnostic Logs running in the background, but it always seem to get killed after a few minutes or so. The best i might be able to do is leave it on in the foreground, which may or may not reflect real-world usage.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/989[Windows 10] Window sharing: Jami will continue to show a yellow border after...2023-07-21T11:57:09ZElys[Windows 10] Window sharing: Jami will continue to show a yellow border after you exit Jamiusing Jami Version (Beta): 202307171543 on Windows 10
Steps to reproduce:
1. Make a call using Jami and select a window you want to share (Now you have a new issue:https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1242 )
1. ...using Jami Version (Beta): 202307171543 on Windows 10
Steps to reproduce:
1. Make a call using Jami and select a window you want to share (Now you have a new issue:https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1242 )
1. Exit Jami
1. If you select the window (for example Brave, Firefox, etc.) you'll still view the yellow border
Actually this issue can appear twice:
- If you are using Windows 10 Jami will be still shown for a few seconds as a tray icon (you disabled "run in background". As soon as the tray icon is gone I think the yellow border is gone
- If you are using **Windows 11** I didn't reproduce this bug with the tray icon but you have to exit all opened windows (although you now can't share a window because of the mentioned issue https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1242 )https://git.jami.net/savoirfairelinux/jami-docs/-/issues/14Missing Glossary2023-03-13T20:27:27ZKitchMMissing GlossaryIt would be nice to have a glossary section in the docs. There is no explanation of what a "device" is supposed to be. Also, charts use the word "Desktop" but fail to specify the associated OS.
Thank you.It would be nice to have a glossary section in the docs. There is no explanation of what a "device" is supposed to be. Also, charts use the word "Desktop" but fail to specify the associated OS.
Thank you.