savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-07-22T15:26:52Zhttps://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/67Test for random failure of some syscall / error handling in pjsip2022-07-22T15:26:52ZMehdi GhayourTest for random failure of some syscall / error handling in pjsiphttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/781[small screen] Add account2022-07-26T13:32:17Zovari[small screen] Add account1. Should the buttons be no wider than the window?
2. Should the buttons, if required, be twice (or more) the height so the text can wrap over two (or more) lines in each button?
3. Should the button labels not be in all uppercase as it ...1. Should the buttons be no wider than the window?
2. Should the buttons, if required, be twice (or more) the height so the text can wrap over two (or more) lines in each button?
3. Should the button labels not be in all uppercase as it can be interpreted as shouting?
![image](/uploads/261876e698ce7b93bf9701adc257df7a/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/648video recording not working (av_write_frame failed: Invalid argument)2022-07-26T14:04:56ZMaxim Cournoyervideo recording not working (av_write_frame failed: Invalid argument)Please specify the following:
- OS: Guix (commit 3c43f2b4f54dead73ce19427eb1e364581b7f2e0)
- Jami version: 20211223.2.37be4c3
- What build you are using: Guix
## Steps to reproduce
Note: Better the scenario is, better we will be able ...Please specify the following:
- OS: Guix (commit 3c43f2b4f54dead73ce19427eb1e364581b7f2e0)
- Jami version: 20211223.2.37be4c3
- What build you are using: Guix
## 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. `guix time-machine --commit=3c43f2b4f54dead73ce19427eb1e364581b7f2e0 -- shell jami -- jami-qt --debug`
2. Initiate a video call.
3. Press the recording button to start video recording.
4. Wait some time (e.g, 30 s).
5. Press the recording button again to stop video recording.
...
- Actual result: No video file is produced, nothing gets recorded; error is silent to the user (no feedback about error).
- Expected result: A video file should have been produced with the recording.
## Additional information
I'm guessing the failure seems may be associated with the message "av_write_frame failed: Invalid argument" as can be seen shortly after enabling recording in the client's logs:
```
[...]
[1642221688.709| 4881|media_encoder.cpp :325 ] Not using hardware encoding for vp8
[1642221688.709| 4881|media_encoder.cpp :797 ] Hardware encoding disabled
[1642221688.709| 4881|media_encoder.cpp :610 ] [libvpx] Using 4 threads
[1642221688.709| 4881|media_encoder.cpp :993 ] VP8 encoder setup: crf=18
[libvpx @ 0x7f5c283fe580] Bitrate not specified for constrained quality mode, using default of 256kbit/sec
[1642221690.371| 4874|sipcall.cpp :613 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f5c64028000] max delay reached. need to consume packet
[sdp @ 0x7f5c64028000] RTP: missed 1 packets
[h264 @ 0x7f5c640219c0] P sub_mb_type 32 out of range at 34 14
[h264 @ 0x7f5c640219c0] error while decoding MB 34 14
[webm @ 0x4af6740] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 633 >= 600
[1642221691.645| 4881|media_encoder.cpp :557 ] av_write_frame failed: Invalid argument
[1642221696.910| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1605 / 160
[1642221696.920| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2093 / 160
[1642221696.920| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1933 / 160
[1642221696.920| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1773 / 160
[1642221696.920| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1613 / 160
[1642221696.920| 4874|sipcall.cpp :613 ] Sending video keyframe request via SIP INFO
[1642221696.930| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2261 / 160
[1642221696.930| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2101 / 160
[1642221696.930| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1941 / 160
[1642221696.930| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1781 / 160
[1642221696.930| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1621 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2581 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2421 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2261 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 2101 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1941 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1781 / 160
[1642221696.940| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1621 / 160
[sdp @ 0x7f5c64028000] max delay reached. need to consume packet
[sdp @ 0x7f5c64028000] RTP: missed 1 packets
[h264 @ 0x7f5c640219c0] out of range intra chroma pred mode
[h264 @ 0x7f5c640219c0] error while decoding MB 42 15
[1642221697.072| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1621 / 160
[1642221697.944| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1621 / 160
[1642221699.177| 9027|webrtc_echo_canceller.cpp:104 ] playback overflow 1621 / 160
[libopus @ 0x6b8b100] Queue input is backward in time
[webm @ 0x4af6740] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 2533 >= 2500
[1642221703.559| 4881|media_encoder.cpp :557 ] av_write_frame failed: Invalid argument
[1642221706.324| 4874|sipcall.cpp :613 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f5c64028000] max delay reached. need to consume packet
[sdp @ 0x7f5c64028000] RTP: missed 1 packets
[webm @ 0x4af6740] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 3000 >= 2967
[1642221707.631| 4881|media_encoder.cpp :557 ] av_write_frame failed: Invalid argument
[libopus @ 0x6b8b100] Queue input is backward in time
[webm @ 0x4af6740] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 3200 >= 3167
[1642221708.776| 4881|media_encoder.cpp :557 ] av_write_frame failed: Invalid argument
[webm @ 0x4af6740] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 4500 >= 4467
[1642221718.371| 4881|media_encoder.cpp :557 ] av_write_frame failed: Invalid argument
```https://git.jami.net/savoirfairelinux/jami-project/-/issues/1246Call recording does not work in LMDE 4 (Together 202105130112)2022-07-28T14:13:42ZPostavCall recording does not work in LMDE 4 (Together 202105130112)Recording audio calls does not work.
Video call recording works, but only a small part of the recording is saved.
On Note 4 (Android 6, Jami version: Together-20210504-01) the icons for making audio and video calls sometimes block and ...Recording audio calls does not work.
Video call recording works, but only a small part of the recording is saved.
On Note 4 (Android 6, Jami version: Together-20210504-01) the icons for making audio and video calls sometimes block and you cannot make calls, but you can receive audio and video calls. The quality of the audio output has improved in audio calls, but deteriorated in video calls.
I hope I am not disturbing you with my reports.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/769wizardview: main wizardview page2022-07-29T13:19:49ZFadi Shehadehwizardview: main wizardview page- replace logo
- update text
- modify pushbutton text
- adjust layout
![Screenshot_from_2022-07-14_10-07-09](/uploads/ea25a7709eaa2e2194e30c92d71faf9c/Screenshot_from_2022-07-14_10-07-09.png)- replace logo
- update text
- modify pushbutton text
- adjust layout
![Screenshot_from_2022-07-14_10-07-09](/uploads/ea25a7709eaa2e2194e30c92d71faf9c/Screenshot_from_2022-07-14_10-07-09.png)Fadi ShehadehFadi Shehadehhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/766welcome view: JamiSwitch, combobox, pushButtons2022-07-29T13:20:00ZFadi Shehadehwelcome view: JamiSwitch, combobox, pushButtonsThe goal is to change the themes of JamiSwitch, Combobox and PushButton to the new ones.
![screen2](/uploads/9a1438a890328a5613aca30fb7452b55/screen2.png)
![screen1](/uploads/5f8df7d3b4b787a1f5acfed72d27fea5/screen1.png)The goal is to change the themes of JamiSwitch, Combobox and PushButton to the new ones.
![screen2](/uploads/9a1438a890328a5613aca30fb7452b55/screen2.png)
![screen1](/uploads/5f8df7d3b4b787a1f5acfed72d27fea5/screen1.png)Fadi ShehadehFadi Shehadehhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/777`Text zoom` with Ctrl+mouse wheel2022-07-30T00:50:29Zovari`Text zoom` with Ctrl+mouse wheelThank you for enabling `Text zoom` with `Ctrl++` and `Ctrl+-`.
Can `Ctrl+mouse wheel` also be added to enlarge and reduce the zoom? This would provided similar functionality with LibreOffice, Firefox and Thunderbird which also support `...Thank you for enabling `Text zoom` with `Ctrl++` and `Ctrl+-`.
Can `Ctrl+mouse wheel` also be added to enlarge and reduce the zoom? This would provided similar functionality with LibreOffice, Firefox and Thunderbird which also support `Ctrl+mouse wheel`
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/767Welcomeview: main welcome page2022-07-30T01:26:58ZFadi ShehadehWelcomeview: main welcome pageAdd JamiIdentifier: JamiID edit, copy, share
Add Tips and customization
Add Never show again button for the tip
Add notification for tips and customization on top right corner
Add resourcesAdd JamiIdentifier: JamiID edit, copy, share
Add Tips and customization
Add Never show again button for the tip
Add notification for tips and customization on top right corner
Add resourcesFadi ShehadehFadi Shehadehhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/731New welcome view2022-07-30T19:09:25ZSébastien BlinNew welcome viewThe goal is to update the current welcome view:
![Screenshot_2022-05-04_at_03-53-34_Adobe_XD](/uploads/0d0fa6b4843023eceeb0e03511bab2d3/Screenshot_2022-05-04_at_03-53-34_Adobe_XD.png)
![Screenshot_2022-05-04_at_03-53-47_Adobe_XD](/uplo...The goal is to update the current welcome view:
![Screenshot_2022-05-04_at_03-53-34_Adobe_XD](/uploads/0d0fa6b4843023eceeb0e03511bab2d3/Screenshot_2022-05-04_at_03-53-34_Adobe_XD.png)
![Screenshot_2022-05-04_at_03-53-47_Adobe_XD](/uploads/8acf501d55134dd49105173a502bfe1b/Screenshot_2022-05-04_at_03-53-47_Adobe_XD.png)
![Screenshot_2022-05-04_at_03-53-59_Adobe_XD](/uploads/9d1f2c2d62663d48a07474a95e58444c/Screenshot_2022-05-04_at_03-53-59_Adobe_XD.png)
![Screenshot_2022-05-04_at_03-54-07_Adobe_XD](/uploads/289e3a27c20576e848854c4940cb7757/Screenshot_2022-05-04_at_03-54-07_Adobe_XD.png)
![Screenshot_2022-05-04_at_03-54-15_Adobe_XD](/uploads/c035f375bc460be4b3ff40cecf598acf/Screenshot_2022-05-04_at_03-54-15_Adobe_XD.png)Fadi ShehadehFadi Shehadehhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/460Add `About Jami` to the first dialog box2022-07-30T22:41:57ZovariAdd `About Jami` to the first dialog boxPlease add an `About Jami` button to the first dialog box shown in the image below.
![AdvancedFeaturesClosed](/uploads/fbb71c44206f714d8a2046daf00aa798/AdvancedFeaturesClosed.png)
This will enable the version of Jami to be discovered.
...Please add an `About Jami` button to the first dialog box shown in the image below.
![AdvancedFeaturesClosed](/uploads/fbb71c44206f714d8a2046daf00aa798/AdvancedFeaturesClosed.png)
This will enable the version of Jami to be discovered.
What do you think?
Thank youBacklogAdrien BéraudCharlotte HoffmannMing Rui ZhangFadi ShehadehAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/785GUI disappears when pressing escape (ESC) key2022-08-01T13:11:01ZMaxim CournoyerGUI disappears when pressing escape (ESC) key- OS: Guix System
- Jami version: 20220726.1515.da8d1da
- What build you are using: Guix
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Launch Jami in a minimalist window manager such as ratpoison.
2. P...- OS: Guix System
- Jami version: 20220726.1515.da8d1da
- What build you are using: Guix
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Launch Jami in a minimalist window manager such as ratpoison.
2. Press escape.
- Actual result: GUI gets hidden. Cannot be brought back.
- Expected result: Escape should not cause the GUI to disappear.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/744[enhancement] add ringing time before autoreplay2022-08-03T11:55:44ZPietro[enhancement] add ringing time before autoreplayHi there,
thanks for this nice software. I'm currently using it to get in touch with my mom, that can no longer handle the mobile phone.
I activated the autoanswer option and everything works great except for one thing: there is no ring...Hi there,
thanks for this nice software. I'm currently using it to get in touch with my mom, that can no longer handle the mobile phone.
I activated the autoanswer option and everything works great except for one thing: there is no ringing time.
It would be very helpful to have a few seconds of ringtone to notify the recipient of the incoming call.
I achieved this very easily, by just adding some sleep time before the auto-answer:
```
diff --git a/src/manager.cpp b/src/manager.cpp
index 582bbc012..3e436a8e8 100644
--- a/src/manager.cpp
+++ b/src/manager.cpp
@@ -2541,7 +2541,7 @@ Manager::ManagerPimpl::processIncomingCall(const std::string& accountId, Call& i
});
} else if (autoAnswer_ || account->isAutoAnswerEnabled()) {
dht::ThreadPool::io().run(
- [this, incomCall = incomCall.shared_from_this()] { base_.answerCall(*incomCall); });
+ [this, incomCall = incomCall.shared_from_this()] { sleep(9); base_.answerCall(*incomCall); });
} else if (currentCall && currentCall->getCallId() != incomCallId) {
// Test if already calling this person
if (currentCall->getAccountId() == account->getAccountID()
```
Are you interested in this option? I'm not sure I can code it through both the deamon and the gui, but I know C++ and QML so I may just need some directions on the structure of the code.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/780[small screen] Confirm action: Do you really want to remove this conversation2022-08-03T15:11:46Zovari[small screen] Confirm action: Do you really want to remove this conversationSuggestion:
1. Should the dialog be no wider than the parent window?
2. Should a question mark `?` be appended to the end of the question? i.e. change<br>
`Do you really want to remove this conversation`<br>
to<br>
`Do you really want t...Suggestion:
1. Should the dialog be no wider than the parent window?
2. Should a question mark `?` be appended to the end of the question? i.e. change<br>
`Do you really want to remove this conversation`<br>
to<br>
`Do you really want to remove this conversation?`
3. Should the `Delete` button label be renamed to `Remove` (to be consistent with the question)? Or rename the question to `Do you really want to delete this conversation?`
![image](/uploads/c2c51a6df67eae968b40bd68ea1faa5d/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/768aborted (core dumped) on OpenSuse 15.32022-08-03T21:42:16ZAlex-K37aborted (core dumped) on OpenSuse 15.3## Describe your environment
- OS: PRETTY_NAME="openSUSE Leap 15.3" with KDE Desktop
- Jami version: jami-qt-20220412.1405.c00d28e-1.x86_64
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at wi...## Describe your environment
- OS: PRETTY_NAME="openSUSE Leap 15.3" with KDE Desktop
- Jami version: jami-qt-20220412.1405.c00d28e-1.x86_64
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. start jami on desktop => nothing shows up
2. commandline: jami >dump 2>&1
- Actual result: "Aborted (core dumped)"
- Expected result: start-up
## Additional information
[dump](/uploads/bdef020423c1eaa92a4a132e86296ba7/dump)
[gdb.txt](/uploads/7f41cc837e5f728f11bb70914eb4f44e/gdb.txt)
The same crash happens with jami-qt-202203* from stable. I just now switched to nightly to check if this was resolved.Sébastien BlinAmin BandaliSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/677fix colorspace conversion2022-08-04T11:57:05ZKateryna Kostiukfix colorspace conversionNow we use com.apple.security.cs.allow-unsigned-executable-memory entitlement to prevent crash on macOS when perform sws_scale. It should be removed in the future when we move colorspace conversion to the client-qt.Now we use com.apple.security.cs.allow-unsigned-executable-memory entitlement to prevent crash on macOS when perform sws_scale. It should be removed in the future when we move colorspace conversion to the client-qt.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/686Fails building: opendht/http.h: No such file or directory2022-08-04T11:59:07ZRichard-RogalskiFails building: opendht/http.h: No such file or directoryHello all, hope you are doing well today.
Distro: gentoo linux
Compiler: gcc 10.3.0
Jami Version: most recent source tarball release (jami_20211223.2.37be4c3.tar.gz)
Ninja version: 1.10.2
I tried building jami-daemon with the i...Hello all, hope you are doing well today.
Distro: gentoo linux
Compiler: gcc 10.3.0
Jami Version: most recent source tarball release (jami_20211223.2.37be4c3.tar.gz)
Ninja version: 1.10.2
I tried building jami-daemon with the instructions on its readme, and it all went fine until I ran `ninja`. This is its output:
https://pastebin.com/xRFPjGME
I thought this was weird, so I ran `find` to try to find this http.h file and found it here:
https://pastebin.com/S7WhL4Dh
What's weirder, is this was the exact same error I got when I tried building jami-daemon in the gentoo jami-overlay. I thought the error was due to the version on the overlay being several years old, but perhaps not.
I'm not sure if I'm doing something wrong, or if my system is causing problems. Any help would be appreciated, if you need more info let me know.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/689Update our code and test due to FFmpeg new release2022-08-04T11:59:59ZMehdi GhayourUpdate our code and test due to FFmpeg new releaseIt's not the priority at the moment, we'll handle it later and will consider a timeline aligned with the product.It's not the priority at the moment, we'll handle it later and will consider a timeline aligned with the product.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/771The last member should be completely shown, bottom half missing, when Jami's ...2022-08-04T13:39:53ZovariThe last member should be completely shown, bottom half missing, when Jami's window height is reduced0. Reduce the height of the Jami window so that the complete member list in a swarm can not be seen at the same time
1. Open a swarm
2. Click on `Details` in the top right
3. Click on hold the vertical scrollbar to the bottom
4. Only the...0. Reduce the height of the Jami window so that the complete member list in a swarm can not be seen at the same time
1. Open a swarm
2. Click on `Details` in the top right
3. Click on hold the vertical scrollbar to the bottom
4. Only the top half of the last member is shown<br>
Bug: The bottom half of the last member should also be shown
Steps to reproduce (STR) are shown in the image below
![Only the top half of the last member in a swarm is shown when the vertical scrollbar is used](/uploads/561e6e1760a78240ed0f950238689e4f/image.png)
Are you able to reproduce and please fix?
Thank you
jami-qt Version: 202207051616<br>
Linux Mint 20.3 Cinnamonhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/730Android: Calling a device around 10 times result in daemon not responding any...2022-08-04T19:21:09ZOlivier DionAndroid: Calling a device around 10 times result in daemon not responding anymore# Devices
- Caller (linux)
- Callee (Android)
# Network topology
Anything. Can be reproduce if both devices are on the same network.
By default, the scenario is run with UPNP and TURN disabled on both devices.
# Symptoms
If y...# Devices
- Caller (linux)
- Callee (Android)
# Network topology
Anything. Can be reproduce if both devices are on the same network.
By default, the scenario is run with UPNP and TURN disabled on both devices.
# Symptoms
If you have any of the following symptoms, it's probably it.
- After around 10 successful calls, the Android device will stop receiving any new call from any peer.
- Toggling the Android account status (online/offline) will keep the green `online` label.
- No peer discovery on the DHT.
# Scenario
1. Call an Android device (can be put in auto-answer mode)
2. Wait a few seconds after picking up the call.
3. Hang up.
4. Reset the connection between the peers by disabling the **caller's** account.
5. Wait a few moment (around 5 seconds) for sockets to be released.
6. Re-enable the caller's account.
7. Jump 1.
There's a [scenario.scm](/uploads/b06305eb52ea5623575f62dd43038ab8/scenario.scm) that automated this process
- You can parameterize the waiting period for the call with `GRACE-PERIOD`
- You can parameterize duration of the call with `MEDIA-FLOW`
- To run the test, call `(run-scenario "result.txt")`.
# Edit 1
From my debugging:
- There's no leak of any file descriptor
- Memory usage is okay and does not seem to have any leak
- Logging continue (for example changing account's preferences)
# Edit 2
Other symptoms:
- Calling a peer from the Android device result in a gray screen (no red hang up button)
- Sending messages to a peer does not show in the conversation history
- In the above case, the peer is never joinedMohamed ChibaniOlivier DionMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/918Maybe all settings should be put in one place?2022-08-04T19:29:01ZChris OcelotMaybe all settings should be put in one place?On android clients, settings are located at top right 3 dots as well as the account tab, it seems a bit odd to me.
At first I found the setting located at account tab, then I thought, OK, setting is here, if there is anything I want to...On android clients, settings are located at top right 3 dots as well as the account tab, it seems a bit odd to me.
At first I found the setting located at account tab, then I thought, OK, setting is here, if there is anything I want to change, I need to check here. Then somebody told me there was also setting on top right corner with the 3 dots. It seems very counter-intuitive to put these setting in different places. My suggestion would be add another setting menu under "advanced" section, call it "conversation", and put what was in the top right corner 3 dots in there.