savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2018-05-21T22:14:14Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/65Wrong IP address in SIP Contact field2018-05-21T22:14:14ZJami BotWrong IP address in SIP Contact fieldIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
I have one laptop connected via Ethernet to a router, and to wifi (different network between Ethernet and wifi).
Ethernet addre...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
I have one laptop connected via Ethernet to a router, and to wifi (different network between Ethernet and wifi).
Ethernet address was 10.10.4.123
Wifi address: 192.168.49.27
I called it from another laptop on the same Wifi network using the Wifi address.
As seen in the wireshark session INVITE is received and answered by a 'Trying' followed by a 'Ringing'.
In the latter, the Contact header is wrong. It contains the ethernet address.
Contact: <sip:10.10.4.123:5060>
Contact URI sip:10.10.4.123:5060
This address is then used as the destination adress. The caller tries to send ACK to that address and got nothing (the caller is on the wifi network, and does not know about Ethernet network)
It's an uncommon issue, but it shows some flaws in our network interface handling
[captureWireshark.pcapng](/uploads/0e69207fea8504afea23be2f168559ab/captureWireshark.pcapng)Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/191Change default ringtone2018-05-22T00:32:31ZJami BotChange default ringtoneIssue generated from Tuleap's migration script.
**Originally submitted by: Cyrille Béraud (cyrille)**
Change default ringtone
Initially 74501\_\_timbre\_\_20335-djgriffin-blipsarp-ringtone-mix-1-wc5000.wav RingDefault.wav
from frees...Issue generated from Tuleap's migration script.
**Originally submitted by: Cyrille Béraud (cyrille)**
Change default ringtone
Initially 74501\_\_timbre\_\_20335-djgriffin-blipsarp-ringtone-mix-1-wc5000.wav RingDefault.wav
from freesound.org
CC licence.
[RingDefault.wav](/uploads/7c65cdc00dbaa9eb1fac02c310c6bf67/RingDefault.wav)Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/401daemon/shm: The first frame (seen by clients) have uninitialized memory [crash]2018-05-21T22:14:49ZJami Botdaemon/shm: The first frame (seen by clients) have uninitialized memory [crash]Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The "size" of the first frame sent from the daemon to LRC to the client contains uninitialized memory when compiled in release m...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The "size" of the first frame sent from the daemon to LRC to the client contains uninitialized memory when compiled in release mode. This cause the size to (often) be a very large int64 value. Using this value in turn will cause invalid memory access when reading the frame, crashing OpenGL.
This doesn't happen in debug mode. Skipping a small bunch of frames always "solve" the issue (tested with 1000 start/stop of the preview).
I made sure the data is initialized in LRC as a test (a good practice anyway), but it will get trashed by the SHM code anyway.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/402daemon: can't seem to output audio to two different devices2018-05-21T22:15:06ZJami Botdaemon: can't seem to output audio to two different devicesIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The clients/lrc seem to be able to correctly set two different devices for output (one for ringtone and a diferent one for in ca...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The clients/lrc seem to be able to correctly set two different devices for output (one for ringtone and a diferent one for in call audio), however the daemon only seems to be able to use one of them.
This seems to get set to whatever the output device is (at least with pulse audio). The daemon logs suggest that the daemon correctly tries to create an audio stream for different devices, but the result is not correct.
This is an issue we seemed to have had for a while, although at some point it possibly worked in sflphone.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/343[lrc] ability of translation missing in `Call::formattedName()`2018-05-25T13:36:52ZJami Bot[lrc] ability of translation missing in `Call::formattedName()`Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Jager (nicolasjager-sfl)**
"error" is returned by `Call::formattedName()` without `tr()`Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Jager (nicolasjager-sfl)**
"error" is returned by `Call::formattedName()` without `tr()`https://git.jami.net/savoirfairelinux/jami-project/-/issues/66[lrc] ability of translation missing in `Call::formattedName()`2018-05-25T13:36:52ZJami Bot[lrc] ability of translation missing in `Call::formattedName()`Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Jager (nicolasjager-sfl)**
"error" is returned by `Call::formattedName()` without `tr()`Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Jager (nicolasjager-sfl)**
"error" is returned by `Call::formattedName()` without `tr()`https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/342lrc: issue during the saving of a new account2018-05-25T13:36:46ZJami Botlrc: issue during the saving of a new accountIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
From: https://gerrit-ring.savoirfairelinux.com/\#/c/3342/2
\* The username field of new RING account wasn't fully validated...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
From: https://gerrit-ring.savoirfairelinux.com/\#/c/3342/2
\* The username field of new RING account wasn't fully validated
\* id() was called before the account is saved, this is invalid
\* The codec model, when saved, set the account back into modified state
There is still some issues to be solved in the future:
\* Saving codecs and credentials before the account id is set wont work
\* The daemon certificate API need an account, it doesn't exist until the account is saved, causing no certificates to be saved
\* The profiles is saved too early and have an empty account ID, this cause an orphan account on the next starthttps://git.jami.net/savoirfairelinux/jami-project/-/issues/67lrc: issue during the saving of a new account2018-05-25T13:36:46ZJami Botlrc: issue during the saving of a new accountIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
From: https://gerrit-ring.savoirfairelinux.com/\#/c/3342/2
\* The username field of new RING account wasn't fully validated...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
From: https://gerrit-ring.savoirfairelinux.com/\#/c/3342/2
\* The username field of new RING account wasn't fully validated
\* id() was called before the account is saved, this is invalid
\* The codec model, when saved, set the account back into modified state
There is still some issues to be solved in the future:
\* Saving codecs and credentials before the account id is set wont work
\* The daemon certificate API need an account, it doesn't exist until the account is saved, causing no certificates to be saved
\* The profiles is saved too early and have an empty account ID, this cause an orphan account on the next starthttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/341lrc: heap-use-after-free detected by ASAN when deleting an account2018-05-25T13:36:42ZJami Botlrc: heap-use-after-free detected by ASAN when deleting an accountIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971==ERROR: AddressSanitizer: heap-use-after-free on address 0x60400031df90 at pc 0x4ebfa9 bp 0x7fffffffc150 sp 0x7fffffffc140
READ of size 4 at 0x60400031df90 thread T0
\#0 0x4ebfa8 in QModelIndex::isValid() const /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64
\#1 0x4ebfa8 in operator() /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:461
\#2 0x4ebfa8 in call /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:494
\#3 0x4ebfa8 in call<QtPrivate::List<const QModelIndex&, const QModelIndex&>, void> /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:551
\#4 0x4ebfa8 in impl /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobject\_impl.h:192
\#5 0x7ffff50db359 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x312359)
\#6 0x7ffff505b099 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x292099)
\#7 0x7ffff50637a9 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29a7a9)
\#8 0x7ffff50652e8 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29c2e8)
\#9 0x7ffff50db9c8 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3129c8)
\#10 0x7ffff51593d3 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3903d3)
\#11 0x7ffff5053589 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28a589)
\#12 0x6023db in AccountModel::remove(Account\*) /home/ssalenikovich/projects/ring-lrc/src/accountmodel.cpp:904
\#13 0x4edb43 in remove\_account /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:282
\#14 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#15 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#16 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#17 0x7ffff674121c (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x10821c)
\#18 0x7ffff6741274 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x108274)
\#19 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#20 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#21 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#22 0x7ffff673f1ff (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1061ff)
\#23 0x7fffee813d8f in ffi\_call\_unix64 (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x5d8f)
\#24 0x7fffee8137f7 in ffi\_call (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x57f7)
\#25 0x7ffff562bf3b in g\_cclosure\_marshal\_generic\_va (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10f3b)
\#26 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#27 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#28 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#29 0x7ffff67e4290 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ab290)
\#30 0x7ffff562e29d in g\_cclosure\_marshal\_VOID\_\_BOXEDv (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x1329d)
\#31 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#32 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#33 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#34 0x7ffff67e187d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a887d)
\#35 0x7ffff67e2cca (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a9cca)
\#36 0x7ffff67e5704 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ac704)
\#37 0x7ffff67b8daa in gtk\_event\_controller\_handle\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x17fdaa)
\#38 0x7ffff6954fdc (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31bfdc)
\#39 0x7ffff6827608 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ee608)
\#40 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#41 0x7ffff5644a4f in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29a4f)
\#42 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#43 0x7ffff69588c3 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31f8c3)
\#44 0x7ffff6824f1d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ebf1d)
\#45 0x7ffff6826b2d in gtk\_main\_do\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1edb2d)
\#46 0x7ffff63c3b41 (/usr/lib/x86\_64-linux-gnu/libgdk-3.so.0+0x50b41)
\#47 0x7ffff5355c3c in g\_main\_context\_dispatch (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49c3c)
\#48 0x7ffff5355f1f (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49f1f)
\#49 0x7ffff5355fcb in g\_main\_context\_iteration (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49fcb)
\#50 0x7ffff591667b in g\_application\_run (/usr/lib/x86\_64-linux-gnu/libgio-2.0.so.0+0xa967b)
\#51 0x4b957f in main /home/ssalenikovich/projects/ring-client-gnome/src/main.cpp:45
\#52 0x7ffff2c14a3f in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a3f)
\#53 0x4b93d8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4b93d8)
0x60400031df90 is located 0 bytes inside of 40-byte region [0x60400031df90,0x60400031dfb8)
freed by thread T0 here:
\#0 0x7ffff6f556af in operator delete(void\*) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x586af)
\#1 0x7ffff505094e in QPersistentModelIndex::operator=(QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28794e)
previously allocated by thread T0 here:
\#0 0x7ffff6f551af in operator new(unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x581af)
\#1 0x7ffff504d485 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x284485)
SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64 QModelIndex::isValid() const
Shadow bytes around the buggy address:
0x0c088005bba0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa
0x0c088005bbb0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 04 fa
0x0c088005bbc0: fa fa fd fd fd fd fd fd fa fa 00 00 00 00 00 fa
0x0c088005bbd0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 02 fa
0x0c088005bbe0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fd
=>0x0c088005bbf0: fa fa[fd]fd fd fd fd fa fa fa fd fd fd fd fd fd
0x0c088005bc00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Contiguous container OOB:fc
ASan internal: fe
==30971==ABORTING
[Thread 0x7fffdba76700 (LWP 30978) exited]
[Thread 0x7ffff7f15a40 (LWP 30971) exited]
[Inferior 1 (process 30971) exited with code 01]https://git.jami.net/savoirfairelinux/jami-project/-/issues/68lrc: heap-use-after-free detected by ASAN when deleting an account2018-05-25T13:36:42ZJami Botlrc: heap-use-after-free detected by ASAN when deleting an accountIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971==ERROR: AddressSanitizer: heap-use-after-free on address 0x60400031df90 at pc 0x4ebfa9 bp 0x7fffffffc150 sp 0x7fffffffc140
READ of size 4 at 0x60400031df90 thread T0
\#0 0x4ebfa8 in QModelIndex::isValid() const /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64
\#1 0x4ebfa8 in operator() /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:461
\#2 0x4ebfa8 in call /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:494
\#3 0x4ebfa8 in call<QtPrivate::List<const QModelIndex&, const QModelIndex&>, void> /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:551
\#4 0x4ebfa8 in impl /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobject\_impl.h:192
\#5 0x7ffff50db359 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x312359)
\#6 0x7ffff505b099 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x292099)
\#7 0x7ffff50637a9 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29a7a9)
\#8 0x7ffff50652e8 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29c2e8)
\#9 0x7ffff50db9c8 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3129c8)
\#10 0x7ffff51593d3 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3903d3)
\#11 0x7ffff5053589 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28a589)
\#12 0x6023db in AccountModel::remove(Account\*) /home/ssalenikovich/projects/ring-lrc/src/accountmodel.cpp:904
\#13 0x4edb43 in remove\_account /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:282
\#14 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#15 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#16 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#17 0x7ffff674121c (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x10821c)
\#18 0x7ffff6741274 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x108274)
\#19 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#20 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#21 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#22 0x7ffff673f1ff (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1061ff)
\#23 0x7fffee813d8f in ffi\_call\_unix64 (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x5d8f)
\#24 0x7fffee8137f7 in ffi\_call (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x57f7)
\#25 0x7ffff562bf3b in g\_cclosure\_marshal\_generic\_va (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10f3b)
\#26 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#27 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#28 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#29 0x7ffff67e4290 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ab290)
\#30 0x7ffff562e29d in g\_cclosure\_marshal\_VOID\_\_BOXEDv (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x1329d)
\#31 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#32 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#33 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#34 0x7ffff67e187d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a887d)
\#35 0x7ffff67e2cca (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a9cca)
\#36 0x7ffff67e5704 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ac704)
\#37 0x7ffff67b8daa in gtk\_event\_controller\_handle\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x17fdaa)
\#38 0x7ffff6954fdc (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31bfdc)
\#39 0x7ffff6827608 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ee608)
\#40 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#41 0x7ffff5644a4f in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29a4f)
\#42 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#43 0x7ffff69588c3 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31f8c3)
\#44 0x7ffff6824f1d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ebf1d)
\#45 0x7ffff6826b2d in gtk\_main\_do\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1edb2d)
\#46 0x7ffff63c3b41 (/usr/lib/x86\_64-linux-gnu/libgdk-3.so.0+0x50b41)
\#47 0x7ffff5355c3c in g\_main\_context\_dispatch (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49c3c)
\#48 0x7ffff5355f1f (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49f1f)
\#49 0x7ffff5355fcb in g\_main\_context\_iteration (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49fcb)
\#50 0x7ffff591667b in g\_application\_run (/usr/lib/x86\_64-linux-gnu/libgio-2.0.so.0+0xa967b)
\#51 0x4b957f in main /home/ssalenikovich/projects/ring-client-gnome/src/main.cpp:45
\#52 0x7ffff2c14a3f in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a3f)
\#53 0x4b93d8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4b93d8)
0x60400031df90 is located 0 bytes inside of 40-byte region [0x60400031df90,0x60400031dfb8)
freed by thread T0 here:
\#0 0x7ffff6f556af in operator delete(void\*) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x586af)
\#1 0x7ffff505094e in QPersistentModelIndex::operator=(QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28794e)
previously allocated by thread T0 here:
\#0 0x7ffff6f551af in operator new(unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x581af)
\#1 0x7ffff504d485 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x284485)
SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64 QModelIndex::isValid() const
Shadow bytes around the buggy address:
0x0c088005bba0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa
0x0c088005bbb0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 04 fa
0x0c088005bbc0: fa fa fd fd fd fd fd fd fa fa 00 00 00 00 00 fa
0x0c088005bbd0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 02 fa
0x0c088005bbe0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fd
=>0x0c088005bbf0: fa fa[fd]fd fd fd fd fa fa fa fd fd fd fd fd fd
0x0c088005bc00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Contiguous container OOB:fc
ASan internal: fe
==30971==ABORTING
[Thread 0x7fffdba76700 (LWP 30978) exited]
[Thread 0x7ffff7f15a40 (LWP 30971) exited]
[Inferior 1 (process 30971) exited with code 01]https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/340lrc: fix warnings2018-05-25T13:36:33ZJami Botlrc: fix warningsIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it....Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it... This is distracting and makes it harder to see errors as well as notice when a new patch introduces new warnings thus potentially reducing code quality.
These warnings should be removed as much as possible, especially the ones easy to fix.https://git.jami.net/savoirfairelinux/jami-project/-/issues/69lrc: fix warnings2018-05-25T13:36:33ZJami Botlrc: fix warningsIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it....Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it... This is distracting and makes it harder to see errors as well as notice when a new patch introduces new warnings thus potentially reducing code quality.
These warnings should be removed as much as possible, especially the ones easy to fix.https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/339LRC: AccountModel "cancel" action is broken2018-05-25T13:36:29ZJami BotLRC: AccountModel "cancel" action is brokenIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model stateIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model statehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/70LRC: AccountModel "cancel" action is broken2018-05-25T13:36:29ZJami BotLRC: AccountModel "cancel" action is brokenIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model stateIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model statehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/71Gnome client segfaults (in libringclient) at launch2018-05-21T22:16:59ZJami BotGnome client segfaults (in libringclient) at launchIssue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
When launching gnome-ring on Linux, it segfaults immediately. This didn't happen a few days ago and seems related to a date, is th...Issue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
When launching gnome-ring on Linux, it segfaults immediately. This didn't happen a few days ago and seems related to a date, is this the new y2k bug? :)
I am using libringclient version c6fc97a4b6e3baea116ec6ce122a73c3ac5af337 and gnome-ring version bd4b37702bb34dee98faa41489dcf98d403d2197. Below is the backtrace provided by gdb:
\~$ gdb gnome-ring
GNU gdb (GDB) 7.10.1
Reading symbols from gnome-ring...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/gnome-ring
[Thread debugging using libthread\_db enabled]
Using host libthread\_db library "/usr/lib/libthread\_db.so.1".
[New Thread 0x7fffe3c99700 (LWP 6694)]
[New Thread 0x7fffe3309700 (LWP 6695)]
[New Thread 0x7fffe2b08700 (LWP 6696)]
\*\* Message: Ring GNOME client version: 0.4.0
\*\* Message: git ref: bd4b37702bb34dee98faa41489dcf98d403d2197
Updating all accounts
Loading "32a968c6894c1912"
[New Thread 0x7fffd3fff700 (LWP 6697)]
[Thread 0x7fffd3fff700 (LWP 6697) exited]
QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>)
Account parameter " "Account.presenceSubscribeSupported" " not found
Loading "IP2IP"
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a99193 in HistoryTimeCategoryModel::indexToName(int) () from /usr/lib/libringclient.so.0.4.0
(gdb) bt
\#0 0x00007ffff7a99193 in HistoryTimeCategoryModel::indexToName(int) () from /usr/lib/libringclient.so.0.4.0
\#1 0x00007ffff7a70d4a in CategorizedHistoryModelPrivate::getCategory(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#2 0x00007ffff7a723a6 in CategorizedHistoryModelPrivate::add(Call\*) () from /usr/lib/libringclient.so.0.4.0
\#3 0x00007ffff7a7270d in CategorizedHistoryModel::addItemCallback(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#4 0x00007ffff7b04279 in LocalHistoryEditor::addExisting(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#5 0x00007ffff7b07643 in LocalHistoryCollection::load() () from /usr/lib/libringclient.so.0.4.0
\#6 0x0000000000427ba9 in LocalHistoryCollection\* CollectionManagerInterface<Call>::addCollection<LocalHistoryCollection>(, LoadOptions) ()
\#7 0x0000000000425b46 in ?? ()
\#8 0x00007ffff5fcc244 in ?? () from /usr/lib/libgobject-2.0.so.0
\#9 0x00007ffff5fe6a46 in g\_signal\_emit\_valist () from /usr/lib/libgobject-2.0.so.0
\#10 0x00007ffff5fe712f in g\_signal\_emit () from /usr/lib/libgobject-2.0.so.0
\#11 0x00007ffff62b6d92 in g\_application\_register () from /usr/lib/libgio-2.0.so.0
\#12 0x00007ffff62b7517 in ?? () from /usr/lib/libgio-2.0.so.0
\#13 0x00007ffff62b785a in g\_application\_run () from /usr/lib/libgio-2.0.so.0
\#14 0x00007ffff3d1e610 in \_\_libc\_start\_main () from /usr/lib/libc.so.6
\#15 0x00000000004249f9 in \_start ()
[0001-history-Fix-segfault-when-fuzzy-dates-span-two-disti.patch](/uploads/61e7415665a0f2d76fe6bc66c80fbe0d/0001-history-Fix-segfault-when-fuzzy-dates-span-two-disti.patch)https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/338New year crash in LRC2018-05-25T13:36:24ZJami BotNew year crash in LRCIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to a version based on my old code but including the changes introduced by the rewrite.
It is faster anyway. In my opinion, it is also clear and simple and don't depend on 3rd party APIs at all, just plain C and decimal logichttps://git.jami.net/savoirfairelinux/jami-project/-/issues/72New year crash in LRC2018-05-25T13:36:24ZJami BotNew year crash in LRCIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to a version based on my old code but including the changes introduced by the rewrite.
It is faster anyway. In my opinion, it is also clear and simple and don't depend on 3rd party APIs at all, just plain C and decimal logichttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/337lrc: wrong or missing audio device selection in certain cases2018-05-25T13:36:13ZJami Botlrc: wrong or missing audio device selection in certain casesIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems to be because the device selection for each driver is not individually stored nor checked against what is selected in the daemon.https://git.jami.net/savoirfairelinux/jami-project/-/issues/73lrc: wrong or missing audio device selection in certain cases2018-05-25T13:36:13ZJami Botlrc: wrong or missing audio device selection in certain casesIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems to be because the device selection for each driver is not individually stored nor checked against what is selected in the daemon.https://git.jami.net/savoirfairelinux/jami-project/-/issues/192Mispelling of Savoir-faire Linux2018-05-22T00:32:32ZJami BotMispelling of Savoir-faire LinuxIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
<p>In many place in code <strong>Savoir-faire Linux</strong> is not correctly written: it's a minus 'f'.</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
<p>In many place in code <strong>Savoir-faire Linux</strong> is not correctly written: it's a minus 'f'.</p>