savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2019-05-02T18:21:58Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/61File transfer without TURN server2019-05-02T18:21:58ZSébastien BlinFile transfer without TURN serverFor now, and because ICE doesn't supports TCP in pjsip, the file transfer has to pass through a TURN server. This is not perfect.
A better way to do that after https://git.ring.cx/savoirfairelinux/ring-project/issues/486 is to negotiate...For now, and because ICE doesn't supports TCP in pjsip, the file transfer has to pass through a TURN server. This is not perfect.
A better way to do that after https://git.ring.cx/savoirfairelinux/ring-project/issues/486 is to negotiate a TCP connection directly between the sender and receivers.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-project/-/issues/524Are group messages supported?2020-01-09T22:07:13ZBraxton PlaxcoAre group messages supported?I was looking through the mobile Android app and the GNOME app and I didn't see an option for multiple people in a conversation. Are there limitations within ring itself preventing group messaging or is it that the clients just don't hav...I was looking through the mobile Android app and the GNOME app and I didn't see an option for multiple people in a conversation. Are there limitations within ring itself preventing group messaging or is it that the clients just don't have the feature implemented yet, or did I miss it in the UI? :smile:
If it is a feature that isn't implemented ye,t is it on the road map, and is there anything I can do to help? I don't have unlimited time on my hands, but I might be able to help out somewhere.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/399Document how LRC is structured.2019-11-21T04:53:12ZSébastien BlinDocument how LRC is structured.In https://git.ring.cx/savoirfairelinux/ring-project/wikis/homeIn https://git.ring.cx/savoirfairelinux/ring-project/wikis/homeNew media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/398Video API2018-12-11T22:42:00ZSébastien BlinVideo APIWe should be able to:
+ List devices
+ Get current device
+ Configure devices
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
We should be able to:
+ List devices
+ Get current device
+ Configure devices
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
New media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/397Audio API2018-12-11T22:42:03ZSébastien BlinAudio APIWe should be able to:
+ List devices
+ Get current device
+ Configure devices
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
We should be able to:
+ List devices
+ Get current device
+ Configure devices
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
New media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/396new Renderer implementation2018-12-11T22:42:01ZSébastien Blinnew Renderer implementationThe new API should provide the necessary functions to render a call and preview. Moreover, this should also fix the issue when a crash occurs when the preview is open.
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
The new API should provide the necessary functions to render a call and preview. Moreover, this should also fix the issue when a crash occurs when the preview is open.
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
New media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/395Define new media API for clients2018-12-11T22:41:55ZSébastien BlinDefine new media API for clientsThe AVModel class should be completed to provide an API to manage Renderers, Video and Audio devices.
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
The AVModel class should be completed to provide an API to manage Renderers, Video and Audio devices.
# Patch
https://gerrit-ring.savoirfairelinux.com/c/ring-lrc/+/10319
New media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/394Migrate Medias to new LRC2018-12-11T22:42:14ZSébastien BlinMigrate Medias to new LRCSprint meta.
# TODO
## Call view
+ [x] Get Video's input (name/resolutions/etc)
+ [x] Get Audio's input (name/resolutions/etc)
+ [x] Add the ability to change the input
+ [x] Video
+ [x] Monitor (full/area)
+ [x] Stream fi...Sprint meta.
# TODO
## Call view
+ [x] Get Video's input (name/resolutions/etc)
+ [x] Get Audio's input (name/resolutions/etc)
+ [x] Add the ability to change the input
+ [x] Video
+ [x] Monitor (full/area)
+ [x] Stream file
+ [x] Get advanced informations (call id/resolutions/codecs) from current side and peer
+ [x] Classes not based on Call and Profiles from old LRC
+ [x] Verify old options (pause/mute/recording/quality)
+ [x] Crash client without daemon resilient?
## Avatar view & Let a message view
+ [x] Preview rendered
## Media settings
+ [x] Enable hardware decoding
+ [x] Set managers / devices for audio and video
# Issues + estimates:
+ #395 = 1d
+ #396 = 2d
+ #397 = 2d
+ #398 = 1d
+ #399 = 1dNew media APISébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/515Messages not syncing across devices2020-09-21T18:22:12ZCalle KaboMessages not syncing across devicesScenario:
I'm logged in to my ring account on android and linux (my laptop).
I send a message to a contact from my android device.
Currently:
My message doesn't show up on my laptop
Expectation:
My message to show up on my laptop Scenario:
I'm logged in to my ring account on android and linux (my laptop).
I send a message to a contact from my android device.
Currently:
My message doesn't show up on my laptop
Expectation:
My message to show up on my laptop Swarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/534Change password for an account2019-04-25T19:42:30ZSébastien BlinChange password for an accountFor now, I don't think there is the ability to change a password for an account on the android client.
Can be important if a user didn't choose a password in the first page.For now, I don't think there is the ability to change a password for an account on the android client.
Can be important if a user didn't choose a password in the first page.Iteration 5Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/389Several issues in the new call model's state machine2018-09-20T14:07:01ZHugo LefeuvreSeveral issues in the new call model's state machineThe new call model's state machine suffers from multiple design issues:
* [x] State transitions are realized at multiple places. This makes handling of specific transitions in the state machine more complicated and leads to [terrific c...The new call model's state machine suffers from multiple design issues:
* [x] State transitions are realized at multiple places. This makes handling of specific transitions in the state machine more complicated and leads to [terrific code](https://git.ring.cx/savoirfairelinux/ring-lrc/blob/master/src/newcallmodel.cpp#L504).
* [x] `callStatusChanged` should never be emitted by `togglePause()`. Instead it should wait for feedback from the daemon.
* [x] `slotCallStateChanged` is handling conference state changes very badly. From the three possible conference states, only `HOLD` is handled properly. The rest is just considered to be an internal error....Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/47LAN users fail to discover each other2022-11-14T21:52:32ZIurii VoitenkoLAN users fail to discover each otherWith true loyalty to distributed p2p communications, it's a real embarrassment to require high speed Internet connection for Ring when used in LAN. Consider the following setup: a private 10.x.x.x LAN network with very strict firewall ru...With true loyalty to distributed p2p communications, it's a real embarrassment to require high speed Internet connection for Ring when used in LAN. Consider the following setup: a private 10.x.x.x LAN network with very strict firewall rules and proxies for Internet connection needs a p2p messenger for chat, VoIP and presence. Moreover, this LAN has just 56K for Internet and about 10M throughput for Intranet. I considered Ring as a major candidate for this task, but I was really frustrated when Ring required the whole bunch of Internet IPs to discover nodes sitting in the same LAN!
Hence, improvement suggestions:
1. Add static IP support.
Yes, sometimes it's much better to simply assign IP address to a contact than allow DHT lookup running for minutes and fail.
2. Significantly lower the required bandwidth when in DHT mode.
If Internet connection is limited in bandwidth the whole DHT feature is not working properly.
3. Add LAN peer discovery support
Peers can send IP multicast/broadcast packets to identify each other and hence skip the DHT lookup at all.LaterMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/44Error during config save leads to major loss of config and account related data2022-11-14T21:52:32ZHugo LefeuvreError during config save leads to major loss of config and account related dataToday I opened my Ring client and found out that most of my account and contact related information has disappeared.
* 4/5 accounts lost their avatar, display name and registered name
* 1 account lost all its linked devices
* 1 account ...Today I opened my Ring client and found out that most of my account and contact related information has disappeared.
* 4/5 accounts lost their avatar, display name and registered name
* 1 account lost all its linked devices
* 1 account lost all its linked devices except one
* several accounts **MAY** have lost some contacts
4/5 accounts are not functional anymore.
Only one account does not appear to have suffered from data loss. This account is still functional.
**Affects:** latest daemon master with latest LRC and GNOME client
**Daemon logs when starting:**
```
[1536072827.730| 7916|ringaccount.cpp :1421 ] [Account 7c2c46b550fdf679] loading Ring account
[1536072827.730| 7916|ringaccount.cpp :898 ] [Account 7c2c46b550fdf679] loading identity: ring_device.crt ring_device.key
[1536072827.878| 7916|certstore.cpp :75 ] CertificateStore: loaded 327 local certificates.
[1536072827.880| 7916|ringaccount.cpp :836 ] [Account 7c2c46b550fdf679] checking device receipt for 7ba67dbee50ab99fe44a1daa0992a8b5d11b1a21
[1536072827.881| 7916|ringaccount.cpp :891 ] [Account 7c2c46b550fdf679] ring:7ba67dbee50ab99fe44a1daa0992a8b5d11b1a21 device 459eda6e5c5a5819b19a157e4fc1e7491bea644d receipt checked successfully
[1536072827.881| 7916|ringaccount.cpp :2695 ] [Account 7c2c46b550fdf679] loading known account device 459eda6e5c5a5819b19a157e4fc1e7491bea644d
[1536072827.882| 7916|ringaccount.cpp :2406 ] [Account 7c2c46b550fdf679] Found account device: 459eda6e5c5a5819b19a157e4fc1e7491bea644d
[1536072827.883| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: 00e29c5d3d518f96297b032ca21f5f8770573da8
[1536072827.884| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: 3c2a2fae84be1713e6d68d39360faa7441220c00
[1536072827.885| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: ded6a9d278d05adac3265a0a69d07bd264e0861a
[1536072827.886| 7916|ringaccount.cpp :3138 ] [Account 7c2c46b550fdf679] error loading trust requests: Can't read file: incomingTrustRequests
[1536072827.886| 7916|manager.cpp :2792 ] Found abandonned Ring account: /home/hlefeuvre/.local/share/ring/500c78989b647104/export.gz
```
```
[1536072828.803| 7916|ringaccount.cpp :1421 ] [Account 7170fb591202047e] loading Ring account
[1536072828.803| 7916|ringaccount.cpp :898 ] [Account 7170fb591202047e] loading identity: ring_device.crt ring_device.key
[1536072828.806| 7916|ringaccount.cpp :836 ] [Account 7170fb591202047e] checking device receipt for e3494b660ea1f988d4d66ed96811d9445eaa093c
[1536072828.807| 7916|ringaccount.cpp :891 ] [Account 7170fb591202047e] ring:e3494b660ea1f988d4d66ed96811d9445eaa093c device 7646c5dad40347ad8dc3524077a533f539d8a719 receipt checked successfully
[1536072828.807| 7916|ringaccount.cpp :2695 ] [Account 7170fb591202047e] loading known account device 7646c5dad40347ad8dc3524077a533f539d8a719
[1536072828.808| 7916|ringaccount.cpp :2406 ] [Account 7170fb591202047e] Found account device: 7646c5dad40347ad8dc3524077a533f539d8a719
[1536072828.809| 7916|ringaccount.cpp :2992 ] [Account 7170fb591202047e] new contact: 00e29c5d3d518f96297b032ca21f5f8770573da8
[1536072828.810| 7916|ringaccount.cpp :2992 ] [Account 7170fb591202047e] new contact: 3c2a2fae84be1713e6d68d39360faa7441220c00
[1536072828.811| 7916|ringaccount.cpp :3138 ] [Account 7170fb591202047e] error loading trust requests: Can't read file: incomingTrustRequests
[1536072828.811| 7916|manager.cpp :2792 ] Found abandonned Ring account: /home/hlefeuvre/.local/share/ring/2c8f461a28b01e2/export.gz
[1536072828.813| 7916|ringaccount.cpp :1421 ] [Account da65023c64f3d1a5] loading Ring account
[1536072828.814| 7916|ringaccount.cpp :898 ] [Account da65023c64f3d1a5] loading identity: ring_device.crt ring_device.key
[1536072828.817| 7916|ringaccount.cpp :836 ] [Account da65023c64f3d1a5] checking device receipt for 4a76358f13177319b906f1cc511175394e09c01a
[1536072828.818| 7916|ringaccount.cpp :891 ] [Account da65023c64f3d1a5] ring:4a76358f13177319b906f1cc511175394e09c01a device d524cf3a29c2db45d927cba48002a03ef73d2276 receipt checked successfully
[1536072828.819| 7916|ringaccount.cpp :2688 ] [Account da65023c64f3d1a5] error loading devices: Can't read file: knownDevicesNames
[1536072828.819| 7916|ringaccount.cpp :3022 ] [Account da65023c64f3d1a5] error loading contacts: Can't read file: contacts
[1536072828.819| 7916|ringaccount.cpp :3138 ] [Account da65023c64f3d1a5] error loading trust requests: Can't read file: incomingTrustRequests
```
**Client logs when starting:**
```
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
Trying to create a certificate node with an already used id. This can have unforneen consequences
```
As you can see the daemon is not able to load account information. In fact these files have been wiped out:
```
.local/share/ring/
├── 2c8f461a28b01e2
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 500c78989b647104
│ ├── export.gz
│ ├── ring_device.crt
│ └── ring_device.key
├── 7170fb591202047e
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 7c2c46b550fdf679
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 9fba7138a1fc3f51
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── incomingTrustRequests
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
.
.
.
```
This bug has been identified on at least 2 different computers with different builds and accounts. One of these two computers might even run a released version of Ring.Next major releasehttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/384Bad handling of URIs in smartlist2018-09-11T21:31:36ZHugo LefeuvreBad handling of URIs in smartlist**Affects**: latest LRC master
Any URI beginning with `ring:` is recognized as a valid RingID by the LRC. Some URIs beginning with `sip:` and followed by letters like `sip:pol` are recognized as valid RingID. This is a big bug.**Affects**: latest LRC master
Any URI beginning with `ring:` is recognized as a valid RingID by the LRC. Some URIs beginning with `sip:` and followed by letters like `sip:pol` are recognized as valid RingID. This is a big bug.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/42Add ringing timeout2022-11-14T21:52:32ZHugo LefeuvreAdd ringing timeoutCurrently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a ti...Currently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a timeout.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/897chatview: graphical glitch with message type call and large timestamps2020-09-30T21:04:12ZHugo Lefeuvrechatview: graphical glitch with message type call and large timestampsIt looks like the message wrapper's width is defined by
```
width: auto;
margin-left: 30%;
margin-right: 30%;
```
leading to ugly graphical glitches/shifts when timestamp is too large.
![Screenshot_from_2018-08-13_15-36-44](/uploads/2...It looks like the message wrapper's width is defined by
```
width: auto;
margin-left: 30%;
margin-right: 30%;
```
leading to ugly graphical glitches/shifts when timestamp is too large.
![Screenshot_from_2018-08-13_15-36-44](/uploads/2adc235b8bd5f6fbc8335dc4a7429cba/Screenshot_from_2018-08-13_15-36-44.png)Next major releasehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/494Redo the smoke tests tool2019-02-05T20:45:43ZSébastien BlinRedo the smoke tests toolWe need several scenarios to verify between each freeze and release.We need several scenarios to verify between each freeze and release.Quality improvementsAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/493Update packaging job2018-08-15T19:30:02ZSébastien BlinUpdate packaging jobThis job needs to produce a new branch where backports can be done (ex: `release_2018_08`)This job needs to produce a new branch where backports can be done (ex: `release_2018_08`)Quality improvementsSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/492Nightly job on Jenkins2018-08-15T19:29:58ZSébastien BlinNightly job on JenkinsAdd a build on jenkins to produce a nightly build every **X** days.Add a build on jenkins to produce a nightly build every **X** days.Quality improvementsSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/377segfault during trust request during interactionStatusUpdated signal2020-06-09T18:27:46ZHugo Lefeuvresegfault during trust request during interactionStatusUpdated signalThe GNOME client crashes during `interactionStatusUpdated` signal (right after opening the trust requests tab).
ASan stacktrace:
```
registered name found for unknown account ""
ASAN:SIGSEGV
============================================...The GNOME client crashes during `interactionStatusUpdated` signal (right after opening the trust requests tab).
ASan stacktrace:
```
registered name found for unknown account ""
ASAN:SIGSEGV
=================================================================
==7770==ERROR: AddressSanitizer: SEGV on unknown address 0x61104d0000be (pc 0x7fc4a74991ee bp 0x7ffe14708940 sp 0x7ffe147080c8 T0)
#0 0x7fc4a74991ed (/lib/x86_64-linux-gnu/libc.so.6+0x16f1ed)
#1 0x7fc4aead774e in memcmp (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x7774e)
#2 0x4bb737 in std::char_traits<char>::compare(char const*, char const*, unsigned long) /usr/include/c++/5/bits/char_traits.h:262
#3 0x4d951a in __gnu_cxx::__enable_if<std::__is_char<char>::__value, bool>::__type std::operator==<char>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) /usr/include/c++/5/bits/basic_string.h:4914
#4 0x5ba700 in webkit_chat_container_ready(_ChatView*)::{lambda(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, lrc::api::interaction::Info)#2}::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, lrc::api::interaction::Info) const (/usr/bin/gnome-ring+0x5ba700)
#5 0x5bd8b8 in call /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#6 0x5bd48d in call<QtPrivate::List<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, long unsigned int, const lrc::api::interaction::Info&>, void> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#7 0x5bd318 in impl /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:192
#8 0x7fc4ac5b7bae in QMetaObject::activate(QObject*, int, int, void**) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2b4bae)
#9 0x7fc4ae6c593b in lrc::api::ConversationModel::interactionStatusUpdated(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, lrc::api::interaction::Info const&) const (/usr/lib/libringclient.so.1.0.0+0x27493b)
#10 0x7fc4ae6c9469 in lrc::api::ConversationModel::setInteractionRead(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long const&) (/usr/lib/libringclient.so.1.0.0+0x278469)
#11 0x5ba3a9 in print_text_recording /home/hlefeuvre/Development/ring-client-gnome/src/chatview.cpp:487
#12 0x5ba9a0 in webkit_chat_container_ready /home/hlefeuvre/Development/ring-client-gnome/src/chatview.cpp:512
#13 0x5bc6f8 in build_chat_view /home/hlefeuvre/Development/ring-client-gnome/src/chatview.cpp:682
#14 0x5bc8c9 in chat_view_new /home/hlefeuvre/Development/ring-client-gnome/src/chatview.cpp:697
#15 0x516060 in displayChatView /home/hlefeuvre/Development/ring-client-gnome/src/ringmainwindow.cpp:1233
#16 0x5157a0 in changeView /home/hlefeuvre/Development/ring-client-gnome/src/ringmainwindow.cpp:1177
#17 0x52001e in slotShowChatView /home/hlefeuvre/Development/ring-client-gnome/src/ringmainwindow.cpp:1931
#18 0x519835 in (anonymous namespace)::details::CppImpl::updateLrc(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, lrc::api::conversation::Info)#8}::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, lrc::api::conversation::Info) const (/usr/bin/gnome-ring+0x519835)
#19 0x528004 in call /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#20 0x5276dc in call<QtPrivate::List<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const lrc::api::conversation::Info&>, void> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#21 0x526f9a in impl /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:192
#22 0x7fc4ac5b7bae in QMetaObject::activate(QObject*, int, int, void**) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2b4bae)
#23 0x7fc4ae721df6 in lrc::api::BehaviorController::showChatView(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, lrc::api::conversation::Info const&) const (/usr/lib/libringclient.so.1.0.0+0x2d0df6)
#24 0x7fc4ae6c6d2c in lrc::api::ConversationModel::selectConversation(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const (/usr/lib/libringclient.so.1.0.0+0x275d2c)
#25 0x5cfaf1 in select_conversation /home/hlefeuvre/Development/ring-client-gnome/src/conversationsview.cpp:396
#26 0x7fc4acafa1d3 (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x101d3)
#27 0x7fc4acb149a5 in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2a9a5)
#28 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#29 0x7fc4ade59fe3 (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x337fe3)
#30 0x7fc4ade5cab3 (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x33aab3)
#31 0x7fc4acafa1d3 (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x101d3)
#32 0x7fc4acb149a5 in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2a9a5)
#33 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#34 0x7fc4ade76579 in gtk_widget_grab_focus (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x354579)
#35 0x7fc4ade5225c (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x33025c)
#36 0x7fc4add3552b (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x21352b)
#37 0x7fc4acaf9efe in g_closure_invoke (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0xfefe)
#38 0x7fc4acb0c56d (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2256d)
#39 0x7fc4acb147f8 in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2a7f8)
#40 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#41 0x7fc4ade772c9 in gtk_widget_child_focus (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3552c9)
#42 0x7fc4addb8bc7 (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x296bc7)
#43 0x7fc4add3552b (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x21352b)
#44 0x7fc4acaf9fa4 in g_closure_invoke (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0xffa4)
#45 0x7fc4acb0c56d (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2256d)
#46 0x7fc4acb147f8 in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2a7f8)
#47 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#48 0x7fc4ade772c9 in gtk_widget_child_focus (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3552c9)
#49 0x7fc4add67755 (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x245755)
#50 0x7fc4acaf9fa4 in g_closure_invoke (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0xffa4)
#51 0x7fc4acb0c56d (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2256d)
#52 0x7fc4acb14d5b in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2ad5b)
#53 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#54 0x7fc4add624aa (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x2404aa)
#55 0x7fc4add35099 (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x213099)
#56 0x7fc4acafa1d3 (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x101d3)
#57 0x7fc4acb144b7 in g_signal_emit_valist (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2a4b7)
#58 0x7fc4acb1508e in g_signal_emit (/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x2b08e)
#59 0x7fc4ade72c3b (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x350c3b)
#60 0x7fc4add323bd (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x2103bd)
#61 0x7fc4add341bb in gtk_main_do_event (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0+0x2121bb)
#62 0x7fc4ad8a1d91 (/usr/lib/x86_64-linux-gnu/libgdk-3.so.0+0x5ad91)
#63 0x7fc4ac823196 in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a196)
#64 0x7fc4ac8233ef (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a3ef)
#65 0x7fc4ac82349b in g_main_context_iteration (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4a49b)
#66 0x7fc4acdead7c in g_application_run (/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xadd7c)
#67 0x4b6df4 in main /home/hlefeuvre/Development/ring-client-gnome/src/main.cpp:37
#68 0x7fc4a734a82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#69 0x4b6a48 in _start (/usr/bin/gnome-ring+0x4b6a48)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ??:0 ??
==7770==ABORTING
```Next major release