Bug#944494: jami aborts when the media sub-menu is entered from the settings menu

[Alexander Necheff]

Package: jami
Version: 20190215.1.f152c98~ds1-1

When selecting the Settings gear menu, then selecting the Media sub-menu,
jami displays the Media settings menu momentarily and then aborts.

Running jami from the command line and performing these steps shows the
following messages:

"
(jami:9721): libnotify-WARNING **: 13:34:45.148: Failed to connect to proxy
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() ?)

(jami:9721): Gtk-CRITICAL **: 13:34:45.463: gtk_scrolled_window_add:
assertion 'child_widget == NULL' failed
No profile selected or none exists
could not open shm area "" , shm_open failed: Invalid argument
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Video::ShmRenderer(0x55fb8e2c2980), parent's thread is
QThread(0x55fb8dfcb7d0), current thread is QThread(0x55fb8dd62b70)
Terminated
"

I am running Debian 10.1, using kernel "4.19.0-6-amd64 #1 SMP Debian
4.19.67-2+deb10u1", and glibc "ldd (Debian GLIBC 2.28-10) 2.28".

I am assuming that "could not open shm area "" , shm_open failed: Invalid
argument" is the critical message here. Though, I have confirmed that
/dev/shm is mounted with the df command, but it appears empty with an ls
-la.

I do not explicitly mount /dev/shm in /etc/fstab; but, it seems like
systemd is supposed to automatically take care of this now? At least
according to the Arch Wiki.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/attachments/20191110/084e89c7/attachment.html>