jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2018-05-25T13:36:46Zhttps://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-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-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-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/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/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-project/-/issues/81LRC: own ContactMethod appears in RecentModel2018-05-25T13:36:02ZJami BotLRC: own ContactMethod appears in RecentModelIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
This seems to happen sometimes when a call immediately fails, or is hung up before it is answered by the peer... though not 100%...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
This seems to happen sometimes when a call immediately fails, or is hung up before it is answered by the peer... though not 100% sure how to reproduce.
The result is that the user's own RingID appears in the RecentModel, though it is appended by "@bootrstrap.ring.cx"
Another weird thing is that sometimes when sending a text message to someone else, the user's RingID in the recent model will jump to the top (ie: its lastUsed is updated).https://git.jami.net/savoirfairelinux/jami-project/-/issues/84LRC: chat with CMs which have not been called / are not contacts are missing ...2018-05-25T13:35:36ZJami BotLRC: chat with CMs which have not been called / are not contacts are missing from the RecentModel after restarting RingIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
This is because the RecentModel and the PhoneDirectoryModel are constructed from the call history and contact backend(s). CMs wh...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
This is because the RecentModel and the PhoneDirectoryModel are constructed from the call history and contact backend(s). CMs which only have a chat history are "lost" after the user quits Ring.
A possible solution is to force a load of all the chat conversations when Ring first starts to recover all the CMs which only have a chat history.https://git.jami.net/savoirfairelinux/jami-project/-/issues/85lrc: peer name data from Call is not set in ContactMethod at run time2018-05-25T13:34:35ZJami Botlrc: peer name data from Call is not set in ContactMethod at run timeIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
During a (incoming) call, the display name (SIP data) is used to set the peerName in the Call object... however this does not se...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
During a (incoming) call, the display name (SIP data) is used to set the peerName in the Call object... however this does not seem to get set in the ContactMethod until Ring is restarted. The result is that the RecentModel view continues to show the uri of the CM, even when the call shows the display name, until the user restarts Ring.https://git.jami.net/savoirfairelinux/jami-project/-/issues/86[LRC] adding ContactMethod to Contact sometimes creates a new CM and so both ...2018-05-25T13:34:18ZJami Bot[LRC] adding ContactMethod to Contact sometimes creates a new CM and so both are shown in the RecentModelIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
DESCRIPTION
Adding a contact from a conversation entry (right click>add to contact) creates seperate conversation entry.
EXPE...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
DESCRIPTION
Adding a contact from a conversation entry (right click>add to contact) creates seperate conversation entry.
EXPECTED BEHAVIOR
Conversation entry should merge with newly created contact.
NOTE
The same is observed when adding contacts manually through gnome-contacts application.
![sshot0](/uploads/84d43fe685956fdce6c2680747e35aa1/sshot0.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/90LRC: ASAN detects "new-delete-type-mismatch" on quitting the client2018-05-25T13:33:47ZJami BotLRC: ASAN detects "new-delete-type-mismatch" on quitting the clientIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Seems to be systematic since the current master. Not sure if it is unique to the GNOME client or not, so marking it as an LRC...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Seems to be systematic since the current master. Not sure if it is unique to the GNOME client or not, so marking it as an LRC issue...</p>
<p>\*\* (gnome-ring:19273): DEBUG: quitting<br />
=================================================================<br />
==19273==ERROR: AddressSanitizer: new-delete-type-mismatch on 0x6020001a4e10 in thread T0:<br />
object passed to delete has wrong type:<br />
size of the allocated type: 16 bytes;<br />
size of the deallocated type: 8 bytes.<br />
\#0 0x7ffff6f034b2 in operator delete(void\*, unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.2+0x9a4b2)<br />
\#1 0x62511d in std::unique\_ptr<GlobalInstances::InstanceManager, std::default\_delete<GlobalInstances::InstanceManager> >::\~unique\_ptr() (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x62511d)<br />
\#2 0x7ffff2b0ed31 (/lib/x86\_64-linux-gnu/libc.so.6+0x39d31)<br />
\#3 0x7ffff2b0ed84 in exit (/lib/x86\_64-linux-gnu/libc.so.6+0x39d84)<br />
\#4 0x7ffff2af5a46 in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a46)<br />
\#5 0x4b3ff8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4b3ff8)</p>
<p>0x6020001a4e10 is located 0 bytes inside of 16-byte region [0x6020001a4e10,0x6020001a4e20)<br />
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 0x4b5e1a in ring\_client\_startup /home/ssalenikovich/projects/ring-client-gnome/src/ring\_client.cpp:306<br />
\#2 0x7ffff555e243 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10243)</p>
<p>SUMMARY: AddressSanitizer: new-delete-type-mismatch ??:0 operator delete(void\*, unsigned long)<br />
==19273==HINT: if you don't care about these warnings you may set ASAN\_OPTIONS=new\_delete\_type\_mismatch=0<br />
==19273==ABORTING<br />
[Thread 0x7fffd5e38700 (LWP 19284) exited]<br />
[Thread 0x7fffd6a94700 (LWP 19283) exited]<br />
[Thread 0x7fffe0922700 (LWP 19276) exited]<br />
[Thread 0x7fffe1123700 (LWP 19275) exited]<br />
[Thread 0x7fffe1bf2700 (LWP 19274) exited]<br />
[Thread 0x7ffff7e71ac0 (LWP 19273) exited]<br />
[Inferior 1 (process 19273) exited with code 01]</p>
<p> </p>
<p> </p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/93LRC leak like hell2018-05-25T13:33:39ZJami BotLRC leak like hellIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
<p>(but mostly on quit)</p>
<p>&nbsp;</p>
<p>Since the KDE CI is no longer used to run intergration, there is tons of ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
<p>(but mostly on quit)</p>
<p> </p>
<p>Since the KDE CI is no longer used to run intergration, there is tons of leaks that have been introduced. Most commits since \~december 2014 have at least 1 leak. Again, most of those are on quit, so it is not "really" a problem "in the real world". But then, a side effect of this is that some important destructor are not executed, causing issues.</p>
<p> </p>
<p>I try to get LRC to run on low memory (128mb) again and resurect the mobile port. So I need my memory back. At some point it was fully leak free, but the accelerated development pace had its nasty side effects.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/104LRC: empty historic doesnt really work anymore2018-05-25T13:33:09ZJami BotLRC: empty historic doesnt really work anymoreIssue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
As we are now loading all text messages and insering them when we empty history all contact with text messages will still be loaded.
...Issue generated from Tuleap's migration script.
**Originally submitted by: Edric Milaret (edric)**
As we are now loading all text messages and insering them when we empty history all contact with text messages will still be loaded.
I propose that we delete all history of text messages tooAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/108LRC: QObject::connect: No such signal ConfigurationManagerInterface::incoming...2018-05-25T13:33:02ZJami BotLRC: QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>) messageIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>gnome client during runtime give the following message from qt:</p>
<p>QObject::connect: No such signal ConfigurationMan...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>gnome client during runtime give the following message from qt:</p>
<p>QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>)</p>
<p>from phonedirectorymodel.cpp:57</p>
<p>seems to be due to using the QMap<QString, QString> instead of the MapStringString typedef in the signal signature</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/131multiple cameras are not correctly tracked2018-05-25T13:32:41ZJami Botmultiple cameras are not correctly trackedIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When plugging and unplugging multiple cameras, the interface does not always correctly display which camera has been unplugge...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When plugging and unplugging multiple cameras, the interface does not always correctly display which camera has been unplugged and which camera is currently selected.</p>
<p>eg:</p>
<ol>
<li>plugged in are cameras: (a,b,c); interface dsiplays cameras: (a,b,c)</li>
<li>user unplugs camera a</li>
<li>interfaces displays cameras: (a,b)</li>
</ol>
<p>This is reproducible easily in the gnome client. Needs to be investigated whether it is an lrc or a daemon issue.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/132cannot change camera in settings after making a call (without saving)2018-05-25T13:32:33ZJami Botcannot change camera in settings after making a call (without saving)Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When first launching (gnome) Ring, going into the media settings and selecting a different camera changes the camera immediat...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When first launching (gnome) Ring, going into the media settings and selecting a different camera changes the camera immediately. After making a call, this is no longer the case. The user is then required to first save the settings to see the effect of changing the camera.</p>
<p>This is likely either a client or lrc bug.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/143LRC: contacs with a ringID are filtered even when a RING account exists2018-05-25T13:31:42ZJami BotLRC: contacs with a ringID are filtered even when a RING account existsIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Person objects with Ring ContactMethods are filtered in CategorizedContactModel even when a RING account exists. This is now ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>Person objects with Ring ContactMethods are filtered in CategorizedContactModel even when a RING account exists. This is now especially visible since the IP2IP account is no longer required nor created by default.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/158clients/lrc: remove SSLv3 as encryption choice2018-05-25T12:53:35ZJami Botclients/lrc: remove SSLv3 as encryption choiceIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>SSLv3 was overdue to be removed from the daemon and this is being done now. It should be removed from all clients/lrc as an e...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>SSLv3 was overdue to be removed from the daemon and this is being done now. It should be removed from all clients/lrc as an encryption choice (fyi it was not showing up in the UI of clients using lrc as there is an off by one error in the model code)</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/159lrc: RecentModel loses selection when a CM is turned into a contact2018-05-25T12:53:31ZJami Botlrc: RecentModel loses selection when a CM is turned into a contactIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When a newcontact calls for the first time, the automatic selection of the call in the RecentModel is often lost. This is bec...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When a newcontact calls for the first time, the automatic selection of the call in the RecentModel is often lost. This is because first a CM is created in the RecentModel. Then, when the profile is transfered, that CM is replaced by a Person. There is a bug in the RecentModel code which causes this new Person to not be selected.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/181LRC - UserActionModel state is not properly updated for new outgoing call2018-05-25T12:53:26ZJami BotLRC - UserActionModel state is not properly updated for new outgoing callIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update the states of the actions. It seems this is because doing CallModel::getIndex() immediately after creating a new call results in an invalid index, thus the selectionModel can't be updated and the UAM relies on the selectionModel.<br />
</p>