savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-25T18:36:16Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/975Link voice setup callback to host (without rtp session)2024-03-25T18:36:16ZSébastien BlinLink voice setup callback to host (without rtp session)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1603Plugin store queried on main thread even if preferences are not opened2024-03-24T17:12:00ZAdrien BéraudPlugin store queried on main thread even if preferences are not openedThe Plugin store is loaded on the main thread, and is starting network requests from the main thread,
at some places like when selecting a conversation,
which creates noticeable UI freezes and glitches, for instance when selecting a conv...The Plugin store is loaded on the main thread, and is starting network requests from the main thread,
at some places like when selecting a conversation,
which creates noticeable UI freezes and glitches, for instance when selecting a conversation.
All of this while Jami didn't have any plugin installed.
1. the Plugin store should not be refreshed on the main thread
2. the Plugin store should not be refreshed if not needed (to be checked that the plugin store doesn't repetitively make network requests when using Jami)
3. the Plugin store should not be refreshed or even loaded if no plugin is installed and the user doesn't go to the Extension settings page.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/974Various asserts and crashes with TURN / PJNATH2024-03-25T18:29:13ZAdrien BéraudVarious asserts and crashes with TURN / PJNATHTypical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 D...Typical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Build fingerprint: 'google/cheetah/cheetah:14/AP1A.240305.019.A1/11445699:user/release-keys'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Revision: 'MP1.0'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A ABI: 'arm64'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Timestamp: 2024-03-22 14:13:31.550572829-0400
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Process uptime: 2s
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Cmdline: cx.ring
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A pid: 8414, tid: 9172, name: Thread-64 >>> cx.ring <<<
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A uid: 10352
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Abort message: '../src/pjnath/turn_session.c:740: pj_status_t pj_turn_session_alloc(pj_turn_session *, const pj_turn_alloc_param *): assertion "sess->state>PJ_TURN_STATE_NULL && sess->state<=PJ_TURN_STATE_RESOLVED" failed'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x0 0000000000000000 x1 00000000000023d4 x2 0000000000000006 x3 000000795e531320
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x4 2f333639622d6d6e x5 2f333639622d6d6e x6 2f333639622d6d6e x7 7f7f7f7f7f7f7f7f
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x8 00000000000000f0 x9 0000007d40c87200 x10 0000000000000001 x11 0000007d40cd1ba0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x12 0000007d5ac86020 x13 000000007fffffff x14 00000000009ffbec x15 00000247cba606d0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x16 0000007d40d3cfc8 x17 0000007d40d1a160 x18 000000795b0d8000 x19 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x20 00000000000023d4 x21 00000000ffffffff x22 0000000000002374 x23 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x24 000000795e5318b0 x25 000000795e5318b0 x26 000000795e531bf0 x27 00000000000fc000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x28 00000000000fe000 x29 000000795e5313a0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A lr 0000007d40cc2e48 sp 000000795e531300 pc 0000007d40cc2e74 pst 0000000000001000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A 11 total frames
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A backtrace:
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #00 pc 000000000005ee74 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #01 pc 000000000005f284 /apex/com.android.runtime/lib64/bionic/libc.so (__assert2+36) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #02 pc 0000000001922e2c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_turn_session_alloc+284) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #03 pc 000000000192a61c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #04 pc 000000000192a258 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #05 pc 000000000194d5f4 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #06 pc 00000000019414bc /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (ioqueue_dispatch_write_event+416) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #07 pc 0000000001945428 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_ioqueue_poll+1476) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #08 pc 0000000001739b98 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #09 pc 00000000000ca7cc /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #10 pc 00000000000607b0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
```Sébastien BlinFrançois-Simon Fauteux-ChapleauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1602Ringtone device problem2024-03-22T09:55:11ZgregkotsaftisRingtone device problemI have two distinct audio outputs; speakers and headphones. I have configured the "Output Device" to be my headphones and "Ringtone Device" to be my speakers. Jami does not respect that and always uses my headphones as the ringtone devic...I have two distinct audio outputs; speakers and headphones. I have configured the "Output Device" to be my headphones and "Ringtone Device" to be my speakers. Jami does not respect that and always uses my headphones as the ringtone device. The same setup is checked with Discord, Skype, etc and is working correctly.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/973Flatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client de...2024-03-22T09:29:01ZovariFlatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client depends on>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.co...>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.com/flathub/net.jami.Jami/issues/86https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1634Power consumption increased significantly in the background since the introdu...2024-03-29T06:29:48ZPreston LeppanenPower consumption increased significantly in the background since the introduction of presence indicator
## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Since recent versions (version 20240308-01), message delivery became much more rel...
## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Since recent versions (version 20240308-01), message delivery became much more reliable. However, I've also observed a significant increase in power consumption of Jami background service. In my phone's battery usage statistics page, Jami drains 940 mAh within 3 hours, surpassing every single other applications, even including the ones I was actively using in foreground, the battery life is also much shorter than before, from an average of 5 hours of active usage down to only around 2 hours.
This is observed on both of my Xiaomi phones (different models with different Android versions: 12 and 13).
## Steps to reproduce
Can you reproduce the bug: always
1. Jami -> Advanced Settings -> Disable Push
2. Jami -> Advanced Settings -> Enable Start Jami on startup
3. Jami -> Advanced Settings -> Enable Run in background
4. Refer to https://dontkillmyapp.com/ for disabling OEM background app killer mechanism
5. Use your phone normally
#### Expected result
Idle consumption would be higher than a typical instant messenger due to the way Jami works, but not by several orders of magnitude.
#### Observed result
The phone overheats continuously and the battery drains very quickly, it heavily impacts the battery life in both active usage and idle time negatively.
## Additional information
I'm not familiar with Jami code base, but one of the thing coming into my mind is this: https://github.com/simplex-chat/simplex-chat/issues/1821 , SimpleX Chat suffers from battery drain as well.
Perhaps the frequency of keep-alive packet and reconnect attempt needs to be reduced, or some talky metadata transfer needs to be deferred and grouped when Jami client isn't on foreground (similar to XMPP).https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1601Implement modified contact profile synchronization2024-03-19T13:01:48ZPierre NicolasImplement modified contact profile synchronizationImplement modified contact profile synchronization across devices. https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972Implement modified contact profile synchronization across devices. https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/361Implement modified contact profile synchronization2024-03-19T13:01:47ZPierre NicolasImplement modified contact profile synchronizationImplement modified contact profile synchronization across devices. https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972Implement modified contact profile synchronization across devices. https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1633Implement modified contact profile synchronization2024-03-19T13:01:47ZPierre NicolasImplement modified contact profile synchronizationImplement modified contact profile synchronization across devices.
https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972Implement modified contact profile synchronization across devices.
https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1632Buttons are missing in CallView when Android interface scaling and font scali...2024-03-19T13:20:57ZPreston LeppanenButtons are missing in CallView when Android interface scaling and font scaling are set to too large## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When yo...## Environment
- Jami version: 20240308-01
- Device model: Xiaomi Mi 10T Lite
- Android version: 12
- What build you are using: F-Droid
## Description
Android has scaling options for interface/font in display settings. When you change the scaling to the largest, buttons in CallView are no longer visible.
<img src="/uploads/f7b16d478c43666770f03231f58ba0b1/c92cb1f3-fcb3-499d-afb5-ea1f8c33ede0.png" width="200"/>
This can be partially considered an accessibility issue, as users with difficulty reading small texts are more likely to change Android interface/font scaling option.
## Steps to reproduce
How often can you reproduce the bug: always
#### Steps:
1. Open Android Settings app -> Display (Some vendors might have different locations, for example in Accessibility -> Vision -> Display)
2. Find Display scale settings, change it to the largest
3. Find Font scale settings, change it to the largest
4. Open Jami, make a voice/video call
#### Expected result:
Buttons in CallView are visible. I can hang-up the call without using Android notification center.
#### Actual result:
Buttons are missing in CallView, including the hang-up button. I have to resort to notification center to hang-up the call.
## Additional information
Jami has multiple similar issues when display scale is too large (logical size is too small), like https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1226 to name one.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1637Show translated article title in the web browser window title2024-03-16T22:01:55ZovariShow translated article title in the web browser window titlePlease show the translated article title in the web browser window title
https://jami.net/improved-reliability-presence-and-message-status/?lang=hu
![image](/uploads/538d1bca53735f8538ac534254484264/image.png)
Thank you
Cc: @plarosePlease show the translated article title in the web browser window title
https://jami.net/improved-reliability-presence-and-message-status/?lang=hu
![image](/uploads/538d1bca53735f8538ac534254484264/image.png)
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1636Newsletter Privacy Policy2024-03-16T21:57:00ZovariNewsletter Privacy PolicyPlease enable `Newsletter Privacy Policy` to be translatable
https://jami.net/newsletter-privacy-policy/?lang=hu
Thank you
Cc: @plarosePlease enable `Newsletter Privacy Policy` to be translatable
https://jami.net/newsletter-privacy-policy/?lang=hu
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1600Swarm conversation does no load after restoring account backup2024-03-25T15:21:11Zring userSwarm conversation does no load after restoring account backupBug report form
---------------
## Describe your environment
Please specify the following:
Device 0. is not available anymore and had account A and had a connection to account B as well ad device 2.
1.
- OS: Ubuntu 22.04
- Jami versi...Bug report form
---------------
## Describe your environment
Please specify the following:
Device 0. is not available anymore and had account A and had a connection to account B as well ad device 2.
1.
- OS: Ubuntu 22.04
- Jami version: Current Snap: Eleutheria Version: 202402141827
- What build you are using: Snap
- EDIT: Account A.
2.
- OS: Android
- Jami version: Current F-Droid: Eleutheria 20240308-01
- What build you are using: Snap
- EDIT: Account B.
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Import a backup of a Jami account A. in Jami 1.
2. Both Jami 1 and Jami 2 are online
3. I open a conversation between Jami 1. and 2.
4. I send a messages from 2. to 1.
- Actual result:
1. If I open the conversation on device 1., I see the following message:
- `Sie haben die Unterhaltungsanfrage angenommen`
- `Warten bis ## eine Verbindung herstellt, um die Unterhaltung zu synchronisieren.`
2. I cannot read any messages or chat because neither the messages nor the chat text field is shown.
3. Calls are working.
4. There is no possibility to continue the conversation.
- Expected result:
1. The conversation is synchronizing or is synchronized and I can use it.
2. The messages send are shown in Jami 1.
3. Calls are working.
4. I can continue the conversation.
## Additional information
```
[1710587184.680|43502|manager.cpp :957 ] ############## START MONITORING ##############
[1710587184.680|43502|manager.cpp :958 ] Using PJSIP version 2.13.1 for x86_64-pc-linux-gnu
[1710587184.680|43502|manager.cpp :959 ] Using GnuTLS version 3.8.2
[1710587184.680|43502|manager.cpp :960 ] Using OpenDHT version 3.1.7
[1710587184.680|43502|manager.cpp :967 ] Opened files: 106
[1710587184.680|43502] ConnectionManager current status:
[1710587184.680|43502] ConnectionManager end status.
[1710587184.680|43502|manager.cpp :976 ] ############## END MONITORING ##############
[1710587196.589|43915] [device ###] Received request answer
[1710587196.589|43915] [device ###] Respond received, but cannot find request
```
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-project/-/issues/1634Add `Subscribe to newsletter` to `Join the Jami community` on https://jami.ne...2024-03-16T10:53:34ZovariAdd `Subscribe to newsletter` to `Join the Jami community` on https://jami.net/contribute/@plarose should `Subscribe to the Jami newsletter` be added to https://jami.net/contribute/ under the section `Join the Jami community`?
![image](/uploads/3614ba3db7ea7192c2095e4f3bb7c18d/image.png)
What do you think?
Thank you@plarose should `Subscribe to the Jami newsletter` be added to https://jami.net/contribute/ under the section `Join the Jami community`?
![image](/uploads/3614ba3db7ea7192c2095e4f3bb7c18d/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1633`Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?2024-03-16T10:43:57Zovari`Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?1. Visit https://jami.net/contribute/
2. Under the `Join the Jami community` heading
3. `Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?<br>
![image](/uploads/07245250bff2357eaf9ce60688ccf32d/image.png)
What do you think?
Than...1. Visit https://jami.net/contribute/
2. Under the `Join the Jami community` heading
3. `Mailling` typo? Should it be `Mailing`, i.e. only 1 "l"?<br>
![image](/uploads/07245250bff2357eaf9ce60688ccf32d/image.png)
What do you think?
Thank you
Cc: @plarosehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1632Add `MUO` article to `Mentioned In` on https://jami.net/2024-03-16T10:25:38ZovariAdd `MUO` article to `Mentioned In` on https://jami.net/@plarose should a link to the `MUO: Make Use Of_` article below be added to https://jami.net/ under the section `Mentioned In`?
![image](/uploads/cf97b795007a0e4a5bd2835799a29ca3/image.png)
`MUO: Make Use Of_` article by Danny Maiorca ...@plarose should a link to the `MUO: Make Use Of_` article below be added to https://jami.net/ under the section `Mentioned In`?
![image](/uploads/cf97b795007a0e4a5bd2835799a29ca3/image.png)
`MUO: Make Use Of_` article by Danny Maiorca and Hilda Munjuri Updated Mar 8, 2024
### The 4 Best Open-Source Video Conferencing Software
https://www.makeuseof.com/open-source-video-conferencing-software/
![image](/uploads/df746224a25bd87821b05939e5e18dbd/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1629First back press close conversation instead of settings2024-03-28T00:05:08ZPierre NicolasFirst back press close conversation instead of settings## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It sho...## Describe your environment
Please specify the following:
- Jami version: 410
## Steps to reproduce
- Can you reproduce the bug: at will
- Actual result: The conversation is closed at my first click
- Expected result: It should close the settings page.
## Additional information
![Screen_recording_20240315_105829](/uploads/58aa1e8b141426437ee7ddfedb775b04/Screen_recording_20240315_105829.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/360update UI for swarm creation2024-03-14T19:42:04ZKateryna Kostiukupdate UI for swarm creationKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1628Layout bugs on settings pages2024-03-13T14:58:49ZVitalii NikitchynLayout bugs on settings pages- Jami version: 20240308-01
- Device model: all (landscape view mode)
- What build you are using: my own -> 86f9804af37b06df6b46a2992c55810782415a80
1. Scrollview cut bottom content on settings pages. Check all settings fragment, ...- Jami version: 20240308-01
- Device model: all (landscape view mode)
- What build you are using: my own -> 86f9804af37b06df6b46a2992c55810782415a80
1. Scrollview cut bottom content on settings pages. Check all settings fragment, including "Account Settings", "Advanced Settings" and "About Jami"
![menu](/uploads/e44094c8558b7b2bd9e12629a0319efd/menu.png)
![Screenshot_1710268084](/uploads/c3ca4443c764d0f320869cb1f8e01d7e/Screenshot_1710268084.png)
2. Settings fragments: Appbar blink on navigation. Check all settings fragment, including "Account Settings", "Advanced Settings" and "About Jami"
![Screen_recording_20240313_101323](/uploads/95dab11c98a7233bfde1a4096952938c/Screen_recording_20240313_101323.mp4)Vitalii NikitchynVitalii Nikitchynhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1598Call ownaccount 1 -> ownaccount 2: Ownaccount 2 does not show the incoming ca...2024-03-12T17:09:11ZElysCall ownaccount 1 -> ownaccount 2: Ownaccount 2 does not show the incoming call unless you click on the account in the contact listusing Jami Version (Beta): 202403061444
Steps to reproduce:
* You are using two own Jami accounts at the same time (desktop; Windows 10)
* Make a call own ownaccount 1 -\> ownaccount 2 (while you are viewing the contact list of "ownacc...using Jami Version (Beta): 202403061444
Steps to reproduce:
* You are using two own Jami accounts at the same time (desktop; Windows 10)
* Make a call own ownaccount 1 -\> ownaccount 2 (while you are viewing the contact list of "ownaccount1")
* You view the ongoing call (like "Connecting", "Calling")
* Now go to ownaccount 2: You just view the contact list (and "ongoing call" within the contact list) but you actually don't view the "incoming call banner" - You have to click on the contact in the contact list to view the call banner
---
Not sure if it should be possible -but system notifications also won't be shown