jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2020-09-30T20:29:26Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/593configured bootsrap node always defaults to port 42222020-09-30T20:29:26ZJami Botconfigured bootsrap node always defaults to port 4222Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
I have found that configuring the port using the GNOME client configuration interface fails to configure a bootstrap address with th...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
I have found that configuring the port using the GNOME client configuration interface fails to configure a bootstrap address with the appropriate port.
I have tried bootstrapping on a local node (on my machine) using an address obtained from the router with first empty port, then changing the port and saving doesn't take the change into account when looking at the log.
I can confirm that this bug doesn't occur on Windows 32 client.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/690Numeric Key pad entries while in a call not valid2018-06-18T10:51:57ZJami BotNumeric Key pad entries while in a call not validIssue generated from Tuleap's migration script.
**Originally submitted by: Jesse James Bruce (jessejbruce)**
When making a call to an IVR (interactive voice menu) menu in any call center the key pad commands are not correct even though ...Issue generated from Tuleap's migration script.
**Originally submitted by: Jesse James Bruce (jessejbruce)**
When making a call to an IVR (interactive voice menu) menu in any call center the key pad commands are not correct even though the commands (numbers) are displayed in the ring key pad correctly.
\* Environment:
Lubuntu Linux
\* Reproduce steps:
Make a call to a call center that has a key pad entry menu and select an option on the key pad
\* Expected result:
It should select the menu or interactive voice menu with a number from the key pad
\* Actual result:
Numbers not valid when i enter selection one during a call in the key pad it displays the number 1 however the remote machine fails respond.
Something is being sent to the remote machine i concluded but it is incorrect.Gnome 2018.07.15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/708Gnome client UI resets to main screen when account connection is re-established2018-07-17T16:43:36ZJami BotGnome client UI resets to main screen when account connection is re-establishedIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (ver...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Any recent Gnome client (version tested: built from sources as of 2018-02-08)
\* Reproduce steps:
1. Open the Gnome client.
2. Enter or create a new chat conversation.
3. Manually disconnect then connect again the network (use the Ethernet cable, the Wi-Fi killswitch, etc.)
4. Notice that when daemon notices about the disconnection, the client redraws its UI to show the main screen and the user is kicked out of its current conversation view.
\* Expected result:
The view should be maintained to the current conversation. If the network problem persists (after a threshold of say, 5 seconds), a visual hint should notify the user that there is currently no connectivity.
\* Actual result:
The user is disoriented/confused since the UI changes under their feet without any action on their part.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/712[GNOME] showing Devices which have been revoked on [Android]2021-08-18T21:42:54ZJami Bot[GNOME] showing Devices which have been revoked on [Android]Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
[Android]
1. Manage accounts
2. Click on account
3. Click on account to delete
4. Enter code
5. Click 'Revoke account'
[GNOME]
1...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
[Android]
1. Manage accounts
2. Click on account
3. Click on account to delete
4. Enter code
5. Click 'Revoke account'
[GNOME]
1. Settings
2. Accounts
3. Click on Account
4. Click on 'Devices' tab
5. The account which have been revoked on Android are incorrectly still shown on the GNOME client
Are you able to reproduce?
Thank youSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/722Segfault on start2018-05-26T19:29:40ZJami BotSegfault on startIssue generated from Tuleap's migration script.
**Originally submitted by: Angelica Andrianova (marzanna)**
\* Environment:
Ubuntu 17.10 with XFCE
\* Reproduce steps:
```
$ gnome-ring
** Message: Ring GNOME client versi...Issue generated from Tuleap's migration script.
**Originally submitted by: Angelica Andrianova (marzanna)**
\* Environment:
Ubuntu 17.10 with XFCE
\* Reproduce steps:
```
$ gnome-ring
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: unknown
** (gnome-ring:16762): WARNING **: could not create symlink: File exists
(gnome-ring:16762): Gtk-WARNING **: GtkGrid does not have a child property called expand
(gnome-ring:16762): Gtk-WARNING **: GtkGrid does not have a child property called fill
(gnome-ring:16762): Gtk-WARNING **: GtkGrid does not have a child property called position
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
** (gnome-ring:16762): WARNING **: Unable to create EDS registry: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit evolution-source-registry.service not found.
Segmentation fault (core dumped)
```
Ring suddenly stopped working. It segfault when I try to start it. here is strace log https://bin.disroot.org/?df834a16d180d261\#Bmaj301Cy2RB28ilpPDDgQCcHYw9+rS0TdZIhrAxG1Q=
:https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/723[GNOME] Ring freezes when deleting an account2018-06-01T19:13:18ZJami Bot[GNOME] Ring freezes when deleting an accountIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Steps:
1. Already have only one RING protocol account
2. Settings → Accounts → Add new [SIP] account
3. Delete [SIP] account wh...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Steps:
1. Already have only one RING protocol account
2. Settings → Accounts → Add new [SIP] account
3. Delete [SIP] account which has been created
4. gnome-ring freezes
Thank you
ring-gnome 2018-03-23 23:25:11 UTC
Linux Mint 18.3 Cinnamon 64-bithttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/732heap-use-after-free and crash when disconnecting network2018-07-16T20:03:32ZJami Botheap-use-after-free and crash when disconnecting networkIssue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
Whenever the network is disconnected, the Ring Daemon crashes.
\* Environment:
latest master, Ubuntu 16.04.4 LTS
\* Reproduce s...Issue generated from Tuleap's migration script.
**Originally submitted by: Hugo Lefeuvre (hle)**
Whenever the network is disconnected, the Ring Daemon crashes.
\* Environment:
latest master, Ubuntu 16.04.4 LTS
\* Reproduce steps:
1) Build dring with ASAN.
$ export CFLAGS="-fsanitize=address -g -O0"
$ export LDFLAGS="-fsanitize=address"
$ export CXXFLAGS="$(CFLAGS)"
$ ./autogen.sh
$ ./configure
$ make
2) Start freshly built daemon
$ ./bin/dring -pcd
3) Dirty-disconnect network (in my case: unplug Ethernet cable)
4) Dring crashes with following ASAN stacktrace (heap-use-after-free)
```
=================================================================
==15382==ERROR: AddressSanitizer: heap-use-after-free on address 0x60f00003e6b8 at pc 0x7f9d82f75b50 bp 0x7ffff45aec20 sp 0x7ffff45aec10
WRITE of size 4 at 0x60f00003e6b8 thread T0
#0 0x7f9d82f75b4f in __exchange_and_add /usr/include/c++/5/ext/atomicity.h:49
#1 0x7f9d82f75c9e in __exchange_and_add_dispatch /usr/include/c++/5/ext/atomicity.h:82
#2 0x7f9d82f78946 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() /usr/include/c++/5/bits/shared_ptr_base.h:147
#3 0x7f9d8358ca09 in dht::Dht::searchSynchedNodeListen(std::shared_ptr<dht::Dht::Search> const&, dht::Dht::SearchNode&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf6ea09)
#4 0x7f9d835a22ec in dht::Dht::searchStep(std::shared_ptr<dht::Dht::Search>) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf842ec)
#5 0x7f9d835a926e in std::_Function_handler<void (), std::_Bind<std::_Mem_fn<void (dht::Dht::*)(std::shared_ptr<dht::Dht::Search>)> (dht::Dht*, std::shared_ptr<dht::Dht::Search>)> >::_M_invoke(std::_Any_data const&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf8b26e)
#6 0x7f9d83587573 in dht::Dht::periodic(unsigned char const*, unsigned long, dht::SockAddr const&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf69573)
#7 0x7f9d835a98f1 in dht::Dht::periodic(unsigned char const*, unsigned long, sockaddr const*, unsigned int) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf8b8f1)
#8 0x7f9d8355e9c0 in dht::DhtRunner::loop_() (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf409c0)
#9 0x7f9d832b1f7e in dht::DhtRunner::loop() /home/hlefeuvre/Development/ring-daemon/contrib/x86_64-linux-gnu/include/opendht/dhtrunner.h:364
#10 0x7f9d832728ef in ring::RingAccount::handleEvents() /home/hlefeuvre/Development/ring-daemon/src/ringdht/ringaccount.cpp:1618
#11 0x7f9d83279437 in ring::RingAccount::doRegister_()::{lambda()#8}::operator()() const (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xc5b437)
#12 0x7f9d8329bfe1 in _M_invoke /usr/include/c++/5/functional:1871
#13 0x7f9d82fca457 in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
#14 0x7f9d82fb09e8 in ring::Manager::pollEvents() /home/hlefeuvre/Development/ring-daemon/src/manager.cpp:1721
#15 0x7f9d83052de5 in DRing::pollEvents() /home/hlefeuvre/Development/ring-daemon/src/ring_api.cpp:85
#16 0x4b01cf in std::_Function_handler<void (), void (*)()>::_M_invoke(std::_Any_data const&) (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x4b01cf)
#17 0x49ccfd in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
#18 0x49b3bf in EventCallback::call(DBus::DefaultTimeout&) const (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x49b3bf)
#19 0x5388d4 in DBus::Slot<void, DBus::DefaultTimeout&>::operator()(DBus::DefaultTimeout&) const (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x5388d4)
#20 0x537eab in DBus::DefaultMainLoop::dispatch() (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x537eab)
#21 0x539c7d in DBus::BusDispatcher::do_iteration() (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x539c7d)
#22 0x53990f in DBus::BusDispatcher::enter() (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x53990f)
#23 0x4930fc in DBusClient::event_loop() /home/hlefeuvre/Development/ring-daemon/bin/dbus/dbusclient.cpp:250
#24 0x48d0d0 in main /home/hlefeuvre/Development/ring-daemon/bin/main.cpp:236
#25 0x7f9d81abf82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#26 0x48c718 in _start (/home/hlefeuvre/Development/ring-daemon/bin/.libs/lt-dring+0x48c718)
0x60f00003e6b8 is located 8 bytes inside of 168-byte region [0x60f00003e6b0,0x60f00003e758)
freed by thread T0 here:
#0 0x7f9d84c5db2a in operator delete(void*) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99b2a)
#1 0x7f9d82f78a23 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() /usr/include/c++/5/bits/shared_ptr_base.h:167
#2 0x7f9d8358c94d in dht::Dht::searchSynchedNodeListen(std::shared_ptr<dht::Dht::Search> const&, dht::Dht::SearchNode&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf6e94d)
#3 0x7f9d835a22ec in dht::Dht::searchStep(std::shared_ptr<dht::Dht::Search>) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf842ec)
previously allocated by thread T0 here:
#0 0x7f9d84c5d532 in operator new(unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99532)
#1 0x7f9d835ca5cf in dht::net::NetworkEngine::sendListen(std::shared_ptr<dht::Node>, dht::Hash<20ul> const&, dht::Query const&, std::vector<unsigned char, std::allocator<unsigned char> > const&, std::shared_ptr<dht::net::Request>, std::function<void (dht::net::Request const&, dht::net::RequestAnswer&&)>&&, std::function<void (dht::net::Request const&, bool)>&&, std::function<void (std::shared_ptr<dht::Node> const&, dht::net::RequestAnswer&&)>&&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xfac5cf)
#2 0x7f9d8358c8cc in dht::Dht::searchSynchedNodeListen(std::shared_ptr<dht::Dht::Search> const&, dht::Dht::SearchNode&) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf6e8cc)
#3 0x7f9d835a22ec in dht::Dht::searchStep(std::shared_ptr<dht::Dht::Search>) (/home/hlefeuvre/Development/ring-daemon/src/.libs/libring.so.0+0xf842ec)
SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/c++/5/ext/atomicity.h:49 __exchange_and_add
Shadow bytes around the buggy address:
0x0c1e7ffffc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1e7ffffc90: 00 fa fa fa fa fa fa fa fa fa 00 00 00 00 00 00
0x0c1e7ffffca0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fa
0x0c1e7ffffcb0: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c1e7ffffcc0: fd fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa
=>0x0c1e7ffffcd0: fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd fd fd
0x0c1e7ffffce0: fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa fa
0x0c1e7ffffcf0: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1e7ffffd00: fd fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa
0x0c1e7ffffd10: fa fa fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1e7ffffd20: fd fd fd fd fd fd fd 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
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
==15382==ABORTING
```
\* Expected result:
Obviously, dring should not crash when network is disconnected.
Please, note: This bug may \*very well\* be located in opendht.
I have marked the bug as affecting GNU/Linux only, but it may very well affect other platforms.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/788"Searching..." displays as a contact2018-07-03T18:53:23ZJami Bot"Searching..." displays as a contactIssue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
After typing ring id in the search bar, adding contact with invite button, and clearing search bar with backspace, search icon appears amon...Issue generated from Tuleap's migration script.
**Originally submitted by: Jan (kromka_chleba)**
After typing ring id in the search bar, adding contact with invite button, and clearing search bar with backspace, search icon appears among contacts.
Platform: GNU/Linux Mint 18.3 cinnamon, kernel 4.13.0-41 generic
Ring build: 2018-05-01https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/798chatview: Unable to display some emojis2019-11-12T20:18:01ZHugo Lefeuvrechatview: Unable to display some emojisThe chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open...The chatview fails to display some emojis. It appears that affected emojis are all part of the Emoji 3.0 (Unicode 9.0) spec.
Some examples: 🦊 (U+1F98A), 🦋 (U+1F98B), 🦍 (U+1F98D), 🥜 (U+1F95C), 🥐 (U+1F950).
**How to reproduce:**
1. Open another client (macOS, Android), and send a fox 🦊 (U+1F98A) Emoji to the GNU/Linux GNOME client.
2. The GNU/Linux GNOME client fails to display received Emoji. Only the background is displayed.
This may be a bug in the dependency chain.Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/803SIP: Add a transfer button in currentcallview2018-06-11T23:12:34ZSébastien BlinSIP: Add a transfer button in currentcallview+ [x] Add a transfer button in the callview linked to a context menu
+ [x] In this context menu, we should see current conversations and if we click on an item, perform a transfer (blind or not if a call id)
+ [x] Also in this context me...+ [x] Add a transfer button in the callview linked to a context menu
+ [x] In this context menu, we should see current conversations and if we click on an item, perform a transfer (blind or not if a call id)
+ [x] Also in this context menu, we should be able to search a new number and perform a blind transfer.SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/809database related crash during exit2020-10-05T20:23:10ZHugo Lefeuvredatabase related crash during exitSometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at r...Sometimes the client crashes during exit with following error messages in the debug output:
```
** (gnome-ring:31292): DEBUG: quitting
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
** (gnome-ring:31292): WARNING **: Can't get conversation at row 0
QSqlQuery::prepare: database not open
terminate called after throwing an instance of 'lrc::Database::QueryError'
what(): Driver not loaded Driver not loaded
Aborted (core dumped)
```
I suspect a race condition in the LRC. Something like:
1. DB is closed
2. a signal comes and the callback tries to access the DB's freed data structures
Since this bug is only reproducible on the GNU/Linux GNOME client I'm reporting it here.
**How to reproduce:**
1. open a GNU/Linux GNOME client
2. close it using "quit" button
This crash is pretty rare, and like most race conditions it may not be reproducible on every machine.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/811chatview: lazy load messages2018-07-03T18:46:37ZHugo Lefeuvrechatview: lazy load messagesCurrently we display the whole conversation in the chatview. This is fine for small to medium sized conversations, but when the chat starts to get large, the size of the conversation becomes a major performances issue.
Lazy loading the ...Currently we display the whole conversation in the chatview. This is fine for small to medium sized conversations, but when the chat starts to get large, the size of the conversation becomes a major performances issue.
Lazy loading the conversation would improve performances considerably.Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/813smartlist: improve support for Display names with emoji2023-05-26T13:59:33ZHugo Lefeuvresmartlist: improve support for Display names with emojiIf a display name contains Emojis, the default avatar contains a question mark '?'.
![Screenshot_from_2018-06-01_16-49-34](/uploads/97e89e4d785cbb9f29113a1382774195/Screenshot_from_2018-06-01_16-49-34.png)
**Expected behaviour:**
It s...If a display name contains Emojis, the default avatar contains a question mark '?'.
![Screenshot_from_2018-06-01_16-49-34](/uploads/97e89e4d785cbb9f29113a1382774195/Screenshot_from_2018-06-01_16-49-34.png)
**Expected behaviour:**
It should contain the default avatar, like this one:
![Screenshot_from_2018-06-01_16-55-43](/uploads/f80dc27208c84d79001a7fbcbd07757c/Screenshot_from_2018-06-01_16-55-43.png)Full Emoji support 🚩https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/820[Gnome] Segmentation Fault After Call Connects2018-07-05T21:31:17Zvindicatorr[Gnome] Segmentation Fault After Call ConnectsCall initiated by double-clicking contact in Gnome to Android device.
Call connects, then nothing is heard/seen in Gnome except for the black screen view.
dring was started with "-cd" before starting ring.
Gnome Ring stayed open after dr...Call initiated by double-clicking contact in Gnome to Android device.
Call connects, then nothing is heard/seen in Gnome except for the black screen view.
dring was started with "-cd" before starting ring.
Gnome Ring stayed open after dring segfaulted.
I think when I also pressed to End Call, gnome ring stated dring wasn't running or something which was correct.
When I brought dring back up manually, I still couldn't end call, but could bring up the chat view which hid the call view.
Double clicking contact again, started the call and while there was no segfault this time, there was still no audio sent/received, though I did see "Connection to PulseAudio server established" in the dring output.
The call view in android went back to chat view, but in gnome, call view remained.
Trying to click End Call said nothing in gnome ring, but dring showed "Could not hang up non-existant call..."
Restarting both dring and gnome ring, I JUST noticed "No audio layer created, possibly built without audio support" from manager.cpp after the "Connection to pulseaudio server established" message.
Weird, started call again and did see audio based output in dring before another segfault:
```
[1528740918.278|31546|media_decoder.cpp :114 ] Trying to open device dummyFilename with format sdp, pixel format , size 0x0, rate 0.000000
[1528740918.278|31545|media_encoder.cpp :549 ] [libopus] Using 4 threads
[1528740918.278|31546|media_decoder.cpp :131 ] Using format sdp
[1528740918.278|31545|media_encoder.cpp :621 ] [libopus] Frame size 960
[1528740918.279|31546|media_decoder.cpp :172 ] Finding audio stream info
[1528740918.279|31331|media_encoder.cpp :549 ] [libvpx] Using 4 threads
Segmentation fault (core dumped)
```
```
Process 29872 (dring) of user 1000 dumped core.
Stack trace of thread 29872:
#0 0x00007fe25d583d66 atoi (libring.so.0)
#1 0x00007fe25d583fa3 _ZN4ring12MediaEncoder9addStreamERKNS_15SystemCodecInfoENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libring.so.0)
#2 0x00007fe25d5874cf _ZN4ring12MediaEncoder14openLiveOutputERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_16MediaDescriptionE (libring.so.0)
#3 0x00007fe25d6837fc _ZN4ring5video11VideoSenderC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_12DeviceParamsERKNS_16MediaDescriptionERNS_10SocketPairEtt (libring.so.0)
#4 0x00007fe25d685329 _ZN4ring5video15VideoRtpSession11startSenderEv (libring.so.0)
#5 0x00007fe25d686221 _ZN4ring5video15VideoRtpSession5startESt10unique_ptrINS_9IceSocketESt14default_deleteIS3_EES6_ (libring.so.0)
#6 0x00007fe25d5620d1 _ZN4ring7SIPCall13startAllMediaEv (libring.so.0)
#7 0x00007fe25d562aa8 operator() (libring.so.0)
#8 0x00007fe25d4f1dc6 _ZNKSt8functionIFbvEEclEv (libring.so.0)
#9 0x00007fe25dc577f3 _ZN4DBus15DefaultMainLoop8dispatchEv (libdbus-c++-1.so.0)
#10 0x00007fe25dc57fb1 _ZN4DBus13BusDispatcher5enterEv (libdbus-c++-1.so.0)
#11 0x000055f3395f6bdf _ZN10DBusClient10event_loopEv (dring)
#12 0x000055f3395f633f main (dring)
#13 0x00007fe2554e506b __libc_start_main (libc.so.6)
#14 0x000055f3395f665a _start (dring)
Stack trace of thread 29972:
#0 0x00007fe2555afea9 __poll (libc.so.6)
#1 0x00007fe25c872773 n/a (libpulse.so.0)
#2 0x00007fe25c863bd0 pa_mainloop_poll (libpulse.so.0)
#3 0x00007fe25c864271 pa_mainloop_iterate (libpulse.so.0)
#4 0x00007fe25c864301 pa_mainloop_run (libpulse.so.0)
#5 0x00007fe25c8726ae n/a (libpulse.so.0)
#6 0x00007fe254ddb81c n/a (libpulsecommon-11.1.so)
#7 0x00007fe25a185075 start_thread (libpthread.so.0)
#8 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30079:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d5dadf0 wait<ring::tls::TlsSession::TlsSessionImpl::handleStateEstablished(ring::tls::TlsSessionState)::<lambda()> > (libring.so.0)
#3 0x00007fe25d5db0c6 _ZNKSt8functionIFN4ring3tls15TlsSessionStateES2_EEclES2_ (libring.so.0)
#4 0x00007fe25d514acd _ZNKSt8functionIFvvEEclEv (libring.so.0)
#5 0x00007fe25d5152ba _ZSt13__invoke_implIvMN4ring10ThreadLoopEFvRNSt6thread2idESt8functionIFbvEES5_IFvvEES9_EPS1_JSt17reference_wrapperIS3_ES7_S9_S9_EET_St21__invoke_memfun_derefOT0_OT1_DpOT2_ (libring.so.0)
#6 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#7 0x00007fe25a185075 start_thread (libpthread.so.0)
#8 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30083:
#0 0x00007fe2555f8398 __GI___strcmp_ssse3 (libc.so.6)
#1 0x00007fe257d66750 av_opt_find2 (libavutil.so.56)
#2 0x00007fe257d6757a n/a (libavutil.so.56)
#3 0x00007fe257d67cb1 av_opt_set (libavutil.so.56)
#4 0x00007fe258dfdf67 n/a (libavcodec.so.58)
#5 0x00007fe258dfe067 avcodec_alloc_context3 (libavcodec.so.58)
#6 0x00007fe25d583a68 _ZN4ring12MediaEncoder21prepareEncoderContextEP7AVCodecb (libring.so.0)
#7 0x00007fe25d583fa3 _ZN4ring12MediaEncoder9addStreamERKNS_15SystemCodecInfoENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE (libring.so.0)
#8 0x00007fe25d5874cf _ZN4ring12MediaEncoder14openLiveOutputERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_16MediaDescriptionE (libring.so.0)
#9 0x00007fe25d5a240a _ZN4ring11AudioSender5setupERNS_10SocketPairE (libring.so.0)
#10 0x00007fe25d514aa9 _ZNKSt8functionIFbvEEclEv (libring.so.0)
#11 0x00007fe25d5152ba _ZSt13__invoke_implIvMN4ring10ThreadLoopEFvRNSt6thread2idESt8functionIFbvEES5_IFvvEES9_EPS1_JSt17reference_wrapperIS3_ES7_S9_S9_EET_St21__invoke_memfun_derefOT0_OT1_DpOT2_ (libring.so.0)
#12 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#13 0x00007fe25a185075 start_thread (libpthread.so.0)
#14 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29875:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d638e63 wait<ring::detail::_ChannelBase<T, N>::receive_wait() [with T = std::unique_ptr<ring::(anonymous namespace)::CtrlMsgBase>; long unsigned int N = 0]::<lambda()> > (libring.so.0)
#3 0x00007fe25d63ffcc _ZZN4ring16DhtPeerConnector4ImplC4ERNS_11RingAccountEENKUlvE_clEv (libring.so.0)
#4 0x00007fe25d5306e9 _ZNKSt8functionIFSt10unique_ptrINSt13__future_base12_Result_baseENS2_8_DeleterEEvEEclEv (libring.so.0)
#5 0x00007fe25a18c9af __pthread_once_slow (libpthread.so.0)
#6 0x00007fe25d63cd88 __gthread_once (libring.so.0)
#7 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#8 0x00007fe25a185075 start_thread (libpthread.so.0)
#9 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29873:
#0 0x00007fe2555b21d7 __select (libc.so.6)
#1 0x00007fe25d691ef2 _ZN4ring5video22VideoDeviceMonitorImpl3runEv (libring.so.0)
#2 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#3 0x00007fe25a185075 start_thread (libpthread.so.0)
#4 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29876:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe25bbb8365 n/a (libthreadutil.so.6)
#2 0x00007fe25bbb7490 n/a (libthreadutil.so.6)
#3 0x00007fe25a185075 start_thread (libpthread.so.0)
#4 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29874:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d638e63 wait<ring::detail::_ChannelBase<T, N>::receive_wait() [with T = std::unique_ptr<ring::(anonymous namespace)::CtrlMsgBase>; long unsigned int N = 0]::<lambda()> > (libring.so.0)
#3 0x00007fe25d63ffcc _ZZN4ring16DhtPeerConnector4ImplC4ERNS_11RingAccountEENKUlvE_clEv (libring.so.0)
#4 0x00007fe25d5306e9 _ZNKSt8functionIFSt10unique_ptrINSt13__future_base12_Result_baseENS2_8_DeleterEEvEEclEv (libring.so.0)
#5 0x00007fe25a18c9af __pthread_once_slow (libpthread.so.0)
#6 0x00007fe25d63cd88 __gthread_once (libring.so.0)
#7 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#8 0x00007fe25a185075 start_thread (libpthread.so.0)
#9 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29879:
#0 0x00007fe25a18b35b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe25bbb71b4 n/a (libthreadutil.so.6)
#2 0x00007fe25a185075 start_thread (libpthread.so.0)
#3 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29878:
#0 0x00007fe25a18b35b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe25bbb71b4 n/a (libthreadutil.so.6)
#2 0x00007fe25a185075 start_thread (libpthread.so.0)
#3 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29881:
#0 0x00007fe25a18b35b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe25bbb71b4 n/a (libthreadutil.so.6)
#2 0x00007fe25a185075 start_thread (libpthread.so.0)
#3 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30077:
#0 0x00007fe2555b21d7 __select (libc.so.6)
#1 0x00007fe25d718d71 pj_sock_select (libring.so.0)
#2 0x00007fe25d714e65 pj_ioqueue_poll (libring.so.0)
#3 0x00007fe25d5180f9 _ZN4ring12IceTransport4Impl12handleEventsEj (libring.so.0)
#4 0x00007fe25d5182de operator() (libring.so.0)
#5 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#6 0x00007fe25a185075 start_thread (libpthread.so.0)
#7 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30080:
#0 0x00007fe2555b21d7 __select (libc.so.6)
#1 0x00007fe25d718d71 pj_sock_select (libring.so.0)
#2 0x00007fe25d714e65 pj_ioqueue_poll (libring.so.0)
#3 0x00007fe25d5180f9 _ZN4ring12IceTransport4Impl12handleEventsEj (libring.so.0)
#4 0x00007fe25d5182de operator() (libring.so.0)
#5 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#6 0x00007fe25a185075 start_thread (libpthread.so.0)
#7 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30084:
#0 0x00007fe258e0e5e0 n/a (libavcodec.so.58)
#1 0x00007fe258947b9f n/a (libavcodec.so.58)
#2 0x00007fe258f216b2 avcodec_open2 (libavcodec.so.58)
#3 0x00007fe2585eb42a avformat_find_stream_info (libavformat.so.58)
#4 0x00007fe25d57ee89 _ZN4ring12MediaDecoder11setupStreamE11AVMediaType (libring.so.0)
#5 0x00007fe25d5a20bf _ZN4ring18AudioReceiveThread5setupEv (libring.so.0)
#6 0x00007fe25d514aa9 _ZNKSt8functionIFbvEEclEv (libring.so.0)
#7 0x00007fe25d5152ba _ZSt13__invoke_implIvMN4ring10ThreadLoopEFvRNSt6thread2idESt8functionIFbvEES5_IFvvEES9_EPS1_JSt17reference_wrapperIS3_ES7_S9_S9_EET_St21__invoke_memfun_derefOT0_OT1_DpOT2_ (libring.so.0)
#8 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#9 0x00007fe25a185075 start_thread (libpthread.so.0)
#10 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29890:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d51581d wait<ring::ThreadPool::run(std::function<void()>&&)::<lambda()>::<lambda()> > (libring.so.0)
#3 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#4 0x00007fe25a185075 start_thread (libpthread.so.0)
#5 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29882:
#0 0x00007fe25a18b35b pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe25bbb71b4 n/a (libthreadutil.so.6)
#2 0x00007fe25a185075 start_thread (libpthread.so.0)
#3 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29914:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d51581d wait<ring::ThreadPool::run(std::function<void()>&&)::<lambda()>::<lambda()> > (libring.so.0)
#3 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#4 0x00007fe25a185075 start_thread (libpthread.so.0)
#5 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29887:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d51581d wait<ring::ThreadPool::run(std::function<void()>&&)::<lambda()>::<lambda()> > (libring.so.0)
#3 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#4 0x00007fe25a185075 start_thread (libpthread.so.0)
#5 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29883:
#0 0x00007fe2555b21d7 __select (libc.so.6)
#1 0x00007fe25bdc5398 n/a (libupnp.so.6)
#2 0x00007fe25bbb7490 n/a (libthreadutil.so.6)
#3 0x00007fe25a185075 start_thread (libpthread.so.0)
#4 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29917:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d51581d wait<ring::ThreadPool::run(std::function<void()>&&)::<lambda()>::<lambda()> > (libring.so.0)
#3 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#4 0x00007fe25a185075 start_thread (libpthread.so.0)
#5 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 30059:
#0 0x00007fe2555b21d7 __select (libc.so.6)
#1 0x00007fe25b3aa975 n/a (libopendht.so.1)
#2 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#3 0x00007fe25a185075 start_thread (libpthread.so.0)
#4 0x00007fe2555ba53f __clone (libc.so.6)
Stack trace of thread 29884:
#0 0x00007fe25a18affc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fe255edfd5d __gthread_cond_wait (libstdc++.so.6)
#2 0x00007fe25d638e63 wait<ring::detail::_ChannelBase<T, N>::receive_wait() [with T = std::unique_ptr<ring::(anonymous namespace)::CtrlMsgBase>; long unsigned int N = 0]::<lambda()> > (libring.so.0)
#3 0x00007fe25d63ffcc _ZZN4ring16DhtPeerConnector4ImplC4ERNS_11RingAccountEENKUlvE_clEv (libring.so.0)
#4 0x00007fe25d5306e9 _ZNKSt8functionIFSt10unique_ptrINSt13__future_base12_Result_baseENS2_8_DeleterEEvEEclEv (libring.so.0)
#5 0x00007fe25a18c9af __pthread_once_slow (libpthread.so.0)
#6 0x00007fe25d63cd88 __gthread_once (libring.so.0)
#7 0x00007fe255ee5d3f execute_native_thread_routine (libstdc++.so.6)
#8 0x00007fe25a185075 start_thread (libpthread.so.0)
#9 0x00007fe2555ba53f __clone (libc.so.6)
```Philippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/823Unsent Messages And Files2019-05-24T19:17:34ZgnulinuxUnsent Messages And FilesHello.
Sometimes text messages and files would not send. Even after sending the message multiple times, the message would appear red with an x by the message.
My friend had the same problem; some messages my friend sent would not be rece...Hello.
Sometimes text messages and files would not send. Even after sending the message multiple times, the message would appear red with an x by the message.
My friend had the same problem; some messages my friend sent would not be received by me.
Sometimes restarting the client worked; other times restarting the client did not work.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/825Client Does Not Automatically Scroll Chat Down2018-07-03T18:45:34ZgnulinuxClient Does Not Automatically Scroll Chat DownThe client does not automatically scroll text messages down, when someone sends them to you, so sometimes new messages are not seen until one scrolls down manually.The client does not automatically scroll text messages down, when someone sends them to you, so sometimes new messages are not seen until one scrolls down manually.Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/826Menu->quit is not working2018-06-16T14:27:32ZSébastien BlinMenu->quit is not workingRing 2018.06.06, Fedora 28.
Note: From IRC, can't reproduce.
# Reproduce steps
1. Open Ring
2. Menu->quit
3. `ps aux | grep dring` daemon is still running like gnome-ring
4. Can't relaunch Ring
# Expected
The daemon and the client s...Ring 2018.06.06, Fedora 28.
Note: From IRC, can't reproduce.
# Reproduce steps
1. Open Ring
2. Menu->quit
3. `ps aux | grep dring` daemon is still running like gnome-ring
4. Can't relaunch Ring
# Expected
The daemon and the client should be stoppedhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/833chatview: major efficiency issues in updateTimestamps2018-07-12T21:04:25ZHugo Lefeuvrechatview: major efficiency issues in updateTimestamps`updateTimestamps()` is affected by several design issues with a large drawbacks on performances:
1. This function goes through all timestamp entries and is called by `addOrUpdateMessage()`. This means that this function is called **eac...`updateTimestamps()` is affected by several design issues with a large drawbacks on performances:
1. This function goes through all timestamp entries and is called by `addOrUpdateMessage()`. This means that this function is called **each and every time a message is displayed** ! This is basically O(n²) algorithm. For instance, displaying 50 messages triggers 1275 timestamp updates.
2. This function handles both text and **position/style updates**. The is probably done in order to simulate some kind of responsive behaviour. This should be done by CSS, not JS.Gnome 2018.07.15Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/880No ring item in appindicator on Ubuntu 18.042019-06-20T12:15:44ZRoberto ResoliNo ring item in appindicator on Ubuntu 18.04The appindicator item for ring is no more present after upgrading to latest Ubuntu LTS (18.04 "bionic"). I'm using ring repo:
`deb https://dl.ring.cx/ring-nightly/ubuntu_18.04/ ring main`The appindicator item for ring is no more present after upgrading to latest Ubuntu LTS (18.04 "bionic"). I'm using ring repo:
`deb https://dl.ring.cx/ring-nightly/ubuntu_18.04/ ring main`Next major releasehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/835drag and drop: fails with paths containing spaces2018-07-05T14:38:30ZHugo Lefeuvredrag and drop: fails with paths containing spacesDrag and drop fails when path contains spaces (latest GNU/Linux GNOME client / LRC / daemon master).
How to reproduce:
1. Create/Rename a file so that its path contains one or more spaces
2. Try to drag & drop it in the chatview
3. Noth...Drag and drop fails when path contains spaces (latest GNU/Linux GNOME client / LRC / daemon master).
How to reproduce:
1. Create/Rename a file so that its path contains one or more spaces
2. Try to drag & drop it in the chatview
3. Nothing happens (expected: file transfer is initialized)
Logs:
* GNOME client / LRC
```
DataTransferModel::sendFile(), error
```
* daemon
```
[1530299596.914|27598|p2p.cpp :780 ] 0x62300000e110[CNX] aborted, no devices for a54f6250337f27f369af896fd5bbd13d80f2fe44
[1530299599.414|27598|data_transfer.cpp :689 ] [XFER] invalid filename '/home/hlefeuvre/Downloads/TEST%20STUFF/poultry-farm-chicken-500x500.jpg'
```Sébastien BlinSébastien Blin