jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2018-05-22T00:37:13Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/607Ring daemon RPM package creation error: Program returns random data in a func...2018-05-22T00:37:13ZJami BotRing daemon RPM package creation error: Program returns random data in a functionIssue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>Creation of RPM package is not possible because Ring daemon has a specific type of warning (return-type) which halts RPM creation proced...Issue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>Creation of RPM package is not possible because Ring daemon has a specific type of warning (return-type) which halts RPM creation procedure. The warning is:</p>
<pre>
[ 212s] ringaccount.cpp: In function 'std::string ring::Migration::mapStateNumberToString(ring::Migration::State)':
[ 212s] ringaccount.cpp:101:1: warning: control reaches end of non-void function [-Wreturn-type]
[ 212s] }
[ 212s] \^
[ ... ]
[ 325s] I: Program returns random data in a function
[ 325s] E: ring-daemon no-return-in-nonvoid-function ringaccount.cpp:101
[ 325s]
[ 325s] lamb25 failed "build ring-daemon.spec" at Mon Feb 13 06:54:21 UTC 2017.</pre>
<p>If possible, please compile all Ring modules with -Werror=return-type to halt the compilation in the second when this type of warning gets in the code because the RPM build system won't let this package to be made.</p>https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/605[gnome] messages randomly appear on (un)focus of chat window2018-05-22T00:37:07ZJami Bot[gnome] messages randomly appear on (un)focus of chat windowIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
Run ring, then
1. Focus on some contact \*A\* in the contact list to make text messages for that contact appear.
2. Notice that...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
Run ring, then
1. Focus on some contact \*A\* in the contact list to make text messages for that contact appear.
2. Notice that some message are missing.
3. Focus on another contact so that the chat window of A disappears.
4. Focus back and notice that some messages have appeared and others (may) have disappeared
Repeat (3) and (4) continuously.
VERSIONS
Daemon: 50d61c300
LRC: b220f82
Gnome client: f2b8badhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/595During account migration, previously used user name cannot be used2018-05-22T00:36:35ZJami BotDuring account migration, previously used user name cannot be usedIssue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
-------
After an upgrade to the latest Ring snapshot (2017-01-20), an account migration dialog appears. In this dialog,...Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
-------
After an upgrade to the latest Ring snapshot (2017-01-20), an account migration dialog appears. In this dialog, the user must enter a password to encrypt the account and choose a user name. However, the user cannot choose the user name he/she had before the migration, forcing the user to either choose a new user name of skip the migration continually.
Steps to reproduce
------------------
1. Have an old Ring account (a 2016 account should work)
2. Upgrade Ring to version 2017-01-20
3. Start Ring
4. In the account migration wizard, enter a password (the wizard does not indicate whether the password must be new or if the old one must be used)
5. Enter the account's user name as a the user name
Current behavior
----------------
Ring will indicate that the user name has been used and cannot be chosen. The user can skip this part of the migration and Ring's UI will appear. However, it is not clear whether the migration was indeed successful. Moreover, restarting Ring can cause the migration dialog to appear.
Expected behavior
-----------------
It is unclear if preventing the user from picking his old user name is intended behavior.
Tested platforms
----------------
\* Ubuntu GNOME 16.04
\* Gentoo AMD64 (ring-overlay)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/594During account migration, wizard cannot be skipped2018-05-22T00:36:34ZJami BotDuring account migration, wizard cannot be skippedIssue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
-------
After an upgrade to the latest Ring snapshot (2017-01-20), a dialog appears, prompting for an account migration...Issue generated from Tuleap's migration script.
**Originally submitted by: Nicolas Juneau (njuneau)**
Summary
-------
After an upgrade to the latest Ring snapshot (2017-01-20), a dialog appears, prompting for an account migration. The dialog indicates the user that he/she can skip the migration by closing Ring and re-opening it. However, doing this procedure does not work. Re-opening Ring will bring back the account migration wizard.
Steps to reproduce
------------------
1. Have an account that is old enough to be migrated (a 2016 account should work)
2. Upgrade the Ring version to 2017-01-20
3. The migration dialog appears, indicating that the account migration can either be done or skipped by restarting Ring
4. Do not perform the migration
5. Restart Ring
Current behavior
----------------
Account migration dialog re-appears
Expected behavior
-----------------
Account migration should not appear, as per the instructions of the dialog.
Tested platforms
----------------
\* Ubuntu GNOME 16.04
\* Gentoo AMD64 (ring-overlay)https://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/584ringID/account not linked with any device2018-05-22T00:36:08ZJami BotringID/account not linked with any deviceIssue generated from Tuleap's migration script.
**Originally submitted by: Oh Dear (bostontea)**
On Ubuntu 16.04 LTS, I installed Ring as described via command line, created an account and a username (capital characters and numbers, not...Issue generated from Tuleap's migration script.
**Originally submitted by: Oh Dear (bostontea)**
On Ubuntu 16.04 LTS, I installed Ring as described via command line, created an account and a username (capital characters and numbers, nothing else) and registered it on the blockchain, and selected an avatar. My ID was then written on the welcome window, so still normal. However, I didn't have any contacts to call, so I simply closed it again (after writing myself and then deleting history, maybe that was a bad idea).
When I started Ring the next day, Ring behaved like I hadn't made an account, my chosen username is blocked if I want to make a new one with it, and I can't reconnect my account (which wouldn't be such a problem if I didn't really want the username, or really would be a problem if I already had had conversations). I still have all my account data (ID, name, password) written down, and I can find them except the password in the namecache folder also, but there is no way to reconnect my programme with my account, it seems, as I can't add a new device and so can't enter the PIN I would get. The only thing I can still find in my settings is my avatar, in the accounts tab nothing is listed.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/575Long messages are not displayed2018-05-22T00:35:53ZJami BotLong messages are not displayedIssue generated from Tuleap's migration script.
**Originally submitted by: Jean-Philippe Gélinas (yakoi)**
As a chat user,
When I write a chat message longer than 115 characters,,
When I hit 'send'
Nothing happens, Nothing is disp...Issue generated from Tuleap's migration script.
**Originally submitted by: Jean-Philippe Gélinas (yakoi)**
As a chat user,
When I write a chat message longer than 115 characters,,
When I hit 'send'
Nothing happens, Nothing is displayed as if nothing was sent. No feedback, no error, no message.
The receiver contact sometimes receives the message anyway (even if it does not appear to be sent on the sender side)
for even longer messages, receiver also sees nothing as if no message was sent at all.
Expected: Message is displayed as 'Sent' on the sender side. Message appears on the receiver side.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/571old \~/.config/ring/dring.yml causes various dysfunction2018-05-22T00:35:44ZJami Botold \~/.config/ring/dring.yml causes various dysfunctionIssue generated from Tuleap's migration script.
**Originally submitted by: max r.d. parmer (maxp)**
<p>Just upgraded {libringclient,ring-daemon,gnome-ring}-20161109.2 to {libringclient,ring-daemon,gnome-ring}-20161116.1 and experienced ...Issue generated from Tuleap's migration script.
**Originally submitted by: max r.d. parmer (maxp)**
<p>Just upgraded {libringclient,ring-daemon,gnome-ring}-20161109.2 to {libringclient,ring-daemon,gnome-ring}-20161116.1 and experienced some issues, terminal logs below:</p>
<blockquote>
<p>% gnome-ring <br />
\*\* Message: Ring GNOME client version: 1.0.0<br />
\*\* Message: git ref: unknown<br />
"Error : dring is not available, make sure it is running"<br />
<br />
\*\* (gnome-ring:19954): CRITICAL \*\*: Error : dring is not available, make sure it is running<br />
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.</p>
<p>% /usr/lib/ring/dring<br />
Ring Daemon 3.0.0, by Savoir-faire Linux 2004-2016<br />
http://www.ring.cx/<br />
[Video support enabled]<br />
<br />
12:14:13.594 os\_core\_unix.c !pjlib 2.5.5 for POSIX initialized<br />
One does not simply initialize the DBus client: cannot initialize libring</p>
</blockquote>
<p>This was resolved via rm of \~/.config/ring/dring.yml (unfortunately, I did not expect it to work, so I did not preserve the problematic dring.yml).</p>https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/565Ring doesn't specify dbus daemon as a dependency2018-05-22T00:35:19ZJami BotRing doesn't specify dbus daemon as a dependencyIssue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
On Debian 9 with upstart without dbus, I installed the ring package as instructed at https://ring.cx/en/download/gnu-linux but ru...Issue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
On Debian 9 with upstart without dbus, I installed the ring package as instructed at https://ring.cx/en/download/gnu-linux but running `ring.cx` in terminal returns an error that the ring daemon is not running.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/564dring: invalid opcode2018-05-22T00:35:14ZJami Botdring: invalid opcodeIssue generated from Tuleap's migration script.
**Originally submitted by: Gernot Tenchio (gernot)**
What i have done:
1. Initiate a call
2. Connection gets established
3. The remote end accepts the incomming call
4. The came...Issue generated from Tuleap's migration script.
**Originally submitted by: Gernot Tenchio (gernot)**
What i have done:
1. Initiate a call
2. Connection gets established
3. The remote end accepts the incomming call
4. The camera light flashes for a short time
5. dring receives SIGILL and crashes
dmesg shows the following:
[ 278.714925] traps: dring[1959] trap invalid opcode ip:c18837 sp:7f820c25ac90 error:0 in dring[400000+af2000]
Package: ring-20161109.2.6f76da7-1.fc24.x86\_64
OS: Fedora release 24 (Twenty Four)
Linux 4.8.6-201.fc24.x86\_64 \#1 SMP
Camera: Logitech, Inc. Webcam C270
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Graphics: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/552WebKitWebProcess using high CPU2018-05-22T00:34:31ZJami BotWebKitWebProcess using high CPUIssue generated from Tuleap's migration script.
**Originally submitted by: Ross (rossington)**
On debian stretch using latest nightly ring, since upgrading to Ring beta 2, the new chat rendering seems to cause 'WebKitWebProcess' to use ...Issue generated from Tuleap's migration script.
**Originally submitted by: Ross (rossington)**
On debian stretch using latest nightly ring, since upgrading to Ring beta 2, the new chat rendering seems to cause 'WebKitWebProcess' to use a high amount of CPU and slow down the system. Sometimes even when chat is not shown, or ring window is closed it continues.
This has occurred on two different hardware systems.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/551ring-daemon fails to build2018-05-22T00:34:22ZJami Botring-daemon fails to buildIssue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
<p>Trying to compile the latest version of ring-daemon fails with:</p>
<pre>
make[4]&nbsp;: on quitte le r&eacute;pertoire &...Issue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
<p>Trying to compile the latest version of ring-daemon fails with:</p>
<pre>
make[4] : on quitte le répertoire « /build/ring-daemon-git/src/ring-daemon/src/ringdht/eth/libdevcrypto »
make[4] : on entre dans le répertoire « /build/ring-daemon-git/src/ring-daemon/src/ringdht »
CXX libringacc\_la-ringaccount.lo
CXX libringacc\_la-sip\_transport\_ice.lo
CXX libringacc\_la-sips\_transport\_ice.lo
CXX libringacc\_la-namedirectory.lo
namedirectory.cpp: Dans la fonction ‘size\_t ring::getContentLength(restbed::Response&)’:
namedirectory.cpp:98:46: erreur : valeur void n'a pas été ignorée comme elle aurait dû l'être
reply.get\_header("Content-Length", length);
\^
make[4]: \*\*\* [Makefile:589: libringacc\_la-namedirectory.lo] Error 1</pre>
<p>Versions used:</p>
<ul>
<li>ring-daemon: 65d5661d047e4d344dd8ecdb9e92bad42e46ffd4</li>
<li>restbed: 4.0</li>
<li>opendht: b5cd6291601ea0844bca8581190858bd8e61f22a</li>
</ul>
<p>This is on Archlinux x86\_64.</p>https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/550Illegal instruction on Bay Trail using official binary2018-05-22T00:34:20ZJami BotIllegal instruction on Bay Trail using official binaryIssue generated from Tuleap's migration script.
**Originally submitted by: planetguy (planetguy)**
I'm using Ubuntu in a chroot on my Bay Trail chromebook. I installed the official Ring binaries from the repository. Opening the Ring GUI...Issue generated from Tuleap's migration script.
**Originally submitted by: planetguy (planetguy)**
I'm using Ubuntu in a chroot on my Bay Trail chromebook. I installed the official Ring binaries from the repository. Opening the Ring GUI says something like "dring is not running". I tried running dring directly, but it immediately got SIGILL and exited. Running dring in Valgrind gives the address as "0x22B8F3", and "C4 E2 7B F7 44 24 10 83" as the bytes responsible. Running dring on a Core 2 Duo system gives the same results.
A disassembler says that it's the "shrx" instruction, which is not available except on Haswell or newer CPUs. Is Ring intended to require very new CPUs?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/536Ring account creation doesn't work2018-05-22T00:33:53ZJami BotRing account creation doesn't workIssue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>Because of an exception in ring-daemon I deleted dring.yml, that's why I had to create a new Ring account to acces the SIP functionality...Issue generated from Tuleap's migration script.
**Originally submitted by: szotsaki (szotsaki)**
<p>Because of an exception in ring-daemon I deleted dring.yml, that's why I had to create a new Ring account to acces the SIP functionality.</p>
<p>First, I started dring with debug options:</p>
<pre>
$>SIPLOGLEVEL=8 /usr/lib64/ring/dring
Ring Daemon 2.3.0, by Savoir-faire Linux 2004-2016
http://www.ring.cx/
[Video support enabled]
15:24:25.112 os\_core\_unix.c !pjlib 2.5.5 for POSIX initialized
15:24:41.577 sip\_endpoint.c Creating endpoint instance...
15:24:41.577 pjlib epoll I/O Queue created (0x1253010)
15:24:41.577 sip\_endpoint.c Module "mod-msg-print" registered
15:24:41.577 sip\_transport. Transport manager created.</pre>
<p>In the Gnome client when I choose Create new account, it fails with an error message on the GUI (Error creating/loading account).</p>
<p>In the console I see:</p>
<pre>
\*\* Message: Ring GNOME client version: 1.0.0
\*\* Message: git ref: unknown
Updating all accounts
Loading vcf from: QDir( "/home/aki/.local/share/gnome-ring/profiles" , nameFilters = { "\*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters( Dirs|Files|Drives|AllEntries ) )
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkAlignment:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkAlignment:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkEntry:primary-icon-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
(gnome-ring:7482): Gtk-WARNING \*\*: gtkwidget.c:8554: widget not within a GtkWindow
(gnome-ring:7482): Gtk-WARNING \*\*: gtkwidget.c:8554: widget not within a GtkWindow
(gnome-ring:7482): Gtk-WARNING \*\*: gtkwidget.c:8554: widget not within a GtkWindow
(gnome-ring:7482): Gtk-WARNING \*\*: gtkwidget.c:8554: widget not within a GtkWindow
(gnome-ring:7482): Gtk-WARNING \*\*: gtkwidget.c:8554: widget not within a GtkWindow
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkWidget:margin-left is deprecated and shouldn't be used anymore. It will be removed in a future version.
<strong>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() ?)
Invalid current audio plugin</strong>
Selection changed 0
Selection changed 0
Building an account from alias: "test-account-3"
Account parameter " "Account.alias" " not found
Account parameter " "Account.username" " not found
Account parameter " "TLS.password" " not found
Account parameter " "Account.type" " not found
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will be removed in a future version.
(gnome-ring:7482): GLib-GObject-WARNING \*\*: The property GtkAlignment:top-padding is deprecated and shouldn't be used anymore. It will be removed in a future version.
Account parameter " "Account.routeset" " not found
Account parameter " "Account.mailbox" " not found
Account parameter " "Account.autoAnswer" " not found
Account parameter " "Account.upnpEnabled" " not found
Account parameter " "Account.dtmfType" " not found
Account parameter " "Account.videoEnabled" " not found
Account parameter " "Account.registrationExpire" " not found
Account parameter " "TLS.enable" " not found
Account parameter " "Account.localPort" " not found
Account parameter " "Account.publishedSameAsLocal" " not found
Account parameter " "Account.publishedAddress" " not found
Account parameter " "Account.publishedPort" " not found
Account parameter " "STUN.enable" " not found
Account parameter " "STUN.server" " not found
Account parameter " "TURN.enable" " not found
Account parameter " "TURN.server" " not found
Account parameter " "TURN.username" " not found
Account parameter " "TURN.password" " not found
Account parameter " "TURN.realm" " not found
Account parameter " "Account.audioPortMin" " not found
Account parameter " "Account.audioPortMax" " not found
Account parameter " "Account.videoPortMin" " not found
Account parameter " "Account.videoPortMax" " not found
Account parameter " "SRTP.enable" " not found
Account parameter " "SRTP.keyExchange" " not found
Account parameter " "SRTP.rtpFallback" " not found
Account parameter " "TLS.certificateListFile" " not found
Account parameter " "TLS.certificateFile" " not found
Account parameter " "TLS.method" " not found
Account parameter " "TLS.serverName" " not found
Account parameter " "TLS.negotiationTimeoutSec" " not found
Account parameter " "TLS.ciphers" " not found
Account parameter " "TLS.verifyServer" " not found
Account parameter " "TLS.verifyClient" " not found
Account parameter " "TLS.requireClientCertificate" " not found
Account parameter " "Account.deviceID" " not found
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Saving profile in: "/home/aki/.local/share/gnome-ring/profiles/1466802808750.vcf"
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Error : getting AccountId of a new account.
Account not configured
Setting accountId = ""
Adding the new account to the account list ( "Message did not receive a reply (timeout by message bus)" )
Unknown registration state ""
<strong>Saving profile in: "/home/aki/.local/share/gnome-ring/profiles/1466802808750.vcf"</strong></pre>
<p>The content of the aforementioned file is:</p>
<pre>
BEGIN:VCARD
VERSION:2.1
UID:1466802808750
FN:test-account-3
X-RINGACCOUNTID:a67b376b942ef87c
X-RINGACCOUNTID:fdd2ebb3e6f651a9
<strong>X-RINGACCOUNTID:Message did not receive a reply (timeout by message bus)</strong>
X-RINGACCOUNTID:Message did not receive a reply (timeout by message bus)
X-RINGACCOUNTID:Message did not receive a reply (timeout by message bus)
PHOTO;ENCODING=BASE64;TYPE=PNG:
END:VCARD</pre>
<p>In Ring Daemon I see only the following:</p>
<pre>
quitting: VoipLinkException occurred: pjsip\_endpt\_create\_resolver(endpt\_, &resv) failed
</pre>https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/534DAEMON: abort due to assert in pulseaudio2018-05-22T00:33:49ZJami BotDAEMON: abort due to assert in pulseaudioIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I get this ocasionally when the peer hangs up the call. Its been reported to possibly happen when the video device is changed...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I get this ocasionally when the peer hangs up the call. Its been reported to possibly happen when the video device is changed as well.</p>
<p> </p>
<pre>
[1476901614.147|29849|sipvoiplink.cpp:801 ] [call:6867938391286618547] INVITE@0x1d52258 state changed to 5 (CONFIRMED): unwaited event type 3
[1476901614.148|29849|videomanager.cpp:80 ] Setting default device to Integrated Camera
Assertion 'pa\_atomic\_load(&(b)->\_ref) > 0' failed at pulsecore/memblock.c:628, function pa\_memblock\_unref(). Aborting.
[New Thread 0x7fffcb7fd700 (LWP 29874)]
[New Thread 0x7fffca7fb700 (LWP 29903)]
[New Thread 0x7fffcf7fe700 (LWP 29902)]
[New Thread 0x7fffe5be7700 (LWP 29900)]
[New Thread 0x7fffe77fe700 (LWP 29883)]
[New Thread 0x7fffeda05700 (LWP 29882)]
[New Thread 0x7fffcbffe700 (LWP 29866)]
[New Thread 0x7fffe4be5700 (LWP 29865)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffcb7fd700 (LWP 29874)]
0x00007ffff2e719c8 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install alsa-lib-1.0.29-1.fc22.x86\_64 bzip2-libs-1.0.6-14.fc22.x86\_64 dbus-c++-0.9.0-8.fc22.x86\_64 dbus-libs-1.8.20-1.fc22.x86\_64 elfutils-libelf-0.166-1.fc22.x86\_64 elfutils-libs-0.166-1.fc22.x86\_64 expat-2.1.1-2.fc22.x86\_64 flac-libs-1.3.1-5.fc22.x86\_64 gsm-1.0.13-12.fc22.x86\_64 json-c-0.12-5.fc22.x86\_64 libasyncns-0.8-8.fc22.x86\_64 libattr-2.4.47-10.fc22.x86\_64 libcap-2.24-7.fc22.x86\_64 libdrm-2.4.61-3.fc22.x86\_64 libgcc-5.3.1-6.fc22.x86\_64 libgcrypt-1.6.3-4.fc22.x86\_64 libgpg-error-1.21-1.fc22.x86\_64 libICE-1.0.9-2.fc22.x86\_64 libogg-1.3.2-2.fc22.x86\_64 libsamplerate-0.1.8-7.fc22.x86\_64 libselinux-2.3-10.fc22.x86\_64 libSM-1.2.2-2.fc22.x86\_64 libsndfile-1.0.25-18.fc22.x86\_64 libstdc++-5.3.1-6.fc22.x86\_64 libupnp-1.6.19-3.fc22.x86\_64 libuuid-2.26.2-4.fc22.x86\_64 libva-1.5.1-1.fc22.x86\_64 libvorbis-1.3.4-3.fc22.x86\_64 libX11-1.6.3-1.fc22.x86\_64 libXau-1.0.8-4.fc22.x86\_64 libxcb-1.11-8.fc22.x86\_64 libXext-1.3.3-2.fc22.x86\_64 libXfixes-5.0.1-4.fc22.x86\_64 libXi-1.7.4-2.fc22.x86\_64 libXtst-1.2.2-4.fc22.x86\_64 nss-mdns-0.10-15.fc22.x86\_64 opus-1.1.2-1.fc22.x86\_64 pcre-8.39-2.fc22.x86\_64 pulseaudio-libs-6.0-8.fc22.x86\_64 speex-1.2-0.23.rc2.fc22.x86\_64 speexdsp-1.2-0.5.rc3.fc22.x86\_64 systemd-libs-219-27.fc22.x86\_64 tcp\_wrappers-libs-7.6-80.fc22.x86\_64 xz-libs-5.2.0-2.fc22.x86\_64 yaml-cpp-0.5.1-6.fc22.x86\_64 zlib-1.2.8-7.fc22.x86\_64
(gdb) bt
\#0 0x00007ffff2e719c8 in raise () from /lib64/libc.so.6
\#1 0x00007ffff2e7365a in abort () from /lib64/libc.so.6
\#2 0x00007ffff27c13f8 in pa\_memblock\_unref () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
\#3 0x00007ffff27c2acf in pa\_memexport\_process\_release () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
\#4 0x00007ffff27ca6da in do\_read () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
\#5 0x00007ffff27ccc64 in do\_pstream\_read\_write () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
\#6 0x00007ffff7040087 in pa\_mainloop\_dispatch () from /lib64/libpulse.so.0
\#7 0x00007ffff704048c in pa\_mainloop\_iterate () from /lib64/libpulse.so.0
\#8 0x00007ffff7040530 in pa\_mainloop\_run () from /lib64/libpulse.so.0
\#9 0x00007ffff704e676 in thread () from /lib64/libpulse.so.0
\#10 0x00007ffff27dc6a8 in internal\_thread\_func () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
\#11 0x00007ffff4eba555 in start\_thread () from /lib64/libpthread.so.0
\#12 0x00007ffff2f3fded in clone () from /lib64/libc.so.6
(gdb) bt full
\#0 0x00007ffff2e719c8 in raise () from /lib64/libc.so.6
No symbol table info available.
\#1 0x00007ffff2e7365a in abort () from /lib64/libc.so.6
No symbol table info available.
\#2 0x00007ffff27c13f8 in pa\_memblock\_unref () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
No symbol table info available.
\#3 0x00007ffff27c2acf in pa\_memexport\_process\_release () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
No symbol table info available.
\#4 0x00007ffff27ca6da in do\_read () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
No symbol table info available.
\#5 0x00007ffff27ccc64 in do\_pstream\_read\_write () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
No symbol table info available.
\#6 0x00007ffff7040087 in pa\_mainloop\_dispatch () from /lib64/libpulse.so.0
No symbol table info available.
\#7 0x00007ffff704048c in pa\_mainloop\_iterate () from /lib64/libpulse.so.0
No symbol table info available.
\#8 0x00007ffff7040530 in pa\_mainloop\_run () from /lib64/libpulse.so.0
No symbol table info available.
\#9 0x00007ffff704e676 in thread () from /lib64/libpulse.so.0
No symbol table info available.
\#10 0x00007ffff27dc6a8 in internal\_thread\_func () from /usr/lib64/pulseaudio/libpulsecommon-6.0.so
No symbol table info available.
\#11 0x00007ffff4eba555 in start\_thread () from /lib64/libpthread.so.0
No symbol table info available.
\#12 0x00007ffff2f3fded in clone () from /lib64/libc.so.6
No symbol table info available.
</pre>
<p> </p>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/532[GNOME] client crash when migrating beta1 account2018-05-22T00:36:10ZJami Bot[GNOME] client crash when migrating beta1 accountIssue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
<ul>
<li><strong>Overview</strong>
<ul>
<li>when launching the account migration procedure the client crashes, when you re...Issue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
<ul>
<li><strong>Overview</strong>
<ul>
<li>when launching the account migration procedure the client crashes, when you restart the client the account is migrated</li>
</ul>
</li>
<li><strong>Steps</strong>
<ul>
<li>launch beta1 version to create an account</li>
<li>launch beta2 to trigger account migration</li>
<li>try to migrate and crash</li>
</ul>
</li>
<li><strong>Result</strong> (vs. expected result)
<ul>
<li>the account is migrated but the client crashes (same with no crash)</li>
<li>on restart everything is fine</li>
</ul>
</li>
<li><strong>Frequency</strong>
<ul>
<li>always</li>
</ul>
</li>
<li><strong>Logs</strong>
<ul>
<li>(gnome-ring:13734): GLib-GObject-CRITICAL \*\*: g\_type\_instance\_get\_private: assertion 'instance != NULL && instance->g\_class != NULL' failed Erreur de segmentation (core dumped)</li>
</ul>
</li>
</ul>https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/528GNOME: Imposibe to deconnect device from RingID2018-05-22T00:33:41ZJami BotGNOME: Imposibe to deconnect device from RingIDIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
In Linux there are no possibility to remove device from RingID once it have been connected.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
In Linux there are no possibility to remove device from RingID once it have been connected.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/526[multi-device][GNOME] account migration fail with device not listed2018-05-22T00:33:39ZJami Bot[multi-device][GNOME] account migration fail with device not listedIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
I did have two accounts to migrate. The first one did fine and I can see the list of devices listed for that account.
The secon...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
I did have two accounts to migrate. The first one did fine and I can see the list of devices listed for that account.
The second seems to have migrated, but when I look at the devices list (Settings>Accounts>My Account>Devices), the list is empty.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/523GNOME: Impossible to create conference call2018-05-22T00:33:34ZJami BotGNOME: Impossible to create conference callIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Impossible to create conference, drag&drop does not work.
version:v1.0.0 - boffc34a2eIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Impossible to create conference, drag&drop does not work.
version:v1.0.0 - boffc34a2ehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/511No window pops-up when someone call2018-05-22T00:33:12ZJami BotNo window pops-up when someone callIssue generated from Tuleap's migration script.
**Originally submitted by: tino13 (tino13)**
Hi,
I'm on Linux Ubuntu 14.04LTS with Unity and using a SIP account. Ring is running on my PC (launched at start), I can see it in the systra...Issue generated from Tuleap's migration script.
**Originally submitted by: tino13 (tino13)**
Hi,
I'm on Linux Ubuntu 14.04LTS with Unity and using a SIP account. Ring is running on my PC (launched at start), I can see it in the systray and my account is OK. When someone calls me, I can hear the bell but the Ring window does not pop up, so I can't take the call ! Clicking on the systray icon show the standard window (history, contacts...) but there's no button here to take the call. The bell continues even when the caller hang up! I have to kill Ring to stop the bell. This bug is not systematic, sometimes it works ... seems to be random.
Thanks for your support.