openSUSE Bugs June 2020

bugs@lists.opensuse.org

1 participants
3968 discussions

[Bug 1172341] New: Cannot open YaST through KDE system settings
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172341 Bug ID: 1172341 Summary: Cannot open YaST through KDE system settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: abhishek_amar2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: I opened the System Settings application under the KDE menu. I scrolled down to the bottom and clicked on YaST under System Administration. As soon as a click that a dialog pops up saying that System Settings has closed unexpectedly and the System Settings crashes. It is worthy to note that I can simply search for YaST and click on the first result that pops up in the KDE menu which is 'YaST(Administrator Settings)' and it opens up and works fine. Reproducible: Always Steps to Reproduce: 1. Super key(Windows key) to open KDE menu 2. Click on 'System Settings' 3. Scroll down to System Administration and under this there are 2 entries, 'System Information' and 'YaST' 4. Click on YaST 5. Dr Konqi dialog pops up on bottom right of the screen saying 'System Settings Closed Unexpectedly' Actual Results: As soon as I perform the above steps a Dr Konqi dialog pops up on bottom right of the screen saying 'System Settings Closed Unexpectedly'. The System Settings crashes and YaST fails to open. Expected Results: YaST administrator settings should have opened. It is worthy to note that I am using the default theme and have installed openSUSE Leap 15.2 RC using ext4 and not btrfs. And as to why I'm not using ext4 is described below: (Irrelevant to this issue: Btrfs on Tumbleweed was causing race conditions because of which all btrfs sub volumes were getting unmounted right after they were getting mounted and I could not access my snapshots without manually mounting each time and this was a systemd bug that isn't fixed and therefore I used ext4. More info here https://forums.opensuse.org/showthread.php/538011-Btrfs-subvolume-snapshots… ) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1172340] New: Several YaST modules can be started by typing "yast2 $module <tab><tab>"
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172340 Bug ID: 1172340 Summary: Several YaST modules can be started by typing "yast2 $module <tab><tab>" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: suse-beta(a)cboltz.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If you have bash-completion installed, several YaST modules can be started by typing yast2 $module <tab><tab> without pressing return. Background: when pressing <tab><tab>, bash completion runs yast2 $module --help in the background to find out which commandline options are available. Affected modules: a) modules that simply get started by yast2 $module --help alternatives auth-client fonts journal krb-server ldapkrb ldap-server partitioner virt-install vpn b) modules that show a window for a second and then print the help (wrong order in the code): users samba-client samba-server c) special case nis - asks to install the "ypbind" package, then exits and prints the help. Also a case of wrong order in the code. I don't have all YaST modules installed, therefore I'd recommend that you test yourself: for mod in `yast2 -l | sed 1d` ; do echo === trying $mod yast2 $mod --help echo === done $mod echo done Each module should at least have enough commandline handling to print This YaST2 module does not support the command line interface. (Ideally using exactly this text, because it's already translated.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172018] New: The 32-bit GStreamer 1.0 packages are broken on 64-bit openSUSE Leap
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172018 Bug ID: 1172018 Summary: The 32-bit GStreamer 1.0 packages are broken on 64-bit openSUSE Leap Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: fgouget(a)codeweavers.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838082 --> http://bugzilla.opensuse.org/attachment.cgi?id=838082&action=edit Test case Description of problem: 32-bit applications fail to find any GStreamer element with errors like: (gst-plugin-scanner:16235): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-1.0/libgstvideoconvert.so': /usr/lib/gstreamer-1.0/libgstvideoconvert.so: wrong ELF class: ELFCLASS32 Versions impacted: This impacts at least gstreamer 1.12.5-lp151.2.5 package in openSUSE Leap 15.1. This issue was supposedly ****fixed in Tumbleweed in may 2018***** (see bug 1049452). Yet here we are two years later with the same issue in openSUSE Leap 15.1, hence this new bug. How reproducible: 100% reproducible. Steps to reproduce: 1. Install a 64-bit version of openSUSE Leap. This is expected to install the 64-bit GStreamer packages. 2. Install the 32-bit GStreamer packages: zypper install gstreamer-32bit gstreamer-plugins-base-32bit 3. Ideally I'd recommend using the 32 bit gst-inspect-1.0 tool but it is nowhere to be found. So instead download the attached test application and compile it: gcc -m32 -o cxgstcheck `pkg-config --cflags gstreamer-1.0` `pkg-config --libs gstreamer-1.0` cxgstcheck.c 4. Clear the 32-bit registry and run the 32-bit cxgstcheck application to force recreating it: rm ~/.cache/gstreamer-1.0/registry.i586.bin ./cxgstcheck Note that while in this case we are using a test application, this affects any 32-bit application. In particular it impacts Wine and thus any 32-bit Windows application (such as games) that uses winegstreamer.dll. Actual results: $ ./cxgstcheck [...] (gst-plugin-scanner:16235): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-1.0/libgstvideoconvert.so': /usr/lib/gstreamer-1.0/libgstvideoconvert.so: wrong ELF class: ELFCLASS32 [...] Bitness: 32 bits could not instantiate h264parse could not instantiate videoconvert could not instantiate vp9dec could not instantiate asfdemux Expected results: cxgstcheck should not issue ELFCLASS32 errors. It should also at least find the videoconvert element since we installed gstreamer-plugins-base-32bit. $ ./cxgstcheck Bitness: 32 bits could not instantiate h264parse found videoconvert could not instantiate vp9dec could not instantiate asfdemux Additional info: The reason for this bug is that GStreamer applications rely on the ~/.cache/gstreamer-1.0/registry.i586.bin file to figure out which plugin (aka library) provides a given GStreamer element. However generating that file is delegated to the /usr/lib/gstreamer-1.0/gst-plugin-scanner tool and on a 64-bit system this is a 64-bit executable provided by the gstreamer package. As a 64-bit tool it is only able to load 64-bit GStreamer plugins. As a result ~/.cache/gstreamer-1.0/registry.i586.bin is empty and 32-bit applications are unable to find any GStreamer element. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1172018] The 32-bit GStreamer 1.0 packages are broken on 64-bit openSUSE Leap
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172018 http://bugzilla.suse.com/show_bug.cgi?id=1172018#c8 --- Comment #8 from Francois Gouget <fgouget(a)codeweavers.com> --- (In reply to Liu Shukui from comment #7) > the reproducer cannot be compiled on sle15sp1. Right. 32-bit GStremaer development is quite broken (what with gstreamer-devel-32bit being missing) but it seems to be making progress. In the meantime here is how to compile it: zypper install gcc-32bit glibc-devel-32bit gstreamer-devel zypper install glib2-devel glib2-devel-32bit zypper install gstreamer-plugins-base-devel gstreamer-plugins-base-devel-32bit ln -s /usr/lib/libgstbase-1.0.so.0 /usr/lib/libgstbase-1.0.so ln -s /usr/lib/libgstreamer-1.0.so.0 /usr/lib/libgstreamer-1.0.so # one line gcc -m32 -o checkgst32 `pkg-config --cflags gstreamer-1.0` `pkg-config --libs gstreamer-1.0` checkgst.c -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172323] New: cmake not using the proper libexec path
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172323 Bug ID: 1172323 Summary: cmake not using the proper libexec path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- By "proper" I mean the SUSE-sanctioned one. CMAKE_INSTALL_LIBEXECDIR points to /usr/libexec instead of /usr/lib: shouldn't it be made to match the %{_libexecdir} macro? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1172331] New: cmake macro sets CMAKE_SKIP_RPATH to ON breaking vtk and possibly other builds
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172331 Bug ID: 1172331 Summary: cmake macro sets CMAKE_SKIP_RPATH to ON breaking vtk and possibly other builds Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since https://build.opensuse.org/request/show/791240 the %cmake macro sets `CMAKE_SKIP_RPATH=ON` which causes rpaths to be disabled entirely from being used, even in the build tree. This is wrong. Several applications (vtk, paraview, others) rightly use rpaths in their build tree only to later strip the installed binaries of any rpaths. What the macro should really set is `CMAKE_SKIP_INSTALL_RPATHS=ON` instead to ensure that installed binaries are stripped of rpaths, but leave CMAKE_SKIP_RPATH untouched. See <https://discourse.vtk.org/t/building-fails-generating-wrap-hierarchy-for-vt…> -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1168661] [Build 20200404] openQA test fails in await_install of installer, fails to reboot on SMP systems
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1168661 http://bugzilla.suse.com/show_bug.cgi?id=1168661#c15 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED Flags|needinfo?(okurz(a)suse.com) | --- Comment #15 from Oliver Kurz <okurz(a)suse.com> --- Hi Daniel, (In reply to Daniel Molkentin from comment #14) > Why was the test disabled even though the last run succeeded? I do not understand why you think the test would be disabled. The description mentions the "Always latest result in this scenario" which currently links to https://openqa.opensuse.org/tests/1282620 from 3 days ago. The test scenario is enabled on Tumbleweed and triggered on every new Tumbleweed snapshot. Please keep in mind that old job results are deleted after some time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172018] The 32-bit GStreamer 1.0 packages are broken on 64-bit openSUSE Leap
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172018 http://bugzilla.suse.com/show_bug.cgi?id=1172018#c7 Liu Shukui <skliu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skliu(a)suse.com --- Comment #7 from Liu Shukui <skliu(a)suse.com> --- the reproducer cannot be compiled on sle15sp1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1049452] The 32 bit GStreamer 1.0 packages are broken on 64 bit openSUSE
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1049452 http://bugzilla.suse.com/show_bug.cgi?id=1049452#c8 Liu Shukui <skliu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skliu(a)suse.com --- Comment #8 from Liu Shukui <skliu(a)suse.com> --- the reproducer cannot be compiled on sle15sp1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1167866] [Build 20200325] yast2 inst_release_notes: no rel notes shown
by bugzilla_noreply＠suse.com 01 Jun '20

01 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1167866 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Flags| |needinfo?(jreidinger(a)suse.c | |om) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs June 2020