savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-06-28T15:53:54Zhttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/55Voice activity detection2022-06-28T15:53:54ZMehdi GhayourVoice activity detectionhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/745Windows 10/11 does not display the startup page. Also reproduced in Windows 1...2022-06-28T13:58:32Zshades-ausWindows 10/11 does not display the startup page. Also reproduced in Windows 10/11 in VMWareHow to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update...How to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: Windows 10, Windows 11, VMWare
- Jami version: ALL versions after jami_x86_64-202112221025 (Win7 Qt5?)
- What build you are using: [jami.net | A store | your own (please specify commit for daemon/lrc/client-qt)...]
## Steps to reproduce
Download any of the new installers (Beta or otherwise) and run the program.
Notifications of messages pop up in the Windows Notifiaction bar however, the login screen is completely white/blank.
This was tested Native on a Windows 10 and then Windows 11 install on a ASUS i7 Laptop using Intel Iris embedded graphics and and old AMD GPU in an AMD x6 Phennom Windows 10 install as well as an Intel 4770S with 32GB RAM installed.
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. At Will
2.![JamiWindows11](/uploads/16a035780878cbab4b165de85a14db3c/JamiWindows11.jpg)
...
- Actual result:
- Expected result:
## Additional information
I beleive this could be due to an OpenGL incompatibility for older inbuilt GPUs like Intel Iris.
Due to the large ammount of affected machines and VMs under Windows, (Any version) i'd not recommend the later versions not stable at all.
Screenshots/videos/logs/etc
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/726SIGSEGV on rendez-vous point.2022-06-27T19:58:09ZOlivier DionSIGSEGV on rendez-vous point.Rendez-vous point crashes when called.
```
Thread 56 "jamid" received signal SIGSEGV, Segmentation fault.
```
[gdb-bt.txt](/uploads/b5f67f30947e3cbd88e89d4d0c0aed2e/gdb.txt).Rendez-vous point crashes when called.
```
Thread 56 "jamid" received signal SIGSEGV, Segmentation fault.
```
[gdb-bt.txt](/uploads/b5f67f30947e3cbd88e89d4d0c0aed2e/gdb.txt).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/738Swarm: infinite loading loop and incorrect merge check2022-06-27T19:40:37ZSébastien BlinSwarm: infinite loading loop and incorrect merge check# Scenario
+ Migrate an account
+ Do a merge commit right after this
# Expected
The repository should have correct informations
# Current result
The repository is malformed and causes infinite loading messages loop
# Detected probl...# Scenario
+ Migrate an account
+ Do a merge commit right after this
# Expected
The repository should have correct informations
# Current result
The repository is malformed and causes infinite loading messages loop
# Detected problems
+ LRC should not call loadingMessages in loop in case of an error
+ we should check the author of the merge commit
+ we should never create a merge commit after a migration without adding the certificateSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1440jami clients won't connect to jams2022-06-23T19:18:53Zsom bugsjami clients won't connect to jamsHi!
I'm trying to setup my "local" only messaging using jams and jami clients.
Want to selfhost everything, so installed jams inside rootless container using podman, setup nginx reverse proxy, made self-signed CA and certificates for tl...Hi!
I'm trying to setup my "local" only messaging using jams and jami clients.
Want to selfhost everything, so installed jams inside rootless container using podman, setup nginx reverse proxy, made self-signed CA and certificates for tls, setup dns resolving for my made-up tld, installed my root ca certificate on client devices.
I assume everything went ok - when i load webpage (jams webinterface) everything loads without an error, there is 'lock' icon in browser's address bar (both on linux pc and android phone).
In jams wizard i've set local database and correct domain. Then created a few users.
I can login in jams webinterface with those logins.
Problem: everytime i try to connect from jami clients i get "Can't find account. Account couldn't be found on the Jami network. Make sure it was exported on Jami from an existing device, and that provided credentials are correct".
Capturing traffic on different machines shows that jami client resolving my jams domain name ("jams.lan"), trying to connect using tls ("Client hello"), server responds ("Server hello"), then they send each other just a few more encrypted packets and then i see that "Can't find accound" message in jami client.
I suspect that jami clients are actually don't trust my self-signed tls certificate. I created fullchain + key bundle (cat server.crt rootca.crt server.key > server.pem) from my already working well certificates from my nginx reverse proxy. Then used mitmproxy:
`$ mitmdump -p 9922 --certs server.pem -w dump.log -m reverse:http://127.0.0.1:9900`
and here is a log (i'm using "jams.lan:9922" as management server url in jami clients):
```
192.168.1.3:41378: client connect
192.168.1.3:41378: server connect 127.0.0.1:9900
192.168.1.3:41378: Client TLS handshake failed. The client does not trust the proxy's certificate for jams.lan (tlsv1 alert unknown ca)
192.168.1.3:41378: client disconnect
192.168.1.3:41378: server disconnect 127.0.0.1:9900
```
and nothing was written to dump.log, so nothing was send back to the actual jams server (which listens on port 9900).
If i try to open this address (jams.lan:9922) in browser then again everything is fine, getting 'lock' icon in address bar, and dump.log has some data.
Please make jami clients trust user installed certificates.Larbi GharibLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/57Smart video layout2022-06-23T18:53:59ZMehdi GhayourSmart video layouthttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/661segmentation fault if changing webcam resolution in settings2022-06-23T18:52:39Zring usersegmentation fault if changing webcam resolution in settingsHow to report a bug
-------------------
## One bug = one bug report
## Avoid duplicates
No duplicate found.
Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04
- Jami versi...How to report a bug
-------------------
## One bug = one bug report
## Avoid duplicates
No duplicate found.
Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: Ubuntu 20.04
- Jami version: Jami 202201251934
- What build you are using: Jami's own apt (https://jami.net/download-jami-linux/#open-modal-ubuntu-20.04-64-bit)
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Open Settings
3. Go to Audio/Video
4. Change resolution
- Expected result:
Resolution changed.
- Actual result:
Jami crashes with segmentation fault (DE: Speicherzugriffsfehler)
## Additional information
Logs:
```
[...]
Texture 0x7fb09717cfc0 () used with different accesses within the same pass, this is not allowed.
Texture 0x7fb09717cfc0 () used with different accesses within the same pass, this is not allowed.
Texture 0x7fb09717cfc0 () used with different accesses within the same pass, this is not allowed.
Texture 0x7fb09717cfc0 () used with different accesses within the same pass, this is not allowed.
Texture 0x7fb09717cfc0 () used with different accesses within the same pass, this is not allowed.
Speicherzugriffsfehler
```
The "Texture 0x..." messages are there if I do not change the screen resolution (so Jami does not crash), too.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/162GNU/Linux->iOS send file after call (to confirm)2022-06-23T18:49:08ZSébastien BlinGNU/Linux->iOS send file after call (to confirm)# Scenario
+ GNU/Linux call iOS
+ iOS just let ringing
+ GNU/Linux hangup
+ GNU/Linux send a file immediately after (will fail, cause iOS will cut the socket)# Scenario
+ GNU/Linux call iOS
+ iOS just let ringing
+ GNU/Linux hangup
+ GNU/Linux send a file immediately after (will fail, cause iOS will cut the socket)Backloghttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/78Building gnome client fails during running Make2022-06-23T18:48:40ZJan WielkiewiczBuilding gnome client fails during running MakeHello, @sblin
I'm investigating the source of the bug #63 and for the purpose I'm trying to build Jami from git repository instead of from tarball.
The code I use is from this repo: https://review.jami.net/admin/repos/ring-client-gnom...Hello, @sblin
I'm investigating the source of the bug #63 and for the purpose I'm trying to build Jami from git repository instead of from tarball.
The code I use is from this repo: https://review.jami.net/admin/repos/ring-client-gnome
It fails during the make stage because of some "web.gresource.xml" that seems to be missing.
Any idea what's wrong?
Configure output:
```
-- No package 'appindicator3-0.1' found
-- Checking for module 'webkit2gtk-4.0'
-- Found webkit2gtk-4.0, version 2.28.2
Failed to open file “/tmp/guix-build-jami-202006-guix.drv-0/source/web/web.gresource.xml”: No such file or directory
-- Found Doxygen: /gnu/store/k1bncnrh2fvi3y8fr9zrsh334bzvhq2k-doxygen-1.8.17/bin/doxygen (found version "1.8.17") found components: doxygen missing components: dot
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/guix-build-jami-202006-guix.drv-0/build
phase `configure' succeeded after 6.2 seconds
```
Make output:
```
[ 36%] Generating ui/ui.gresource.c
cd /tmp/guix-build-jami-202006-guix.drv-0/source/ui &&
/gnu/store/kgdq89g6h3mjclxf3zb0sp7lz0yslrd4-glib-2.62.6-bin/bin/glib-compile-resources
--generate-source
--target=/tmp/guix-build-jami-202006-guix.drv-0/build/ui/ui.gresource.c
/tmp/guix-build-jami-202006-guix.drv-0/source/ui/ui.gresource.xml
make[2]: *** No rule to make target
'/tmp/guix-build-jami-202006-guix.drv-0/source/web/web.gresource.xml',
needed by 'web/web.gresource.c'. Stop. make[2]: Leaving directory
'/tmp/guix-build-jami-202006-guix.drv-0/build' make[1]: ***
[CMakeFiles/Makefile2:1258: CMakeFiles/jami-gnome.dir/all] Error 2
make[1]: Leaving directory
'/tmp/guix-build-jami-202006-guix.drv-0/build' make: *** [Makefile:133:
all] Error 2 command "make" failed with status 2 builder for
`/gnu/store/66cihl0vgkq5bh49mhqyqr21rgnc9pg2-jami-202006-guix.drv'
failed with exit code 1 build of
/gnu/store/66cihl0vgkq5bh49mhqyqr21rgnc9pg2-jami-202006-guix.drv failed
View build log at
'/var/log/guix/drvs/66/cihl0vgkq5bh49mhqyqr21rgnc9pg2-jami-202006-guix.drv.bz2'.
```https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/502Transform conversation into a QObject2022-06-23T18:48:10ZSébastien BlinTransform conversation into a QObjectand add signals for changing the profiles for exampleand add signals for changing the profiles for examplehttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/503Reading a vcard file with QFile/QTextStream takes a really long time2022-06-23T18:46:00ZAndreas TraczykReading a vcard file with QFile/QTextStream takes a really long time```
QTextStream in(&file);
QByteArray vcard = in.readAll().toUtf8();
```
takes ~40 seconds for a 43MB file```
QTextStream in(&file);
QByteArray vcard = in.readAll().toUtf8();
```
takes ~40 seconds for a 43MB fileAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1099F-Droid listing doesn't mention VOIP2022-06-23T18:41:37ZMustaqim MalimF-Droid listing doesn't mention VOIPHello, when using F-Droid's search function, and searching for "Voice over IP" or "VOIP", Jami doesn't show up as a result. Also its icon is the default iconless showing.
Thank you for this amazing product!Hello, when using F-Droid's search function, and searching for "Voice over IP" or "VOIP", Jami doesn't show up as a result. Also its icon is the default iconless showing.
Thank you for this amazing product!https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/590Emoji style on GNU/Linux2022-06-23T18:38:16ZAltonsEmoji style on GNU/LinuxIs this kind of emoji styling the expected result?
![image](/uploads/a87689651c2694f456c402da5e00ed04/image.png)
![image](/uploads/b9fbf88db96cab64e5b7964596e99036/image.png)
I feel like this style is not very appealing. Is this an is...Is this kind of emoji styling the expected result?
![image](/uploads/a87689651c2694f456c402da5e00ed04/image.png)
![image](/uploads/b9fbf88db96cab64e5b7964596e99036/image.png)
I feel like this style is not very appealing. Is this an issue on my device or an expected result? For me it would be more logical for the end-user experience to have a consistent style accross the emoji-picker and the conversation.
Jami version: 202111042021 GNU/Linux
OS: Fedora 35, Gnome + Waylandhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1445Is there an issue with the 332 apk file on fdroid?2022-06-23T17:08:39ZJames BealeIs there an issue with the 332 apk file on fdroid?When I upgrade through fdroid, version 332 immediately crashes on launch.
When I do a fresh re-install of 332, downloaded from fdroid, version 332 crashes on launch.
I've had to downgrade to 331 to make Jami work.
I created an entry in ...When I upgrade through fdroid, version 332 immediately crashes on launch.
When I do a fresh re-install of 332, downloaded from fdroid, version 332 crashes on launch.
I've had to downgrade to 331 to make Jami work.
I created an entry in the forum on 15th June to ask if anyone else was having this problem:
> Has anyone else found that Version 20220602-01 (332) for Android crashes instantly upon launch?
>
> I’ve had to downgrade to 331.
>
> Steps taken:
>
> Ran upgrade within F-Droid - 332 crashed upon launch
> Uninstalled
> Installed 332 from .apk (cx.ring_332.apk) - crashed upon launch
> Uninstalled and downgraded to 331 using the .apk
>
> Hardware & OS:
> Amazon Fire 7 (9th generation)
> Android 9 (I think)
>
> Before posting a formal technical/bug report, it would be good to know if anyone else has experienced this.
So far nobody else has reported an issue.
Because the crash happens immediately upon launch, and every time, I get no option to look at the logs.
Hardware & OS:
- Amazon Fire 7 (9th generation)
- Android 9 (I think)
Steps undertaken today, 21st June:
Android settings / clear data (storage and cache) for Jami, then uninstall.
Install 332 from .apk file downloaded from fdroid site (https://f-droid.org/packages/cx.ring/).
Crashes on launch.
- Boot to safe mode.
- Settings / clear data (storage and cache) for Jami, then uninstall.
- Re-download .apk file from fdroid site (https://f-droid.org/packages/cx.ring/).
- Install. Immediate crash on launch.
- Settings / clear data (storage and cache) for Jami, then uninstall.
- Revert to 331 from .apk file.
- All fine.
Is there an issue with the copy of 332 on the fdroid site? Or something else? 331 is working fine on my equipment.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/687Agent: add a bulk calls scenario2022-06-22T20:57:49ZMohamed ChibaniAgent: add a bulk calls scenario# Description
Add a Scheme test scenario to perform 50 calls in a row. The calls must be made in a single registration (do not unregister the account after each call).
# Configuration
- Jami account
- UPNP disabled
- TURN enabled
- Audi...# Description
Add a Scheme test scenario to perform 50 calls in a row. The calls must be made in a single registration (do not unregister the account after each call).
# Configuration
- Jami account
- UPNP disabled
- TURN enabled
- Audio/Video calls
# Test scenario
- Create and register two accounts (Alice + Bob)
- While (callCount < 5)
- Alice calls Bob
- Bob answers
- Alice waits 4 seconds
- Alice hangs up
- Alice waits 4 seconds
The scenario must work flawlessly on local machines and CI test machines (Jenkins)
The scenario will be added to CI (Jenkins) either as a separate job or added to daemon-test job (to be determined)Mohamed ChibaniOlivier DionMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/740Build fail: issue with ice_transport.cpp2022-06-22T20:31:46ZEnricoBuild fail: issue with ice_transport.cppI attempted to build jami-daemon on openSUSE Tumbleweed.
The project repository can be found here: https://build.opensuse.org/package/show/home:iDesmI:jami/jami-daemon
I'll attach the build log:
[_log-jami-daemon.txt](/uploads/fd190a2639...I attempted to build jami-daemon on openSUSE Tumbleweed.
The project repository can be found here: https://build.opensuse.org/package/show/home:iDesmI:jami/jami-daemon
I'll attach the build log:
[_log-jami-daemon.txt](/uploads/fd190a263971d22ceb9b40aa2f3f3a13/_log-jami-daemon.txt)
There seems to be a problem in compiling ice_transport.cpphttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1441Failed to reinstall2022-06-21T01:38:24ZChangranZhangFailed to reinstallI tried to remove and reinstall jami since it is impossible for jami to upgrade itself. However, the remove step is finished luckily, but the reinstall step failed with an error like "unable to find device or file". As I cancelled the in...I tried to remove and reinstall jami since it is impossible for jami to upgrade itself. However, the remove step is finished luckily, but the reinstall step failed with an error like "unable to find device or file". As I cancelled the installation, a dialog tell me that that the installer has encountered an unexpected error with error code 2755. Could someone please tell me how can I reinstall it? Thanks a lot!https://git.jami.net/savoirfairelinux/jami-project/-/issues/1439Add contact: Contact is shown twice if you remove the contact2022-06-20T18:43:34ZElysAdd contact: Contact is shown twice if you remove the contactusing newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
...using newest beta version (both) Android and Windows 10 (different user accounts "account 1" -> "account 2")
(group chat (experimental) disabled)
Steps to reproduce
1. (Windows 10 user ="account 1") Search for a new user name /contact
2. (Windows 10 user ="account 1") Select the username "account 2" and click "Add to conversation"
3. [Android user ="account 2"] Accept contact and go to "Conversations"
4. (Windows 10 user ="account 1") Remove user "account 2"
5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
Now you have 2 possibilities (Windows 10 user ="account 1"):
a) If you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
b) The Windows 10 user ="account 1" did **NOT** select "Add to conversation" but immediately makes a video call (step 2) and already ended the video call. - So the windows 10 user only views the chat view anymore.
A little bit different:
> 4. (Windows 10 user ="account 1") Remove user "account 2"
> 5. "account 2" (Swarm: Is true) is gone **but "account 2" (Swarm: Is false) appears**
However if you (windows 10 user) right click on the contact you can only view "Stop call" (although you don't have any call anymore) and contact details
(Windows 10:) You have to exit Jami and open Jami again: Now you can still view the "account 2" (Swarm: Is false) but you right click on the contact ("account 2") you can view all options and remove the contact
- The contact is now completely gone
However - [Android user ="account 2"] still has contact 1 in his contact list (not sure if this is a bug?)
If the android user ("account 2") does not remove "account 1" from his device and the windows 10 user (="account 1") start from step 1 mentioned above, Jami (Windows 10) will show the contact "account 2" Swarm: is falsehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/756A removed Swarm contact should be removed from the conversations list2022-06-20T15:37:14ZannaA removed Swarm contact should be removed from the conversations listHere are the steps to reproduce my issue.
1. I add a Swarm contact to my conversations.
2. Right click and choose "remove contact".
3. A new conversation with the deleted contact is immediately created and I see "Contact added" in the c...Here are the steps to reproduce my issue.
1. I add a Swarm contact to my conversations.
2. Right click and choose "remove contact".
3. A new conversation with the deleted contact is immediately created and I see "Contact added" in the chat history with the current time.
4. I repeat the right-click option. Now the conversation is removed from my list.
My expectation would be that removing contact once is enough to remove a contact.
I am using the latest version of the Qt client on Linux.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/754Jami client icons color fadded2022-06-17T21:51:29ZTNT BOM BOMJami client icons color fadded## Describe your environment
Please specify the following:
- OS: Debian 11
- Jami version: (There is no clearer way to know from within jami)
```
user@host:~$ apt policy jami
jami:
Installed: 20220516.0214.9b42ad3~dfsg1-1
```
- Wha...## Describe your environment
Please specify the following:
- OS: Debian 11
- Jami version: (There is no clearer way to know from within jami)
```
user@host:~$ apt policy jami
jami:
Installed: 20220516.0214.9b42ad3~dfsg1-1
```
- What build you are using: Using jami from repository for debian
## Steps to reproduce
- Can you reproduce the bug: always
- Steps:
1. Complete user registration
2. Check the colors of the icon (check the uploaded image)
- Actual result: No colors for the icons
- Expected result: There should be colors for the icons
## Additional information
![jaminocolors.cleaned](/uploads/2ecdfc2494cc7795678c2f2790fb2578/jaminocolors.cleaned.png)
logs:
[jamilog.txt](/uploads/a4543b66cac5e16b9ac60e280db07e26/jamilog.txt)