September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203427] New: distrobox should be installed by default for microos desktop
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203427 Bug ID: 1203427 Summary: distrobox should be installed by default for microos desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: pranav.sharma.ama(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- distrobox requires less fiddling with podman / base image, especially to get gui apps to work -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202162] New: MicroOS Desktop: Shutdown with Update results in Restart
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202162 Bug ID: 1202162 Summary: MicroOS Desktop: Shutdown with Update results in Restart Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time I select 'Shutdown' and the pop-up asks to install pending updates, the system performs a restart, not a shutdown.... -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1200461] New: Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200461 Bug ID: 1200461 Summary: Dracut locks computer, fails to generate initrd file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mfdemicco(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859545 --> http://bugzilla.opensuse.org/attachment.cgi?id=859545&action=edit Photo of screen at moment of freeze When I update to kernel 5.18.1-1 or 5.18.2.1, Dracut locks up my system requiring a power button reboot when creating the initrd file. I also tried installing the latest version of Tumbleweed to another partition, and the installation locked up the computer about 50% into the installation with no creation of the initrd file. The computer freezes at: Dracut: *** Including module: kernel-modules *** When I look in my /boot folder, everything for the kernel is created except for the initrd file I've done a search and can't find anyone that has the same problem. The system runs file with the older kernel 5.17.4-1. I have a legacy BIOS system. -- You are receiving this mail because: You are on the CC list for the bug.

1 39

[Bug 1194202] New: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header)
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194202 Bug ID: 1194202 Summary: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- PE images have a timestamp in the header: https://blog.beuc.net/posts/Practical_basics_of_reproducible_builds_2/ Debian has some patches to use SOURCE_DATE_EPOCH instead of the current time: https://salsa.debian.org/mingw-w64-team/binutils-mingw-w64/-/blob/master/de… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1202662] New: VUL-0: CVE-2020-35511: pngcheck: Buffer overflow in pngcheck 2.4.0 via a crafted png file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202662 Bug ID: 1202662 Summary: VUL-0: CVE-2020-35511: pngcheck: Buffer overflow in pngcheck 2.4.0 via a crafted png file Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/340566/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pgajdos(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-35511 A global buffer overflow was discovered in pngcheck function in pngcheck-2.4.0(5 patches applied) via a crafted png file. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35511 https://www.cve.org/CVERecord?id=CVE-2020-35511 http://www.libpng.org/pub/png/apps/pngcheck.html -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1202269] New: supportconfig does not include expected YaST logs
by bugzilla_noreply＠suse.com 20 Dec '22

20 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202269 Bug ID: 1202269 Summary: supportconfig does not include expected YaST logs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We've notice that expected YaST logs aren't being (fully) included in recently attached supportconfig files. For example, we miss the content of the /var/log/YaST2/y2log. After taking a look at the code, we think it could be because of a recent change in `conf_files`. Please, have a look at the issue created in the supportconfig's Github project, https://github.com/openSUSE/supportutils/issues/134 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1168405] New: adjust issue handling to new agetty
by bugzilla_noreply＠novell.com 20 Dec '22

20 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1168405 Bug ID: 1168405 Summary: adjust issue handling to new agetty Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- agetty from util-linux 2.35 (not yet packaged) supports reading issue files from /run and /usr in the following way: if /etc/issue exists: read /etc/issue and /etc/issue.d else if /run/issue exists or /run/issue.d has any files read those else read /usr/lib/issue read /usr/lib/issue.d Moreover, the \4 and \6 escape codes use the first configured interface to print the IP address. That means for the most useful default case we don't need to run the extra code of issue generator to enumerate network interfaces and merge issue files anymore. We can rely on agetty built-in features only. Those who need the extra features to print ssh keys or custom computed stuff could still install issue-generator. So I propose the following change: - don't hard require issue-generator in openSUSE-release - don't ship /etc/issue - ship /usr/lib/issue.d/10-openSUSE.issue with the following content: Welcome to \S{PRETTY_NAME} \S{VERSION_ID} - Kernel \r (\l). \4 \6 -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1189991] New: qt5 rcc error: No data signature found
by bugzilla_noreply＠suse.com 20 Dec '22

20 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189991 Bug ID: 1189991 Summary: qt5 rcc error: No data signature found 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: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- build log: [ 104s] g++ -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -DOPENSSL_LOAD_CONF -g -Wall -fprofile-arcs -ftest-coverage -fno-access-control -O0 -O2 -std=gnu++11 -pthread -Wall -Wextra -D_REENTRANT -fPIC -DVERSION=5.9.13 -DQT_NO_DEBUG_OUTPUT -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_DBUS_LIB -DQT_TESTLIB_LIB -DQT_CORE_LIB -DQT_TESTCASE_BUILDDIR='"/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests"' -c ./qrc_files.cpp -o ./qrc_files.tmp.o [ 104s] /usr/lib64/qt5/bin/rcc -name files files.qrc -pass 2 -temp ./qrc_files.tmp.o -o qrc_files.o [ 104s] No data signature found [ 104s] make[1]: *** [Makefile:884: qrc_files.o] Error 1 [ 104s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests' [ 105s] make[1]: Entering directory '/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests' Removing resources_big from .pro can workaround this issue. But it will be out of memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1177083] New: python-aliyun-python-sdk-core package ships a vendored python-requests package
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1177083 Bug ID: 1177083 Summary: python-aliyun-python-sdk-core package ships a vendored python-requests package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: adrian.glaubitz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The python-aliyun-python-sdk-core ships a vendored version of the python-requests package which should be removed in the next version update to avoid hidden vulnerabilities in the embedded version of python-requests as well as avoid code duplicity. -- You are receiving this mail because: You are on the CC list for the bug.

1 9