savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-02-09T20:27:46Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1346IDENTIFIANT RING IDENTIQUE POUR 2 UTILISATEURS DIFFERENTS2024-02-09T20:27:46ZVERO JEAN-LUCveroniquejeanluc@lilo.orgIDENTIFIANT RING IDENTIQUE POUR 2 UTILISATEURS DIFFERENTSComment ces deux noms d'utilisateurs différents verojeanluc et veroniquejeanluc peuvent ils avoir le même identifiant ring 553dec1f75758ef6ea…1c027bf397f3062700 ?
Ces deux comptes ont été ouvert par nous, mais nous n'utilisons que veroje...Comment ces deux noms d'utilisateurs différents verojeanluc et veroniquejeanluc peuvent ils avoir le même identifiant ring 553dec1f75758ef6ea…1c027bf397f3062700 ?
Ces deux comptes ont été ouvert par nous, mais nous n'utilisons que verojeanluc et nous avons supprimé véroniquejeanluc
![JAMI_verojeanluc_Debian_2021-11-13_08-16-32](/uploads/5dc3f85ed8a58349694d0b67bc0cee37/JAMI_verojeanluc_Debian_2021-11-13_08-16-32.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1485[Feature request] Improve the chatview (quote, copy url, delete one single me...2024-02-09T20:20:53ZElys[Feature request] Improve the chatview (quote, copy url, delete one single message)all supported OS:
Until now if you want to quote a message you need to right click and select "answer". I didn't see any notification that shows that you can quote text messages so you have to know that this is possible.
I think it wou...all supported OS:
Until now if you want to quote a message you need to right click and select "answer". I didn't see any notification that shows that you can quote text messages so you have to know that this is possible.
I think it would help if you provide a for example a vertical 3-Dot menu for each (text)message like this example:
https://help.nextcloud.com/uploads/default/original/3X/f/b/fb54f5f3773af340ff1e6fd6c55c0d29e1ad287c.png
(Example icons: https://www.freepik.com/premium-vector/hamburger-menu-icons-web-mobile-navigation-buttons-app-ui-isolated-vector-burger-menu-symbols-collapsed-menu-navigation-bar-with-three-horizontal-bars-squares-dots-ellipsis_26019487.htm)
So if you **left** click the three-dot button you get a menu that allows you to select (for example)
- Quote the message
- Go to website (if a url was used)
- Copy link
- Copy (just this one) message
- Delete (just this one) message from chat view
- Forward (just this one) message
- Forward (just this one) attachment (If you use have multiple attachments maybe you can select which attachments will be forwarded)
Also, please allow to copy just parts of the text messagehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1489[Feature request] Allow to select different video devices and/or audio device...2024-02-09T20:19:40ZElys[Feature request] Allow to select different video devices and/or audio devices per (own) user accountall supported OS:
If you create two own user accounts ("username1" and "username2") you can only select one video devices and one audio device for both user accounts.
I would like to have the option (same client) to choose for example
...all supported OS:
If you create two own user accounts ("username1" and "username2") you can only select one video devices and one audio device for both user accounts.
I would like to have the option (same client) to choose for example
* "username1": camera 1; microphone 1; headset 2
* "username": camera 2; microphone 3, Headset 1
I saw you can enable/disable video per own user account but you can't select different video and/or audio devices for each user (own) account.
I already made a feature request regarding audio calls: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1385https://git.jami.net/savoirfairelinux/jami-project/-/issues/1513Jami will remain "connecting" (Windows 10->Android) sameuseraccount -> sameus...2024-02-09T20:19:01ZElysJami will remain "connecting" (Windows 10->Android) sameuseraccount -> sameuseraccountALWAYS DISABLE "run in background"
updated bug report:
using
* Jami Version (Beta): 202302011426 and Windows 10
* Jami 20230210-01 and Android
Steps to reproduce:
sameuseraccount -> sameuseraccount
different network both devices
1....ALWAYS DISABLE "run in background"
updated bug report:
using
* Jami Version (Beta): 202302011426 and Windows 10
* Jami 20230210-01 and Android
Steps to reproduce:
sameuseraccount -> sameuseraccount
different network both devices
1. Open Jami on Windows 10 and Android
1. Make a call Windows 10 -> Android
1. Jami on Windows 10 will stuck on "connecting"
The only way to fix this issue is to exit Jami on Android and enter Jami on Android again
(maybe multiple times) - Remember you keep the call running JUST on Windows 10.
After 20 or 30 seconds the call suddenly works although Jami on Windows 10 just showed "Connecting".
-------
EDIT: I think:
- might be related to https://git.jami.net/savoirfairelinux/jami-project/-/issues/1512
- It does not matter how long you wait until you enter Jami (Android) again if you make a call useraccount1 (Windows 10) -> useraccount2 (Android)
- I think you can't reproduce if you exit Jami (Android only) and open Jami (Android) very fast again but you are making a call sameuseraccount -> sameuseraccount
- I think you **CAN reproduce** if you exit Jami (Android only) **wait** over 30 seconds or even longer and THEN make a call **sameuseraccount -> sameuseraccount**
Steps to reproduce:
useraccount 1 -> useraccount2 (different network)
1. You open Jami on Windows 10 and Android
1. Now wait 30 seconds or longer (Maybe you can make successfully calls?)
1. Now just exit Jami on Android
1. **Before** the Android user can view the green dot of the Windows 10 contact, the Windows 10 user makes a call Windows 10 -> Android
1. The Windows 10 user will just get a "Connecting" message (forever?/for a minute) even if a few seconds later the Android user can view the green dot of the Windows 10 contact
Both users might get "Missed outgoing call"?
Same issue if the Windows 10 user tries to call the Android contact once he exits Jami.
If I wait until the Android user can view the green dot of the Windows 10 contact I get this issue: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1512
However - **No issues** if you make a call **Android -> Windows 10** - **even** if the **green dot** of the Windows 10 in the contact list of the Android user is **not visible** yethttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1480Removing contact won't work for both if one contact is offline (or just after...2024-02-09T20:18:37ZElysRemoving contact won't work for both if one contact is offline (or just after some time?)using newest beta version of Jami
Android - Android
maybe you can also try to reproduce
Desktop - Android
I added my own username in the contact list of both devices ("samerusername1")
If both devices (Android and Android) are onlin...using newest beta version of Jami
Android - Android
maybe you can also try to reproduce
Desktop - Android
I added my own username in the contact list of both devices ("samerusername1")
If both devices (Android and Android) are online (since you've already opened Jami) once a user removes "sameusername1" from the contact list both devices won't show "sameusername1" in the contact list anymore.
However it should be possible that Jami will also remove the contact from the contact list as soon as the other user (who is offline at the moment) is online again?
Because I get this issue:
I always used the same username
Device 1: Android Smartphone
Device 2: Android tablet
Add your own username in the contact list (both devices)
Just the Android tablet: exit Jami (and go to idle state)
(Just) Android smartphone: remove the contact
Android tablet: enter Jami (again)
Now you can't make a call Android Tablet (the contact (removed just from the Jami contact list of the Smartphone) is still present) -) Android Smartphone (and of course not from the Android smartphone itself since the contact is now gone)
Just smartphone: Add the (previously) removed contact again by searching the username
Smartphone: Now the removed contact is visible in the contact list again
Calls Tablet -) Smartphone are still NOT possible
same issue if you are sending text messages Tabet-)Smartphone) ?
However: After some time I received an invitation (because of the text message)? It will just show "Downloading conversation from peer". I had this issue: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1120 (I had to exit the Android tablet and enter again)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/750Wrong username in contact list after adding an account and import leads to "S...2024-02-09T19:58:29ZElysWrong username in contact list after adding an account and import leads to "Swarm: Is false"?Not sure if you can reproduce but I think these were the steps I reproduced this bug (maybe I need to change my description and the steps later)
- Jami (Windows 10): Click add account
- Jami (Windows 10): I now add my own account (I alr...Not sure if you can reproduce but I think these were the steps I reproduced this bug (maybe I need to change my description and the steps later)
- Jami (Windows 10): Click add account
- Jami (Windows 10): I now add my own account (I already have the same user account on my android device)
- I use the option "Import from another device"
- Now all my contacts from the android device are also transferred except one contact (I have three contacts in this test; My own user account "test1"; another user account"test2"; and a "real" contact)
- However the other user account "test2" does not show up but a version like 7b2d4af12345... ( I didn't check if matches the "test2" account)
- I delete the 7b2d4af12345... contact
- After some time (over 30 seconds or more?) I get an invitation (Windows 10) of the user account "test2" with the "real" name "test2"(but I think also the Android version of Jami sent me an invitation) (Maybe related?: https://git.jami.net/savoirfairelinux/jami-project/-/issues/1449#note_36195 ) so no 7b2d4af12345... etc.
- Even if I accept (just Windows 10 or even both: Android and Windows 10) I just see "You have accepted the conversation request. Waiting until "test2" connects to synchoronize the conversation"
- Now I exit Jami just Windows 10
- Suddenly "test2" is in contact list **but my own account is gone **(just in the contact list of course)
- As soon as I exit Jami (Windows 10) and enter again my own account in the contact list is visible again
So the issues should be at least that I get a 89dfs0if... contact in the contact list instead of a user name and sometimes
Note: Android: I never deleted the "real"contact (just one in past so I get "Swarm: Is true") but my other account "test2" was often deleted and re-added so maybe that's also the issue? (Although I reproduced (another) issue if I use the Windows 10 client)
----
another issue?
In the contact list: my own account "test1" and my other account "test2" show "Swarm: Is false";
However my third contact shows "Swarm: Is true"
This happend after I followed the steps mentioned abovehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/913heap-use-after free2024-02-09T19:57:02ZSébastien Blinheap-use-after free```
=================================================================
==41866==ERROR: AddressSanitizer: heap-use-after-free on address 0x0002a5258a88 at pc 0x000105383380 bp 0x0003157867b0 sp 0x0003157867a8
READ of size 4 at 0x0002a5258a...```
=================================================================
==41866==ERROR: AddressSanitizer: heap-use-after-free on address 0x0002a5258a88 at pc 0x000105383380 bp 0x0003157867b0 sp 0x0003157867a8
READ of size 4 at 0x0002a5258a88 thread T17074
#0 0x10538337c in stun_on_request_complete+0xc54 (Jami:arm64+0x102a9b37c)
#1 0x10537859c in stun_tsx_on_complete+0x2a8 (Jami:arm64+0x102a9059c)
#2 0x105380240 in retransmit_timer_callback+0x12c (Jami:arm64+0x102a98240)
#3 0x105313d94 in pj_timer_heap_poll+0x468 (Jami:arm64+0x102a2bd94)
#4 0x1046db30c in dhtnet::IceTransport::Impl::handleEvents(unsigned int)+0x110 (Jami:arm64+0x101df330c)
#5 0x1046f6128 in void* std::__1::__thread_proxy[abi:v160006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, dhtnet::IceTransport::Impl::initIceInstance(dhtnet::IceTransportOptions const&)::$_6>>(void*)+0x154 (Jami:arm64+0x101e0e128)
#6 0x186caf030 in _pthread_start+0x84 (libsystem_pthread.dylib:arm64e+0x7030)
#7 0x186ca9e38 in thread_start+0x4 (libsystem_pthread.dylib:arm64e+0x1e38)
0x0002a5258a88 is located 200 bytes inside of 256-byte region [0x0002a52589c0,0x0002a5258ac0)
freed by thread T17074 here:
#0 0x11162ace0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x52ce0)
#1 0x10530167c in pj_pool_destroy_int+0xbc (Jami:arm64+0x102a1967c)
#2 0x105302530 in cpool_release_pool+0xec (Jami:arm64+0x102a1a530)
#3 0x105391e58 in dataconn_on_data_read+0x13c (Jami:arm64+0x102aa9e58)
#4 0x1052f18f0 in ioqueue_on_read_complete+0x39c (Jami:arm64+0x102a098f0)
#5 0x1052e154c in ioqueue_dispatch_read_event+0x700 (Jami:arm64+0x1029f954c)
#6 0x1052e6564 in pj_ioqueue_poll+0x900 (Jami:arm64+0x1029fe564)
#7 0x1046db3ec in dhtnet::IceTransport::Impl::handleEvents(unsigned int)+0x1f0 (Jami:arm64+0x101df33ec)
#8 0x1046f6128 in void* std::__1::__thread_proxy[abi:v160006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, dhtnet::IceTransport::Impl::initIceInstance(dhtnet::IceTransportOptions const&)::$_6>>(void*)+0x154 (Jami:arm64+0x101e0e128)
#9 0x186caf030 in _pthread_start+0x84 (libsystem_pthread.dylib:arm64e+0x7030)
#10 0x186ca9e38 in thread_start+0x4 (libsystem_pthread.dylib:arm64e+0x1e38)
```
[use_after_free.log](/uploads/9f8d90ce3d2e0ac87d6359747d8173a9/use_after_free.log)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/939ut_scheduler test newly fails (20231222.2)2024-02-09T19:37:52ZMaxim Cournoyerut_scheduler test newly fails (20231222.2)This test (along with `ut_media_player`, already repoted here https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/935) newly fails from version 20231201.0, and also in the latest nightly, 20231222.2.
```
FAIL: ut_scheduler
======...This test (along with `ut_media_player`, already repoted here https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/935) newly fails from version 20231201.0, and also in the latest nightly, 20231222.2.
```
FAIL: ut_scheduler
==================
.F
!!!FAILURES!!!
Test Results:
Run: 1 Failures: 1 Errors: 0
1) test: jami::test::SchedulerTest::schedulerTest (F) line: 74 scheduler.cpp
assertion failed
- Expression: cv.wait_for(lk, std::chrono::seconds(3), [&]{ return taskRun == N; })
FAIL ut_scheduler (exit status: 1)
```
I've skipped ut_media_player; here's the failure per test-suite.log:
```
=======================================================
Jami Daemon 13.11.0: test/unitTest/test-suite.log
=======================================================
# TOTAL: 15
# PASS: 13
# SKIP: 0
# XFAIL: 1
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: ut_scheduler
==================
.F
!!!FAILURES!!!
Test Results:
Run: 1 Failures: 1 Errors: 0
1) test: jami::test::SchedulerTest::schedulerTest (F) line: 74 scheduler.cpp
assertion failed
- Expression: cv.wait_for(lk, std::chrono::seconds(3), [&]{ return taskRun == N; })
FAIL ut_scheduler (exit status: 1)
XFAIL: ut_media_player
======================
.�[22;36m[1704680039.242|20007] �[0mUPnPContext: starting dedicated io_context thread
�[0m�[22;36m[1704680039.243|20007] �[0mCreating UPnPContext instance [0xd5cf10]
�[0m�[22;36m[1704680039.243|20008] �[0mPUPnP: Creating instance [0x7fffec000b80] ...
�[0m�[22;36m[1704680039.243|20007|ringbuffer.cpp :55 ] �[0mCreate new RingBuffer audiolayer_id
�[0m�[22;36m[1704680039.244|20007|manager.cpp :732 ] �[0mNot initialized
�[0m�[22;36m[1704680039.244|20007|manager.cpp :732 ] �[0mNot initialized
�[0m�[22;36m[1704680039.244|20007|manager.cpp :732 ] �[0mNot initialized
�[0m�[22;36m[1704680039.249|20007|manager.cpp :806 ] �[0mUsing PJSIP version 2.13.1 for x86_64-unknown-linux-gnu
�[0m�[22;36m[1704680039.249|20007|manager.cpp :807 ] �[0mUsing GnuTLS version 3.7.7
�[0m�[22;36m[1704680039.249|20007|manager.cpp :808 ] �[0mUsing OpenDHT version 3.1.7
�[0m�[22;36m[1704680039.249|20007|manager.cpp :809 ] �[0mUsing FFmpeg version 6.1.1
�[0m�[22;36m[1704680039.249|20007|manager.cpp :812 ] �[0mUsing Libgit2 version 1.6.4
�[0m�[22;36m[1704680039.249|20007|manager.cpp :257 ] �[0m02:13:59.249 sip_endpoint.c Creating endpoint instance...
�[0m�[22;36m[1704680039.249|20007|manager.cpp :257 ] �[0m02:13:59.249 pjlib epoll I/O Queue created (flags:0x1, ptr=0xde8e90)
�[0m�[22;36m[1704680039.249|20007|manager.cpp :257 ] �[0m02:13:59.249 sip_endpoint.c Module "mod-msg-print" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_transport.c Transport manager created.
�[0m�[22;36m[1704680039.250|20007|sipvoiplink.cpp :648 ] �[0mUsing SIP nameserver: 127.0.0.1
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-tsx-layer" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-stateful-util" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-ua" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-100rel" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "jami" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-evsub" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-refer" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 evsub.c Event pkg "refer" registered by mod-refer
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 sip_endpoint.c Module "mod-presence" registered
�[0m�[22;36m[1704680039.250|20007|manager.cpp :257 ] �[0m02:13:59.250 evsub.c Event pkg "presence" registered by mod-presence
�[0m�[22;36m[1704680039.251|20007|manager.cpp :257 ] �[0m02:13:59.251 sip_endpoint.c Module "mod-presence-server" registered
�[0m�[22;36m[1704680039.251|20007|manager.cpp :257 ] �[0m02:13:59.251 sip_endpoint.c Module "mod-invite" registered
�[0m�[22;36m[1704680039.251|20007|sipvoiplink.cpp :742 ] �[0mSIPVoIPLink@0xdcc960
�[0m�[22;36m[1704680039.251|20007|manager.cpp :830 ] �[0mConfiguration file path: jami-sample.yml
�[0m�[22;36m[1704680039.253|20007|ringbuffer.cpp :55 ] �[0mCreate new RingBuffer urgentRingBuffer_id
�[0m�[22;36m[1704680039.253|20007|audiolayer.cpp :60 ] �[0m[audiolayer] AGC: 1, noiseReduce: auto, VAD: 1, echoCancel: auto, audioProcessor: webrtc
�[0m�[22;36m[1704680039.253|20007|pulselayer.cpp :69 ] �[0m[audiolayer] created pulseaudio layer
�[0m�[22;36m[1704680039.253|20007|audiolayer.cpp :169 ] �[0m[audiolayer] setHasNativeNS: 0
�[0m�[22;36m[1704680039.257|20007|pulselayer.cpp :146 ] �[0mWaiting....
�[0m�[22;36m[1704680039.285|20013|pulselayer.cpp :146 ] �[0mWaiting....
�[0m�[22;36m[1704680039.286|20013|pulselayer.cpp :146 ] �[0mWaiting....
�[0m�[22;36m[1704680039.286|20013|pulselayer.cpp :150 ] �[0mConnection to PulseAudio server established
�[0m�[22;36m[1704680039.286|20013|pulselayer.cpp :180 ] �[0mUpdating PulseAudio sink list
�[0m�[22;36m[1704680039.286|20013|pulselayer.cpp :197 ] �[0mUpdating PulseAudio source list
�[0m�[22;36m[1704680039.286|20013|pulselayer.cpp :214 ] �[0mUpdating PulseAudio server infos
�[0m�[22;36m[1704680039.289|20013|pulselayer.cpp :685 ] �[0mPulseAudio server info:
Server name: pulseaudio
Server version: 16.1
Default Sink auto_null
Default Source auto_null.monitor
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
�[0m�[22;36m[1704680039.289|20013|audiolayer.cpp :73 ] �[0mHardware audio format available : {s16, 2 channels, 44100Hz} 0
�[0m�[22;36m[1704680039.289|20013|manager.cpp :2680] �[0mAudio format changed: {s16, 1 channels, 16000Hz} -> {s16, 2 channels, 44100Hz}
�[0m�[22;36m[1704680039.384|20007|test_media_player.cpp :106 ] �[0mStart testCreate
�[0m�[22;36m[1704680039.384|20007|audio_input.cpp :53 ] �[0mCreating audio input with id: ./media/test_video_file.mp4
�[0m�[22;36m[1704680039.384|20007|ringbuffer.cpp :55 ] �[0mCreate new RingBuffer ./media/test_video_file.mp4
�[0m�[22;36m[1704680039.384|20007|sinkclient.cpp :335 ] �[0m[Sink:0xe61d70] Sink [./media/test_video_file.mp4] created
�[0m�[22;36m[1704680039.385|20007|video_input.cpp :607 ] �[0mMRL: './media/test_video_file.mp4'
�[0m�[22;36m[1704680039.385|20030|media_player.cpp :81 ] �[0m�[01;33mGuessing file type for ./media/test_video_file.mp4
�[0m�[22;36m[1704680039.386|20030|media_decoder.cpp :152 ] �[0mTrying to open input ./media/test_video_file.mp4 with format , pixel format , size 0x0, rate 0
�[0m�[22;36m[1704680039.391|20030|media_decoder.cpp :172 ] �[0mOpened input Using format and resolution 320x240
�[0m�[22;36m[1704680039.392|20030|media_decoder.cpp :555 ] �[0mUsing libopus Opus (libopus) decoder for audio
�[0m�[22;36m[1704680039.392|20030|media_decoder.cpp :566 ] �[0m�[01;33mNot using hardware decoding for opus
�[0m�[22;36m[1704680039.392|20030|ringbufferpool.cpp :155 ] �[0mBind rbuf './media/test_video_file.mp4' to ringbuffer 'audiolayer_id'
�[0m�[22;36m[1704680039.392|20030|ringbufferpool.cpp :151 ] �[0m�[01;33mRingBuffer has a readoffset on itself
�[0m�[22;36m[1704680039.392|20030|ringbufferpool.cpp :155 ] �[0mBind rbuf './media/test_video_file.mp4' to ringbuffer './media/test_video_file.mp4'
�[0m�[22;36m[1704680039.411|20030|audiostream.cpp :54 ] �[0mPlayback: Creating stream with device (s16le, 44100Hz, 1 channels)
�[0m�[22;36m[1704680039.411|20030|audiostream.cpp :258 ] �[0mStream is creating...
�[0m�[22;36m[1704680039.412|20030|threadloop.cpp :74 ] �[0m�[22;31malready started
�[0m�[22;36m[1704680039.412|20030|media_decoder.cpp :585 ] �[0m�[22;31mUnsupported codec
�[0m�[22;36m[1704680039.412|20030|sinkclient.cpp :190 ] �[0m[ShmHolder:Jami Daemon_shm_20007_0] New size: f=0, a=103
�[0m�[22;36m[1704680039.412|20030|sinkclient.cpp :157 ] �[0m[ShmHolder:Jami Daemon_shm_20007_0] New holder created
�[0m�[22;36m[1704680039.412|20030|sinkclient.cpp :284 ] �[0m[Sink:0xe61d70] Shared memory [Jami Daemon_shm_20007_0] created
�[0mXFAIL ut_media_player (exit status: 139)
```Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1542QObject::moveToThread warning when starting Jami2024-02-09T17:36:39ZFrançois-Simon Fauteux-ChapleauQObject::moveToThread warning when starting JamiThe following warning is generated when starting Jami:
```
default [1706022418678][WRN]: QObject::moveToThread: Cannot move objects with a parent
```The following warning is generated when starting Jami:
```
default [1706022418678][WRN]: QObject::moveToThread: Cannot move objects with a parent
```https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1478Consommation anormale de ressources CPU2024-02-09T17:05:17ZFirenze RéatConsommation anormale de ressources CPUBonjour,
Je constate une sollicitation anormale du processeur dans Jami. Cela se produit au bout de quelques minutes après le démarrage.
SE : Debian GNU/Linux 11 bullseye
Version de Jami : Using Qt runtime version: 6.5.3...Bonjour,
Je constate une sollicitation anormale du processeur dans Jami. Cela se produit au bout de quelques minutes après le démarrage.
SE : Debian GNU/Linux 11 bullseye
Version de Jami : Using Qt runtime version: 6.5.3
Jami 202312222019
La consommation de ressource CPU a ici été mesurée en ligne de commande avec l'outil top avec un load average 1 ou supérieur (première capture d'écran)
La seconde capture d'écran est celle du tableau qui indique l'état du réseau dans la rubrique de dépannage.
Le fichier texte est une copie de la sortie du terminal au lancement de jami.
Je n'ai pas pu obtenir le contenu du journal de déverminage ou déboguage, faute de réponse de l'application Jami.
![Capture_d_écran_du_2023-12-26_18-50-19](/uploads/db2f8f9b1f9453479e59ff757c18ca59/Capture_d_écran_du_2023-12-26_18-50-19.png)
![Capture_d_écran_du_2023-12-26_18-49-02](/uploads/d30b33f0e7b4e08ce4a170801a9e36c0/Capture_d_écran_du_2023-12-26_18-49-02.png)
[Observation_depuis_le_terminal_20231226](/uploads/5001f6205578ab7e9c0285e1339f5899/Observation_depuis_le_terminal_20231226)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/15033rdparty/qrencode-win32 submodule refers to unknown commit2024-02-09T17:04:09ZMaxim Cournoyer3rdparty/qrencode-win32 submodule refers to unknown commitHello,
```
~/src/jami$ git submodule deinit -f 3rdparty/qrencode-win32
Répertoire '3rdparty/qrencode-win32' nettoyé
Sous-module '3rdparty/qrencode-win32' (https://github.com/blizzard4591/qrencode-win32.git) non enregistré pour le chemin...Hello,
```
~/src/jami$ git submodule deinit -f 3rdparty/qrencode-win32
Répertoire '3rdparty/qrencode-win32' nettoyé
Sous-module '3rdparty/qrencode-win32' (https://github.com/blizzard4591/qrencode-win32.git) non enregistré pour le chemin '3rdparty/qrencode-win32'
~/src/jami$ rm -rf 3rdparty/qrencode-win32/
~/src/jami$ ./build.py --init
Sous-module '3rdparty/qrencode-win32' (https://github.com/blizzard4591/qrencode-win32.git) enregistré pour le chemin '3rdparty/qrencode-win32'
fatal : erreur distante : upload-pack: not our ref 5ccf9bd4455dfd55a41acfdf0bdbeb85605e10b6
fatal : Chemin de sous-module '3rdparty/qrencode-win32' récupéré, mais il ne contenait pas 5ccf9bd4455dfd55a41acfdf0bdbeb85605e10b6. La récupération directe de ce commit a échoué.
Traceback (most recent call last):
File "/home/maxim/src/jami/./build.py", line 826, in <module>
main()
File "/home/maxim/src/jami/./build.py", line 795, in main
run_init(parsed_args)
File "/home/maxim/src/jami/./build.py", line 311, in run_init
subprocess.run(["git", "submodule", "update", "--init"],
File "/gnu/store/mvza3hr80ywy78jg6cbgvcm8aiis9nc0-python-3.10.7/lib/python3.10/subprocess.py", line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', 'submodule', 'update', '--init']' returned non-zero exit status 128.
```
This happens on commit a4300308dc8d03d59f620bb5fed753df5cf31ed9.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1560Some files doesn't load in chatview but are there2024-02-09T17:00:37ZSébastien BlinSome files doesn't load in chatview but are there# Scenario
+ Send files
+ Reload Jami
+ Some are not showing in the chatview, but they are showing in other panels (search or files in details)# Scenario
+ Send files
+ Reload Jami
+ Some are not showing in the chatview, but they are showing in other panels (search or files in details)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1531messageBar is broken when sending file2024-02-09T16:57:58ZCapucine BerthetmessageBar is broken when sending file## Describe your environment
Please specify the following:
- OS: macOs
- Jami version: 202401092311
- App Store version
## Steps to reproduce
- Can you reproduce the bug: at will
## I) Steps to reproduce the bug with the show typo d...## Describe your environment
Please specify the following:
- OS: macOs
- Jami version: 202401092311
- App Store version
## Steps to reproduce
- Can you reproduce the bug: at will
## I) Steps to reproduce the bug with the show typo displayed:
1. open a conversation
2. click on the show typo button to have all the options displayed
3. send a file
4. click on the show typo button to hide all the options
## Actual result:
The messageBar rectangle is too high
![7420a5beaa37f63f0ee20f1b672406657ba3c594_164208656894147](/uploads/cf0e059d9040b58ecb8f67236b83a330/7420a5beaa37f63f0ee20f1b672406657ba3c594_164208656894147.png)
## Expected result:
The messageBar rectangle should resize to it initial size
## II) Steps to reproduce the bug without the show typo displayed:
1. open a conversation
2. make sure the typo options are hidden (by clicking on the showtypo button if they are displayed)
3. send a file
4. click on the show typo button
## Actual result:
No typo options are displayed and the only button remaining is the preview button.
We can't even click again the show typo button.
![9640b56191d2263472e6bafe526ceeedff346653_6275153125194285](/uploads/75377fd74d14c354c1e80ea000600e0b/9640b56191d2263472e6bafe526ceeedff346653_6275153125194285.png)
## Expected result:
All the typo options should be displayedhttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/21Timeout during UPnPContext shutdown2024-02-08T20:16:00ZFrançois-Simon Fauteux-ChapleauTimeout during UPnPContext shutdownThe function `PUPnP::terminate(std::condition_variable&)`, which is called when UPnP shuts down, includes the following line:
```
cvOngoing_.wait(lk, [&]() { return ongoingOps_ == 0; });
```
This line frequently (though not always) takes...The function `PUPnP::terminate(std::condition_variable&)`, which is called when UPnP shuts down, includes the following line:
```
cvOngoing_.wait(lk, [&]() { return ongoingOps_ == 0; });
```
This line frequently (though not always) takes a very long time to complete due to a timeout in `PUPnP::downLoadIgdDescription`. More specifically, `PUPnP::downLoadIgdDescription` calls `UpnpDownloadXmlDoc`, which calls `UpnpDownloadUrlItem`, which calls `http_Download`, which calls `http_RequestAndResponse`. The `http_RequestAndResponse` function returns a `UPNP_E_SOCKET_CONNECT` error code after its attempt to establish a connection (via a call to `private_connect`) fails. This can cause a delay of over two minutes when closing Jami if multiple downloads fail (which does happen - I often got four failure while testing, e.g.:
```
PUPnP: Discovered a new IGD [uuid:C084EDD9-1DE4-9E6A-DEAD-34A8C7031F76 url: http://192.168.51.82:1780/InternetGatewayDevice.xml]
PUPnP: Discovered a new IGD [uuid:0F2A137C-6FF1-C2BE-A962-0150A7DA9FA9 url: http://192.168.51.82:1780/InternetGatewayDevice.xml]
PUPnP: Discovered a new IGD [uuid:64D4257E-8CFC-3924-97C1-9183CCBFEDB1 url: http://192.168.51.82:1780/InternetGatewayDevice.xml]
PUPnP: Discovered a new IGD [uuid:08780A31-017A-6198-F7A9-0B060FA1B336 url: http://192.168.51.82:1780/InternetGatewayDevice.xml]
[...]
Error downloading device XML document from http://192.168.51.82:1780/InternetGatewayDevice.xml -> UPNP_E_SOCKET_CONNECT
Error downloading device XML document from http://192.168.51.82:1780/InternetGatewayDevice.xml -> UPNP_E_SOCKET_CONNECT
Error downloading device XML document from http://192.168.51.82:1780/InternetGatewayDevice.xml -> UPNP_E_SOCKET_CONNECT
Error downloading device XML document from http://192.168.51.82:1780/InternetGatewayDevice.xml -> UPNP_E_SOCKET_CONNECT
```
)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1557Crash when deleting account [non-deterministic]2024-02-08T20:09:13ZAndreas TraczykCrash when deleting account [non-deterministic]- Steps to reproduce: delete an account that has at least one conversation
- Possibly related to https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1081- Steps to reproduce: delete an account that has at least one conversation
- Possibly related to https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1081https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1470Deleting a message on TV does not work (just the display)2024-02-08T19:35:24ZEmma FalkiewitzDeleting a message on TV does not work (just the display)If we want to delete a message on TV :
![Screen_recording_20231130_164011](/uploads/ae3906468519b35a97f8cac4691476d1/Screen_recording_20231130_164011.mp4)
The function works but not the display:
![image](/uploads/b05d3f4dabf59fa89e41a...If we want to delete a message on TV :
![Screen_recording_20231130_164011](/uploads/ae3906468519b35a97f8cac4691476d1/Screen_recording_20231130_164011.mp4)
The function works but not the display:
![image](/uploads/b05d3f4dabf59fa89e41aa8f60c78ce3/image.png)Emma FalkiewitzEmma Falkiewitzhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/21SIP register fails: No username on digest authentication2024-02-08T18:58:54ZAlba MendezSIP register fails: No username on digest authenticationThis bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register....This bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register.
My Asterisk server sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>;tag=as3f952c47
...
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0074f5d0"
And Ring then sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>
...
Authorization: Digest , realm="asterisk", nonce="0074f5d0", uri="sip:10.139.205.101", response="631415fcf3715907a48f11fec1e6a880", algorithm=MD5
i.e. notice the space and comma after `Digest`
ring-daemon version 2018-07-07. Bug could be on upstream, for some reason username is not set on `pjsip/src/pjsip/sip_auth_client.c` when adding the Authorization header, [header printed here](https://github.com/asterisk/pjproject/blob/106ec876a371b57bb3db8231a55cb5f368e6266b/pjsip/src/pjsip/sip_auth_msg.c#L73).Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1550No option to delete file2024-02-08T15:56:58ZPierre NicolasNo option to delete fileYou should have two options:
* Delete file from device
* Delete message
See qt-ticket : https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1287You should have two options:
* Delete file from device
* Delete message
See qt-ticket : https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1287https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1194Difficult to visualy dissociate replied message from the reply message2024-02-08T15:43:47ZPierre NicolasDifficult to visualy dissociate replied message from the reply message![Screenshot_20230320_170851](/uploads/8a1dd5c59ae0df07f02db156e2b59206/Screenshot_20230320_170851.png)![Screenshot_20230320_170851](/uploads/8a1dd5c59ae0df07f02db156e2b59206/Screenshot_20230320_170851.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1215Call: Camera preview is displayed in portrait instead of landscape2024-02-08T15:42:14ZPierre NicolasCall: Camera preview is displayed in portrait instead of landscape## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start a call with camera in landscape orientation.
2. Minimize app and come back to it.
- Actual result: Your camera preview switched to portrait orientation.
## Additional information
![image_shape_is_not_adapted_](/uploads/5fc8d73ce9535d40be349ccf95426fb6/image_shape_is_not_adapted_.mp4)