savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-04-13T16:07:33Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1258Invalid dbus answer. Daemon not running2021-04-13T16:07:33ZLukas WallischInvalid dbus answer. Daemon not runningBug report form
---------------
## OS Ubuntu 20.04
<!-- e.g. Debian, Ubuntu, etc. -->
## Jami daemon version:
not under the given path `/usr/lib/ring/dring`
instead under `snap/jami/132/usr/lib/ring/dring`
Jami Daemon 9.8.0-a6d5ad32d...Bug report form
---------------
## OS Ubuntu 20.04
<!-- e.g. Debian, Ubuntu, etc. -->
## Jami daemon version:
not under the given path `/usr/lib/ring/dring`
instead under `snap/jami/132/usr/lib/ring/dring`
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
<!-- type `/usr/lib/ring/dring -h` into your terminal -->
## Jami GNOME client version:
<!-- type `jami-gnome -v` into your terminal -->
not from 'jami-gnome' instead only 'jami'
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [x] snap package manager
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
<!-- The better your scenario is, the better we will be able to help
you. Please try to describe only one bug here. Open multiple issues
for multiple bugs -->
this is where i'm not sure -.-
## What you expect to happen:
-Able to change Account Settings.
-on fresh install setup a SIP-Account
## What happens instead:
-Account settings open very very slow (~1m)
-after click on create Account ( in Advanced/create SIP Account) nothing happens
## Logs
### Console Output
```
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...and using ALSA.
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]
One does not simply initialize the client: Another daemon is detected
** (jami-gnome:14285): DEBUG: 11:52:00.893: debug enabled
** Message: 11:52:00.895: Jami GNOME client version: f6d50ba8bd027d9d02964f0954b40275c472267b
** Message: 11:52:00.895: git ref: eb9b95966519bb90e07d040a22c464c7c85bd918
** (jami-gnome:14285): DEBUG: 11:52:00.895: enabling autostart
** (jami-gnome:14285): DEBUG: 11:52:00.895: checking /usr/share/jami-gnome/jami-gnome.desktop
** (jami-gnome:14285): DEBUG: 11:52:00.895: checking /usr/local/share/jami-gnome/jami-gnome.desktop
** (jami-gnome:14285): DEBUG: 11:52:00.895: '/home/wallisch/snap/jami/132/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/local/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.909: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.913: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.914: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.117: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.120: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.121: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-DEBUG: 11:52:01.144: Connecting to session manager
Invalid dbus answer. Daemon not running
** (jami-gnome:14285): DEBUG: 11:52:01.182: notify server name: gnome-shell, vendor: GNOME, version: 3.36.7, spec: 1.2
** (jami-gnome:14285): DEBUG: 11:52:01.185: building conversationsview for inexistant account (just removed ?)
** (jami-gnome:14285): DEBUG: 11:52:01.185: building conversationsview for inexistant account (just removed ?)
** (jami-gnome:14285): WARNING **: 11:52:01.212: drawChannels out_of_range exception
(jami-gnome:14285): Gtk-CRITICAL **: 11:52:01.395: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.457: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.461: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.462: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
** (jami-gnome:14285): DEBUG: 11:52:01.473: real_name = Wallisch Lukas
** (jami-gnome:14285): DEBUG: 11:52:01.473: user_name = wallisch
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.474: Theme parsing error: <data>:1:270: not a number
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.603: Theme parsing error: gtk.css:1566:23: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.607: Theme parsing error: gtk.css:3616:25: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.608: Theme parsing error: gtk.css:4078:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.124: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
```
<!-- run
journalctl --since "24h ago" | grep dring
in your terminal -->
### journalctl:
```
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: [XFER] facade created, pimpl @0x55b1168ec7a0
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Default video settings: 800x600, 30 FPS
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Manager not initialized yet
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Not initialized
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Not initialized
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
Apr 13 08:22:07 wallisch-TERRA-PC dring[2715]: UPnP: check for valid IGD timeout
Apr 13 11:48:54 wallisch-TERRA-PC dring[2715]: NAT-PMP: can't send request
```
## Additional information
**After terminating `dring` via `htop` it seems to work just fine now ¯\\\_(ツ)\_/¯**https://git.jami.net/savoirfairelinux/jami-project/-/issues/1223WASM Web Browser Client2021-04-12T16:38:57ZjfftckWASM Web Browser ClientIt would be great to compile the app into WASM to have a web based version. I know that this would be a major undertaking. This would allow sharing a link that could give a user the option to download the native app or continue with the ...It would be great to compile the app into WASM to have a web based version. I know that this would be a major undertaking. This would allow sharing a link that could give a user the option to download the native app or continue with the web based one.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1222Appear Offline Mode2023-04-07T20:10:49ZthoranAppear Offline ModeHaving a mode to appear offline is especially important given that I need to have Jami on/open in order for messages to be sent and received. In order to not be disturbed, if working for instance, I have to close Jami, which means that m...Having a mode to appear offline is especially important given that I need to have Jami on/open in order for messages to be sent and received. In order to not be disturbed, if working for instance, I have to close Jami, which means that messages are neither sent nor received.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/921status and hangup button in portrait call-screen are misaligned2021-04-20T06:13:22Zrtwin_xstatus and hangup button in portrait call-screen are misaligned## Environment
Galaxy A71, Android 10, Versie One UI 2.5
Jami: Together-20210409-01, from Google Play Store
## Steps to reproduce
Call someone while phone in potrait mode.
- Actual result: Target-name and Status text and 'hangup' b...## Environment
Galaxy A71, Android 10, Versie One UI 2.5
Jami: Together-20210409-01, from Google Play Store
## Steps to reproduce
Call someone while phone in potrait mode.
- Actual result: Target-name and Status text and 'hangup' button are off-center to the left. Only the big sounding circle is center aligned
- Expected result: all text and buttons are center aligned
## Additional information
See attachment![Jami_Together-20210409-01](/uploads/561f71b146a293ab6e6450c7e64eff47/Jami_Together-20210409-01.jpg)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/920Messages are delayed in Jami-Android2023-02-17T20:50:08Zb16 r05Messages are delayed in Jami-AndroidI have had, at times, messages not going and at other times getting delayed. The latest, ... my messages reached the recipient after 17 hours.
The work around I have used is to: long press app > go to app info > then, clear cache and f...I have had, at times, messages not going and at other times getting delayed. The latest, ... my messages reached the recipient after 17 hours.
The work around I have used is to: long press app > go to app info > then, clear cache and force close > reopen the app. Sometimes, I reboot my phone.
Just wondering: is this a known issue or is anyone else experiencing similar problems?https://git.jami.net/savoirfairelinux/jami-project/-/issues/1221Connectivity issue with DHTproxy2021-04-24T12:33:21ZChris OcelotConnectivity issue with DHTproxyI am using latest play store version of jami:20210226-01 on my Oneplus 5T with Oxygen OS, Android version 10.0
I have encountered a problem when using DHTproxy. I have compiled dhtnode binary from the latest release source code on githu...I am using latest play store version of jami:20210226-01 on my Oneplus 5T with Oxygen OS, Android version 10.0
I have encountered a problem when using DHTproxy. I have compiled dhtnode binary from the latest release source code on github, which is 2.1.10. I used jami's official bootstrap as my bootstrap. Most stuff works fine, I disabled push notification, so my DHTproxy could send notification to my Android phone directly.
The only problem is that when I restart the DHTproxy, my phone is unable to reconnect to it. When other people sends me messages or calls, it's not going through, it's not sent on their end, and not received on my end. I have to manually toggle the connection off and on in order for my phone to be able to connect to the proxy.
Side note, I can confirm that my OS does not kill jami app. If I do not restart the proxy, my app is able to receive message notification for a couple of days without problem. As soon as I restart the proxy, I lost connection.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1220[Jami-Gnome] Implement native Wayland2021-04-08T00:55:52Z[Jami-Gnome] Implement native WaylandCurrently jami-gnome only works via XWayland. I found that out, because setting ``CLUTTER_BACKEND=wayland`` leads to this error:
```
(jami-gnome:165584): GLib-DEBUG: 02:08:49.578: setenv()/putenv() are not thread-safe and should not be u...Currently jami-gnome only works via XWayland. I found that out, because setting ``CLUTTER_BACKEND=wayland`` leads to this error:
```
(jami-gnome:165584): GLib-DEBUG: 02:08:49.578: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:165584): DEBUG: 02:08:49.578: debug enabled
(jami-gnome:165584): dconf-DEBUG: 02:08:49.580: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** Message: 02:08:49.581: Jami GNOME client version: development
** Message: 02:08:49.581: git ref: f4f19c4a753bb073d790db06a96b0ec6db2d8232
** (jami-gnome:165584): DEBUG: 02:08:49.581: disabling autostart
** (jami-gnome:165584): DEBUG: 02:08:49.581: '/home/mika/.config/autostart/jami-gnome.desktop' doesn't exist, nothing to do
(jami-gnome:165584): Clutter-Gtk-ERROR **: 02:08:49.589: *** Unsupported backend.
zsh: trace trap (core dumped) install/client-gnome/bin/jami-gnome -d
```
I could verify that it falls back to XWayland by using xeyes (without setting ``CLUTTER_BACKEND``).
One temporary fix would be to also set ``CLUTTER_BACKEND`` to ``x11`` in the main.cpp (as the ``GDK_BACKEND``). This would allow people to launch it, even if they have set ``CLUTTER_BACKEND`` to ``wayland``.
It is however able to launch, if you remove the ``setenv("GDK_BACKEND", "x11", true);`` line from ``main.cpp``. But that is described [here](https://git.jami.net/savoirfairelinux/ring-client-gnome/-/issues/1100).https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/365plugins: setting in handler activation popup2023-04-07T18:38:18ZAline Gondim Santosplugins: setting in handler activation popupFollow directives from: https://www.sketch.com/s/164f7656-95fd-48d0-9d19-c2aaf211b5c3Follow directives from: https://www.sketch.com/s/164f7656-95fd-48d0-9d19-c2aaf211b5c3BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/511ICE components ID numbering - Comply to RFC-5245 and RFC-84452021-04-14T16:23:23ZMing Rui ZhangICE components ID numbering - Comply to RFC-5245 and RFC-8445Component ID must be incremented per media starting from 1 as specified in https://tools.ietf.org/html/rfc5245#section-15.1:
```
<component-id>: is a positive integer between 1 and 256 that
identifies the specific component of th...Component ID must be incremented per media starting from 1 as specified in https://tools.ietf.org/html/rfc5245#section-15.1:
```
<component-id>: is a positive integer between 1 and 256 that
identifies the specific component of the media stream for which
this is a candidate. It MUST start at 1 and MUST increment by 1
for each component of a particular candidate. For media streams
based on RTP, candidates for the actual RTP media MUST have a
component ID of 1, and candidates for RTCP MUST have a component
ID of 2. Other types of media streams that require multiple
components MUST develop specifications that define the mapping of
components to component IDs. See Section 14 for additional
discussion on extending ICE to new media streams.
```
Also in https://tools.ietf.org/html/rfc8445Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/510Upnp Controller - Create instance only when needed2021-04-19T13:21:34ZMohamed ChibaniUpnp Controller - Create instance only when neededUPNP Cotroller instance used by the Account class (and derived classes) must be created only if needed. Currently, the creation is done in enableUpnp(bool) method which is called when the account data are stored or loaded. The required c...UPNP Cotroller instance used by the Account class (and derived classes) must be created only if needed. Currently, the creation is done in enableUpnp(bool) method which is called when the account data are stored or loaded. The required change is to particularly prevent creating UPNP controller instance when storing the account data.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/509Bump pjproject to version 2.112021-07-23T15:16:28ZSébastien BlinBump pjproject to version 2.11https://git.jami.net/savoirfairelinux/ring-daemon/blob/master/contrib/src/pjproject/rules.mak
We're using pjproject 2.10, and we need to migrate our patches and remove the one already upstreamed.
Cf new features (like trickle ICE for m...https://git.jami.net/savoirfairelinux/ring-daemon/blob/master/contrib/src/pjproject/rules.mak
We're using pjproject 2.10, and we need to migrate our patches and remove the one already upstreamed.
Cf new features (like trickle ICE for medias?)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1219Please fix distribution process for Ubuntu2021-05-21T15:26:51ZreubenfirminPlease fix distribution process for UbuntuThe version in 20.04's apt is very old and has bugs. The version in snap is 3 months old, but apparently has issues that have been fixed. Unfortunately, installing the version directly from your site does not pick up the settings from th...The version in 20.04's apt is very old and has bugs. The version in snap is 3 months old, but apparently has issues that have been fixed. Unfortunately, installing the version directly from your site does not pick up the settings from the snap version (I am guessing because snap is sandboxed), so it is not easy to go back and forth from the snap to the downloaded version.
Snap or flatpak are a better solution than distributing your own deb packages. Please consider putting resources into maintaining the latest version in those stores rather than building your own, as it'll result in a more cohesive experience for end users.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/364Warning of invalid map<K, T> key (map::at)2021-04-14T14:42:01ZMing Rui ZhangWarning of invalid map<K, T> key (map::at)Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/363incorrect behavior when copying a jami id from contact profile (text displaye...2023-04-07T18:38:38ZGuillaume Hellerincorrect behavior when copying a jami id from contact profile (text displayed is copied instead of value)Scenario:
- right click on contact
- select profile
- if the id is truncated, when copying it, it only copies the text displayed (instead of the value)
![image](/uploads/f835be7d2ac26bc4f30f8301557fa6db/image.png)Scenario:
- right click on contact
- select profile
- if the id is truncated, when copying it, it only copies the text displayed (instead of the value)
![image](/uploads/f835be7d2ac26bc4f30f8301557fa6db/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/362Linux chatview weird font2021-04-13T19:16:17ZSébastien BlinLinux chatview weird fonthttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/919Can send text and emoticons, but can't send pictures.2021-08-20T20:00:52ZFrederikSchackCan send text and emoticons, but can't send pictures.I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly...I'm new to this app and I'm not a developer.
I'm able to send text, but not pictures. We did occasionally have success with video/voice calling, but sometimes we can't.
We're in what is a big commercial private network, that is fairly unstable. One issue I have is that we share one public IP, which means we can't redirect a port to more than one subscriber inside the network.
It's the same issue with several phones.
We don't have problems with Bittorrent or any other program accessing the Internet, except for losing Internet connection once in a while.https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/19build: create Jenkins job for Mac2021-04-07T22:42:34ZAline Gondim Santosbuild: create Jenkins job for MacBuild and test plugins
- [x] AutoAnswer
- [x] AudioFilter
- [x] WaterMark
- [x] GreenScreenBuild and test plugins
- [x] AutoAnswer
- [x] AudioFilter
- [x] WaterMark
- [x] GreenScreenAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/466Exiting jami-qt segfaults (SIGSEGV) when the LRC is built with -DENABLE_LIBWR...2021-06-08T21:13:09ZMaxim CournoyerExiting jami-qt segfaults (SIGSEGV) when the LRC is built with -DENABLE_LIBWRAP=trueEDIT: This original finding no longer holds for version 20210606.1.e2f9490. The only crash now seems to be upon exiting jami-qt. See the 2nd comment.
I found this issue building with the recently released 20210326.1.cfba013 code.
Add...EDIT: This original finding no longer holds for version 20210606.1.e2f9490. The only crash now seems to be upon exiting jami-qt. See the 2nd comment.
I found this issue building with the recently released 20210326.1.cfba013 code.
Adding `-DENABLE_LIBWRAP=true` as a CMake option would cause the following segfault when attempting to do a video call:
```
[1617377403.268|27762|manager.cpp :2989 ] Did not find conference 7014912808852927
[1617377403.300|28030|accel.cpp :180 ] Device type vaapi successfully created.
[1617377403.300|28030|accel.cpp :213 ] -- Init passed for vaapi with default device.
[1617377403.303|28030|media_decoder.cpp :489 ] Using hardware decoding for h264 with vaapi
[1617377403.303|28030|media_decoder.cpp :496 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1617377403.303|28030|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_27762_1]: new sizes: f=0, a=103
[1617377403.303|28030|sinkclient.cpp :158 ] ShmHolder: new holder 'Jami Daemon_shm_27762_1'
[1617377403.303|28030|sinkclient.cpp :429 ] Start sink <7014912808852927 / Jami Daemon_shm_27762_1>, size=1280x720, mixer=0
[1617377403.303|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.304|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.305|28030|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[1617377403.305|28030|media_decoder.cpp :568 ] Decoding error falling back to software
[New Thread 0x7fff21283700 (LWP 28061)]
[Thread 0x7fff23c87700 (LWP 28057) exited]
[Thread 0x7fff22c85700 (LWP 28059) exited]
[Thread 0x7fff22484700 (LWP 28060) exited]
[Thread 0x7fff23486700 (LWP 28058) exited]
[1617377403.388|28030|media_decoder.cpp :496 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1617377403.388|28030|media_decoder.cpp :506 ] Not using hardware decoding for h264
[New Thread 0x7fff22484700 (LWP 28062)]
[New Thread 0x7fff22c85700 (LWP 28063)]
[1617377403.391|27811|sipcall.cpp :419 ] Sending video keyframe request via SIP INFO
[1617377403.540|28030|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_27762_1]: new sizes: f=3686400, a=7372903
--Type <RET> for more, q to quit, c to continue without paging--c
Thread 1 "..jami-qt-real-" received signal SIGSEGV, Segmentation fault.
0x00007fffeeab4710 in __memmove_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
(gdb) bt
#0 0x00007fffeeab4710 in __memmove_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
#1 0x0000000000452d3d in FrameWrapper::slotFrameUpdated(QString const&) ()
#2 0x00007fffef105914 in void doActivate<false>(QObject*, int, void**) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#3 0x00007ffff7d93c55 in lrc::api::AVModel::frameUpdated(QString const&) () from /gnu/store/3scnwm1jlhpxii7261p6zifbj1r9a1ah-libringclient-20210326.1.cfba013/lib/libringclient.so.1.0.0
#4 0x00007fffef0fc763 in QObject::event(QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#5 0x00007ffff7155c3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Widgets.so.5
#6 0x00007ffff715c57f in QApplication::notify(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Widgets.so.5
#7 0x00007fffef0ca373 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#8 0x00007fffef0cd521 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#9 0x00007fffef129d53 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#10 0x00007ffff769908a in g_main_context_dispatch () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#11 0x00007ffff7699288 in g_main_context_iterate.isra () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#12 0x00007ffff769930c in g_main_context_iteration () from /gnu/store/1m34rwlhv2pyjbp69n63grlncnkjyi31-glib-2.62.6/lib/libglib-2.0.so.0
#13 0x00007fffef12944c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#14 0x00007fffef0c8d2a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#15 0x00007fffef0d1e53 in QCoreApplication::exec() () from /gnu/store/sbf77k7xzwhkx4ygqjzgkviz9vy4qhf6-qtbase-5.15.2/lib/libQt5Core.so.5
#16 0x00000000004280a6 in main ()
```
Simply setting this option to false resolves the issue (no longer segfaults and the video call proceeds normally).
Interestingly, audio calls are not affected and the jami-qt client works normally otherwise.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/280plugins: create base UI2021-05-28T14:40:33ZAline Gondim Santosplugins: create base UI- Add plugin to jami settings: enable/disable, (un)install and (un)load;
- Add a plugin to calls and conversations;
- Add plugins preferences to settings view;- Add plugin to jami settings: enable/disable, (un)install and (un)load;
- Add a plugin to calls and conversations;
- Add plugins preferences to settings view;Kateryna KostiukAline Gondim SantosKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/508plugins: add MACOSX ABI to plugin installation options2021-04-08T18:53:40ZAline Gondim Santosplugins: add MACOSX ABI to plugin installation optionsInstallation function needs to know host details to properly extract plugins libraries from the jpl archive.Installation function needs to know host details to properly extract plugins libraries from the jpl archive.Aline Gondim SantosAline Gondim Santos