jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2018-05-23T01:28:52Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/748Impossible d'installer Ring sur Ubuntu 16.042018-05-23T01:28:52ZJami BotImpossible d'installer Ring sur Ubuntu 16.04Issue generated from Tuleap's migration script.
**Originally submitted by: Frédéric Potvin (fpotvin)**
Lors de l'installation de Ring, en suivant les instructions de https://ring.cx/en/download/gnu-linux pour Ubuntu 16.04, lors de la co...Issue generated from Tuleap's migration script.
**Originally submitted by: Frédéric Potvin (fpotvin)**
Lors de l'installation de Ring, en suivant les instructions de https://ring.cx/en/download/gnu-linux pour Ubuntu 16.04, lors de la commande `sudo apt-get update`, une erreur est survenu.
Err:12 https://dl.ring.cx/ring-nightly/ubuntu\_16.04 ring/main amd64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: The repository 'https://dl.ring.cx/ring-nightly/ubuntu\_16.04 ring Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://dl.ring.cx/ring-nightly/ubuntu\_16.04/dists/ring/main/binary-amd64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
Le dépôt des binaires AMD 64 n'est donc pas téléchargé et je ne peux pas installer Ring.
▶ sudo apt-get install ring
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ring
Le log complet est attaché au billet.
[ring-failed-to-install.log](/uploads/c6295ec2b7186bb43c966cb6fdb6ac4b/ring-failed-to-install.log)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/755Ubuntu 14.04 - Mate desktop bugs2018-05-23T01:34:09ZJami BotUbuntu 14.04 - Mate desktop bugsIssue generated from Tuleap's migration script.
**Originally submitted by: Adil Karaöz (structi)**
I am using Ubuntu 14.04 with Mate Desktop. I don't use Unity. Ring notification icon is showing very big on my notification area. Also wh...Issue generated from Tuleap's migration script.
**Originally submitted by: Adil Karaöz (structi)**
I am using Ubuntu 14.04 with Mate Desktop. I don't use Unity. Ring notification icon is showing very big on my notification area. Also when I open the Ring application, I can't see any add friend or any related icon or button.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/756[Blockchain] Username not registering after account setting2018-05-23T01:35:11ZJami Bot[Blockchain] Username not registering after account settingIssue generated from Tuleap's migration script.
**Originally submitted by: Dorina Mosku (dmosku15)**
After installing Ring and registering a username on the blockchain, the actual username doesn't seem to be registered on the General Ac...Issue generated from Tuleap's migration script.
**Originally submitted by: Dorina Mosku (dmosku15)**
After installing Ring and registering a username on the blockchain, the actual username doesn't seem to be registered on the General Account Settings section.
See attached filehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/758GNOME: crashes on Wayland (fedora) when starting call2018-05-23T01:37:23ZJami BotGNOME: crashes on Wayland (fedora) when starting callIssue generated from Tuleap's migration script.
**Originally submitted by: m h (mhack)**
Ring GUI crashes whenever starting or receive a call on fedora 24, after the crash the webcame light stays active on my laptop and the call continu...Issue generated from Tuleap's migration script.
**Originally submitted by: m h (mhack)**
Ring GUI crashes whenever starting or receive a call on fedora 24, after the crash the webcame light stays active on my laptop and the call continues (audio and video continue to stream to the android client)
till the recipient or caller hangs up
[comandline_output](/uploads/faee63eb42247fefd015fdfe6257250f/comandline_output)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/761[GNOME] call doesnt shutdown on invite timeout2018-05-23T01:40:35ZJami Bot[GNOME] call doesnt shutdown on invite timeoutIssue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
When a call connection times out, the state showed to the user is still, "searching for".
Instead the call should be closed.
[tr...Issue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
When a call connection times out, the state showed to the user is still, "searching for".
Instead the call should be closed.
[trace.txt](/uploads/7167220f7ee1c697943953bec418a18d/trace.txt)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/762GNOME - Text does not appear in chat2018-05-23T01:42:03ZJami BotGNOME - Text does not appear in chatIssue generated from Tuleap's migration script.
**Originally submitted by: Steve Poandl (poandlsl)**
Using Ring on Fedora 25 (GNOME), I am unable to see text in the chat area. However, on the Windows build and Android build, all text f...Issue generated from Tuleap's migration script.
**Originally submitted by: Steve Poandl (poandlsl)**
Using Ring on Fedora 25 (GNOME), I am unable to see text in the chat area. However, on the Windows build and Android build, all text for the conversation appears.
Steps to reproduce:
1. Start a conversation with another Ring user
2. Observe no text in chat area
Result:
No text appears in chat area
Expected Result:
Text should appear in chat area
Frequency:
This happens for each run of Ring
Logs:
\*I am unsure which logs to attach\*
Ring version: ring-20170126.1.cd1aa0d-1.fc25.x86\_64
OS: Fedora 25 Workstation x64
![SS-RING_GNOME](/uploads/0e853feda744396ed3868936b967acad/SS-RING_GNOME.png)
![SS-RING_WINDOWS](/uploads/f196663688ab702d2a76cd94eab0051c/SS-RING_WINDOWS.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/763[Daemon] No video from correspondant2018-05-23T01:44:01ZJami Bot[Daemon] No video from correspondantIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Mention all details about the ...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Mention all details about the system/environment used (OS, version, build date, ...)
Peer 1
======
Build:
Ubuntu 16.04 package release date: 20170223
OS:
Ubuntu 16.04
Peer 2
======
Build:
Daemon git hash 72ee06ef4
LRC git hash: e124448
GNOME client hash: 6aa46d1
OS:
Debian Stretch
\* Reproduce steps:
Clearly mention the steps to reproduce the bug.
Peer 1 and peer 2 instantiate a call. Peer 1's video is not visible by peer 2 while peer 2's video is visible by peer 1. The log peer 2 has is shown in peer2.txt. This part of the log shows where peer 2 tries to mute camera, see the result and unmute the camera and see the result. Repeating this indefinitely wouldn't change a thing.
Finally, stopping the call and calling again did not trigger this bug. Therefore, it is not deterministically
reproducible.
\* Expected result:
How application should behave on the above mentioned steps.
Peer 1 and peer 2 see each other's video when both have its video unmuted.
[peer2.txt](/uploads/3023e727e038c7daebb8d6a3fee8565d/peer2.txt)
[log_video](/uploads/9fae86389b29e2dda63b12964183cfe8/log_video)Philippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/767Apple FacetimeHD Camera not detected (greyed out), Debian 9 Gnome2018-05-23T01:45:45ZJami BotApple FacetimeHD Camera not detected (greyed out), Debian 9 GnomeIssue generated from Tuleap's migration script.
**Originally submitted by: Pranav Vats (pranavats)**
<p>It appears that my Apple FacetimeHD (Broadcom 1570) camera is not being detected, the option to select a camera device and other set...Issue generated from Tuleap's migration script.
**Originally submitted by: Pranav Vats (pranavats)**
<p>It appears that my Apple FacetimeHD (Broadcom 1570) camera is not being detected, the option to select a camera device and other settings appear to be greyed out and is unclickable. This could be a problem with the driver, but other apps seem to work fine with the same driver (other apps include cheese, mplayer, kamerka camorama, enable viacam, easyscreencast), while one other app failed to detect it (QtQR). Since ring did not give much information about what went wrong, here is the output from mplayer :</p>
<blockquote>
<p>$ mplayer tv://<br />
MPlayer 1.3.0 (Debian), built with gcc-6.2.1 (C) 2000-2016 MPlayer Team<br />
do\_connect: could not connect to socket<br />
connect: No such file or directory<br />
Failed to open LIRC support. You will not be able to use your remote control.</p>
<p>Playing tv://.<br />
TV file format detected.<br />
Selected driver: v4l2<br />
name: Video 4 Linux 2 input<br />
author: Martin Olschewski <olschewski@zpr.uni-koeln.de><br />
comment: first try, more to come ;-)<br />
v4l2: your device driver does not support VIDIOC\_G\_STD ioctl, VIDIOC\_G\_PARM was used instead.<br />
Selected device: Apple Facetime HD<br />
Capabilities: video capture read/write streaming<br />
supported norms:<br />
inputs: 0 = Camera;<br />
Current input: 0<br />
Current format: YUYV<br />
tv.c: norm\_from\_string(pal): Bogus norm parameter, setting default.<br />
v4l2: ioctl enum norm failed: Inappropriate ioctl for device<br />
Error: Cannot set norm!<br />
Selected input hasn't got a tuner!<br />
v4l2: ioctl set mute failed: Invalid argument<br />
Failed to open VDPAU backend libvdpau\_i965.so: cannot open shared object file: No such file or directory<br />
[vdpau] Error when calling vdp\_device\_create\_x11: 1<br />
==========================================================================<br />
Opening video decoder: [raw] RAW Uncompressed Video<br />
Could not find matching colorspace - retrying with -vf scale...<br />
Opening video filter: [scale]<br />
Movie-Aspect is undefined - no prescaling applied.<br />
[swscaler @ 0x55d361563da0] bicubic scaler, from yuyv422 to yuv420p using MMXEXT<br />
[swscaler @ 0x55d361563da0] using unscaled yuyv422 -> yuv420p special converter<br />
VO: [xv] 640x480 => 640x480 Planar YV12<br />
Selected video codec: [rawyuy2] vfm: raw (RAW YUY2)<br />
==========================================================================<br />
Audio: no sound<br />
Starting playback...<br />
V: 0.0 70/ 70 ??% ??% ??,?% 0 0</p>
<p><br />
MPlayer interrupted by signal 2 in module: video\_read\_frame<br />
V: 0.0 71/ 71 ??% ??% ??,?% 0 0<br />
v4l2: ioctl set mute failed: Invalid argument<br />
v4l2: 71 frames successfully processed, -70 frames dropped.</p>
<p>Exiting... (Quit)</p>
</blockquote>
<p>Here is the source code of drivers I use (If there is something wrong you can see with the driver, please bring it to my notice, I would create an issue there.) : https://github.com/patjak/bcwc\_pcie</p>
<p>If there is any other information I can provide, please tell me how to collect it (running ring with --debug option doesn't help much since after the gui opens up, the command exits (prompt comes back), if it is supposed to provide debug info through ring itself, or some log file, please let me know.</p>
<p>\* Environment: Debian 9 Stretch testing, ring version - 1.0.0 - unknown,</p>
<p>\* Reproduce steps: The steps I performed were simply installing ring according to instructions on the website, and opened it. Installing and loading that FacetimeHD driver might or might not reproduce the problem (because I am not sure what exactly is causing this problem).</p>
<p>\* Expected result: It might or might not reproduce the bug, in my case, it does. (The cause is unknown for now)</p>
<p>\* Actual result: The bug is reproduced.</p>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/768SIP: Can't answer calls on gnome client (Can't find where should click)2018-05-23T01:46:28ZJami BotSIP: Can't answer calls on gnome client (Can't find where should click)Issue generated from Tuleap's migration script.
**Originally submitted by: TurBoss (turboss)**
Hello
I'm on ubuntu 16.10 using the gnome-client
I have configured my own SIP account but when I receive a call I can't find where...Issue generated from Tuleap's migration script.
**Originally submitted by: TurBoss (turboss)**
Hello
I'm on ubuntu 16.10 using the gnome-client
I have configured my own SIP account but when I receive a call I can't find where i should click to answer ( Nothing is shown , I can only ear the ring tone )
is this a bug or I'm missing something?
Thankshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/769Ring crashes on start from GDB2018-05-23T01:47:05ZJami BotRing crashes on start from GDBIssue generated from Tuleap's migration script.
**Originally submitted by: Tirifto (Tirifto)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Fedora 25 (XFCE spin, Linux-libre kerne...Issue generated from Tuleap's migration script.
**Originally submitted by: Tirifto (Tirifto)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Fedora 25 (XFCE spin, Linux-libre kernel)
Ring Beta 2, built 2017-06-15 (git ref: f109fd3c7d78f90badf9477540c95752b5847257)
\* Reproduce steps:
gdb gnome-ring
run
\* Expected result:
Ring starts up normally and I can carry out the steps needed to reproduce a bug I'm trying to trace. This works when starting outside of GDB.
\* Actual result:
Ring crashes right away, the window left unresponsive. I tried getting a trace (which I'm attaching as trace.log) and then I quit gdb.
[trace.log](/uploads/b5e5f0b056aa9f341dfa80ac522f86e9/trace.log)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/702Webcam is not detected2018-05-26T19:39:07ZJami BotWebcam is not detectedIssue generated from Tuleap's migration script.
**Originally submitted by: rugk (rugk)**
In my case the (built-in-)webcam is not detected.
\* Environment:
Fedora 26, GNOME
v1.0
\* Reproduce steps:
Go into the settings...Issue generated from Tuleap's migration script.
**Originally submitted by: rugk (rugk)**
In my case the (built-in-)webcam is not detected.
\* Environment:
Fedora 26, GNOME
v1.0
\* Reproduce steps:
Go into the settings -> Media.
\* Expected result:
Detect and offer webcam.
\* Actual result:
The fields for webcams are greyed out in the settings. There is a black "image" on the right side.
BTW Cheesy (preinstalled app under GNOME) does detect my webcam. Same as Firefox with WebRTC.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/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/713[GNOME] Remove Device, Rename Device and Update Device Name2018-06-11T23:15:34ZJami Bot[GNOME] Remove Device, Rename Device and Update Device NameIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
1. Click "Settings" button
2. Click "Accounts"
3. Click on account
4. Click on "Devices" tab
5. Click on a device shown in the list
Sug...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
1. Click "Settings" button
2. Click "Accounts"
3. Click on account
4. Click on "Devices" tab
5. Click on a device shown in the list
Suggestions:
a) Please add a "Remove device" button
b) Please add a "Rename device" button
c) When no device is selected, the "Remove device" and "Rename device" buttons should be grayed out, i.e. disabled
Reinstalling GNOME of a fresh install creates many device listing for the same computer. This feature will help remove duplicates.
Please note that the Rename device and Remove device are available in the Android version of Ring.
Suggestion:
d) When an Android device is renamed, the updated Android name should show in the GNOME version of Ring.
What do you think?
Thank youGnome 2018.07.15Sé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/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/742GNOME Ring segfaults on startup after muting audio during call2018-07-06T15:57:31ZJami BotGNOME Ring segfaults on startup after muting audio during callIssue generated from Tuleap's migration script.
**Originally submitted by: Jonathan Frederickson (jfred)**
\* Environment:
Fedora 27, Ring GNOME client version: 1.0.0
\* Reproduce steps:
Call an audio-only SIP number, mute and ...Issue generated from Tuleap's migration script.
**Originally submitted by: Jonathan Frederickson (jfred)**
\* Environment:
Fedora 27, Ring GNOME client version: 1.0.0
\* Reproduce steps:
Call an audio-only SIP number, mute and unmute video while in-call, then attempt to mute audio.
\* Expected result:
Local audio should be muted.
\* Actual result:
Ring client crashes, and segfaults upon further attempt to start the client. Call continues in the background.
```
[jfred@terracard \~]$ ring.cx
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: unknown
(gnome-ring:10364): Gtk-WARNING **: GtkGrid does not have a child property called expand
(gnome-ring:10364): Gtk-WARNING **: GtkGrid does not have a child property called fill
(gnome-ring:10364): 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() ?)
/usr/bin/ring.cx: line 46: 10364 Segmentation fault (core dumped) gnome-ring $*
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/736Not adding an account breaks ring2018-07-06T15:59:21ZJami BotNot adding an account breaks ringIssue generated from Tuleap's migration script.
**Originally submitted by: Nat Tuck (nattuck)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ubuntu 16.04 under Gnome 3
\* Rep...Issue generated from Tuleap's migration script.
**Originally submitted by: Nat Tuck (nattuck)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ubuntu 16.04 under Gnome 3
\* Reproduce steps:
- Fresh install
- Add an existing account
- Press the add account button again
- Change account type to SIP
\* Expected result:
- The app doesn't crash and corrupt its own config.
\* Actual result:
- The app crashes and can't restart.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/775GNOME client crash when starting call2018-07-06T16:00:34ZJami BotGNOME client crash when starting callIssue generated from Tuleap's migration script.
**Originally submitted by: Anthony Léonard (aleonard)**
How to reproduce :
- Type a ringID (without “ring:” prefix) in the search bar
- Double click on the temporary item or click on c...Issue generated from Tuleap's migration script.
**Originally submitted by: Anthony Léonard (aleonard)**
How to reproduce :
- Type a ringID (without “ring:” prefix) in the search bar
- Double click on the temporary item or click on call button in conversation view
- Boom !
It may be not necessary to omit the “ring:” prefix but it is the way it happened on my machine.
Double clicking in conversation list or clicking on call button in conversation panel gives backtraces with little differences.
[backtrace.txt](/uploads/80175533084798c6af64105dfe6d5dca/backtrace.txt)Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/848smartlist: invitation tab disappears when switching account2018-07-09T13:56:17ZHugo Lefeuvresmartlist: invitation tab disappears when switching accountGNU/Linux GNOME client, latest master.
**How to reproduce:**
You need a client with at least two accounts A and B. First account is A.
1. Using a third account C on another device, send an invitation to B.
2. Make sure invitation arri...GNU/Linux GNOME client, latest master.
**How to reproduce:**
You need a client with at least two accounts A and B. First account is A.
1. Using a third account C on another device, send an invitation to B.
2. Make sure invitation arrived.
3. Switch to account A.
4. Switch back to account B. Now the invitation tab does not appear anymore. Instead you will only see a fat, ugly conversations tab.
Note: The invitation tab pops back when using the search bar.Gnome 2018.07.15Sébastien BlinSébastien Blin