savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-12-01T21:30:50Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/659swarm: stay in "Already fetching for"2021-12-01T21:30:50ZSébastien Blinswarm: stay in "Already fetching for"Sometime, communication between 2 same devices is blocked.
In the logs, I see "Already fetching for"
For now, no scenario is identifiedSometime, communication between 2 same devices is blocked.
In the logs, I see "Already fetching for"
For now, no scenario is identifiedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1028Conversation: Missing messages in conversation2022-08-28T03:07:30Zmika-nlConversation: Missing messages in conversation
When you receive a message on android, you do not see the message appear (not even a notification) but I know that the other person has sent something.
force closing and reopening the android app solves the problem for a while.
this hap...
When you receive a message on android, you do not see the message appear (not even a notification) but I know that the other person has sent something.
force closing and reopening the android app solves the problem for a while.
this happens a few times a day.
Sometimes the contact list is also empty, even then it helps to close the app completely and restart it.
It seems that the demon continues to work but the UI crashes
Please specify the following:
- Ring version: latest jami (beta) but also earlyer beta
- Device model: oneplus 6
- Android version: lineageOS
- What build you are using: Play Store
but also same version jami on oppo a72 give this problem.Maxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/22crash: WaterMark not initilizing filter2021-11-18T01:50:19ZAline Gondim Santoscrash: WaterMark not initilizing filter```
on JPEG) (mjpeg)
[1636201319.764| 6174|accel.cpp :151 ] Found compatible hardware format for mjpeg decoder with nvdec
Watermark: [logo]scale=0.251280:0.25720:force_original_aspect_ratio='decrease',format=yuva444p,split=2[bg]...```
on JPEG) (mjpeg)
[1636201319.764| 6174|accel.cpp :151 ] Found compatible hardware format for mjpeg decoder with nvdec
Watermark: [logo]scale=0.251280:0.25720:force_original_aspect_ratio='decrease',format=yuva444p,split=2[bg][fg],[bg]drawbox=c='black@0.0':replace=1:t=fill[bg],[bg][fg]overlay=format=auto
Input #0, png_pipe, from '/home/cyrille/savoirfairelinux.png':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: png, rgba(pc), 1280x361 [SAR 3543:3543 DAR 1280:361], 25 fps, 25 tbr, 25 tbn, 25 tbc
[Parsed_scale_0 @ 0x7fc1e08aa980] [Eval @ 0x7fc200ff3430] Invalid chars '.251280' at the end of expression '0.251280'
[Parsed_scale_0 @ 0x7fc1e08aa980] Cannot parse expression for width: '0.251280'
[AVFilterGraph @ 0x7fc1e08a5580] Error initializing filter 'scale' with args '0.251280:0.25*720:force_original_aspect_ratio=decrease'
Frame Filter: : (-22) Failed to parse filter graph
Frame Filter: : (-1) Filter not initialized
Frame Filter: : (-1) Filter not initialized
Frame Filter: : (-1) Not properly initialized
Erreur de segmentation (core dumped)
```Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1341two jami settings don't work in android2021-11-16T14:58:50Zhigol higoltwo jami settings don't work in androida gorgeous messenger, very necessary! but two rather important settings don't work in android 5 and 6 (I haven't tested them in newer versions of android, I don't have them). 1- disabled jamie autorun at system startup and permission to ...a gorgeous messenger, very necessary! but two rather important settings don't work in android 5 and 6 (I haven't tested them in newer versions of android, I don't have them). 1- disabled jamie autorun at system startup and permission to run in the background. 2- forbade jamie autorun in permissions. 3- stopped jamie in the settings. However, after a while (about 2-3 hours, I won't say more precisely), jamie still starts itself! I believe it starts because of cyclic data synchronization, which should be disabled by these settings, for example, by disabling work in the background. Please tell me, is this how it should be, or is it a mistake?![Screenshot_2021-11-08-18-17-03](/uploads/f13109b0e189ed3259a3a847cdba57fa/Screenshot_2021-11-08-18-17-03.png)![Screenshot_2021-11-08-18-18-43](/uploads/f4e9e7d98d6785e8734794d91710196e/Screenshot_2021-11-08-18-18-43.png)![Screenshot_2021-11-08-18-19-47](/uploads/130aa2dd8ad5b7a39bb3aa315e77e4c9/Screenshot_2021-11-08-18-19-47.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/588Duplicate items in the conversation list2021-11-10T10:42:07ZovariDuplicate items in the conversation listThe conversation list has duplicates of some, but not all, of the conversations.
Seems to be a regression since the update to Version: 202111041938.
Are you able to reproduce? And fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt...The conversation list has duplicates of some, but not all, of the conversations.
Seems to be a regression since the update to Version: 202111041938.
Are you able to reproduce? And fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202111041938 deb editionhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1340Can't delete messages option on Linux2021-11-11T14:12:23ZNikolaY DimitrovCan't delete messages option on LinuxThere is no way to delete messages on Linux's Jami after last update Version: 202111051449. And messages gets gray to black immediately, but are not send.
Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Deskto...There is no way to delete messages on Linux's Jami after last update Version: 202111051449. And messages gets gray to black immediately, but are not send.
Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionichttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1339Missing tag android/release_3212021-12-23T12:41:37ZBruno PaganiMissing tag android/release_321This tag does not appear under https://git.jami.net/savoirfairelinux/jami-project/-/tags, which implies F-Droid did not pick it up, while this is the version available in the PlayStore.This tag does not appear under https://git.jami.net/savoirfairelinux/jami-project/-/tags, which implies F-Droid did not pick it up, while this is the version available in the PlayStore.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1027the jami interface in android 5.1 is distorted2021-11-30T15:21:05Zhigol higolthe jami interface in android 5.1 is distorted![Screenshot_2021-09-22-15-05-13](/uploads/ea3a011fd67381c739473206b6c7ccf3/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/13b13d8250aaf4dc0c398f909fcf66c0/Screenshot_2021-11-05-18-07-48.png)![Screenshot_2021-09-22-15-05-13](/uploads/ea3a011fd67381c739473206b6c7ccf3/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/13b13d8250aaf4dc0c398f909fcf66c0/Screenshot_2021-11-05-18-07-48.png)Maxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1338the jami interface in android 5.1 is distorted2021-11-05T18:42:12Zhigol higolthe jami interface in android 5.1 is distorted![Screenshot_2021-09-22-15-05-13](/uploads/049ed03880e3369461886fd51326f0c5/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/8187f58fd724d857706c3d7304c4300c/Screenshot_2021-11-05-18-07-48.png)![Screenshot_2021-09-22-15-05-13](/uploads/049ed03880e3369461886fd51326f0c5/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/8187f58fd724d857706c3d7304c4300c/Screenshot_2021-11-05-18-07-48.png)Maxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1337The incoming call is displayed for 30 seconds, no more2021-11-05T12:50:12ZIvan DanyliukThe incoming call is displayed for 30 seconds, no moreI use my own sip account
the incoming call is displayed for 30 seconds and is interrupted
on the sip server there are no restrictions, tested on other softphones, everything works
can i adjust this somehow in the settings jami?
Jami Dae...I use my own sip account
the incoming call is displayed for 30 seconds and is interrupted
on the sip server there are no restrictions, tested on other softphones, everything works
can i adjust this somehow in the settings jami?
Jami Daemon 10.1.0 (linux)
Linux-Mint 19-20https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/658Lag with decodingAccelerated: true2021-12-23T21:54:34ZSébastien BlinLag with decodingAccelerated: trueIn fact I see 3 bugs:
1. In `SinkClient::update`
doTransfer is True even if video-split is not used yet (cf Conference::sendConferenceInfos(), no delay if createSinks is commented). This must be false if sink is not used. This means th...In fact I see 3 bugs:
1. In `SinkClient::update`
doTransfer is True even if video-split is not used yet (cf Conference::sendConferenceInfos(), no delay if createSinks is commented). This must be false if sink is not used. This means that registerSinkClient is done in LRC even if sink is not used
2. HAVE_SHM is true if libwrap is true in LRC. We should change the configure to have enable-shm with dbus and not with libwrap.
3. `HardwareAccel::transferToMainMemory` is called for every participant, for every sink client. It should be done only once and then cropped by the sink clients.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/657conference/RDV - remote participant crash when changing layout2021-11-16T22:04:31ZMohamed Chibaniconference/RDV - remote participant crash when changing layoutScenario as reported:
- configure an account as RDV, and add participants
- the moderator toggles the layout between ONE_BIG and GRID (mosaic)
- sometimes, one of the remote participants crashes
[UPDATE] might be fixed by [#580](https:/...Scenario as reported:
- configure an account as RDV, and add participants
- the moderator toggles the layout between ONE_BIG and GRID (mosaic)
- sometimes, one of the remote participants crashes
[UPDATE] might be fixed by [#580](https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/580), need confirmation \
[UPDATE 2] was not reproduced since the merge of [#580](https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/580)Mohamed ChibaniSébastien BlinMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1336No line-break on Debian 112022-03-17T14:29:13ZriveravaldezNo line-break on Debian 11Hi, this is an updated Debian Stable 11 (Bullseye) with:
```
$ uname -a
Linux debian 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
$ apt-cache policy jami jami-daemon
jami:
Instalados: 20210112.2.b757bac~ds1-1
...Hi, this is an updated Debian Stable 11 (Bullseye) with:
```
$ uname -a
Linux debian 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
$ apt-cache policy jami jami-daemon
jami:
Instalados: 20210112.2.b757bac~ds1-1
Candidato: 20210112.2.b757bac~ds1-1
Tabla de versión:
*** 20210112.2.b757bac~ds1-1 500
500 https://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
jami-daemon:
Instalados: 20210112.2.b757bac~ds1-1
Candidato: 20210112.2.b757bac~ds1-1
Tabla de versión:
*** 20210112.2.b757bac~ds1-1 500
500 https://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
```
, and the issue is visible in the non-crossed-out lines below:
**Non-maximized window.**
![JamiNoLineBreak](/uploads/6681b85c332987aecffe9afc4f71fe15/JamiNoLineBreak.png)
**Maximized window.**
![JamiNoLineBreakMaximized](/uploads/9a5023d572009870908e3c7161a78ac1/JamiNoLineBreakMaximized.png)
Let me know if there's any other info I could add to help deal with this, please.
Kind regards and thanks a lot!https://git.jami.net/savoirfairelinux/jami-project/-/issues/1335Links on https://jami.net/contribute/2023-05-05T21:16:29ZovariLinks on https://jami.net/contribute/Please:
1. - [x] Update the `GitLab` link from https://git.jami.net/savoirfairelinux/ring-project/wikis/home to https://git.jami.net/savoirfairelinux/jami-project/-/wikis/home
2. - [x] Update the `Instructions` link from https://git.jami...Please:
1. - [x] Update the `GitLab` link from https://git.jami.net/savoirfairelinux/ring-project/wikis/home to https://git.jami.net/savoirfairelinux/jami-project/-/wikis/home
2. - [x] Update the `Instructions` link from https://git.jami.net/savoirfairelinux/ring-project to https://git.jami.net/savoirfairelinux/jami-project
3. - [ ] Add a `Donate` link to https://www.paypal.com/donate?hosted_button_id=MGUDJLQZ4TP5W (unless there is a page for giving financial donations in addition to PayPal as described in https://git.jami.net/savoirfairelinux/jami-project/-/issues/1330)
![image](/uploads/096b77efdedfaf1c031b7e74f69d3483/image.png)
What do you think?
Thank you
Cf. https://forum.jami.net/t/changes-in-addresses-of-jamis-git-repositories/944Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/587Code smell: remove set_currentRenderingDeviceType from avadapter2023-02-21T20:59:19ZSébastien BlinCode smell: remove set_currentRenderingDeviceType from avadapterThere is already the info in LRC per call. This should be used.There is already the info in LRC per call. This should be used.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1277Call UI not shown when being answered2021-11-12T02:56:37ZPier-Luc ThériaultCall UI not shown when being answeredBug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square bracket...Bug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [ ] I downloaded it from jami.net
- [x] I built it from source using the build.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1.Open Jami
2.Make a call
3.Wait for connection
## What you expect to happen:
When the other side picks up the call UI is shown.
## What happens instead:
The connecting interface is kept with the Talking label.
I need to click the contact to see the call ui.
## Additional information
At that moment I am already listening to my asterisk music
![connecting](/uploads/7cf2b7e00ecfe8d27fe69f3ec6079b66/connecting.png)
It should look like this:
![call-ui](/uploads/8fd36bf6cb3d81068d5af0ded0d435cb/call-ui.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1334French version of the jami.net/contribute website is broken2021-11-02T09:18:06ZAltonsFrench version of the jami.net/contribute website is brokenOn the bottom of the page, the social media part of the french version of https://jami.net/contribute is broken.
![image](/uploads/c89bbeaa739bbc09beed90b2463c7324/image.png)On the bottom of the page, the social media part of the french version of https://jami.net/contribute is broken.
![image](/uploads/c89bbeaa739bbc09beed90b2463c7324/image.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1333libappindicator3-dev removed in debian 112021-11-01T13:35:07ZPier-Luc Thériaultlibappindicator3-dev removed in debian 11Hi libappindicator3-dev is deprecated and have been removed from debian 11.
Changing the dependency for libayatana-appindicator3-dev in build.py allowed me to build.
I am not aware of side effects of this solutionHi libappindicator3-dev is deprecated and have been removed from debian 11.
Changing the dependency for libayatana-appindicator3-dev in build.py allowed me to build.
I am not aware of side effects of this solutionhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/585Starting jami-qt leads to white window only2021-10-29T18:26:27ZJee XStarting jami-qt leads to white window onlyHow 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: Arch Linux
- Jami version: Jami 202110182000 (from arch repo).
## Steps to reproduce
When I start jami-qt I have white window without any text or options. The icon appears ok.
Here is starting log:
```
$ jami-qt --debug
"notify server name: mako, vendor: emersion, version: 0.0.0, spec: 1.2"
No migration required
Cannot find dbus interface for screen saver
Syncing lrc accounts list with the daemon
NetworkManager client initialized, version: , daemon running: no , networking enabled: no
no primary network connection detected, check network settings
qrc:/src/mainview/MainView.qml:327:9: Type WizardView unavailable
qrc:/src/wizardview/WizardView.qml:125:13: Type BackupKeyPage unavailable
qrc:/src/wizardview/components/BackupKeyPage.qml:56:5: Type SimpleMessageDialog unavailable
qrc:/src/commoncomponents/SimpleMessageDialog.qml:26:1: Type BaseDialog unavailable
qrc:/src/commoncomponents/BaseDialog.qml:20:1: module "QtQuick.Dialogs" is not installed
^CTerminated
```
Details. My network set using systemd-networkd.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1026Can trigger calls with return from PiP2021-11-09T20:44:10ZSébastien BlinCan trigger calls with return from PiP# Scenario
+ Open Jami
+ Launch a call
+ Go in PiP mode (via Home)
+ Return from the PiP to the call
+ Press on return (not home)
=> This open the launcher without PiP
+ Click on Overview and select the latest Jami
=> A new call is l...# Scenario
+ Open Jami
+ Launch a call
+ Go in PiP mode (via Home)
+ Return from the PiP to the call
+ Press on return (not home)
=> This open the launcher without PiP
+ Click on Overview and select the latest Jami
=> A new call is launched, there is two instances of Jami with 2 active calls.