savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-10-05T18:30:36Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/240Merge subcall crashs2020-10-05T18:30:36ZCyrille BéraudMerge subcall crashs```[1593028407.287|12882|manager.cpp :1945 ] [call:8367187783238858] Peer ringing
[1593028407.287|12882|manager.cpp :1945 ] [call:8367187783238858] Peer ringing
[1593028407.287|12882|call.cpp :476 ] [call:8367187783...```[1593028407.287|12882|manager.cpp :1945 ] [call:8367187783238858] Peer ringing
[1593028407.287|12882|manager.cpp :1945 ] [call:8367187783238858] Peer ringing
[1593028407.287|12882|call.cpp :476 ] [call:8367187783238858] subcall 2172395774784029 answered by peer
[1593028407.287|12882|sipcall.cpp :1449 ] [sipcall:8367187783238858] merge subcall 2172395774784029
--Type <RET> for more, q to quit, c to continue without paging--
Thread 2 "dring" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6c69700 (LWP 12882)]
0x00005555558e63f0 in jami::SIPCall::merge(jami::Call&) ()
(gdb) bt
#0 0x00005555558e63f0 in jami::SIPCall::merge(jami::Call&) ()
#1 0x000055555587066d in jami::Call::subcallStateChanged(jami::Call&, jami::Call::CallState, jami::Call::ConnectionState) ()
#2 0x0000555555870b3d in std::_Function_handler<void (), jami::runOnMainThread<jami::Call::addSubCall(jami::Call&)::{lambda(jami::Call::CallState, jami::Call::ConnectionState, int)#1}::operator()(jami::Call::CallState, jami::Call::ConnectionState, int) const::{lambda()#1}>(jami::Call::addSubCall(jami::Call&)::{lambda(jami::Call::CallState, jami::Call::ConnectionState, int)#1}::operator()(jami::Call::CallState, jami::Call::ConnectionState, int) const::{lambda()#1}&&)::{lambda()#1}>::_M_invoke(std::_Any_data const&) ()
#3 0x00005555558af251 in jami::ScheduledExecutor::loop() ()
#4 0x00005555558af369 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::ScheduledExecutor::ScheduledExecutor()::{lambda()#1}> > >::_M_run()
()
#5 0x00007ffff795ccb4 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00007ffff7c1d609 in start_thread (arg=<optimized out>)
at pthread_create.c:477
#7 0x00007ffff764a103 in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)
#0 0x00005555558e63f0 in jami::SIPCall::merge(jami::Call&) ()
#1 0x000055555587066d in jami::Call::subcallStateChanged(jami::Call&, jami::Call::CallState, jami::Call::ConnectionState) ()
#2 0x0000555555870b3d in std::_Function_handler<void (), jami::runOnMainThread<jami::Call::addSubCall(jami::Call&)::{lambda(jami::Call::CallState, jami::Call::ConnectionState, int)#1}::operator()(jami::Call::CallState, jami::Call::ConnectionState, int) const::{lambda()#1}>(jami::Call::addSubCall(jami::Call&)::{lambda(jami::Call::CallState, jami::Call::ConnectionState, int)#1}::operator()(jami::Call::CallState, jami::Call::ConnectionState, int) const::{lambda()#1}&&)::{lambda()#1}>::_M_invoke(std::_Any_data const&) ()
#3 0x00005555558af251 in jami::ScheduledExecutor::loop() ()
#4 0x00005555558af369 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::ScheduledExecutor::ScheduledExecutor()::{lambda()#1}> > >::_M_run()
()
#5 0x00007ffff795ccb4 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00007ffff7c1d609 in start_thread (arg=<optimized out>)
at pthread_create.c:477
#7 0x00007ffff764a103 in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/235Black screen when call Android devices2020-10-05T18:34:16ZPierre LespagnolBlack screen when call Android devicesIf the daemon fail to receive the first packet sent by MediaCodec (Android with hardware acceleration), the decoding session fail to be initialised.If the daemon fail to receive the first packet sent by MediaCodec (Android with hardware acceleration), the decoding session fail to be initialised.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/768No push notification2020-10-05T18:53:22ZMikhailNo push notificationThere is no push notification incoming messages.
Jami version - 20200623-01
MI9
MIUI ver 11.0.5.0
Android ver 10 QKQ1.190825.002There is no push notification incoming messages.
Jami version - 20200623-01
MI9
MIUI ver 11.0.5.0
Android ver 10 QKQ1.190825.002https://git.jami.net/savoirfairelinux/jami-jams/-/issues/43Replace jamiId with id in the directory search response2020-10-05T18:57:15ZLarbi GharibReplace jamiId with id in the directory search responseReplace jamiId with id in the directory search response
/api/auth/directory/searchReplace jamiId with id in the directory search response
/api/auth/directory/searchFélix SidokhineFélix Sidokhinehttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/40web client: never try to load full list of users2020-10-05T20:17:06ZAdrien Béraudweb client: never try to load full list of usersPaginate or avoid making the request for a full list.
Paginate or avoid making the request for a full list.
Larbi GharibLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/809database related crash during exit2020-10-05T20:23:10ZHugo Lefeuvredatabase related crash during exitSometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at r...Sometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
terminate called after throwing an instance of 'lrc::Database::QueryError'
what(): Driver not loaded Driver not loaded
Aborted (core dumped)
```
I suspect a race condition in the LRC. Something like:
1. DB is closed
2. a signal comes and the callback tries to access the DB's freed data structures
Since this bug is only reproducible on the GNU/Linux GNOME client I'm reporting it here.
**How to reproduce:**
1. open a GNU/Linux GNOME client
2. close it using "quit" button
This crash is pretty rare, and like most race conditions it may not be reproducible on every machine.https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/226Bad image quality on iOS/MacOS due to missed packets2020-10-05T20:23:20ZGuillaume HellerBad image quality on iOS/MacOS due to missed packetsWhen a video call is done with an iOS/MacOS device, the image quality is bad.
Following errors are raised in the logs:
```
[1571929580.296| 815|media_decoder.cpp :306 ] Hardware decoding disabled by user preference
[1571929580.296| ...When a video call is done with an iOS/MacOS device, the image quality is bad.
Following errors are raised in the logs:
```
[1571929580.296| 815|media_decoder.cpp :306 ] Hardware decoding disabled by user preference
[1571929580.296| 815|media_decoder.cpp :311 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1571929580.296| 815|sinkclient.cpp :195 ] ShmHolder[Jami Daemon_shm_19985_1]: new sizes: f=0, a=103
[1571929580.297| 815|sinkclient.cpp :161 ] ShmHolder: new holder 'Jami Daemon_shm_19985_1'
[1571929580.297| 815|sinkclient.cpp :418 ] Start sink <7221885205892140 / Jami Daemon_shm_19985_1>, size=848x480, mixer=0
[1571929580.301| 815|sinkclient.cpp :195 ] ShmHolder[Jami Daemon_shm_19985_1]: new sizes: f=1628160, a=3256423
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 3 packets
[1571929581.803|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[1571929583.765|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 2 packets
[1571929585.595|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[1571929585.655| 815|sip_utils.cpp :203 ] Registered thread 0x7f3d21fe0dd0 (0x4E11)
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[1571929586.631|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 2 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 2 packets
[1571929587.662|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 30 packets
[h264 @ 0x7f3d781c5480] out of range intra chroma pred mode
[h264 @ 0x7f3d781c5480] error while decoding MB 6 1
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 2 packets
[sdp @ 0x7f3d78898e60] max delay reached. need to consume packet
[sdp @ 0x7f3d78898e60] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[sdp @ 0x7f3d680262e0] max delay reached. need to consume packet
[sdp @ 0x7f3d680262e0] RTP: missed 1 packets
[1571929590.911|19986|sipcall.cpp :284 ] Sending video keyframe request via SIP INFO
[1571929590.932|19985|manager.cpp :1662 ] [call:7221885205892140] Remove local audio
[1571929590.932|19985|sipcall.cpp :302 ] [call:7221885205892140] Terminate SIP session
[1571929590.933|19985|sipcall.cpp :1050 ] [call:7221885205892140] stopping all medias
```New release 1https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/553Profile (name) not editable2020-10-05T20:29:22ZRing ThingProfile (name) not editableDuring creation of a Jami-ID one can edit the profile data to be shown to peers, however I could not find a way to edit this information after the Jami-ID was created. Editing the account name ("Ring-Account" by default) for example, see...During creation of a Jami-ID one can edit the profile data to be shown to peers, however I could not find a way to edit this information after the Jami-ID was created. Editing the account name ("Ring-Account" by default) for example, seems unrelated.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/743Jami for Iran During Internet shutdown2020-10-05T20:53:23ZkouhiJami for Iran During Internet shutdownI'm not sure if you anyone within the Jami core team have followed the recent protests in Iran that led the state to shut down the internet for more than 100 hours. More context can be found here (https://ooni.io/post/2019-iran-internet-...I'm not sure if you anyone within the Jami core team have followed the recent protests in Iran that led the state to shut down the internet for more than 100 hours. More context can be found here (https://ooni.io/post/2019-iran-internet-blackout/).
#### Here is a scenario:
Let's assume that the internet in Iran is shutdown and people do not have access to the international traffic. It's only the national intranet which led users access all websites and infrastructures hosted in Iran.
#### Here is a question:
Given that Jami works on openDHT, would Jami still be able to find peers during the internet shutdown? Would users in the country be able to safely communicate with each other even when the internet is down. To make my question specific, how would the peer-discovery perform during the time when access to the international traffic is blocked?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1018Intercom audio-only calls and chats not working Jami built on 2019-05-02 13:3...2020-10-05T21:05:09ZovariIntercom audio-only calls and chats not working Jami built on 2019-05-02 13:32:46 UTCLinux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-02 13:32:46 UTC
1. Intercom audio calls are not calling calling on the other device. Both devices calling each other at the same time not working either.
2. Intercom chats are not getti...Linux Mint 19.1 Cinnamon<br>
Jami built on 2019-05-02 13:32:46 UTC
1. Intercom audio calls are not calling calling on the other device. Both devices calling each other at the same time not working either.
2. Intercom chats are not getting through to the other device
3. Intercom chats are now showing on the device that wrote the message once the device is shut down and restarted. As you can see in the image below, we shut down the device and turned on the device 12 hours later and our own message was shown. This message should not have been shown as we sent it. Should there be an if statement in the chatview like:<br>
```
IF ( (incomingMessageAccountID=thisDeviceAccountID) AND (incomingMessageDeviceID=thisDeviceID) ) {
// do nothing as this message originated from this device
} ELSE {
// show message is this message did not originate from this device
}
```
![Intercom_audio_calls_and_chats_not_working_Jami_built_on_2019-05-02_133246_UTC](/uploads/e36b3a95dbc7141fbe4b153b28518863/Intercom_audio_calls_and_chats_not_working_Jami_built_on_2019-05-02_133246_UTC.png)
Could this pleased be fixed in the next update as this is a feature we have been using frequently to test Jami. This seems to be a regression as intercom audio calls worked in the previous version of Jami.
Thank you
https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/677<br>
https://git.jami.net/savoirfairelinux/ring-project/issues/554https://git.jami.net/savoirfairelinux/jami-project/-/issues/818ring-lrc compile failed on conversationmodel.cpp2020-10-05T21:12:58Zrobdyckring-lrc compile failed on conversationmodel.cppCompile of ring-lrc/src/conversationmodel.cpp failed. The error was CANCELLED is not a member of DRing::Account::MessageStates. However MessageStates is defined in ring-daemon and includes CANCELLED but appears to be out of scope in ring...Compile of ring-lrc/src/conversationmodel.cpp failed. The error was CANCELLED is not a member of DRing::Account::MessageStates. However MessageStates is defined in ring-daemon and includes CANCELLED but appears to be out of scope in ring-lrc. I found in ring-daemon/src/manager.cpp a method that casts MessageStatus to MessageStates. The method is called statusFromImStatus. The MessageStates CANCELLED is missing from this method.
I added "case im::MessageStatus::CANCELLED:
return static_cast<int>(DRing::Account::MessageStates::CANCELLED);"
For both ring-daemon and ring-lrc I did make clean. Both compiled successfully.https://git.jami.net/savoirfairelinux/jami-project/-/issues/563video/audio not synchronized (delay)2020-10-05T21:13:37ZVinogradov Romanvideo/audio not synchronized (delay)Ubuntu 16.04 (32-bit) does not send messages and does not receive outgoing calls (audio and video). I accept incoming messages and calls and everything is fine. Sometimes when sending messages Jami is turned off. What could be the problem?Ubuntu 16.04 (32-bit) does not send messages and does not receive outgoing calls (audio and video). I accept incoming messages and calls and everything is fine. Sometimes when sending messages Jami is turned off. What could be the problem?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/275Getting error when starting daemon: ==25277==ASan runtime does not come first...2020-10-06T02:26:26ZDoron BeharGetting error when starting daemon: ==25277==ASan runtime does not come first in initial library listHi, I'm getting this error when trying to run `$jami-daemon/lib/dring/dring`:
```
==27318==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELO...Hi, I'm getting this error when trying to run `$jami-daemon/lib/dring/dring`:
```
==27318==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
```
I also noticed I get it when trying to run the tests:
https://review.jami.net/c/ring-daemon/+/15021https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/611Change "Ring" to "Jami" from created Jami accounts !2020-10-06T18:51:33ZNokia808Change "Ring" to "Jami" from created Jami accounts !Dears there is still in Android application of Jami, a remnant still show "ring" instead "jami": on upper right corner of UI a gear icon beside it "Jami", when clicked it will show already created accounts & 2 options, one to add new Jam...Dears there is still in Android application of Jami, a remnant still show "ring" instead "jami": on upper right corner of UI a gear icon beside it "Jami", when clicked it will show already created accounts & 2 options, one to add new Jami account & 2nd to create SIP account. But any already created Jami account will be mentioned in UI as "ring: ..........."
This should corrected !https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/228app crashes at file transfer reception2020-10-07T20:14:56ZGuillaume Hellerapp crashes at file transfer receptionJami 20191128 - macOS Mojave 10.14.6
**How to reproduce:** send a file or leave an audio/video message from any client to a MacOS device
Logs:
> [1575472433.045|0x70000e9db000|p2p.cpp :842 ] [Account:d948a1f802df4676] ICE ...Jami 20191128 - macOS Mojave 10.14.6
**How to reproduce:** send a file or leave an audio/video message from any client to a MacOS device
Logs:
> [1575472433.045|0x70000e9db000|p2p.cpp :842 ] [Account:d948a1f802df4676] ICE negotiation succeed. Answering with local SDP
[1575472435.564|0x70000e9db000|p2p.cpp :860 ] [Account d948a1f802df4676] [CNX] start TLS session
[1575472435.564|0x70000e9db000|ice_transport.cpp :573 ] ICE as slave
[1575472435.564|0x70000e958000|tls_session.cpp :759 ] [TLS] Start server session
[1575472435.583|0x70000e958000|tls_session.cpp :456 ] [TLS] User identity loaded
[1575472435.584|0x70000e958000|tls_session.cpp :854 ] [TLS] handshake
[1575472436.103|0x70000e958000|sip_utils.cpp :203 ] Registered thread 0x7f979eb53810 (0x6E9C)
[1] 28316 segmentation fault /Applications/Jami\ beta/Jami.app/Contents/MacOS/Jami
➜ ~
More log details in the file attached
[log_crash_file_transfer_reception.pdf](/uploads/b128c4bd29faeaf36f3a18a9001f4687/log_crash_file_transfer_reception.pdf)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/74Contact request UI issues2020-10-08T14:24:08ZAlbert Babí OllerContact request UI issues1. From a "normal" contact conversation it is not possible to switch to a conversation/call from the "Invitations" menu.
2. Incoming call from a non-contact does not switch to menu "Invitations" and corresponding conversation.
3. Accep...1. From a "normal" contact conversation it is not possible to switch to a conversation/call from the "Invitations" menu.
2. Incoming call from a non-contact does not switch to menu "Invitations" and corresponding conversation.
3. Accepting an invitation from the conversation menu does not update the conversation header (remove button +Accept Contact).
![Screenshot_at_2020-09-14_14-48-18](/uploads/4f395eed8fce7a92f971741832695c33/Screenshot_at_2020-09-14_14-48-18.png)
4. Invitation text does not elide properly
![Screenshot_at_2020-09-14_11-40-42](/uploads/73b5d57f4f9c1573f0836844335d70f6/Screenshot_at_2020-09-14_11-40-42.png)Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/103callview not displayed when receiving a call and auto-answer is enabled2020-10-08T14:24:24ZGuillaume Hellercallview not displayed when receiving a call and auto-answer is enabledWhen a call is received and auto answer is enabled, callview should be selected so user knows that a call is ongoingWhen a call is received and auto answer is enabled, callview should be selected so user knows that a call is ongoingAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/134Chat view first access can show blank conversation2020-10-08T14:24:38ZAlbert Babí OllerChat view first access can show blank conversationAccessing to a conversation right after the application starts does not load its content.
```
js: Uncaught ReferenceError: hideMessagesDiv is not defined
js: Uncaught ReferenceError: showTypingIndicator is not defined
js: Uncaught Refere...Accessing to a conversation right after the application starts does not load its content.
```
js: Uncaught ReferenceError: hideMessagesDiv is not defined
js: Uncaught ReferenceError: showTypingIndicator is not defined
js: Uncaught ReferenceError: requestSendMessageContent is not defined
```Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/126Shortcuts: End call doesn't work anymore (Ctrl+D)2020-10-08T14:49:23ZSébastien BlinShortcuts: End call doesn't work anymore (Ctrl+D)All is in the titleAll is in the titleItération 21https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/142file transfer: partial file remains on pc after cancel2020-10-08T17:51:44ZPhilippe Gorleyfile transfer: partial file remains on pc after cancelCancelling a file transfer (on the receiving side) should remove the partial file.Cancelling a file transfer (on the receiving side) should remove the partial file.Sébastien BlinSébastien Blin