savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-05-28T13:12:02Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/419String "is calling you" not translatable2021-05-28T13:12:02ZGuillaume HellerString "is calling you" not translatable![image](/uploads/4d72d5217029c0a679d0a02a79abcf79/image.png)![image](/uploads/4d72d5217029c0a679d0a02a79abcf79/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/418Block contact doesn't work2021-05-19T17:34:31ZSébastien BlinBlock contact doesn't work## Describe your environment
Please specify the following:
master, built
## Steps to reproduce
+ Alice blocks Bob
## Current result
+ Bob is staying in the smartlist
## Expected
+ Bob should be removed unless for exact matches## Describe your environment
Please specify the following:
master, built
## Steps to reproduce
+ Alice blocks Bob
## Current result
+ Bob is staying in the smartlist
## Expected
+ Bob should be removed unless for exact matcheshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1251GTK-CRITICAL with JAMI-GNOME & JAMI (QT)2022-07-11T14:40:00Zcement-headGTK-CRITICAL with JAMI-GNOME & JAMI (QT)```
$ jami-gnome
** Message: 10:06:44.505: Jami GNOME client version: development
** Message: 10:06:44.505: git ref: unknown
** (jami-gnome:9787): WARNING **: 10:06:44.505: could not create symlink: File exists
No migration required
(j...```
$ jami-gnome
** Message: 10:06:44.505: Jami GNOME client version: development
** Message: 10:06:44.505: git ref: unknown
** (jami-gnome:9787): WARNING **: 10:06:44.505: could not create symlink: File exists
No migration required
(jami-gnome:9787): Gtk-WARNING **: 10:06:44.894: Child name 'calls' not found in GtkStack
contact update attempted for inexistent conversation
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.895: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.895: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.895: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.896: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.896: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:44.896: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
(jami-gnome:9787): Gtk-CRITICAL **: 10:06:45.193: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
Syncing lrc accounts list with the daemon
Syncing lrc accounts list with the daemon
Syncing lrc accounts list with the daemon
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/550To investigate2021-05-19T13:15:30ZSébastien BlinTo investigate```
1621367021.443|15196|tls_session.cpp :799 ] HTTP OCSP Request state=0 status_code=0
[1621367021.541| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=1 status_code=0
[1621367021.541| 8355|tls_session.cpp :799 ] HTTP OCSP ...```
1621367021.443|15196|tls_session.cpp :799 ] HTTP OCSP Request state=0 status_code=0
[1621367021.541| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=1 status_code=0
[1621367021.541| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=3 status_code=0
[1621367021.542| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=1 status_code=0
[1621367021.542| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=3 status_code=0
[1621367021.554| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=2 status_code=404
[1621367021.554| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=4 status_code=404
[1621367021.554| 8355|tls_session.cpp :746 ] HTTP OCSP Request Failed with code 404
[1621367021.554| 8355|tls_session.cpp :697 ] Skipping OCSP verification 2b6ad943b85848949df139a27c98ca4622bfaef8: request failed
[1621367021.554| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=2 status_code=404
[1621367021.554| 8355|tls_session.cpp :799 ] HTTP OCSP Request state=4 status_code=404
[1621367021.554| 8355|tls_session.cpp :746 ] HTTP OCSP Request Failed with code 404
[1621367021.554| 8355|tls_session.cpp :697 ] Skipping OCSP verification 2b6ad943b85848949df139a27c98ca4622bfaef8: request failed
[1621367021.562|15194|tls_session.cpp :1191 ] [TLS] session established: (TLS1.3)-(ECDHE-SECP384R1)-(RSA-PSS-RSAE-SHA384)-(AES-256-GCM)
[1621367021.562|15196|tls_session.cpp :1191 ] [TLS] session established: (TLS1.3)-(ECDHE-SECP384R1)-(RSA-PSS-RSAE-SHA384)-(AES-256-GCM)
[1621367021.562|15194|connectionmanager.cpp:690 ] Connection to 2b6ad943b85848949df139a27c98ca4622bfaef8 is ready - Initied by DHT request. Vid: 17729604957344243654
[1621367021.562|15196|connectionmanager.cpp:690 ] Connection to 2b6ad943b85848949df139a27c98ca4622bfaef8 is ready - Initied by DHT request. Vid: 15841830044988338181
[New Thread 0x7ffed0ff9640 (LWP 15198)]
[New Thread 0x7ffed17fa640 (LWP 15197)]
[New Thread 0x7ffeb7fff640 (LWP 15199)]
[1621367022.203| 8489|channeled_transport.cpp:48 ] ChanneledSIPTransport@0x7fff04016e80 {tr=0x7fff04016ed0}
[1621367022.203| 8489|siptransport.cpp :81 ] SipTransport@0x7fff0005a320 {tr=0x7fff04016ed0 {rc=1}}
[1621367022.203| 8489|jamiaccount.cpp :5035 ] [Account 132642d000b21ad1] New SIP channel opened with 2b6ad943b85848949df139a27c98ca4622bfaef8
[1621367022.203| 8489|jamiaccount.cpp :4975 ] Peer 2b6ad943b85848949df139a27c98ca4622bfaef8 already got an up-to-date vcard
[1621367022.243| 8391|p2p.cpp :317 ] Incoming transfer request with id(1802370016735664233)
[1621367022.742|15198|ftp_server.cpp :213 ] [FTP] header: 'Content-Length' = '52630'
[1621367022.742|15198|ftp_server.cpp :213 ] [FTP] header: 'Display-Name' = 'Screenshot from 2021-05-18 15-42-46.png'
[1621367022.742|15198|ftp_server.cpp :213 ] [FTP] header: 'Offset' = '0'
[1621367022.742|15198|data_transfer.cpp :572 ] [FTP] incoming transfert of 52630 byte(s): Screenshot from 2021-05-18 15-42-46.png
[1621367023.243|15198|data_transfer.cpp :635 ] [FTP] file closed, rx 52630 on 52630
[1621367023.243|15198|p2p.cpp :343 ] Channel down for incoming transfer with id(1802370016735664233)
[1621367023.243|15198|sip_utils.cpp :251 ] Registered thread 0x7ffed0ff9428 (0x20A0)
malloc(): unsorted double linked list corrupted
--Type <RET> for more, q to quit, c to continue without paging--
Thread 53 "dring" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff32ffd640 (LWP 8490)]
0x00007ffff71ec769 in GI_libc_free (mem=0x7ff9479176b9) at malloc.c:3288
3288 malloc.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 0x00007ffff71ec769 in GI_libc_free (mem=0x7ff9479176b9)
at malloc.c:3288
#1 0x00005555558e6505 in gnu_cxx::new_allocator<unsigned char*>::deallocate
(this=0x7fff32ff9de7, p=0x7ff9479176b9, __t=140731993093888)
at /usr/include/c++/10/ext/new_allocator.h:133
#2 0x00005555558e0d84 in std::allocator_traits<std::allocator<unsigned char*> >::deallocate (a=..., p=0x7ff9479176b9, __n=140731993093888)
at /usr/include/c++/10/bits/alloc_traits.h:492
#3 0x00005555558db325 in std::_Deque_base<unsigned char, std::allocator<unsigned char> >::Mdeallocate_map (this=0x7fff32ff9ee0, p=0x7ff9479176b9,
n=140731993093888) at /usr/include/c++/10/bits/stl_deque.h:580
#4 0x00005555558d7dc3 in std::_Deque_base<unsigned char, std::allocator<unsigned char> >::~_Deque_base (this=0x7fff32ff9ee0, __in_chrg=<optimized out>)
at /usr/include/c++/10/bits/stl_deque.h:600
#5 0x00005555558da006 in std::deque<unsigned char, std::allocator<unsigned char> >::~deque (this=0x7fff32ff9ee0, __in_chrg=<optimized out>)
at /usr/include/c++/10/bits/stl_deque.h:1004
#6 0x00005555558d129a in jami::MultiplexedSocket::setOnRecv(unsigned short const&, std::function<long (unsigned char const*, unsigned long)>&&) (
this=0x7ffed401a640, channel=@0x7fff50238628: 43971, cb=...)
at multiplexed_socket.cpp:713
#7 0x00005555558d1f4f in jami::ChannelSocket::setOnRecv(std::function<long (unsigned char const*, unsigned long)>&&) (this=0x7fff64007a90, cb=...)
--Type <RET> for more, q to quit, c to continue without paging--
at multiplexed_socket.cpp:895
#8 0x0000555555c181cc in jami::ChanneledIncomingTransfer::~ChanneledIncomingTransfer (this=0x7fff64004b90, __in_chrg=<optimized out>)
at channeled_transfers.cpp:95
#9 0x000055555590c212 in std::default_delete<jami::ChanneledIncomingTransfer>::operator() (this=0x7fff640087d8, __ptr=0x7fff64004b90)
at /usr/include/c++/10/bits/unique_ptr.h:85
#10 0x000055555590a9f6 in std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> >::~unique_ptr (
this=0x7fff640087d8, __in_chrg=<optimized out>)
at /usr/include/c++/10/bits/unique_ptr.h:361
#11 0x000055555590fc8a in std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >::~pair (this=0x7fff640087d0, __in_chrg=<optimized out>)
at /usr/include/c++/10/bits/stl_pair.h:211
#12 0x000055555590fcae in gnu_cxx::new_allocator<std::_Rb_tree_node<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::destroy<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > (this=0x7fff8c308070,
p=0x7fff640087d0) at /usr/include/c++/10/ext/new_allocator.h:156
#13 0x000055555590f09b in std::allocator_traits<std::allocator<std::_Rb_tree_node<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer--Type <RET> for more, q to quit, c to continue without paging--
, std::default_delete<jami::ChanneledIncomingTransfer> > > > > >::destroy<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > (a=...,
p=0x7fff640087d0) at /usr/include/c++/10/bits/alloc_traits.h:531
#14 0x000055555590df71 in std::_Rb_tree<unsigned long, std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::Mdestroy_node (
this=0x7fff8c308070, __p=0x7fff640087b0)
at /usr/include/c++/10/bits/stl_tree.h:646
#15 0x000055555590c575 in std::_Rb_tree<unsigned long, std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::Mdrop_node (
this=0x7fff8c308070, __p=0x7fff640087b0)
at /usr/include/c++/10/bits/stl_tree.h:654
#16 0x000055555590ad56 in std::_Rb_tree<unsigned long, std::pair<unsigned long c--Type <RET> for more, q to quit, c to continue without paging--
onst, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::Merase (
this=0x7fff8c308070, __x=0x7fff640087b0)
at /usr/include/c++/10/bits/stl_tree.h:1921
#17 0x000055555590e3c6 in std::_Rb_tree<unsigned long, std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::clear (this=0x7fff8c308070)
at /usr/include/c++/10/bits/stl_tree.h:1261
#18 0x000055555590cb33 in std::_Rb_tree<unsigned long, std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::Merase_aux (
--Type <RET> for more, q to quit, c to continue without paging--
this=0x7fff8c308070, first=
{first = 1802370016735664233, second = std::unique_ptr<jami::ChanneledIncomingTransfer> = {get() = 0x7fff64004b90}}, last=
{first = 1, second = std::unique_ptr<jami::ChanneledIncomingTransfer> = {get() = 0x0}}) at /usr/include/c++/10/bits/stl_tree.h:2528
#19 0x000055555590b10b in std::_Rb_tree<unsigned long, std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > >, std::_Select1st<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::erase (
this=0x7fff8c308070, __x=@0x7ffeb86867e0: 1802370016735664233)
at /usr/include/c++/10/bits/stl_tree.h:2542
#20 0x0000555555909f3f in std::map<unsigned long, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> >, std::less<unsigned long>, std::allocator<std::pair<unsigned long const, std::unique_ptr<jami::ChanneledIncomingTransfer, std::default_delete<jami::ChanneledIncomingTransfer> > > > >::erase (this=0x7fff8c308070,
__x=@0x7ffeb86867e0: 1802370016735664233)
at /usr/include/c++/10/bits/stl_map.h:1069
#21 0x0000555555904c7a in operator() (__closure=0x7ffeb86867d0) at p2p.cpp:351
#22 0x0000555555907f3e in std::invoke_impl<void, jami::DhtPeerConnector::onInc--Type <RET> for more, q to quit, c to continue without paging--
omingConnection(const string&, const DataTransferId&, const std::shared_ptr<jami::ChannelSocket>&, jami::InternalCompletionCb&&)::<lambda()>::<lambda()>&>(std::invoke_other, struct {...} &) (__f=...)
at /usr/include/c++/10/bits/invoke.h:60
#23 0x000055555590721a in std::invoke_r<void, jami::DhtPeerConnector::onIncomingConnection(const string&, const DataTransferId&, const std::shared_ptr<jami::ChannelSocket>&, jami::InternalCompletionCb&&)::<lambda()>::<lambda()>&>(struct {...} &) (fn=...) at /usr/include/c++/10/bits/invoke.h:110
#24 0x0000555555906376 in std::_Function_handler<void(), jami::DhtPeerConnector::onIncomingConnection(const string&, const DataTransferId&, const std::shared_ptr<jami::ChannelSocket>&, jami::InternalCompletionCb&&)::<lambda()>::<lambda()> >::Minvoke(const std::_Any_data &) (__functor=...)
at /usr/include/c++/10/bits/std_function.h:291
#25 0x0000555555d82c4d in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dht::ThreadPool::run(std::function<void ()>&&)::{lambda()#1}> > >::Mrun()
()
#26 0x00007ffff7586694 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#27 0x00007ffff7be8450 in start_thread (arg=0x7fff32ffd640)
at pthread_create.c:473
#28 0x00007ffff726cd53 in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/417leaving the settings when in a call will select the "current" call, but not d...2021-05-19T00:54:46ZAndreas Traczykleaving the settings when in a call will select the "current" call, but not display the call viewAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/416in-call chatview cannot be opened if the conversation has not been reselected...2021-05-26T14:13:54ZAndreas Traczykin-call chatview cannot be opened if the conversation has not been reselected after engaging the callAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/415in-call chatview and dialogs do not close when call ends2021-05-26T14:13:39ZAndreas Traczykin-call chatview and dialogs do not close when call endsif the in-call chat view is open when a call ends, it stays on top of the stack until the call stack is reset by changing accountsif the in-call chat view is open when a call ends, it stays on top of the stack until the call stack is reset by changing accountsAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/549Crash in waitForData2021-05-18T19:07:09ZSébastien BlinCrash in waitForData```
2021-05-17 11:15:50.420 16384-17009/cx.ring D/libdring: Registered thread 0xb400007926e57898 (0x4000)
2021-05-17 11:15:50.420 16384-16937/cx.ring A/libc: FORTIFY: pthread_mutex_lock called on a destroyed mutex (0xb4000078c9163ac0)
20...```
2021-05-17 11:15:50.420 16384-17009/cx.ring D/libdring: Registered thread 0xb400007926e57898 (0x4000)
2021-05-17 11:15:50.420 16384-16937/cx.ring A/libc: FORTIFY: pthread_mutex_lock called on a destroyed mutex (0xb4000078c9163ac0)
2021-05-17 11:15:50.421 16384-16937/cx.ring A/libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 16937 (Thread-1236), pid 16384 (cx.ring)
2021-05-17 11:15:50.426 16384-16925/cx.ring I/libdring: Peer 77c565d1c02d70756356c00dbf989bf7efc8ce9a already got an up-to-date vcard
2021-05-17 11:15:50.517 16384-16875/cx.ring D/libdring: [ice:0xb4000079e69c64b0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16884/cx.ring D/libdring: [ice:0xb4000079e69cd3d0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16890/cx.ring D/libdring: [ice:0xb4000079e69f3700] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16877/cx.ring D/libdring: [ice:0xb4000079e69d42f0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16923/cx.ring D/libdring: [ice:0xb4000079e6a0f380] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16888/cx.ring D/libdring: [ice:0xb4000079e69e2130] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16930/cx.ring D/libdring: [ice:0xb4000079e6a1d1c0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16902/cx.ring D/libdring: [ice:0xb4000079e69fa620] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16926/cx.ring D/libdring: [ice:0xb4000079e6a19a30] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16900/cx.ring D/libdring: [ice:0xb4000079e69fddb0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16906/cx.ring D/libdring: [ice:0xb4000079e6a04cd0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16904/cx.ring D/libdring: [ice:0xb4000079e6a01540] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16896/cx.ring D/libdring: [ice:0xb4000079e69f6e90] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16894/cx.ring D/libdring: [ice:0xb4000079e69e9050] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16886/cx.ring D/libdring: [ice:0xb4000079e69e58c0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16928/cx.ring D/libdring: [ice:0xb4000079e6a08460] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 17013-17013/? I/crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
2021-05-17 11:15:50.517 16384-16892/cx.ring D/libdring: [ice:0xb4000079e69eff70] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16883/cx.ring D/libdring: [ice:0xb4000079e69de9a0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16876/cx.ring D/libdring: [ice:0xb4000079e69c9c40] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16879/cx.ring D/libdring: [ice:0xb4000079e69db210] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.517 16384-16878/cx.ring D/libdring: [ice:0xb4000079e69d7a80] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.518 16384-16921/cx.ring D/libdring: [ice:0xb4000079e6a0bbf0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.518 16384-16898/cx.ring D/libdring: [ice:0xb4000079e69ec7e0] ioqueue error 120004: Interrupted system call
2021-05-17 11:15:50.523 1019-1019/? I/tombstoned: received crash request for pid 16937
2021-05-17 11:15:50.525 17013-17013/? I/crash_dump64: performing dump of process 16384 (target tid = 16937)
2021-05-17 11:15:50.527 16384-16425/cx.ring E/libdring: pjsip_endpt_handle_events failed with error Interrupted system call
2021-05-17 11:15:50.532 17013-17013/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-05-17 11:15:50.532 17013-17013/? A/DEBUG: Build fingerprint: 'google/coral/coral:11/RQ2A.210505.002/7246365:user/release-keys'
2021-05-17 11:15:50.532 17013-17013/? A/DEBUG: Revision: 'MP1.0'
2021-05-17 11:15:50.532 17013-17013/? A/DEBUG: ABI: 'arm64'
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: Timestamp: 2021-05-17 11:15:50-0400
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: pid: 16384, tid: 16937, name: Thread-1236 >>> cx.ring <<<
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: uid: 10284
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0xb4000078c9163ac0)'
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x0 0000000000000000 x1 0000000000004229 x2 0000000000000006 x3 000000771fab2b30
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0000000000000028
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x8 00000000000000f0 x9 e29ef6db2cb5d1b4 x10 0000000000000000 x11 ffffffc0fffffbdf
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x12 0000000000000001 x13 000004872fe49c80 x14 0018f749d7f00558 x15 0000000001bf5fee
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x16 0000007ada911c80 x17 0000007ada8f3870 x18 000000771f840000 x19 0000000000004000
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x20 0000000000004229 x21 00000000ffffffff x22 0000000000000000 x23 0000000000000001
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x24 000000771fab4000 x25 b4000078a69d35a0 x26 000000771fab4000 x27 00000077d65af5a8
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: x28 0000000000000000 x29 000000771fab2bb0
2021-05-17 11:15:50.533 17013-17013/? A/DEBUG: lr 0000007ada8a72a0 sp 000000771fab2b10 pc 0000007ada8a72cc pst 0000000000000000
2021-05-17 11:15:50.533 3506-12715/? W/ChimeraUtils: Module com.google.android.gms.gcm has empty metadata display_name_string_id
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: backtrace:
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #00 pc 000000000004e2cc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #01 pc 00000000000b1428 /apex/com.android.runtime/lib64/bionic/libc.so (__fortify_fatal(char const*, ...)+124) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #02 pc 00000000000b0a24 /apex/com.android.runtime/lib64/bionic/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #03 pc 00000000000b087c /apex/com.android.runtime/lib64/bionic/libc.so (pthread_mutex_lock+160) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #04 pc 00000000000af1e4 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_cond_timedwait+132) (BuildId: 49090ae59e6ae37f8beae53c551820ad)
2021-05-17 11:15:50.536 17013-17013/? A/DEBUG: #05 pc 0000000000077a74 /data/app/~~P0scAgy5GUGb4kmKHvGx_A==/cx.ring-ouedHu4DuW0yvXeHMkL-rQ==/lib/arm64/libc++_shared.so (std::__ndk1::condition_variable::__do_timed_wait(std::__ndk1::unique_lock<std::__ndk1::mutex>&, std::__ndk1::chrono::time_point<std::__ndk1::chrono::system_clock, std::__ndk1::chrono::duration<long long, std::__ndk1::ratio<1l, 1000000000l> > >)+112) (BuildId: d776b1a67f4b0934ff585c6af89b742a8169d6b7)
```
In `MultiplexedSocket::waitForData` (std::unique_lock<std::mutex> lk {channelData->mutex};)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/470web chat view: no visual difference between received and unreceived hyperlink...2021-07-16T19:39:37ZAndreas Traczykweb chat view: no visual difference between received and unreceived hyperlink messageshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/548Add Fuzzy tests2021-05-26T13:08:17ZSébastien BlinAdd Fuzzy testsA lot of places in Jami are receiving data from another point.
This can cause crashes, potential attacks, etc. The goal is to improve quality and avoid crashes in the daemon whenever random payloads can be received.
Some place I can lis...A lot of places in Jami are receiving data from another point.
This can cause crashes, potential attacks, etc. The goal is to improve quality and avoid crashes in the daemon whenever random payloads can be received.
Some place I can list:
+ Sockets in connecting Manager:
+ SIP calls
+ File transfer
+ SIP Messages
+ ICE sockets
+ OpenDHT (DHT protocol & Jami messages)
+ Media calls
+ UPnP
+ SIP account
+ Account imports (via archive)
So, as a first step, we can:
+ Experiment various tools to perform fuzz testing
+ Generate random payloads for the places listed before.
Note that for some places this will need some investigation to send payloads to the component. However, for SIP/ConnectionManager/ICE it should not be difficult as sockets are exposed.Olivier DionOlivier Dionhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/136camera not stopped when peer refuse call2021-06-02T14:40:18ZKateryna Kostiukcamera not stopped when peer refuse callSteps:
1. Start call from iOS
2. Refuse call on another side
3. Expected result: call stopped, the camera stopped. Actual results: call stopped but the camera still runningSteps:
1. Start call from iOS
2. Refuse call on another side
3. Expected result: call stopped, the camera stopped. Actual results: call stopped but the camera still runningKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/940Tricky useless scrolls in Account>>Media>>Audio/Video settings2022-08-31T16:26:12ZTricky useless scrolls in Account>>Media>>Audio/Video settingsIn "Account" in "Media" settings there are many elements that can be seen by scrolling, but elements groupped in "Audio" have a scroll of their own which can give an impression that it is the end of all elements in "Media" settings
Usel...In "Account" in "Media" settings there are many elements that can be seen by scrolling, but elements groupped in "Audio" have a scroll of their own which can give an impression that it is the end of all elements in "Media" settings
Useless audio scroll doesn't reveal anything new, but just moves few pixels up and down
+Video elements scroll can give that impression toohttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1249Feature request: send location as coordinates and option to pick location on OSM2022-11-26T20:12:25ZFeature request: send location as coordinates and option to pick location on OSMSharing location which is a one time message and which can be manually picked is a popular messenger feature.
Using OpenStreetMaps gives the courage to share location from android, but as a place which is important and which stays in c...Sharing location which is a one time message and which can be manually picked is a popular messenger feature.
Using OpenStreetMaps gives the courage to share location from android, but as a place which is important and which stays in conversation loghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1248Feature request: Block contact without removing conversation or add mute opti...2023-09-07T19:24:35ZFeature request: Block contact without removing conversation or add mute option with inform/not toggle the contact which is being mutedWe need an option to choose wether to delete/not the whole conversation after clicking block contact. Because it is not deleted, as seen on android (block and unblock a contact)
Or add some kind of mute option which informs the contact ...We need an option to choose wether to delete/not the whole conversation after clicking block contact. Because it is not deleted, as seen on android (block and unblock a contact)
Or add some kind of mute option which informs the contact that notifications aren't enabled on other side
Reason: Our conversation is shared data, i have the right to see it even if i don't want him in contactshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/939Feature request: Make Plugins menu more noticable2021-05-15T07:28:52ZFeature request: Make Plugins menu more noticableBenefit: all users who are scared to enable plugins because they haven't seen such an option in any messenger
Reason: When i saw Plugins as toggle setting i thought it can't be anything more than a toggle, and that plugins are for advan...Benefit: all users who are scared to enable plugins because they haven't seen such an option in any messenger
Reason: When i saw Plugins as toggle setting i thought it can't be anything more than a toggle, and that plugins are for advanced users or users in Rendezvous mode or that Plugins are a incall option. And started clicking other toggle settings to check if they have a menu
Plugins menu needs to be noticable, so people can know for sure that it is not just a toggle, but now a toggle which when enabled turnes the label to a link to a menuhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/938Settings buttons on right side can overlap with labels2023-04-07T20:25:34ZSettings buttons on right side can overlap with labelsReproduced by switching android language to russian
![Screenshot_2021-05-15-08-56-07-764_cx.ring](/uploads/795b5b3747205231c484e26f5252a4dd/Screenshot_2021-05-15-08-56-07-764_cx.ring.jpg)
1. "Share" button hid four letters of the label o...Reproduced by switching android language to russian
![Screenshot_2021-05-15-08-56-07-764_cx.ring](/uploads/795b5b3747205231c484e26f5252a4dd/Screenshot_2021-05-15-08-56-07-764_cx.ring.jpg)
1. "Share" button hid four letters of the label on the left
2. "Register Name" button hid parts of both labels in "register username" field
Together 20210503-01 fdroid, miui 12.0.2, android 10, xiaomi redmi 8https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/937Feature request: change language independent from android2023-07-22T15:08:41ZFeature request: change language independent from androidOption to change the language app is showing even though system language may differ
Benefit: people that are more comfortable with specific language for important apps, but still need english as system language because in many cases som...Option to change the language app is showing even though system language may differ
Benefit: people that are more comfortable with specific language for important apps, but still need english as system language because in many cases some android US settings can't translate good enoughhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/936"This device" shown in all three spots when returned to app2023-04-07T20:25:03Z"This device" shown in all three spots when returned to appReproduce by:
1. Entering jami
2. Clicking "Account" button down right
3. Clicking android's square button that shows all currently running apps
4. Clicking Jami app
Now "registered username" and "identity" get replaced by "this dev...Reproduce by:
1. Entering jami
2. Clicking "Account" button down right
3. Clicking android's square button that shows all currently running apps
4. Clicking Jami app
Now "registered username" and "identity" get replaced by "this device" which makes three identical fields
![Screenshot_2021-05-15-07-40-59-456_cx.ring](/uploads/bed57fd5e8b562b810c93d024089fe43/Screenshot_2021-05-15-07-40-59-456_cx.ring.jpg)
Reproduce steps for seeing normal fields after present reproducing:
1. Click "contact requests"/"conversations"
2. Go back to "account"
together 20210503-01 fdroid, Miui 12.0.2, Android 10, Xiaomi redmi 8https://git.jami.net/savoirfairelinux/jami-project/-/issues/1247Question: Profile picture auto download attack2021-11-19T16:59:05ZQuestion: Profile picture auto download attackexample: one guy has little internet from provider and enabled manual accepting recieved files, but several contacts put their profile images with unreal resolution, or a file which they renamed to *.jpg
question: Do the profile pics ge...example: one guy has little internet from provider and enabled manual accepting recieved files, but several contacts put their profile images with unreal resolution, or a file which they renamed to *.jpg
question: Do the profile pics get downloaded even if manual file accepting is enabled?
additional reason: Because android phones were known for little space (even if sd card is inserted, and additional file can slow down the phone and maybe block recieving sms because of little storage...)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/414Squash ongoing Audio and Video call views2021-05-25T15:47:30ZAline Gondim SantosSquash ongoing Audio and Video call viewsAline Gondim SantosAline Gondim Santos