savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-11-20T13:19:54Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1223Chat between two linux gnome jami not working2020-11-20T13:19:54ZJürgen LütersChat between two linux gnome jami not workingHallo,
i have two debian - testing systems.
systema intel nuc
systemb thinkpad x1 first generation
Chat does not work properly
after typing one or two characters, gui does not react any longer.
However after pressing the return key the...Hallo,
i have two debian - testing systems.
systema intel nuc
systemb thinkpad x1 first generation
Chat does not work properly
after typing one or two characters, gui does not react any longer.
However after pressing the return key the message gets delivered to system a.
Messages sent form system a do not show up in systemb chat window.
**From jami-systemb.log**
ov 20 12:03:02 x1rover jami-gnome.desktop[5689]: No migration required
Nov 20 12:03:02 x1rover jami-gnome[5689]: Child name 'calls' not found in GtkStack
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:02 x1rover jami-gnome[5689]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 20 12:03:03 x1rover jami-gnome.desktop[5689]: QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call begin
Structure() ?)
Nov 20 12:03:03 x1rover jami-gnome.desktop[5689]: QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructur
e() ?)
Nov 20 12:03:03 x1rover jami-gnome.desktop[5689]: QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call
beginStructure() ?)
Nov 20
[jami-jami-systema.log](/uploads/bab67ba7712ae15aa75d0cb184a12eee/jami-jami-systema.log)
[jami-jami-systemb.log](/uploads/f9cfd33b5ad3c0621eb561ee965e483e/jami-jami-systemb.log)
[jami-lsb-systema.log](/uploads/3843fc9ba3678226bdb70eef7d940df1/jami-lsb-systema.log)
[jami-ring-systema.log](/uploads/68fd0ab9e2a05eda88891cf9586ca917/jami-ring-systema.log)
[jami-lsb-systemb.log](/uploads/002124940902bd6fba2439e4f8267bfd/jami-lsb-systemb.log)
[jami-ring-systemb.log](/uploads/471d2b5f773c153cb2205ddd90c12b3b/jami-ring-systemb.log)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/198uri not shown on mainview or account disabled2021-08-20T16:06:17ZSébastien Blinuri not shown on mainview or account disabled![Screenshot_from_2020-11-20_10-58-56](/uploads/5edfc4446f1dc1094f032058f94503ce/Screenshot_from_2020-11-20_10-58-56.png)![Screenshot_from_2020-11-20_10-58-56](/uploads/5edfc4446f1dc1094f032058f94503ce/Screenshot_from_2020-11-20_10-58-56.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/845Answers without permission or notification2021-05-06T20:31:21ZF EAnswers without permission or notification## Describe your environment
On November 18, 2020, I installed Jami on my Moto g7 which runs a recent Android. I downloaded it and installed it using Google Play.
## Steps to reproduce
I don't know how to reproduce it, after this happ...## Describe your environment
On November 18, 2020, I installed Jami on my Moto g7 which runs a recent Android. I downloaded it and installed it using Google Play.
## Steps to reproduce
I don't know how to reproduce it, after this happened I uninstalled the software because I judged it to be a security risk.
## Additional information
I use Arch Linux and I first installed `jami-gnome` on my laptop with `pacman`.
I created a new account successfully.
Then I installed Jami on my phone. I created a new account on my phone.
I tried call my phone using my laptop. The first time I called myself, the phone played music but there was no visual indication that anyone was calling. I could not figure out how to answer the call.
The second time I tried calling myself from my laptop, the phone appeared to be unresponsive. However, I soon heard a feedback squeal which gradually increased in volume.
I tried saying some things and determined that the feedback was indeed due to the laptop's microphone picking up the phone's speaker, and the phone's microphone picking up the laptop's speaker.
This indicated to me that my phone had answered the call without my permission and without informing me.
I concluded that anyone who knew the username that I had created for my phone, would be able to spy on me by muting their microphone and calling that username. They would then be able to listen to me using my phone without my knowledge or permission.
Since this seemed to be a pretty serious security hole, I uninstalled the app. I apologize for not being able to give more information about the phone environment as the app is no longer installed.
Part of the problem is that the Android operating system doesn't notify me when an app is accessing my microphone or camera. I read that there are apps I can install on Android which help provide better security and give me notifications when my microphone is being accessed. I'm not very knowledgeable about smart phones and prefer to keep my environment simple.
Lately I've been using Signal which seems reasonably stable. It does have the drawback that I cannot call myself to test it out, since it is tied to my phone number and it is difficult to create a second account.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1224Animated Stickers2020-11-22T17:51:50ZCyrille BéraudAnimated Stickershttps://forum.jami.net/t/animated-stickers/149https://forum.jami.net/t/animated-stickers/149Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/846Outgoing Calls fail2022-02-13T10:53:49ZElysOutgoing Calls failSending and receiving text massages works between two (different) android Tablets.
But if you try to to make audio/video call it always fails. (Android 8.1 Tablet)
I tried to change almost every settings options but it never worked.
...Sending and receiving text massages works between two (different) android Tablets.
But if you try to to make audio/video call it always fails. (Android 8.1 Tablet)
I tried to change almost every settings options but it never worked.
Installed from the playstore (current version 20201102-01)
There was only one option that worked: If I used the windows app and checked only audio "opus 48 kHz" and video "h263-1993" and "mp4-es" I was sometimes able to receive audio/video calls from the pc BUT not always. Sometimes it works sometimes it doesn't.
Another attempt:
I used a mate 20 pro (Android 10): I always receive audio/video calls from the pc (even if I use the other tablet as a mobile hotspot). But I never received audio/video (from the windows app) with the tablet (alone or together with the other phone (at the same time)). But suddenly I can use the tablet for audio/video calls that I can receive with my mobile phone.
Using mate 20 pro to make an audio/video call everything worked.
I also received audio/video calls with my pc (AND Tablet).
Next attempt: It didn't work at all.
Next attempt: Calling from the tablet I received video calls with my mobile phone. The windows app doesn't recognizie any audio/video calls anymore. I also can't send audio/video calls with windows.
Last attempt:
Windows -> Android 10 Phone WORKS |
Windows -> Tablet doesn't work (never)
Tablet -> Windows doesn't work |
Phone -> Tablet works |
Phone -> Windows doesn't work (anymore)
Windows -> Tablet OR Phone doesn't work (anymore) |
again:
Tablet -> Windows doesn't work |
suddenly:
Phone -> Windows and Tablet (both at the same time. even if the app (Jami) is closed) received incoming call |
I believe it did (always) work before the last (Android) update.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/157Allow conference moderators to mute or kick participants2021-01-16T13:50:34ZAdrien BéraudAllow conference moderators to mute or kick participantsIteration 26Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1225Jami does not release Camera device2021-07-09T21:02:34ZSurendrajatJami does not release Camera deviceThe camera device is still in use after hanging up the call.
##### Steps to reproduce:
1. Accept a video call.
2. Click settings -> Media -> wait till you see the Camera preview.
3. Click on any other settings tab (General/Account/Plugi...The camera device is still in use after hanging up the call.
##### Steps to reproduce:
1. Accept a video call.
2. Click settings -> Media -> wait till you see the Camera preview.
3. Click on any other settings tab (General/Account/Plugin) and click on Media again.
4. Go back to Call View.
5. Hang up the call and you will see the Camera indicator still on.
##### Additional info
Jami: `"Together" built on 2020-11-18 22:41:28 UTC`
OS: `elementaryOS 5.1.7 (Ubuntu 18.04)`https://git.jami.net/savoirfairelinux/jami-project/-/issues/1110microphone closed2021-11-19T16:51:51ZOlivier Meuniermicrophone closed Hi,
I've a sound issue when I use the android version of JAMY on my smartphone.
When I'm trying to call with or without a vidéo, the icon of the microphone is mute and I can't click on it to activate it.
I've uninstall et re install... Hi,
I've a sound issue when I use the android version of JAMY on my smartphone.
When I'm trying to call with or without a vidéo, the icon of the microphone is mute and I can't click on it to activate it.
I've uninstall et re install the application but it's the same.
Can you help me please ?
![1](/uploads/69d32e9fce288c50c68bbdd902439706/1.png)
![2](/uploads/f2557fa5191181da16223fa7fb345449/2.png)
![3](/uploads/0852de8bf55526794653705654608534/3.png)
![4](/uploads/ed159f843b4d149a4cae9bbd5d789ca7/4.png)
![5](/uploads/ac297738128701a48a64d93f1ef865f9/5.png)https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/449chatview: should display received images only2021-11-19T21:31:49ZHugo Lefeuvrechatview: should display received images onlyWhenever an image is received by file transfer, it is stored in a user defined folder and displayed by the chatview. If the image stored at this location changes, the chatview will not notify the user about the changes and silently displ...Whenever an image is received by file transfer, it is stored in a user defined folder and displayed by the chatview. If the image stored at this location changes, the chatview will not notify the user about the changes and silently display the replaced image. This is a bug.
**What should be done instead**: Implement a mechanism that checks image integrity before displaying it. For example, the database could store a hash of the image and check it before triggering display. If the image isn't available anymore (removed, replaced) then a message placeholder should be displayed, e.g. "Image is not available anymore (deleted, replaced)".Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/337allow moderators to hangup a participant2021-01-06T14:55:39ZAdrien Béraudallow moderators to hangup a participantIteration 25Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/848Sending attachments never works2021-11-19T21:32:24ZElysSending attachments never worksUsing Android 8.1 Tablet (and latest update):
Can't (send and) receive attachments of a text message. It never works - only the text is shown.
If sent from pc the error message "unjoinable peer" appears.
If sent from tablet the error m...Using Android 8.1 Tablet (and latest update):
Can't (send and) receive attachments of a text message. It never works - only the text is shown.
If sent from pc the error message "unjoinable peer" appears.
If sent from tablet the error message "partner not available" appears.
However it is possible to receive text messages (WITHOUT attachment) immediately.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1111Video call not working2021-08-20T19:00:53ZElysVideo call not workingI tried to make many video calls with the same settings options using different plattforms at the same time. But it often didn't work (please see the table below)
<table>
<tbody>
<tr>
<td width="57">
<p>Attempt</p>
</td>
<td width="151...I tried to make many video calls with the same settings options using different plattforms at the same time. But it often didn't work (please see the table below)
<table>
<tbody>
<tr>
<td width="57">
<p>Attempt</p>
</td>
<td width="151">
<p>(video call)</p>
<p>send from …</p>
</td>
<td width="151">
<p>receiver & status</p>
<p> </p>
</td>
<td width="151">
<p>receiver & status</p>
</td>
</tr>
<tr>
<td width="57">
<p>1</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td width="151">
<p>PC: received</p>
</td>
<td width="151">
<p>Tablet NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>2</p>
</td>
<td width="151">
<p>an Android tablet</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p> PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>3</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>Android tablet NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>4</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td colspan="2" width="302">
<p>NOT received (never)</p>
</td>
</tr>
<tr>
<td width="57">
<p>5</p>
</td>
<td width="151">
<p>an Android tablet</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>6</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td width="151">
<p>Android tablet: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>7</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td colspan="2" width="302">
<p>NOT received (never)</p>
</td>
</tr>
<tr>
<td width="57">
<p>8</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>Android tablet NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>9</p>
</td>
<td width="151">
<p>an Android tablet</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>10</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>Android tablet NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>11</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td width="151">
<p>Android tablet: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>12</p>
</td>
<td width="151">
<p>an Android tablet</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>13</p>
</td>
<td width="151">
<p>a PC</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>14</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td colspan="2" width="302">
<p>NOT received (never)</p>
</td>
</tr>
<tr>
<td width="57">
<p>15</p>
</td>
<td width="151">
<p>an Android tablet</p>
</td>
<td width="151">
<p>smartphone: received</p>
</td>
<td width="151">
<p>PC NOT received</p>
</td>
</tr>
<tr>
<td width="57">
<p>16</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td width="151">
<p>Android tablet: received</p>
</td>
<td width="151">
<p>PC: received</p>
</td>
</tr>
<tr>
<td width="57">
<p>17</p>
</td>
<td width="151">
<p>a smartphone</p>
</td>
<td width="151">
<p>Android tablet: received</p>
</td>
<td width="151">
<p>PC: received</p>
</td>
</tr>
</tbody>
</table>
However, sending text messages (WITHOUT Attachment) always worked.
See also: https://git.jami.net/savoirfairelinux/ring-client-android/issues/846https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/199Video call is still shown2021-05-14T20:24:34ZElysVideo call is still shownSometimes if I make a video call using an android tablet and I hang up the pc version still shows the video of the video call (All you see is a black screen instead of the other person). (Windows 10:) If you press the end call button Jam...Sometimes if I make a video call using an android tablet and I hang up the pc version still shows the video of the video call (All you see is a black screen instead of the other person). (Windows 10:) If you press the end call button Jami freezes.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/334UPNP/NAT-PMP - Provision port mapping to avoid delay2021-02-08T15:31:50ZMohamed ChibaniUPNP/NAT-PMP - Provision port mapping to avoid delayOn some UPNP/NAT-PMP implementations, port mapping requests may take up to few seconds to be granted. In the current daemon version, the port mapping requests are made just before ICE negotiation starts, which causes the connectivity che...On some UPNP/NAT-PMP implementations, port mapping requests may take up to few seconds to be granted. In the current daemon version, the port mapping requests are made just before ICE negotiation starts, which causes the connectivity check on those ports to fail if the mapping is not granted quickly enough.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1112Character encoding issue on Windows client2020-11-25T13:09:39ZSybren A. StüvelCharacter encoding issue on Windows clientThe Windows client (version 202011191640) doesn't display non-ASCII characters correctly in profile names. The contact list seems to assume Latin-1 encoding, whereas the top of the chat window does show the correct name.
![image](/uploa...The Windows client (version 202011191640) doesn't display non-ASCII characters correctly in profile names. The contact list seems to assume Latin-1 encoding, whereas the top of the chat window does show the correct name.
![image](/uploads/2412851af4de02d96f3b2fc50056b5bc/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/200Character encoding issue on Windows client2020-12-09T16:44:10ZSybren A. StüvelCharacter encoding issue on Windows clientThe Windows client (version 202011191640) doesn't display non-ASCII characters correctly in profile names. The contact list seems to assume Latin-1 encoding, whereas the top of the chat window does show the correct name.
![image](/uploa...The Windows client (version 202011191640) doesn't display non-ASCII characters correctly in profile names. The contact list seems to assume Latin-1 encoding, whereas the top of the chat window does show the correct name.
![image](/uploads/41675921dfd6b3deb89efe0844418f71/image.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/356What are the license for ringtone files2021-11-19T21:46:34ZSahil DhimanWhat are the license for ringtone filesI would like to add the Jami [ringtone](https://git.jami.net/savoirfairelinux/ring-daemon/tree/master/ringtones) are nice. Could you specify what are license terms for it, if they're under CC license or not.
and thanks for the amazing ...I would like to add the Jami [ringtone](https://git.jami.net/savoirfairelinux/ring-daemon/tree/master/ringtones) are nice. Could you specify what are license terms for it, if they're under CC license or not.
and thanks for the amazing work and sorry for the noise.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/357Conference - crash in call_factory.h2021-12-14T15:14:36ZMohamed ChibaniConference - crash in call_factory.hA crash occurred when hosting a conference. See the full back-trace in the attached file.
BuildL: Jami Daemon 9.6.0-2e35f9a59b
[daemon-crash-conference.txt](/uploads/abc03baf2e0e2f9748fb5f4079b9a3ad/daemon-crash-conference.txt)A crash occurred when hosting a conference. See the full back-trace in the attached file.
BuildL: Jami Daemon 9.6.0-2e35f9a59b
[daemon-crash-conference.txt](/uploads/abc03baf2e0e2f9748fb5f4079b9a3ad/daemon-crash-conference.txt)Backloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/201Video preview device switching will block UI for a short period of time2022-12-17T02:38:09ZMing Rui ZhangVideo preview device switching will block UI for a short period of timehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1113chat view doesn't work in Fedora 33 Fresh Install in Wayland session2020-11-27T13:07:42ZMerenda Olivierchat view doesn't work in Fedora 33 Fresh Install in Wayland sessionJami doesn't show Chat View in Fresh Install fedora 33 in wayland session
without apply System Updates
/usr/lib64/ring/dring -d -c
> Jami Daemon 9.6.0, by Savoir-faire Linux 2004-2019
jami-gnome -d
````
test2@localhost ~]$ jami-...Jami doesn't show Chat View in Fresh Install fedora 33 in wayland session
without apply System Updates
/usr/lib64/ring/dring -d -c
> Jami Daemon 9.6.0, by Savoir-faire Linux 2004-2019
jami-gnome -d
````
test2@localhost ~]$ jami-gnome -d
(jami-gnome:10404): GLib-DEBUG: 12:58:08.777: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:10404): DEBUG: 12:58:08.777: debug enabled
** Message: 12:58:08.780: Jami GNOME client version: 711b1d677dfc9b9dd7ccda3a8a03240e97d7a0d9
** Message: 12:58:08.780: git ref: unknown
** (jami-gnome:10404): DEBUG: 12:58:08.780: enabling autostart
** (jami-gnome:10404): DEBUG: 12:58:08.780: checking /usr/share/jami-gnome/jami-gnome.desktop
** (jami-gnome:10404): DEBUG: 12:58:08.780: '/home/test2/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:10404): dconf-DEBUG: 12:58:08.782: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
(jami-gnome:10404): GLib-GIO-DEBUG: 12:58:08.798: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
** (jami-gnome:10404): DEBUG: 12:58:08.998: installed translations for fr
** (jami-gnome:10404): DEBUG: 12:58:08.998: installed translations for fr_FR
(jami-gnome:10404): GLib-DEBUG: 12:58:09.035: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:10404): Gtk-DEBUG: 12:58:09.035: Connecting to session manager
** (jami-gnome:10404): DEBUG: 12:58:09.173: notify server name: gnome-shell, vendor: GNOME, version: 3.38.1, spec: 1.2
(jami-gnome:10404): Gtk-WARNING **: 12:58:09.176: Child name 'calls' not found in GtkStack
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.178: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.178: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.179: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.179: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.179: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.179: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:10404): dconf-DEBUG: 12:58:09.179: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
(jami-gnome:10404): dconf-DEBUG: 12:58:09.310: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:10404): dconf-DEBUG: 12:58:09.311: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:10404): dconf-DEBUG: 12:58:09.506: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:10404): Gtk-CRITICAL **: 12:58:09.530: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:10404): dconf-DEBUG: 12:58:09.560: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.560: change_notify: /net/jami/JamiGnome/show-main-window
(jami-gnome:10404): dconf-DEBUG: 12:58:09.612: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.612: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:10404): dconf-DEBUG: 12:58:09.612: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.612: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:10404): dconf-DEBUG: 12:58:09.634: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.634: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:10404): dconf-DEBUG: 12:58:09.634: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.634: change_notify: /net/jami/JamiGnome/window-height
(process:10443): GLib-GIO-DEBUG: 12:58:09.637: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:10443): GLib-GIO-DEBUG: 12:58:09.642: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ?gio-network-monitor?
QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.245'
(jami-gnome:10404): dconf-DEBUG: 12:58:09.669: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.669: change_notify: /net/jami/JamiGnome/window-maximized
(WebKitWebProcess:10442): GLib-GIO-DEBUG: 12:58:09.670: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:10404): dconf-DEBUG: 12:58:09.689: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.689: change_notify: /net/jami/JamiGnome/window-maximized
(jami-gnome:10404): dconf-DEBUG: 12:58:09.691: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.691: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:10404): DEBUG: 12:58:09.710: NetworkManager client initialized, version: 1.26.2
daemon running: yes
nnetworking enabled: yes
** (jami-gnome:10404): DEBUG: 12:58:09.711: primary network connection: bf97b3b6-07bc-3aed-a347-c0c3df1488ea, default: yes
(jami-gnome:10404): dconf-DEBUG: 12:58:09.722: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.722: change_notify: /net/jami/JamiGnome/window-maximized
(process:10443): GLib-GIO-DEBUG: 12:58:09.781: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:10404): dconf-DEBUG: 12:58:09.815: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.815: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:10404): dconf-DEBUG: 12:58:09.815: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.815: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:10404): dconf-DEBUG: 12:58:09.885: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.885: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:10404): dconf-DEBUG: 12:58:09.885: change_fast
(jami-gnome:10404): dconf-DEBUG: 12:58:09.885: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:10404): dconf-DEBUG: 12:58:09.905: change_fast
````
rpm -qa webkit2gtk3
> webkit2gtk3-2.30.1-1.fc33.x86_64