savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2018-05-25T13:36:57Zhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/344LRC: Add more metadata to text recordings2018-05-25T13:36:57ZJami BotLRC: Add more metadata to text recordingsIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
With the increased use of text messaging (not with offline one), manipulating TextRecording object is now more and more common. ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
With the increased use of text messaging (not with offline one), manipulating TextRecording object is now more and more common. Such new features need easy access to various metadata collected by the recording, but not currently easily exposed. The most pressing one is knowing if the recording contains relevant payloads. Some TextRecording may only contain "invisible" MIME payloads. In those case, raising the text widget and sending notifications is only spamming the user.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/48missing call to callFailure in timeout case2022-11-14T21:52:32ZHugo Lefeuvremissing call to callFailure in timeout caseIntroduced in 9a12c78a.
In the case where call timeout is reached, the daemon calls hangup(486), terminating the call. However this hangup call is not followed by any kind of callFailure() call meaning that the tone and media states in ...Introduced in 9a12c78a.
In the case where call timeout is reached, the daemon calls hangup(486), terminating the call. However this hangup call is not followed by any kind of callFailure() call meaning that the tone and media states in the manager will not be reinitialized. As a consequence the daemon will continue to ring even if the call has ended.
Should be fixed asap.Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/77daemon/lrc: bizzare call state transitions when call fails immediately2018-05-25T13:36:07ZJami Botdaemon/lrc: bizzare call state transitions when call fails immediatelyIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
lrc log:
Creating the call to "ring" failed
Calling action ACCEPT (0) on Call(0x603000b18aa0) with state "Dialing" . Become "Failed"
Call State Changed for call "15222503668050492823" . New state : "FAILURE"
Call not found "15222503668050492823" new state "FAILURE"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
Call State Changed for call "15222503668050492823" . New state : "OVER"
Call not found "15222503668050492823" new state "OVER"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
State changing from "Failed" to "Over" on Call(0x603000b18aa0)
Cannot remove Call(0x603000b18aa0) : call not found in tree
Calling action REFUSE (1) on Call(0x603000b18aa0) with state "Failed" . Become "Over"https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/418gnome: copying name or number in the history view results in ASAN use after f...2018-05-21T22:53:43ZJami Botgnome: copying name or number in the history view results in ASAN use after free detectionIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>=================================================================<br />
==13413==ERROR: AddressSanitizer: heap-use-after-fr...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>=================================================================<br />
==13413==ERROR: AddressSanitizer: heap-use-after-free on address 0x606000acd558 at pc 0x7ffff6ed966b bp 0x7fffffffd130 sp 0x7fffffffc8d8<br />
READ of size 18 at 0x606000acd558 thread T0<br />
\#0 0x7ffff6ed966a in \_\_interceptor\_strlen (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x7066a)<br />
\#1 0x7ffff68e3137 in gtk\_clipboard\_set\_text (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x36a137)<br />
\#2 0x510f07 in copy\_number /home/ssalenikovich/projects/ring-client-gnome/src/historyview.cpp:168<br />
\#3 0x7ffff555e014 in g\_closure\_invoke (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10014)<br />
\#4 0x7ffff5570060 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x22060)<br />
\#5 0x7ffff5578dfb in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2adfb)<br />
\#6 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#7 0x7ffff68bb29d in gtk\_widget\_activate (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x34229d)<br />
\#8 0x7ffff67a0735 in gtk\_menu\_shell\_activate\_item (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x227735)<br />
\#9 0x7ffff67a0a63 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x227a63)<br />
\#10 0x7ffff6782379 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x209379)<br />
\#11 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)<br />
\#12 0x7ffff5578557 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a557)<br />
\#13 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#14 0x7ffff68bc283 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x343283)<br />
\#15 0x7ffff677f81d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x20681d)<br />
\#16 0x7ffff67814cd in gtk\_main\_do\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x2084cd)<br />
\#17 0x7ffff62fd321 (/usr/lib/x86\_64-linux-gnu/libgdk-3.so.0+0x58321)<br />
\#18 0x7ffff5288ff6 in g\_main\_context\_dispatch (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49ff6)<br />
\#19 0x7ffff528924f (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x4a24f)<br />
\#20 0x7ffff52892fb in g\_main\_context\_iteration (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x4a2fb)<br />
\#21 0x7ffff584aafb in g\_application\_run (/usr/lib/x86\_64-linux-gnu/libgio-2.0.so.0+0xa9afb)<br />
\#22 0x4bcbf3 in main /home/ssalenikovich/projects/ring-client-gnome/src/main.cpp:34<br />
\#23 0x7ffff2af5a3f in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a3f)<br />
\#24 0x4bca48 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4bca48)</p>
<p>0x606000acd558 is located 24 bytes inside of 64-byte region [0x606000acd540,0x606000acd580)<br />
freed by thread T0 here:<br />
\#0 0x7ffff6f016aa in \_\_interceptor\_free (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x986aa)<br />
\#1 0x510e96 in QTypedArrayData<char>::deallocate(QArrayData\*) /usr/include/x86\_64-linux-gnu/qt5/QtCore/qarraydata.h:222<br />
\#2 0x510e96 in QByteArray::\~QByteArray() /usr/include/x86\_64-linux-gnu/qt5/QtCore/qbytearray.h:431<br />
\#3 0x510e96 in copy\_number /home/ssalenikovich/projects/ring-client-gnome/src/historyview.cpp:167<br />
\#4 0x7ffff555e014 in g\_closure\_invoke (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10014)</p>
<p>previously allocated by thread T0 here:<br />
\#0 0x7ffff6f01d2a in realloc (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x98d2a)<br />
\#1 0x7ffff37e619a in QByteArray::reallocData(unsigned int, QFlags<QArrayData::AllocationOption>) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0xa619a)<br />
\#2 0x7ffff527747a (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x3847a)</p>
<p>SUMMARY: AddressSanitizer: heap-use-after-free ??:0 \_\_interceptor\_strlen<br />
Shadow bytes around the buggy address:<br />
0x0c0c80151a50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa<br />
0x0c0c80151a60: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa<br />
0x0c0c80151a70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa<br />
0x0c0c80151a80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa<br />
0x0c0c80151a90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa<br />
=>0x0c0c80151aa0: fa fa fa fa fa fa fa fa fd fd fd[fd]fd fd fd fd<br />
0x0c0c80151ab0: fa fa fa fa 00 00 00 00 00 00 00 fa fa fa fa fa<br />
0x0c0c80151ac0: 00 00 00 00 00 00 00 00 fa fa fa fa 00 00 00 00<br />
0x0c0c80151ad0: 00 00 00 00 fa fa fa fa fd fd fd fd fd fd fd fa<br />
0x0c0c80151ae0: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa<br />
0x0c0c80151af0: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd<br />
Shadow byte legend (one shadow byte represents 8 application bytes):<br />
Addressable: 00<br />
Partially addressable: 01 02 03 04 05 06 07<br />
Heap left redzone: fa<br />
Heap right redzone: fb<br />
Freed heap region: fd<br />
Stack left redzone: f1<br />
Stack mid redzone: f2<br />
Stack right redzone: f3<br />
Stack partial redzone: f4<br />
Stack after return: f5<br />
Stack use after scope: f8<br />
Global redzone: f9<br />
Global init order: f6<br />
Poisoned by user: f7<br />
Container overflow: fc<br />
Array cookie: ac<br />
Intra object redzone: bb<br />
ASan internal: fe<br />
==13413==ABORTING</p>
<p> </p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/265multi-arch: second arch copied twice in project2018-05-21T23:42:16ZJami Botmulti-arch: second arch copied twice in projectIssue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>The second compiled architecture is present two times in src/main/libs.</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>The second compiled architecture is present two times in src/main/libs.</p>https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/136MAC: Incorrect ringtone2018-05-22T00:35:09ZJami BotMAC: Incorrect ringtoneIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Ring-tone in mac version the same as call sound.
version 10.11.2016Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Ring-tone in mac version the same as call sound.
version 10.11.2016https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/345[LRC] Add finer date and time related roles to calls2018-05-25T13:37:02ZJami Bot[LRC] Add finer date and time related roles to callsIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
I made a new proxy model that deduplicate/merge QModelIndex when a role is identical. So I used the displayname, but for categor...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
I made a new proxy model that deduplicate/merge QModelIndex when a role is identical. So I used the displayname, but for categories like "last year", it is strange to see 2 calls from 2 different months being merged. So I need to add a second role for "do not merge if the day is different" but LRC have no such role
I also noticed formattedDate could be better cached as it is called quite a lot be the viewhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/49daemon crashes when receiving a SIP or Ring call when display name has a colo...2021-12-07T18:13:27ZAndreas Traczykdaemon crashes when receiving a SIP or Ring call when display name has a colon or chevron in itAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/78daemon: SIP out of call messages don't work2018-05-21T22:21:09ZJami Botdaemon: SIP out of call messages don't workIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
Confirmed by testing. The message is "sent"; however the SIP server returns a "401 Unauthorized" status which seems to be due to...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
Confirmed by testing. The message is "sent"; however the SIP server returns a "401 Unauthorized" status which seems to be due to the fact that we did not do a publish/subrscribe.
This is a bug (or missing feature) in the deamon; however the gnome/osx/win clients currently allow the user to send an out of call text via a SIP account, but it is not very likely to every work.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/419gnome: deleting an account results in ASAN heap-use-after-free detection2018-05-21T22:53:52ZJami Botgnome: deleting an account results in ASAN heap-use-after-free detectionIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Removing &quot;New Account&quot; &quot;ba6584f1a7caa8e2&quot;<br />
[New Thread 0x7fffcdcd3700 (LWP 22903)]<br />
=======...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Removing "New Account" "ba6584f1a7caa8e2"<br />
[New Thread 0x7fffcdcd3700 (LWP 22903)]<br />
=================================================================<br />
==22088==ERROR: AddressSanitizer: heap-use-after-free on address 0x604000023a50 at pc 0x0000004eac8f bp 0x7fffffffbda0 sp 0x7fffffffbd90<br />
READ of size 4 at 0x604000023a50 thread T0<br />
\#0 0x4eac8e in QModelIndex::isValid() const /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64<br />
\#1 0x4eac8e in operator() /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:458<br />
\#2 0x4eac8e in call /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:494<br />
\#3 0x4eac8e in call<QtPrivate::List<const QModelIndex&, const QModelIndex&>, void> /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:551<br />
\#4 0x4eac8e in impl /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobject\_impl.h:192<br />
\#5 0x7ffff39f2616 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x2b2616)<br />
\#6 0x7ffff39732a9 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x2332a9)<br />
\#7 0x7ffff397b47c (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x23b47c)<br />
\#8 0x7ffff397bec8 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x23bec8)<br />
\#9 0x7ffff39f2789 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x2b2789)<br />
\#10 0x7ffff3a698e3 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3298e3)<br />
\#11 0x7ffff396a642 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x22a642)<br />
\#12 0x5f49dc in AccountModel::remove(Account\*) /home/ssalenikovich/projects/ring-lrc/src/accountmodel.cpp:932<br />
\#13 0x4ec91e in remove\_account /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:273<br />
\#14 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)<br />
\#15 0x7ffff5578a45 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2aa45)<br />
\#16 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#17 0x7ffff66953fc (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x11c3fc)<br />
\#18 0x7ffff6695464 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x11c464)<br />
\#19 0x7ffff555e014 in g\_closure\_invoke (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10014)<br />
\#20 0x7ffff556fb9b (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x21b9b)<br />
\#21 0x7ffff5578dfb in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2adfb)<br />
\#22 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#23 0x7ffff66934ef (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x11a4ef)<br />
\#24 0x7fffee1f0d8f in ffi\_call\_unix64 (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x5d8f)<br />
\#25 0x7fffee1f07f7 in ffi\_call (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x57f7)<br />
\#26 0x7ffff555ed64 in g\_cclosure\_marshal\_generic\_va (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10d64)<br />
\#27 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)<br />
\#28 0x7ffff5578a45 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2aa45)<br />
\#29 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#30 0x7ffff673c090 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1c3090)<br />
\#31 0x7ffff5560e2d in g\_cclosure\_marshal\_VOID\_\_BOXEDv (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x12e2d)<br />
\#32 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)<br />
\#33 0x7ffff5578a45 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2aa45)<br />
\#34 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#35 0x7ffff67396ad (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1c06ad)<br />
\#36 0x7ffff673aafa (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1c1afa)<br />
\#37 0x7ffff673d534 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1c4534)<br />
\#38 0x7ffff671025a in gtk\_event\_controller\_handle\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x19725a)<br />
\#39 0x7ffff68b896c (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x33f96c)<br />
\#40 0x7ffff6782379 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x209379)<br />
\#41 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)<br />
\#42 0x7ffff5578557 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a557)<br />
\#43 0x7ffff557912e in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2b12e)<br />
\#44 0x7ffff68bc283 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x343283)<br />
\#45 0x7ffff677f81d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x20681d)<br />
\#46 0x7ffff67814cd in gtk\_main\_do\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x2084cd)<br />
\#47 0x7ffff62fd321 (/usr/lib/x86\_64-linux-gnu/libgdk-3.so.0+0x58321)<br />
\#48 0x7ffff5288ff6 in g\_main\_context\_dispatch (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49ff6)<br />
\#49 0x7ffff528924f (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x4a24f)<br />
\#50 0x7ffff52892fb in g\_main\_context\_iteration (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x4a2fb)<br />
\#51 0x7ffff584aafb in g\_application\_run (/usr/lib/x86\_64-linux-gnu/libgio-2.0.so.0+0xa9afb)<br />
\#52 0x4bcb93 in main /home/ssalenikovich/projects/ring-client-gnome/src/main.cpp:34<br />
\#53 0x7ffff2af5a3f in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a3f)<br />
\#54 0x4bc9e8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4bc9e8)</p>
<p>0x604000023a50 is located 0 bytes inside of 40-byte region [0x604000023a50,0x604000023a78)<br />
freed by thread T0 here:<br />
\#0 0x7ffff6f02eaa in operator delete(void\*) (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x99eaa)<br />
\#1 0x7ffff39695ce in QPersistentModelIndex::operator=(QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x2295ce)</p>
<p>previously allocated by thread T0 here:<br />
\#0 0x7ffff6f028b2 in operator new(unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x998b2)<br />
\#1 0x7ffff3966791 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x226791)</p>
<p>SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64 QModelIndex::isValid() const<br />
Shadow bytes around the buggy address:<br />
0x0c087fffc6f0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa<br />
0x0c087fffc700: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa<br />
0x0c087fffc710: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa<br />
0x0c087fffc720: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fa<br />
0x0c087fffc730: fa fa 00 00 00 00 04 fa fa fa fd fd fd fd fd fd<br />
=>0x0c087fffc740: fa fa fd fd fd fd fd fd fa fa[fd]fd fd fd fd fa<br />
0x0c087fffc750: fa fa fd fd fd fd fd fd fa fa 00 00 00 00 00 04<br />
0x0c087fffc760: fa fa fd fd fd fd fd fd fa fa fd fd fd fd fd fa<br />
0x0c087fffc770: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fd<br />
0x0c087fffc780: fa fa 00 00 00 00 05 fa fa fa fd fd fd fd fd fa<br />
0x0c087fffc790: fa fa 00 00 00 00 00 fa fa fa fd fd fd fd fd fd<br />
Shadow byte legend (one shadow byte represents 8 application bytes):<br />
Addressable: 00<br />
Partially addressable: 01 02 03 04 05 06 07<br />
Heap left redzone: fa<br />
Heap right redzone: fb<br />
Freed heap region: fd<br />
Stack left redzone: f1<br />
Stack mid redzone: f2<br />
Stack right redzone: f3<br />
Stack partial redzone: f4<br />
Stack after return: f5<br />
Stack use after scope: f8<br />
Global redzone: f9<br />
Global init order: f6<br />
Poisoned by user: f7<br />
Container overflow: fc<br />
Array cookie: ac<br />
Intra object redzone: bb<br />
ASan internal: fe<br />
==22088==ABORTING</p>
<p> </p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/266Failure to connect Android->desktop, from public WiFi to desktop behind firewall2020-06-19T18:08:05ZJami BotFailure to connect Android->desktop, from public WiFi to desktop behind firewallIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
<p>I am trying to communicate between the Ring Android app on the public WiFi and desktop Ring app running behind firewall without UPnP. Commun...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
<p>I am trying to communicate between the Ring Android app on the public WiFi and desktop Ring app running behind firewall without UPnP. Communication fails completely.</p>
<p> </p>
<p>I tried both desktop Windows app and FreeBSD ring-gnome port.</p>
<p>Communication between Android app and ring-gnome succeeds when on the same LAN.</p>
<p> </p>
<p>What might be a problem? Is it that firewall doesn't have UPnP enabled? I think every time the app asks for UPnP there should be an alternative to manually enter the port forward on firewall.</p>
<p> </p>
<p>Additionally, Android app doesn't clearly say that the text message failed. It first says "Sending mesage ...", and then just shows the time of the message as if it has been sent.</p>
<p> </p>https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/137Add QR Code to Mac OSX app2018-05-22T00:35:26ZJami BotAdd QR Code to Mac OSX appIssue generated from Tuleap's migration script.
**Originally submitted by: Teutone Dreizehn (teutone)**
<p>Would be nice to be able to share the Ring-ID via QR Code within the Mac OS app as well</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Teutone Dreizehn (teutone)**
<p>Would be nice to be able to share the Ring-ID via QR Code within the Mac OS app as well</p>https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/346[LRC] Some variants of history sorting are broken2018-05-25T13:37:07ZJami Bot[LRC] Some variants of history sorting are brokenIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
Many categories that should be sorted by integer IDs are sorted by their string representation
One of the bug was "always" ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
Many categories that should be sorted by integer IDs are sorted by their string representation
One of the bug was "always" there while the other one was introduced in the history model rewrite earlier this yearhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/79Crash when loading text message sent with no longer existing account2018-05-21T22:21:27ZJami BotCrash when loading text message sent with no longer existing accountIssue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
- Send text message with your account
- Suppress the account
- Re-Create an account
- Load an ancient conversation
- Crash
-...Issue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
- Send text message with your account
- Suppress the account
- Re-Create an account
- Load an ancient conversation
- Crash
- Potentially any platform that use Qt::DecorationRolehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/420v4l2: crash when a camera has no channel2018-05-21T22:59:18ZJami Botv4l2: crash when a camera has no channelIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/267smartlist: search does not support special characters2018-05-21T23:43:33ZJami Botsmartlist: search does not support special charactersIssue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>As a user, when I perform a search in the smartlist, the engine does not support the special characters.</p>
<p>Example: Ga&euml;...Issue generated from Tuleap's migration script.
**Originally submitted by: Romain B. (rbertozzi)**
<p>As a user, when I perform a search in the smartlist, the engine does not support the special characters.</p>
<p>Example: Gaël does not match Gael.</p>https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/138[OSX] blockchain name should be displayed instead of ringID2018-05-22T00:35:45ZJami Bot[OSX] blockchain name should be displayed instead of ringIDIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
In the conversation screen we should see the blockchain name when available, not the ringIDIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
In the conversation screen we should see the blockchain name when available, not the ringIDhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/347[LRC] Implement DecorationRole for all relevant objects roleData()2018-05-25T13:37:11ZJami Bot[LRC] Implement DecorationRole for all relevant objects roleData()Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
Currently,some models have DecorationRole (icons), but some others need to dereference the object and play with the pixmapmanipu...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
Currently,some models have DecorationRole (icons), but some others need to dereference the object and play with the pixmapmanipulationinterface to get them.
While dealing with icons is tricky because the actual icon "object" is dependant on the GUI toolkit (GDK pixmaps or Cairo surfaces for GTK, QIcon for Qt, etc), the API should at least be consistent on how this is handled. For now, there is no coherent way for "dumb" model bindings to display icons.
For the KDE and Windows client, Qt5 offer the QIconEngine() class that allow to create resolution independant icons.
The reason why this wasn't done sooner was the lack of "proper" research on how to handle resolution independence. After further investigation, it is not really an issue at all and can totally be implemented.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/51Crash during ICE negotiation2021-12-07T18:13:27ZPhilippe GorleyCrash during ICE negotiationThere is a crash during the ICE negotiation. It seems to happen at random (while connecting to a peer, while switching inputs to share the screen/stream a file).
I get it fairly often between my two Ubuntu 18.04 PCs. Attached is a backt...There is a crash during the ICE negotiation. It seems to happen at random (while connecting to a peer, while switching inputs to share the screen/stream a file).
I get it fairly often between my two Ubuntu 18.04 PCs. Attached is a backtrace of all threads during the crash.
[pj_bt_all_threads.txt](/uploads/1e3ac597e9582ea4d42756bc7cc13115/pj_bt_all_threads.txt)Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/276Unable to record a conference call2020-09-10T18:43:09ZCyrille BéraudUnable to record a conference callRecord stops as soon I add a participant to a conferenceRecord stops as soon I add a participant to a conferenceItération 21Pierre LespagnolMohamed ChibaniPierre Lespagnol