[packman] A segmentation fault in attempting to play a .mp4 file in vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 in a 64-bit, openSUSE, Leap-15.3, Linux operating system installed in VirtualBox

Lawrence Patrick Somerville spring2014day at gmail.com
Wed Dec 15 22:34:53 CET 2021


 Hello.  I have not knowingly received a reply by electronic mail (e-mail)
from anyone on the e-mailing list of packman at links2linux.de to my November
12, 2021 e-mail letter sent to that e-mail address.


Question: Am I supposed to join that e-mailing list of
packman at links2linux.de in order for me to receive such a reply?


I suppose not. A disadvantage of my joining that e-mailing list is that if
I would join it I might receive lots of e-mail about matters irrelevant to
my current computer-software problems. Here I present additional data and
more diagnostic information than I presented on November 12, 2021, which
hopefully will "spark" more ideas helpful to me among one or more expert
readers of my electronic mail than following my November 12, 2021 e-mail
letter.


In a 64-bit, openSUSE, Leap-15.3, Linux operating system, which is
installed as a so-called "guest" in Virtual "Machine" (VM) in Oracle
(Corporation) VM VirtualBox, which in turn is installed in my so-called
"host," Windows 10 Home Edition operating system, I have gratefully had
success in the playing of a .mp4 (Moving or Motion Picture Experts Group,
audio layer-4) file in
vlc-beta-20211028.5ed8c5c794-pm153.9.1.x86_64.16.1.x86_64
with the Linux kernel 5.3.18-59.27.1-default. But in
vlc-beta-20211104.b9e50b090c-pm153.10.1.16.1.x86_64 I had only the audio
signals and not the video signals in the playing of that video. And later
in vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 with the Linux kernel
5.3.18-59.37.2-default I attempted to open vlc-beta, or the Video Local
Area Network (LAN) Client (VLC) multimedia player (VLC) by double-clicking
on a desktop shortcut for it, but saw its main window only for a very brief
period of time, accompanied probably a short time later with the message
"Segmentation fault (core dumped)"; so I could not even attempt to play
that .mp4 file normally with this version of vlc-beta when using its
probably default, Qt interface.


I at least began the process of preparation toward having a .rpm (RedHat
package manager) file "built" for my Leap-15.3 installation using downloaded
source code for vlc-beta-20211104.b9e50b090c-pm153.10.1.16.1 or
20211104.b9e50b090c-pm153.10.1.16.1.x86_64 and an rpmbuild... command, but
failed in that effort due to "Failed build dependencies". I started that
kind of process also with vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 by
starting to obtain some software packages missing in my Leap-15.3
installation. And that process for my Leap-15.3 installation not only
required a list of some tens of software packages; but I discovered two
other difficult factors: 1) The software package mentioned between the
parentheses of a pkgconfig(...) "response" following an rpmbuild... command
is sometimes different than the name of a software package I could obtain
from an openSUSE or Packman online repository. And I don't know for certain
if I can even obtain the exact package "requested" from somewhere on the
Internet. 2) But in a "user-friendly" way it might be that sometimes
rpmbuild might "accept" packages with names similar, but not exactly the
same as the names of the packages between the parentheses of pkgconfig(...)
(For example, I installed libnfs13, which has a name slightly different
from the name of the required package libnfs for rpmbuild....). But if
similar names would not be "accepted" by rpmbuild and I could not obtain
the exact software packages requested, in that case I don't know what I
should do to "satisfy" the "rpmbuild" computer code.


Rather than try to find and obtain some tens of software packages required
for the successful execution of an rpmbuild command using the downloaded
source code for vlc-beta-20211206.07ed287157-pm153.16.1.x86_64, I read that
it is possible to have such a .rpm file "built" online using the openSUSE
Build Service of the Open Build Service (OBS, https://build.opensuse.org/ on
the Internet). It seems to be reported that such "building" could ease the
action of obtaining the software packages "required" by rpmbuild. But I
have not learned how to use OBS or tried it to make a .rpm file. But even
if I would be successful in somehow "building" such a .rpm file for
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64,
it is possible that it might not eliminate the segmentation faults I have
encountered, especially if it would be a change in the vlc-beta source code
which would be needed to eliminate such segmentation faults.


Although the .rpm installation file for version
20211028.5ed8c5c794-pm153.9.1.x86_64.16.1.x86_64 of the software package
vlc-beta is probably unfortunately no longer available from
http://packman.links2linux.de/package/vlc-beta or
https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/Multimedia/x86_64/,
fortunately I have the capability to restore my Leap-15.3 installation,
including the installation of
vlc-beta-20211028.5ed8c5c794-pm153.9.1.x86_64.16.1.x86_64
in it, from a previously written backup of the data on my Dell notebook
computer's internal hard-disk drive. For a period of time I was able to
"lock" or protect that version of vlc-beta, which has worked well for me,
from being updated to a newer version of vlc-beta, which thus far has not
worked for me when using its Qt interface. However, considering the likely
future updates to some software packages and the Linux kernel elsewhere in
my Leap-15.3 installation, the arrangement of
vlc-beta-20211028.5ed8c5c794-pm153.9.1.x86_64.16.1.x86_64
working well with a number of newer software packages might at some time in
the future no longer be a mutually well-working arrangement for me. At
least by the time of an upgrade from version 15.3 to version 15.4 of Leap on
or after June 8, 2022, there could be a possible software mismatch, since
according to http://packman.links2linux.de/package/vlc-beta the version
vlc-beta-20211028.5ed8c5c794-pm153.9.1.x86_64.16.1.x86_64 saved in my
hard-disk drive's backup data is reported to be suitable for a Leap-15.3
installation. So I have been attempting to find some way to make the
version of vlc-beta released to the public on December 6, 2021, namely
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64, work in my Leap-15.3
installation. And the hope would be that after having made it to work in my
Leap-15.3 installation that making later versions of vlc-beta to work in my
Leap-15.3 installation might be easier than now for
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64.


I have been able to play a .mp4 file in
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 using a command of the form
"vlc -I dummy FILE_NAME.mp4" in a directory containing the file with a name
of the form FILE_NAME.mp4. Otherwise entering the command "vlc" or "gdb
vlc", using the GNU's Not Unix (GNU) debugger (gdb), in the directory
/usr/bin resulted in the main window for vlc-beta opening, but with most of
it transparent; then very soon afterward I received the message "Segmentation
fault (core dumped)". Those same two things occurred after I entered the
command "vlc -I qt" in the directory /usr/bin. So my current problem is
associated with Qt and the main window of vlc-beta, not the so-called
"dummy interface" of vlc-beta. If the "menu" items and/or software controls
on vlc-beta's main window are considered plugins, then it appears to me
that the problem is in displaying those items on vlc-beta's main window.
But in vlc-beta's code and its output and on the Internet this main window
is called the main interface; or Qt has been called the default interface
for VLC on https://wiki.videolan.org/Qt_Interface/. In some of my past
executions of "vlc" I have seen the output "ReferenceError: mainInterface
is not defined," but not on December 15, 2021, after having installed lots
of software packages relating to the display protocol Wayland (
https://www.maketecheasier.com/what-is-wayland/) and/or the widget "tool
kit" Qt, version 5, for making graphical user interfaces and applications
suitable for use in various computer operating systems, which are otherwise
called platforms [https://en.wikipedia.org/wiki/Qt_(software)].


Here is a listing of my virtual computer's "hardware" in my Leap-15.3
installation in VirtualBox on December 15, 2021.


newbie at linux-hdi0:/usr/bin> inxi -G

Graphics:

Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter

driver: vboxvideo v: 6.1.30 r148432

Display: x11 server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa

resolution: 1308x600

OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.2.4

newbie at linux-hdi0:/usr/bin>


And here is a list of the online repositories to which I currently have set
up access in my Leap-15.3 installation when it is online. To obtain this
list I entered the command "zypper repos" as a "root" user.


linux-hdi0:/usr/bin # zypper repos

Repository priorities are without effect. All enabled repositories share
the same priority.


# | Alias | Name | Enabled | GPG Check | Refresh

---+----------------------------------+---------------------------------------------------------------------------------------------+---------+-----------+--------

1 | http-ftp.gwdg.de-2f96c871 | Packman Repository | Yes | (r ) Yes | Yes

2 | http-opensuse-guide.org-46cfd2d4 | libdvdcss repository | Yes | (r )
Yes | Yes

3 | openSUSE-Leap-15.3-1 | openSUSE-Leap-15.3-1 | Yes | (r ) Yes | No

4 | repo-backports-debug-update | Update repository with updates for
openSUSE Leap debuginfo packages from openSUSE Backports | No | ---- | ----

5 | repo-backports-update | Update repository of openSUSE Backports | Yes |
(r ) Yes | Yes

6 | repo-debug | Debug Repository | No | ---- | ----

7 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ----

8 | repo-debug-update | Update Repository (Debug) | No | ---- | ----

9 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No |
---- | ----

10 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes

11 | repo-oss | Main Repository | Yes | (r ) Yes | Yes

12 | repo-sle-debug-update | Update repository with debuginfo for updates
from SUSE Linux Enterprise 15 | No | ---- | ----

13 | repo-sle-update | Update repository with updates from SUSE Linux
Enterprise 15 | Yes | (r ) Yes | Yes

14 | repo-source | Source Repository | No | ---- | ----

15 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes

16 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes |
Yes

linux-hdi0:/usr/bin #


With the help of a good teaching video on how to use the GNU’s Not Unix
(GNU) debugger (gdb) on https://www.youtube.com/watch?v=bWH-nL7v5F4, by
Doctor Chris Bourke of the University of Nebraska in Lincoln, Nebraska, The
United States of America, I was able to proceed, statement-by-statement, in
some of vlc-beta’s computer code with those statements looking to me like
C-language statements, but more often looking like C-programming-language
statements if I omitted the command within gdb of “layout next”;
otherwise after
entering the command “layout next” on December 14, 2021 I saw a number of
lines in an upper panel each containing a hexadecimal address, a short word
or phrase like “mov”, “test”, “call”, “je”, et cetera (Maybe it was
assembly language??? But perhaps things looked strange instead of like
C-language statements because I was missing some installed debugging
packages, as the output below seemed to indicate.) Below the input “n”
stands for “next” to instruct the computer program to go to the next
statement to execute it in the computer code. So below are the results of
some exploring of mine with vlc-beta on December 15, 2021 using the gdb.
Despite "vlc" instead of vlc-beta appearing in the first command below, it
is for vlc-beta. And I removed all of the VLC computer software and the
VLC-based computer program caffeine from openSUSE in my Leap-15.3
installation. Instead I have vlc-beta computer software from the Packman
online repository installed in my Leap-15.3 installation.


newbie at linux-hdi0:~> gdb vlc

GNU gdb (GDB; SUSE Linux Enterprise 15) 11.1

Copyright (C) 2021 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-suse-linux".

Type "show configuration" for configuration details.

For bug reporting instructions, please see:

<http://bugs.opensuse.org/>.

Find the GDB manual and other documentation resources online at:

<http://www.gnu.org/software/gdb/documentation/>.


For help, type "help".

Type "apropos word" to search for commands related to "word"...

Reading symbols from vlc...

Reading symbols from
/usr/lib/debug/usr/bin/vlc-20211210.736213df13-pm153.17.1.x86_64.debug...

(gdb) break libvlc_add_intf

Breakpoint 1 at 0x1140

(gdb) run

Starting program: /usr/bin/vlc

Missing separate debuginfos, use: zypper install
glibc-debuginfo-2.31-9.6.1.x86_64

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

VLC media player 20211210 Otto Chriek (revision 736213df13)

[New Thread 0x7ffff7f16700 (LWP 4794)]

[New Thread 0x7ffff4470700 (LWP 4795)]

[New Thread 0x7ffff436f700 (LWP 4796)]

[New Thread 0x7ffff426e700 (LWP 4797)]

[New Thread 0x7ffff416d700 (LWP 4798)]

[New Thread 0x7ffff2576700 (LWP 4799)]

[New Thread 0x7fffedd75700 (LWP 4800)]

[New Thread 0x7fffeda5f700 (LWP 4801)]


Thread 1 "vlc" hit Breakpoint 1, libvlc_add_intf
(p_instance=p_instance at entry=0x55555575dbd0, name=name at entry=0x0) at
playlist.c:40

40 {

Missing separate debuginfos, use: zypper install
libFLAC8-debuginfo-1.3.2-3.6.1.x86_64 libXau6-debuginfo-1.0.8-1.26.x86_64
libcap2-debuginfo-2.26-4.6.1.x86_64
libdbus-1-3-debuginfo-1.12.2-8.11.2.x86_64
libgpg-error0-debuginfo-1.29-1.8.x86_64
libidn11-debuginfo-1.34-3.2.2.x86_64 liblz4-1-debuginfo-1.9.2-3.3.1.x86_64
liblzma5-debuginfo-5.2.3-4.3.1.x86_64 libogg0-debuginfo-1.3.2-1.24.x86_64
libpcre1-debuginfo-8.45-20.10.1.x86_64 libpulse0-debuginfo-14.2-4.2.x86_64
libsndfile1-debuginfo-1.0.28-5.12.1.x86_64
libspeex1-debuginfo-1.2-3.3.1.x86_64
libsystemd0-debuginfo-246.16-7.21.1.x86_64
libvorbis0-debuginfo-1.3.6-4.3.1.x86_64
libvorbisenc2-debuginfo-1.3.6-4.3.1.x86_64
libxcb1-debuginfo-1.13-3.5.1.x86_64 libzstd1-debuginfo-1.4.4-1.6.1.x86_64

(gdb) n

41 if( libvlc_InternalAddIntf( p_instance->p_libvlc_int, name ))

(gdb) print *p_instance

$1 = {p_libvlc_int = 0x55555575dc40, ref_count = {refs = 1},

p_callback_list = 0x0, log = {cb = 0x0, data = 0x0}, dialog = {cbs = {

pf_display_error = 0x0, pf_display_login = 0x0,

pf_display_question = 0x0, pf_display_progress = 0x0, pf_cancel = 0x0,

pf_update_progress = 0x0}, data = 0x0}}

(gdb) print *Quit

(gdb) print *0x55555575dc40

$2 = 1433787704

(gdb) print *p_libvlc_int

No symbol "p_libvlc_int" in current context.

(gdb) print name

$3 = 0x0

(gdb) print p_libvlc_int

No symbol "p_libvlc_int" in current context.

(gdb) print *0x0

Cannot access memory at address 0x0

(gdb) quit

A debugging session is active.


Inferior 1 [process 4790] will be killed.


Quit anyway? (y or n) y

newbie at linux-hdi0:~>


With some repetition, but going farther along than in the above sequence of
entries:


newbie at linux-hdi0:/usr/bin> gdb vlc

GNU gdb (GDB; SUSE Linux Enterprise 15) 11.1

Copyright (C) 2021 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-suse-linux".

Type "show configuration" for configuration details.

For bug reporting instructions, please see:

<http://bugs.opensuse.org/>.

Find the GDB manual and other documentation resources online at:

<http://www.gnu.org/software/gdb/documentation/>.


For help, type "help".

Type "apropos word" to search for commands related to "word"...

Reading symbols from vlc...

Reading symbols from
/usr/lib/debug/usr/bin/vlc-20211210.736213df13-pm153.17.1.x86_64.debug...

(gdb) break libvlc_add_intf

Breakpoint 1 at 0x1140

(gdb) run

Starting program: /usr/bin/vlc

Missing separate debuginfos, use: zypper install
glibc-debuginfo-2.31-9.6.1.x86_64

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

VLC media player 20211210 Otto Chriek (revision 736213df13)

[New Thread 0x7ffff7f16700 (LWP 6320)]

[New Thread 0x7ffff4470700 (LWP 6321)]

[New Thread 0x7ffff436f700 (LWP 6322)]

[New Thread 0x7ffff426e700 (LWP 6323)]

[New Thread 0x7ffff416d700 (LWP 6324)]

[New Thread 0x7ffff2576700 (LWP 6325)]

[New Thread 0x7ffff1d75700 (LWP 6326)]

[New Thread 0x7ffff1a5f700 (LWP 6327)]


Thread 1 "vlc" hit Breakpoint 1, libvlc_add_intf
(p_instance=p_instance at entry=0x55555575dbd0, name=name at entry=0x0) at
playlist.c:40

40 {

Missing separate debuginfos, use: zypper install
libFLAC8-debuginfo-1.3.2-3.6.1.x86_64 libXau6-debuginfo-1.0.8-1.26.x86_64
libcap2-debuginfo-2.26-4.6.1.x86_64
libdbus-1-3-debuginfo-1.12.2-8.11.2.x86_64
libgpg-error0-debuginfo-1.29-1.8.x86_64
libidn11-debuginfo-1.34-3.2.2.x86_64 liblz4-1-debuginfo-1.9.2-3.3.1.x86_64
liblzma5-debuginfo-5.2.3-4.3.1.x86_64 libogg0-debuginfo-1.3.2-1.24.x86_64
libpcre1-debuginfo-8.45-20.10.1.x86_64 libpulse0-debuginfo-14.2-4.2.x86_64
libsndfile1-debuginfo-1.0.28-5.12.1.x86_64
libspeex1-debuginfo-1.2-3.3.1.x86_64
libsystemd0-debuginfo-246.16-7.21.1.x86_64
libvorbis0-debuginfo-1.3.6-4.3.1.x86_64
libvorbisenc2-debuginfo-1.3.6-4.3.1.x86_64
libxcb1-debuginfo-1.13-3.5.1.x86_64 libzstd1-debuginfo-1.4.4-1.6.1.x86_64

(gdb) n

41 if( libvlc_InternalAddIntf( p_instance->p_libvlc_int, name ))

(gdb) n

40 {

(gdb) n

41 if( libvlc_InternalAddIntf( p_instance->p_libvlc_int, name ))

(gdb) n

n[000055555575dc40] main libvlc: Running vlc with the default interface.
Use 'cvlc' to use vlc without interface.

[Detaching after vfork from child process 6328]

[New Thread 0x7ffff0152700 (LWP 6335)]

[New Thread 0x7fffcbe1f700 (LWP 6336)]

[New Thread 0x7fffc1e03700 (LWP 6337)]

[New Thread 0x7fffc1602700 (LWP 6338)]

[New Thread 0x7fffc0e01700 (LWP 6339)]

[New Thread 0x7fffb3dd5700 (LWP 6340)]

[New Thread 0x7fffb26ad700 (LWP 6341)]

[New Thread 0x7fff9bbfd700 (LWP 6342)]

[New Thread 0x7fff9b3fc700 (LWP 6343)]

[New Thread 0x7fff9abfb700 (LWP 6344)]

[New Thread 0x7fff9a3fa700 (LWP 6345)]

[New Thread 0x7fff99bf9700 (LWP 6346)]

[New Thread 0x7fff993f8700 (LWP 6347)]

[New Thread 0x7fff98bf7700 (LWP 6348)]

[New Thread 0x7fff83fff700 (LWP 6349)]

[New Thread 0x7fff837fe700 (LWP 6350)]

[New Thread 0x7fff81ca4700 (LWP 6351)]

50 }

Missing separate debuginfos, use: zypper install
Mesa-dri-debuginfo-20.2.4-57.12.x86_64
Mesa-libGL1-debuginfo-20.2.4-57.13.x86_64
Mesa-libglapi0-debuginfo-20.2.4-57.13.x86_64
dbus-1-glib-debuginfo-0.108-1.29.x86_64
fcitx-qt5-debuginfo-1.2.5-bp153.2.2.1.x86_64
fontconfig-debuginfo-2.12.6-4.3.1.x86_64 gconf2-debuginfo-3.2.6-9.26.x86_64
gsettings-backend-dconf-debuginfo-0.34.0-2.27.x86_64
gtk2-theming-engine-adwaita-debuginfo-3.22.3-4.3.1.x86_64
gvfs-debuginfo-1.42.2-4.24.x86_64
kimageformats-debuginfo-5.76.0-bp153.3.2.1.x86_64
libHalf23-debuginfo-2.2.1-1.17.x86_64
libIex-2_2-23-debuginfo-2.2.1-1.17.x86_64
libIlmImf-2_2-23-debuginfo-2.2.1-3.38.1.x86_64
libIlmThread-2_2-23-debuginfo-2.2.1-1.17.x86_64
libKF5Archive5-debuginfo-5.76.0-bp153.2.2.1.x86_64
libLLVM11-debuginfo-11.0.1-1.26.x86_64
libQt5Core5-debuginfo-5.12.7-4.12.2.x86_64
libQt5DBus5-debuginfo-5.12.7-4.12.2.x86_64
libQt5Gui5-debuginfo-5.12.7-4.12.2.x86_64
libQt5Network5-debuginfo-5.12.7-4.12.2.x86_64
libQt5QuickControls2-5-debuginfo-5.12.7-1.53.x86_64
libQt5Svg5-debuginfo-5.12.7-3.3.1.x86_64
libQt5Widgets5-debuginfo-5.12.7-4.12.2.x86_64
libQt5X11Extras5-debuginfo-5.12.7-1.49.x86_64
libQtQuick5-debuginfo-5.12.7-4.2.1.x86_64
libSM6-debuginfo-1.2.2-1.23.x86_64
libX11-xcb1-debuginfo-1.6.5-3.21.1.x86_64
libXcomposite1-debuginfo-0.4.4-1.23.x86_64
libXcursor1-debuginfo-1.1.15-1.18.x86_64
libXext6-debuginfo-1.3.3-1.30.x86_64 libXi6-debuginfo-1.7.9-3.2.1.x86_64
libXinerama1-debuginfo-1.1.3-1.22.x86_64
libXrandr2-debuginfo-1.5.1-2.17.x86_64
libXrender1-debuginfo-0.9.10-1.30.x86_64
libblkid1-debuginfo-2.36.2-4.5.1.x86_64
libbz2-1-debuginfo-1.0.6-5.11.1.x86_64
libcairo2-debuginfo-1.16.0-1.55.x86_64
libcanberra-gtk0-debuginfo-0.30-3.2.3.x86_64
libcanberra-gtk2-module-debuginfo-0.30-3.2.3.x86_64
libdatrie1-debuginfo-0.2.9-1.25.x86_64
libdouble-conversion3-debuginfo-3.1.5-3.2.1.x86_64
libdrm_nouveau2-debuginfo-2.4.104-1.12.x86_64
libdrm_radeon1-debuginfo-2.4.104-1.12.x86_64
libedit0-debuginfo-3.1.snap20150325-2.12.x86_64
libelf1-debuginfo-0.168-4.5.3.x86_64 libexpat1-debuginfo-2.2.5-3.6.1.x86_64
libffi7-debuginfo-3.2.1.git259-10.8.x86_64
libfreetype6-debuginfo-2.10.1-4.8.1.x86_64
libfribidi0-debuginfo-1.0.5-3.3.1.x86_64
libgcc_s1-debuginfo-11.2.1+git610-1.3.9.x86_64
libglib-2_0-0-debuginfo-2.62.6-3.6.1.x86_64
libglvnd-debuginfo-1.3.2-1.49.x86_64
libgobject-2_0-0-debuginfo-2.62.6-3.6.1.x86_64
libgtk-2_0-0-debuginfo-2.24.32+67-2.28.x86_64
libharfbuzz0-debuginfo-2.6.4-1.56.x86_64
libicu-suse65_1-debuginfo-65.1-4.2.1.x86_64
libjasper4-debuginfo-2.0.14-3.19.1.x86_64
libjbig2-debuginfo-2.1-1.31.x86_64 libjpeg8-debuginfo-8.1.2-5.18.1.x86_64
liblcms2-2-debuginfo-2.9-3.3.1.x86_64 libltdl7-debuginfo-2.4.6-3.4.1.x86_64
libmodman1-debuginfo-2.0.1-1.27.x86_64
libmount1-debuginfo-2.36.2-4.5.1.x86_64
libopenssl1_1-debuginfo-1.1.1d-11.30.1.x86_64
libpango-1_0-0-debuginfo-1.44.7+11-1.25.x86_64
libpcre2-16-0-debuginfo-10.31-3.3.1.x86_64
libpng16-16-debuginfo-1.6.34-3.9.1.x86_64
libproxy1-debuginfo-0.4.15-12.41.x86_64
libqt5-qtimageformats-debuginfo-5.12.7-1.50.x86_64
libqt5-qtquickcontrols2-debuginfo-5.12.7-1.53.x86_64
libstdc++6-debuginfo-11.2.1+git610-1.3.9.x86_64
libthai0-debuginfo-0.1.27-1.16.x86_64
libuuid1-debuginfo-2.36.2-4.5.1.x86_64
libwayland-client0-debuginfo-1.18.0-1.19.x86_64
libwebp7-debuginfo-1.0.3-1.62.x86_64
libxcb-composite0-debuginfo-1.13-3.5.1.x86_64
libxcb-damage0-debuginfo-1.13-3.5.1.x86_64
libxcb-dri2-0-debuginfo-1.13-3.5.1.x86_64
libxcb-dri3-0-debuginfo-1.13-3.5.1.x86_64
libxcb-keysyms1-debuginfo-0.4.0-1.23.x86_64
libxcb-present0-debuginfo-1.13-3.5.1.x86_64
libxcb-render-util0-debuginfo-0.3.9-1.23.x86_64
libxcb-render0-debuginfo-1.13-3.5.1.x86_64
libxcb-shape0-debuginfo-1.13-3.5.1.x86_64
libxcb-shm0-debuginfo-1.13-3.5.1.x86_64
libxcb-sync1-debuginfo-1.13-3.5.1.x86_64
libxcb-util1-debuginfo-0.4.0-1.23.x86_64
libxcb-xfixes0-debuginfo-1.13-3.5.1.x86_64
libxkbcommon-x11-0-debuginfo-0.8.2-3.3.1.x86_64
libxml2-2-debuginfo-2.9.7-3.37.1.x86_64 libz1-debuginfo-1.2.11-3.21.1.x86_64

(gdb) n

[Thread 0x7fffb26ad700 (LWP 6341) exited]

main (argc=<optimized out>, argv=0x7fffffffdf28) at vlc.c:245

245 libvlc_playlist_play (vlc);

Missing separate debuginfos, use: zypper install
libqt5-qtgraphicaleffects-debuginfo-5.12.7-1.53.x86_64

(gdb) n

249 sigdelset (&set, SIGCHLD);

(gdb) n

250 pthread_sigmask (SIG_SETMASK, &set, NULL);

(gdb) n

253 if (signal_ignored (SIGHUP))

(gdb) n

256 sigdelset (&set, SIGPIPE);

(gdb) n


Thread 25 "QQmlThread" received signal SIGSEGV, Segmentation fault.

[Switching to Thread 0x7fff837fe700 (LWP 6350)]

0x00007fffdba86613 in ?? () from /usr/lib64/libQt5Qml.so.5

(gdb) n

Cannot find bounds of current function

(gdb) n

Cannot find bounds of current function

(gdb) n

Cannot find bounds of current function

(gdb) quit

A debugging session is active.


Inferior 1 [process 6316] will be killed.


Quit anyway? (y or n) y

newbie at linux-hdi0:/usr/bin>


I tried to follow numerous other people's postings on the Internet to
enable the playing of a .mp4 file in the VLC. But unfortunately I failed in
all of those efforts with a segmentation fault using
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 or else with the lack of a
displayed video signal in
vlc-beta-20211104.b9e50b090c-pm153.10.1.16.1.x86_64 when in each case using
their Qt interfaces. So please help me eliminate the "Segmentation fault"
error and to be able to play a .mp4 video in
vlc-beta-20211206.07ed287157-pm153.16.1.x86_64 using its probably default,
Qt interface.


More information about the Packman mailing list