savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-07-11T15:54:13Zhttps://git.jami.net/savoirfairelinux/jami-docs/-/issues/3Choose a license2022-07-11T15:54:13ZAnjandev MomiChoose a licenseAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/719Call Audio Recording Not Working2022-07-13T13:28:17ZtrymeoutCall Audio Recording Not WorkingRecording files are not made when the call is an audio only. I would expect a audio or video file to be generated when recording a call were no ones camera is on.Recording files are not made when the call is an audio only. I would expect a audio or video file to be generated when recording a call were no ones camera is on.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/682pjnath/ice_strans: Relay candidate has invalid socket.2022-07-13T13:50:45ZOlivier Dionpjnath/ice_strans: Relay candidate has invalid socket.### How to reproduce
Call someone until there's too many open file descriptor (failed allocation of turn socket). Must have `TURN.enable` set to `true`.
### Result
Failed assertion in `pjnath/ice_strans.c:`
```
pj_assert(pj_sockaddr...### How to reproduce
Call someone until there's too many open file descriptor (failed allocation of turn socket). Must have `TURN.enable` set to `true`.
### Result
Failed assertion in `pjnath/ice_strans.c:`
```
pj_assert(pj_sockaddr_has_addr(&cand->addr));
```
where `cand` has type `PJ_ICE_CAND_TYPE_RELAYED` and status of `PJ_SUCCESS`, but does not have a foundation nor a valid socket (sa_family == 0).
I suspect
```c
/* If the error happens during pj_turn_sock_create() or
* pj_turn_sock_alloc(), the candidate hasn't been added
* to the list.
*/
if (cand) {
pj_turn_session_info info;
pj_turn_sock_get_info(turn_sock, &info);
cand->status = (old_state == PJ_TURN_STATE_RESOLVING)? PJ_ERESOLVE : info.last_status;
}
```
to be the cause, because the candidate is added to the list between `pj_turn_sock_create()`
and `pj_turn_sock_alloc()`.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/298Swarm: Remove a device from the conversation2022-07-13T17:35:28ZSébastien BlinSwarm: Remove a device from the conversation+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add tests+ Implement https://git.jami.net/savoirfairelinux/ring-project/wikis/Group-chat-feature-(design-draft)#remove-a-device-from-a-conversation
+ Add testsSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-docs/-/issues/5When do I need a server?2022-07-13T17:51:25ZElysWhen do I need a server?There are already articles about the servers that can be used:
https://jami.net/why-is-jami-truly-distributed/ and https://jami.net/establishing-peer-to-peer-connections-with-jami/
But can you add examples where I must use a server:
E...There are already articles about the servers that can be used:
https://jami.net/why-is-jami-truly-distributed/ and https://jami.net/establishing-peer-to-peer-connections-with-jami/
But can you add examples where I must use a server:
Example:
Sending and receiving text messages with/without attachments actually needs no servers (STUN, TURN, etc)?
- it does not matter if all participants use the same network or different networks?
- just name servers?
- text conversations with more users (1:1, up to 8 users; even more)
- size of the attachment does not affect the need of servers
Make video / audio calls
- I don't need any (signaling?) servers if all users use the same network
- I need servers (STUN, TURN, etc) if all users / or one user use(s) different networkshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/710Jami uses the GPU when idle2022-07-14T19:18:43ZA. SpennerJami uses the GPU when idleJami is using about 7-8 percentage in an idle/passive state when GUI is open.
"Enable hardware acceleration" is disabled inside Audio/Video settings.
The result above can also be seen as an overlay if running Jami together with "MSI Af...Jami is using about 7-8 percentage in an idle/passive state when GUI is open.
"Enable hardware acceleration" is disabled inside Audio/Video settings.
The result above can also be seen as an overlay if running Jami together with "MSI Afterburner" / "RivaTuner Statistics Server".
OS: Windows 10 Pro (20H2 19042.1466)
Version: 202112221635 TaranisAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/605Make qt client accessible to screen reader2022-07-14T19:59:35ZSébastien BlinMake qt client accessible to screen readerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/581Move `Leave call` button away from the microphone and camera buttons to preve...2022-07-14T20:05:44ZovariMove `Leave call` button away from the microphone and camera buttons to prevent accidental call hang-upsMove `Leave call` button away from the microphone and camera buttons to prevent accidental call hang-ups
[Jitsi Meet](https://meet.jit.si/), [Google Meet](https://meet.google.com/) have the `Leave call` button to the far right (in LTR s...Move `Leave call` button away from the microphone and camera buttons to prevent accidental call hang-ups
[Jitsi Meet](https://meet.jit.si/), [Google Meet](https://meet.google.com/) have the `Leave call` button to the far right (in LTR scripts).
![Jitsi Meet](/uploads/b0b1ee154a8df49aa45813e39dd5416c/image.png)
![Google Meet](/uploads/efdc120b2d57f98c8adf332c730af780/image.png)
**Reasoning**
>* Leave call button is moved away from the microphone and camera buttons to prevent accidental call hang-ups.
https://workspaceupdates.googleblog.com/2021/04/google-meet-now-gives-you-more-space.html
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/31Conference layout: lookup on hashes from conferences infos2022-07-14T20:05:54ZSébastien BlinConference layout: lookup on hashes from conferences infosReceiving conferences infos with participants not in the contact list will show the hash. The client-qt should perform a lookup on the name server to get the username if possibleReceiving conferences infos with participants not in the contact list will show the hash. The client-qt should perform a lookup on the name server to get the username if possibleBacklogMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/595Windows exe icon weird border2022-07-14T20:06:08ZMing Rui ZhangWindows exe icon weird borderNeed to update ico files to contain multiple sizes
https://docs.microsoft.com/en-us/windows/win32/uxguide/vis-icons?redirectedfrom=MSDNNeed to update ico files to contain multiple sizes
https://docs.microsoft.com/en-us/windows/win32/uxguide/vis-icons?redirectedfrom=MSDNMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/704Next message overlap with received apk2022-07-15T06:32:40ZlinsuiNext message overlap with received apkIf I received an apk, then the next message box will overlap with it.
![image](/uploads/f0dceab2850a0fd558fb6e53609892b8/image.png)
![image](/uploads/0dc24c1b31adc007c5f74d9ee0d42531/image.png)If I received an apk, then the next message box will overlap with it.
![image](/uploads/f0dceab2850a0fd558fb6e53609892b8/image.png)
![image](/uploads/0dc24c1b31adc007c5f74d9ee0d42531/image.png)Fadi ShehadehFadi Shehadehhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/656`Select a screen to share` window show on the same monitor as the parent window2022-07-18T00:01:50Zovari`Select a screen to share` window show on the same monitor as the parent window* Device A: Linux Mint 20.3 Cinnamon<br>
2 monitors, primary monitor on the right, secondary monitor on the left (data cable connected, power turned off)<br>
client-qt deb edition from jami.net Version 202201251934<br>
* Device B: Androi...* Device A: Linux Mint 20.3 Cinnamon<br>
2 monitors, primary monitor on the right, secondary monitor on the left (data cable connected, power turned off)<br>
client-qt deb edition from jami.net Version 202201251934<br>
* Device B: Android
1. Device A makes an intercom call to Device B
1. Device A clicks `Share screen` (note the Jami client is on the primary monitor which is situated on the right
1. `Select a screen to share` opens and shows on the secondary monitor which is situation on the left.
Should the `Select a screen to share` to open show on the same monitor as the Jami client (i.e. it's parent window)?
Having the `Select a screen to share` window show on the same monitor as the parent window would be better the for UX as:
* Users don't need to search of the window on another monitor
* The secondary monitor may not be on as we generally use the computer without the secondary monitor having its power turned on. We do leave it plugged in, but generally don't have it on.
Are there other child windows that open in Jami? If so, should they also open on the same monitor as the parent window?
What do you think?
Thank youAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/696SelectScreen: keep it in front of main window2022-07-18T00:01:51ZAline Gondim SantosSelectScreen: keep it in front of main windowFrom Ovari:
1. Intercom audio call
2. Click `Share window`
3. Click on the parent window (i.e. the Jami window), the `Select a screen to share` window is now behind the main Jami window
4. Click `Share window` and it doesn’t come to the...From Ovari:
1. Intercom audio call
2. Click `Share window`
3. Click on the parent window (i.e. the Jami window), the `Select a screen to share` window is now behind the main Jami window
4. Click `Share window` and it doesn’t come to the front (it is still behind the main Jami window)
If the `Select a screen to share` window is not required, it should never be behind the main Jami program window as it noticeably slows down Jami on low-powered devices.
Can the UX behavior be improved so that the `Select a screen to share` window is always on top of the Jami window (i.e. the `Select a screen to share` window can never be behind the main Jami window)?Jami for education(2)Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/691Child windows/dialogs at most the size of the parent window2022-07-18T00:01:51ZovariChild windows/dialogs at most the size of the parent windowPlease enable child windows/dialogs to be at most the size of the parent window.
For example:
* `About Jami` both width and height too large<br>
![About Jami](/uploads/da5c21072c82868998cc125b4f844f31/image.png)
* `Contact details` widt...Please enable child windows/dialogs to be at most the size of the parent window.
For example:
* `About Jami` both width and height too large<br>
![About Jami](/uploads/da5c21072c82868998cc125b4f844f31/image.png)
* `Contact details` width too large<br>
![Contact details](/uploads/7dab21bb4f622d11b8aa79edab78e6b9/image.png)
* `Share screen`/`Share window` (title: `Select a screen to share`/`Select a window to share`) width too large<br>
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/668#note_34325<br>
![Share screen/window](/uploads/6d89e7e0235000440eb69069352d57c2/image.png)
What do you think?
Thank youJami for education(2)Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/772[Linux Mint 20.3 (Una)] Core Dump Segmentation fault when starting jami-qt at...2022-07-18T14:47:50Zmmtsuchi[Linux Mint 20.3 (Una)] Core Dump Segmentation fault when starting jami-qt at libring.soHi, Core Dump Segmentation fault when starting jami-qt
- OS: Linux Mint 20.3 Mate 64 bits
- Jami version: Using Qt runtime version: 6.2.3
Jami 202207051616
- What build you are using: jami.net (via apt sources)
## Steps to reproduce
- C...Hi, Core Dump Segmentation fault when starting jami-qt
- OS: Linux Mint 20.3 Mate 64 bits
- Jami version: Using Qt runtime version: 6.2.3
Jami 202207051616
- What build you are using: jami.net (via apt sources)
## Steps to reproduce
- Can you reproduce the bug: at will
- Step: when starting jami
## Additional information
- UFW enabled
- segmentation fault at libring.so
gdb jami-qt
> ...
> Thread 48 "jami-qt" received signal SIGSEGV, Segmentation fault.
>
> [Switching to Thread 0x7fff197fa700 (LWP 28681)]
>
> 0x00007fffe93566a6 in ?? () from /lib/libring.so.0
>
> (gdb) bt
>
> #0 0x00007fffe93566a6 in () at /lib/libring.so.0
>
> #1 0x00007fffe91611f7 in () at /lib/libring.so.0
>
> #2 0x00007fffe9161c28 in () at /lib/libring.so.0
>
> #3 0x00007fffe8fb8f81 in () at /lib/libring.so.0
>
> #4 0x00007fffe8fb9069 in () at /lib/libring.so.0
>
> #5 0x00007fffe8b65de4 in () at /lib/x86_64-linux-gnu/libstdc++.so.6
>
> #6 0x00007fffe8c7b609 in start_thread (arg=<optimized out>) at pthread_create.c:477
>
> #7 0x00007fffe8852133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[jami_journalctl_segmentation_fault.txt](/uploads/616ca83fd3b616d78d76f26ce3935698/jami_journalctl_segmentation_fault.txt)
The line command "jami --version" doesn't crash.
Install from apt jami.net, or from .deb packages (for linux mint 20.3). Same results.
Best regardshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/651Media Change - use requestMediaChange instead of deprecated APIs2022-07-19T14:01:09ZMohamed ChibaniMedia Change - use requestMediaChange instead of deprecated APIsrequestMediaChange API allows modifying many attributes of the media (add new media, mute media, change source, ...). This API must be used instead of the deprecated APIs such as muteMedia and switchInput.requestMediaChange API allows modifying many attributes of the media (add new media, mute media, change source, ...). This API must be used instead of the deprecated APIs such as muteMedia and switchInput.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/703Jami window width increases when `Open settings` is clicked with a small Jami...2022-07-19T21:30:00ZovariJami window width increases when `Open settings` is clicked with a small Jami window; with left and right panels showing1. Set the size of the Jami window to the dimensions shown in the image below; with the left panel and the right panel showing<br>
![image](/uploads/8649c32dec5d06241f834a71c6ace720/image.png)
2. Click `Open settings` and the Jami window...1. Set the size of the Jami window to the dimensions shown in the image below; with the left panel and the right panel showing<br>
![image](/uploads/8649c32dec5d06241f834a71c6ace720/image.png)
2. Click `Open settings` and the Jami window dimensions change automatically to the one shown in the image below<br>
![image](/uploads/9eee85ef369414a31ca102e6f540288e/image.png)
It seems that only the width of Jami's window increases.
Should opening Jami's setting not change the size of the Jami window?
Are you able to reproduce?
Thank you
Linux Mint 20.3 Cinnamon<br>
Jami Version: 202203172105https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/722ICE/TURN - assertion failure in PJNATH2022-07-22T15:25:27ZMohamed ChibaniICE/TURN - assertion failure in PJNATHAssertion failure in pjnath (pj_assert) when calling pj_ice_strans_init_ice. See back trace in the comments. The error seems to be caused by a failure of TURN allocation. \
Note that the assertion is only enabled in debug mode. In releas...Assertion failure in pjnath (pj_assert) when calling pj_ice_strans_init_ice. See back trace in the comments. The error seems to be caused by a failure of TURN allocation. \
Note that the assertion is only enabled in debug mode. In release mode, the error might not be noticeable, ICE session will succeed/fail depending on the other candidates of the impacted component. \
Might be related to https://github.com/pjsip/pjproject/pull/2525Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/643SIPCall/PJSIP - Deadlock between main thread and MultiplexedSocket thread2022-07-22T15:26:12ZMohamed ChibaniSIPCall/PJSIP - Deadlock between main thread and MultiplexedSocket threadA deadlock may occur the main thread (or any thread that calls the Call/SIPCall methods that try to access an existing invite session) and the MultiplexedSocket (event loop) thread. The deadlock involves callMutex_ and pjsip_dialog group...A deadlock may occur the main thread (or any thread that calls the Call/SIPCall methods that try to access an existing invite session) and the MultiplexedSocket (event loop) thread. The deadlock involves callMutex_ and pjsip_dialog group lock. See bt in the comment.BacklogMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/585sip/sdp: Use after free of pjmedia_sdp_session from pjsip_inv_session2022-07-22T15:26:31ZOlivier Dionsip/sdp: Use after free of pjmedia_sdp_session from pjsip_inv_sessionSee [repport.txt](/uploads/de0c11137a3ff76b2a5b26041e842999/bt.txt)
This happen very often after a merge of callsSee [repport.txt](/uploads/de0c11137a3ff76b2a5b26041e842999/bt.txt)
This happen very often after a merge of calls