[Pkg-utopia-maintainers] Bug#919880: gstreamer1.0-pipewire: segfault when pipewire is not installed

[Antonio Ospite]

Package: gstreamer1.0-pipewire
Version: 0.2.5-1
Severity: normal

Dear Maintainer,

I installed gstreamer1.0-pipewire and tried to inspect piepwiresrc with
gst-inspect-1.0 and I got a segfault:

-----------------------------------------------------------------------
$ gdb -ex run --args gst-inspect-1.0 pipewiresrc
GNU gdb (Debian 8.2-1) 8.2
...
Reading symbols from gst-inspect-1.0...Reading symbols from /usr/lib/debug/.build-id/0f/35e5a3a648136149cd078270645dc16506eb5a.debug...done.
done.
Starting program: /usr/bin/gst-inspect-1.0 pipewiresrc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: impossibile aprire il file oggetto condiviso: File o directory non esistente

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff756b006 in pw_thread_loop_new () from /usr/lib/x86_64-linux-gnu/libpipewire-0.2.so.1
(gdb) bt
#0  0x00007ffff756b006 in pw_thread_loop_new () at /usr/lib/x86_64-linux-gnu/libpipewire-0.2.so.1
#1  0x00007ffff75cc4fa in  () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpipewire.so
#2  0x00007ffff7e340b7 in g_type_create_instance (type=<optimized out>) at ../../../gobject/gtype.c:1864
#3  0x00007ffff7e16518 in g_object_new_internal (class=class at entry=0x5555557e8f50, params=params at entry=0x0, n_params=n_params at entry=0)
    at ../../../gobject/gobject.c:1805
#4  0x00007ffff7e17c95 in g_object_new_with_properties
    (object_type=0x5555557e8140 [GstPipeWireSrc/GstPushSrc/GstBaseSrc/GstElement/GstObject/GInitiallyUnowned], n_properties=0, names=names at entry=0x0, values=values at entry=0x0) at ../../../gobject/gobject.c:1973
#5  0x00007ffff7e18701 in g_object_new (object_type=<optimized out>, first_property_name=first_property_name at entry=0x0) at ../../../gobject/gobject.c:1645
#6  0x00007ffff7eb5672 in gst_element_factory_create (factory=0x5555557decb0 [GstElementFactory], name=0x0) at gstelementfactory.c:372
#7  0x000055555555b8e3 in print_element_info (feature=<optimized out>, print_names=0) at gst-inspect.c:1375
#8  0x0000555555558ed7 in print_feature_info (print_all=0, feature_name=0x7fffffffe34d "pipewiresrc") at gst-inspect.c:1338
#9  0x0000555555558ed7 in main (argc=<optimized out>, argv=<optimized out>) at gst-inspect.c:1818
(gdb) 

-----------------------------------------------------------------------

The problem can be easily resolved by installing the "pipewire" package.

I am reporting it because in case of a missing library I would have
expected a failure but not a segfault.

Maybe pipewire should also be a Depend or a Recommend for
gstreamer1.0-pipewire or for libpipewire-0.2-1 (the segfault is in
libpipewire-0.2.so.1).

Not sure if this is an upstream problem too, I have no experience with
pipewire.

Anyways, thank you for the packages, they are useful to start playing
with pipewire.

Ciao,
   Antonio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gstreamer1.0-pipewire depends on:
ii  libc6                           2.28-5
ii  libglib2.0-0                    2.58.2-4
ii  libgstreamer-plugins-base1.0-0  1.14.4-1
ii  libgstreamer1.0-0               1.14.4-1
ii  libpipewire-0.2-1               0.2.5-1

gstreamer1.0-pipewire recommends no packages.

gstreamer1.0-pipewire suggests no packages.

-- no debconf information
-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?