May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223169] New: gcc14 compilation fails
by bugzilla_noreply＠suse.com 12 Nov '24

12 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1223169 Bug ID: 1223169 Summary: gcc14 compilation fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: rguenther(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our gcc14 build fails - possibly because I am using -j1 for deterministic compilation order. [31724s] /bin/sh ./libtool --tag=CC --mode=compile /home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/xgcc -B/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/ -B/usr/x86_64-suse-linux/bin/ -B/usr/x86_64-suse-linux/lib/ -isystem /usr/x86_64-suse-linux/include -isystem /usr/x86_64-suse-linux/sys-include -DHAVE_CONFIG_H -I. -I../../../../libgfortran -iquote../../../../libgfortran/io -I../../../../libgfortran/../gcc -I../../../../libgfortran/../gcc/config -I../../.././gcc -I../../../../libgfortran/../libgcc -I../../libgcc -I../../../../libgfortran/../libbacktrace -I../../libbacktrace -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -m32 -MT unix.lo -MD -MP -MF .deps/unix.Tpo -c -o unix.lo `test -f 'io/unix.c' || echo '../../../../libgfortran/'`io/unix.c [31724s] libtool: compile: /home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/xgcc -B/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/ -B/usr/x86_64-suse-linux/bin/ -B/usr/x86_64-suse-linux/lib/ -isystem /usr/x86_64-suse-linux/include -isystem /usr/x86_64-suse-linux/sys-include -DHAVE_CONFIG_H -I. -I../../../../libgfortran -iquote../../../../libgfortran/io -I../../../../libgfortran/../gcc -I../../../../libgfortran/../gcc/config -I../../.././gcc -I../../../../libgfortran/../libgcc -I../../libgcc -I../../../../libgfortran/../libbacktrace -I../../libbacktrace -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -m32 -MT unix.lo -MD -MP -MF .deps/unix.Tpo -c ../../../../libgfortran/io/unix.c -fPIC -DPIC -o .libs/unix.o [31724s] ../../../../libgfortran/io/unix.c: In function ‘find_file’: [31724s] ../../../../libgfortran/io/unix.c:1704:26: error: ‘id’ undeclared (first use in this function) [31724s] 1704 | # define FIND_FILE0_ARGS id, path [31724s] | ^~ [31724s] ../../../../libgfortran/io/unix.c:1778:30: note: in expansion of macro ‘FIND_FILE0_ARGS’ [31724s] 1778 | u = find_file0 (unit_root, FIND_FILE0_ARGS); [31724s] | ^~~~~~~~~~~~~~~ [31724s] ../../../../libgfortran/io/unix.c:1704:26: note: each undeclared identifier is reported only once for each function it appears in [31724s] 1704 | # define FIND_FILE0_ARGS id, path [31724s] | ^~ [31724s] ../../../../libgfortran/io/unix.c:1778:30: note: in expansion of macro ‘FIND_FILE0_ARGS’ [31724s] 1778 | u = find_file0 (unit_root, FIND_FILE0_ARGS); [31724s] | ^~~~~~~~~~~~~~~ [31724s] make[6]: *** [Makefile:6863: unix.lo] Error 1 [31724s] make[6]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/x86_64-suse-linux/32/libgfortran' [31724s] make[5]: *** [Makefile:1677: all] Error 2 [31724s] make[5]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/x86_64-suse-linux/32/libgfortran' [31724s] make[4]: *** [Makefile:7877: multi-do] Error 1 [31724s] make[4]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/x86_64-suse-linux/libgfortran' [31724s] make[3]: *** [Makefile:7847: all-multi] Error 2 [31724s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/x86_64-suse-linux/libgfortran' [31724s] make[2]: *** [Makefile:1677: all] Error 2 [31724s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/x86_64-suse-linux/libgfortran' [31724s] make[1]: *** [Makefile:22460: all-target-libgfortran] Error 2 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218342] New: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed
by bugzilla_noreply＠suse.com 11 Nov '24

11 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218342 Bug ID: 1218342 Summary: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed 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: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted for OpenSSL 3.2.0 upgrade in Tumbleweed. OpenSSL 3.2 migration guide: https://www.openssl.org/docs/man3.2/man7/migration_guide.html -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1221676] New: openSUSE MicroOS cannot boot up after installation from Tumbleweed
by bugzilla_noreply＠suse.com 08 Nov '24

08 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221676 Bug ID: 1221676 Summary: openSUSE MicroOS cannot boot up after installation from Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873628 --> https://bugzilla.suse.com/attachment.cgi?id=873628&action=edit all logs /var/log install MicroOS from Tumbleweed on my RPi 4: After installation I try to install microos_gnome_desktop without success(see blow details). Then I reboot it. But it comes to boot menu and cannot boot up and stucks forever. I tried to boot from recovery mode and it can reach to emergency mode only. -- localhost:~ # zypper in -t pattern microos_base Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed pattern:microos_base-5.0-85.1.aarch64 requires 'patterns-microos-base', but this requirement cannot be provided not installable providers: patterns-microos-base-5.0-85.1.aarch64[repo-oss] Solution 1: Following actions will be done: deinstallation of product:openSUSE-20240314-0.aarch64 deinstallation of product:openSUSE-20240314-0.aarch64 deinstallation of systemd-presets-branding-openSUSE-12.2-23.3.noarch Solution 2: do not install pattern:microos_base-5.0-85.1.aarch64 Solution 3: break pattern:microos_base-5.0-85.1.aarch64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1 Resolving dependencies... Resolving package dependencies... The following 18 NEW packages are going to be installed: MicroOS-release MicroOS-release-appliance btrfsmaintenance busybox health-checker-plugins-MicroOS kdump kexec-tools lastlog2 liblastlog2-1 makedumpfile mandoc-bin microos-tools patterns-microos-base read-only-root-fs rebootmgr salt-transactional-update systemd-presets-branding-MicroOS wtmpdb The following NEW pattern is going to be installed: microos_base The following NEW product is going to be installed: "openSUSE MicroOS" The following 2 packages are going to be REMOVED: openSUSE-release systemd-presets-branding-openSUSE The following product is going to be REMOVED: "openSUSE Tumbleweed" 18 new packages to install, 2 to remove. Overall download size: 4.1 MiB. Already cached: 0 B. After the operation, additional 3.7 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: MicroOS-release-appliance-20240310-2096.1.aarch64 (openSUSE-Tumbleweed-Oss) (1/18), 8.5 KiB Retrieving: MicroOS-release-appliance-20240310-2096.1.aarch64.rpm .................................................[done] Retrieving: btrfsmaintenance-0.5-2.10.noarch (openSUSE-Tumbleweed-Oss) (2/18), 36.0 KiB Retrieving: btrfsmaintenance-0.5-2.10.noarch.rpm ....................................................[done (222.1 KiB/s)] Retrieving: busybox-1.36.1-3.3.aarch64 (openSUSE-Tumbleweed-Oss) (3/18), 677.0 KiB Retrieving: busybox-1.36.1-3.3.aarch64.rpm ............................................................[done (3.5 MiB/s)] Retrieving: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch (openSUSE-Tumbleweed-Oss) (4/18), 10.9 KiB Retrieving: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch.rpm ................................[done] Retrieving: kexec-tools-2.0.28-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (5/18), 116.4 KiB Retrieving: kexec-tools-2.0.28-1.1.aarch64.rpm ......................................................[done (927.1 KiB/s)] Retrieving: liblastlog2-1-1.3.1-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (6/18), 17.0 KiB Retrieving: liblastlog2-1-1.3.1-1.1.aarch64.rpm ......................................................[done (60.4 KiB/s)] Retrieving: makedumpfile-1.7.4-1.3.aarch64 (openSUSE-Tumbleweed-Oss) (7/18), 274.3 KiB Retrieving: makedumpfile-1.7.4-1.3.aarch64.rpm ......................................................[done (629.2 KiB/s)] Retrieving: mandoc-bin-1.14.6-5.3.aarch64 (openSUSE-Tumbleweed-Oss) (8/18), 220.0 KiB Retrieving: mandoc-bin-1.14.6-5.3.aarch64.rpm .......................................................[done (638.1 KiB/s)] Retrieving: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch (openSUSE-Tumbleweed-Oss) (9/18), 20.9 KiB Retrieving: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch.rpm ................................[done (141.0 KiB/s)] Retrieving: rebootmgr-2.3-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (10/18), 51.4 KiB Retrieving: rebootmgr-2.3-1.1.aarch64.rpm ...........................................................[done (358.5 KiB/s)] Retrieving: salt-transactional-update-3006.0-9.1.aarch64 (openSUSE-Tumbleweed-Oss) (11/18), 60.8 KiB Retrieving: salt-transactional-update-3006.0-9.1.aarch64.rpm ........................................[done (384.9 KiB/s)] Retrieving: wtmpdb-0.11.0-1.3.aarch64 (openSUSE-Tumbleweed-Oss) (12/18), 31.1 KiB Retrieving: wtmpdb-0.11.0-1.3.aarch64.rpm ...........................................................[done (180.6 KiB/s)] Retrieving: systemd-presets-branding-MicroOS-20230214-2.4.noarch (openSUSE-Tumbleweed-Oss) (13/18), 11.8 KiB Retrieving: systemd-presets-branding-MicroOS-20230214-2.4.noarch.rpm ................................[done (118.8 KiB/s)] Retrieving: MicroOS-release-20240310-2096.1.aarch64 (openSUSE-Tumbleweed-Oss) (14/18), 2.4 MiB Retrieving: MicroOS-release-20240310-2096.1.aarch64.rpm ...............................................[done (6.7 MiB/s)] Retrieving: lastlog2-1.3.1-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (15/18), 24.6 KiB Retrieving: kdump-2.0.1-1.2.aarch64 (openSUSE-Tumbleweed-Oss) (16/18), 99.1 KiB Retrieving: kdump-2.0.1-1.2.aarch64.rpm .............................................................[done (265.0 KiB/s)] Retrieving: microos-tools-2.21+git12-1.1.aarch64 (openSUSE-Tumbleweed-Oss) (17/18), 25.9 KiB Retrieving: microos-tools-2.21+git12-1.1.aarch64.rpm .................................................[done (59.1 KiB/s)] Retrieving: patterns-microos-base-5.0-85.1.aarch64 (openSUSE-Tumbleweed-Oss) (18/18), 26.1 KiB Retrieving: patterns-microos-base-5.0-85.1.aarch64.rpm ...............................................[done (58.0 KiB/s)] Checking for file conflicts: ......................................................................................[done] ( 1/20) Removing openSUSE-release-20240314-2110.1.aarch64 .........................................................[done] ( 2/20) Removing systemd-presets-branding-openSUSE-12.2-23.3.noarch ...............................................[done] ( 3/20) Installing: MicroOS-release-appliance-20240310-2096.1.aarch64 .............................................[done] Created symlink /etc/systemd/system/multi-user.target.wants/btrfsmaintenance-refresh.path -> /usr/lib/systemd/system/btrfsmaintenance-refresh.path. Created symlink /etc/systemd/system/timers.target.wants/btrfs-balance.timer -> /usr/lib/systemd/system/btrfs-balance.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-defrag.timer -> /usr/lib/systemd/system/btrfs-defrag.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-scrub.timer -> /usr/lib/systemd/system/btrfs-scrub.timer. Created symlink /etc/systemd/system/timers.target.wants/btrfs-trim.timer -> /usr/lib/systemd/system/btrfs-trim.timer. Updating /etc/sysconfig/btrfsmaintenance ... ( 4/20) Installing: btrfsmaintenance-0.5-2.10.noarch ..............................................................[done] ( 5/20) Installing: busybox-1.36.1-3.3.aarch64 ....................................................................[done] ( 6/20) Installing: health-checker-plugins-MicroOS-1.10+git20240111.cb84209-1.3.noarch ............................[done] ( 7/20) Installing: kexec-tools-2.0.28-1.1.aarch64 ................................................................[done] ( 8/20) Installing: liblastlog2-1-1.3.1-1.1.aarch64 ...............................................................[done] ( 9/20) Installing: makedumpfile-1.7.4-1.3.aarch64 ................................................................[done] (10/20) Installing: mandoc-bin-1.14.6-5.3.aarch64 .................................................................[done] (11/20) Installing: read-only-root-fs-1.0+git20240228.d85232a-1.1.noarch ..........................................[done] (12/20) Installing: rebootmgr-2.3-1.1.aarch64 .....................................................................[done] (13/20) Installing: salt-transactional-update-3006.0-9.1.aarch64 ..................................................[done] Created symlink /etc/systemd/system/default.target.wants/wtmpdb-update-boot.service -> /usr/lib/systemd/system/wtmpdb-update-boot.service. Created symlink /etc/systemd/system/timers.target.wants/wtmpdb-rotate.timer -> /usr/lib/systemd/system/wtmpdb-rotate.timer. (14/20) Installing: wtmpdb-0.11.0-1.3.aarch64 .....................................................................[done] (15/20) Installing: systemd-presets-branding-MicroOS-20230214-2.4.noarch ..........................................[done] (16/20) Installing: MicroOS-release-20240310-2096.1.aarch64 .......................................................[done] Created symlink /etc/systemd/system/default.target.wants/lastlog2-import.service -> /usr/lib/systemd/system/lastlog2-import.service. (17/20) Installing: lastlog2-1.3.1-1.1.aarch64 ....................................................................[done] Updating /etc/sysconfig/kdump ... (18/20) Installing: kdump-2.0.1-1.2.aarch64 .......................................................................[done] (19/20) Installing: microos-tools-2.21+git12-1.1.aarch64 ..........................................................[done] (20/20) Installing: patterns-microos-base-5.0-85.1.aarch64 ........................................................[done] %posttrans(kexec-tools-2.0.28-1.1.aarch64) script output: dracut[I]: Executing: /usr/bin/dracut --kver=6.7.9-1-default -f dracut[I]: Module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut[I]: Module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut[I]: Module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: bash *** dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: fips *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut[I]: *** Including module: kernel-modules *** dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: resume *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** dracut[I]: *** Including module: securityfs *** dracut[I]: *** Including module: masterkey *** dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: integrity *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=overlay dracut[I]: resume=UUID=040f3b6b-3961-46c1-a351-bd41381da55b dracut[I]: root=UUID=0280d16e-5971-4b2f-b705-317b6e96a4c3 rootfstype=ext4 rootflags=rw,noatime,nobarrier dracut[I]: *** Creating image file '/boot/initrd-6.7.9-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.9-1-default' done *** %posttrans(systemd-presets-branding-MicroOS-20230214-2.4.noarch) script output: Unit /usr/lib/systemd/system/drkonqi-coredump-processor@.service is added as a dependency to a non-existent unit systemd-coredump@.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init-local.service -> /usr/lib/systemd/system/cloud-init-local.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-final.service -> /usr/lib/systemd/system/cloud-final.service. Created symlink /etc/systemd/system/multi-user.target.wants/rebootmgr.service -> /usr/lib/systemd/system/rebootmgr.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init.service -> /usr/lib/systemd/system/cloud-init.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-final.service -> /usr/lib/systemd/system/cloud-final.service. Created symlink /etc/systemd/system/multi-user.target.wants/rebootmgr.service -> /usr/lib/systemd/system/rebootmgr.service. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init.service -> /usr/lib/systemd/system/cloud-init.service. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_start.timer -> /usr/lib/systemd/system/mdcheck_start.timer. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdcheck_continue.timer -> /usr/lib/systemd/system/mdcheck_continue.timer. Created symlink /etc/systemd/system/default.target.wants/issue-add-ssh-keys.service -> /usr/lib/systemd/system/issue-add-ssh-keys.service. Created symlink /etc/systemd/system/multi-user.target.wants/man-db-create.service -> /usr/lib/systemd/system/man-db-create.service. Created symlink /etc/systemd/system/mdmonitor.service.wants/mdmonitor-oneshot.timer -> /usr/lib/systemd/system/mdmonitor-oneshot.timer. Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-config.service -> /usr/lib/systemd/system/cloud-config.service. Created symlink /etc/systemd/system/default.target.wants/health-checker.service -> /usr/lib/systemd/system/health-checker.service. Created symlink /etc/systemd/system/timers.target.wants/container-image-prune.timer -> /usr/lib/systemd/system/container-image-prune.timer. Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service -> /usr/lib/systemd/system/kubelet.service. Created symlink /etc/systemd/user/sockets.target.wants/drkonqi-coredump-launcher.socket -> /usr/lib/systemd/user/drkonqi-coredump-launcher.socket. %posttrans(microos-tools-2.21+git12-1.1.aarch64) script output: /usr/lib/tmpfiles.d/inn.conf:1: Line references path below legacy directory /var/run/, updating /var/run/news → /run/news; please update the tmpfiles.d/ drop-in file accordingly. /usr/lib/tmpfiles.d/nagios.conf:2: Line references path below legacy directory /var/run/, updating /var/run/nagios → /run/nagios; please update the tmpfiles.d/ drop-in file accordingly. Running post-transaction scripts ..................................................................................localhost:~ # zypper se microos_gnome_desktop Loading repository data... Reading installed packages... S | Name | Summary | Type --+-----------------------+-----------------------+-------- | microos_gnome_desktop | MicroOS GNOME Desktop | pattern localhost:~ # zypper se -t microos_gnome_desktop The flag type is not compatible with argument microos_gnome_desktop (Unknown package type). localhost:~ # zypper se microos_gnome_desktop Loading repository data... Reading installed packages... S | Name | Summary | Type --+-----------------------+-----------------------+-------- | microos_gnome_desktop | MicroOS GNOME Desktop | pattern localhost:~ # zypper in -t microos_gnome_desktop The flag type is not compatible with argument microos_gnome_desktop (Unknown package type). localhost:~ # reboot -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219988] New: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219988 Bug ID: 1219988 Summary: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT 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: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.x tool 'go tool dist' and 'go tool distpack' require the source file VERSION to be present in GOROOT. Current go1.x packaging is missing this file, ensure it is present. Example: $ go version go1.22.0 linux/amd64 $ go tool dist list go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT $ go tool distpack distpack: open /usr/lib64/go/1.22/VERSION: no such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215090] New: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver/html/
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215090 Bug ID: 1215090 Summary: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver /html/ 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: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Include the missing directory src/cmd/vendor/github.com/google/pprof/internal/driver/html/ in our go1.1x toolchain packages. This will fix failing builds with applications that directly import runtime/pprof e.g. kubeconform which failed to build with the following error: /usr/lib64/go/1.21/src/cmd/vendor/github.com/google/pprof/internal/driv er/webhtml.go:26:12: pattern html: no matching files found Upstream Go sources vendor certain tools including the pprof profiler [1]. pprof has an asset directory pprof/internal/driver/html containing only html templates used by the pprof viewer and no Go source code. Our go packaging tries to be conservative in what we include in the RPM, and with our find/glob patterns this directory has never been included in the packaging. The issue was first reported with go1.21. However, the last vendoring update was for go1.20, so we will include the fix in go1.20 packaging as well: bb917bd 2022-11-22 09:39 cmd/vendor: update vendored github.com/google/pprof for Go 1.20 release [1] https://github.com/google/pprof -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221849] New: grub2 bash-completion failed with '_split_longopt: command not found'
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221849 Bug ID: 1221849 Summary: grub2 bash-completion failed with '_split_longopt: command not found' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading bash-completion to 2.12, grub2 bash-completion scripts stopped to work and showed the error: _split_longopt: command not found. It's because bash-completion 2.12 renamed '_split_longopt' as '_comp__split_longopt', and bash-completion upstream(*) stated that '_split_longopt' is a private API so it should not be used directly. Instead, the script should use '_init_completion -s' or the newer '_comp_initialize -s' to initialize 'cur', 'prev', and 'split'. (*) https://github.com/scop/bash-completion/issues/1135 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221865] New: Allow Pipewire to operate under the superuser account.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221865 Bug ID: 1221865 Summary: Allow Pipewire to operate under the superuser account. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://gitlab.freedesktop.org/pipewire/pipewire/-/iss ues/2244#note_2336608 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Community User Blocker: No Provide a SystemD override file, as https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2244#note_2336608 explains, to allow the superuser account to use Pipewire when authenticated. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215639] New: Provide the user with a choice of where they want their SWAP partition to be.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215639 Bug ID: 1215639 Summary: Provide the user with a choice of where they want their SWAP partition to be. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing OpenSUSE with multiple internal drives, per https://forums.opensuse.org/t/how-to-transfer-swap-partition-to-os-drive-fr…, the OSTW installer places the SWAP partition on a (seemingly random) secondary internal drive. I don't want this - if I don't select the other drives when asked, it shouldn't touch them (I realize the quoted post states I did, but it refers to a previous installation; I've tested both). Consequently, either don't put the SWAP partiton on another drive unless multiple have been selected (this is the reason for this issue's designation as a bug rather than an enhancement) or allow the user to choose separately where the SWAP partition should be without needing to use the expert partitioner. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1213784] New: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213784 Bug ID: 1213784 Summary: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- When I file a report at opensuse.bugzilla.org and receive a message via e-mail about it, all links in the post direct me to bguzilla.suse.com instead. This is quite the hassle when dealing with frequent notifications on multiple tickets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220626] New: bash-completion: error: "bash: have: command not found"
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220626 Bug ID: 1220626 Summary: bash-completion: error: "bash: have: command not found" 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: werner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This was problem in the past (#1060111) and now, after update to 2.12.0-1.1 (https://build.opensuse.org/request/show/1149849) it strikes again: bash: have: command not found bash: have: command not found bash: have: command not found $ rpm -qa |grep bash-completion perf-bash-completion-6.7.6-83.14.x86_64 SwayNotificationCenter-bash-completion-0.10.0-1.1.noarch bash-completion-2.12.0-1.1.noarch playerctl-bash-completion-2.4.1-1.11.noarch cpupower-bash-completion-6.7.6-6.9.noarch ethtool-bash-completion-6.7-1.1.noarch lightdm-bash-completion-1.32.0-2.5.noarch tig-bash-completion-2.5.8-1.6.noarch python-tqdm-bash-completion-4.66.1-3.4.noarch firewalld-bash-completion-2.1.1-1.2.noarch udisks2-bash-completion-2.10.0-2.2.noarch augeas-bash-completion-1.14.1-1.2.x86_64 virt-v2v-bash-completion-2.4.0-3.1.noarch docker-bash-completion-25.0.3_ce-2.1.noarch alacritty-bash-completion-0.13.1-1.2.noarch whois-bash-completion-5.5.20-1.2.noarch subversion-bash-completion-1.14.3-1.4.noarch kmod-bash-completion-31-2.2.noarch android-tools-bash-completion-34.0.4-2.3.noarch iproute2-bash-completion-6.7-1.2.x86_64 wl-clipboard-bash-completion-2.2.0-1.2.noarch btrfsprogs-bash-completion-6.7.1-1.1.x86_64 mbimcli-bash-completion-1.28.4-2.2.noarch pulseaudio-bash-completion-17.0-2.1.x86_64 yt-dlp-bash-completion-2023.12.30-1.4.noarch nvme-cli-bash-completion-2.8-1.1.noarch fwupd-bash-completion-1.9.13-1.1.noarch ModemManager-bash-completion-1.20.6-2.2.noarch mpv-bash-completion-0.37.0+git20231121.2a57a6ee-1.3.noarch $ rpm -q bash bash-5.2.26-10.3.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1224199] New: [Build 20240512] Unlock Users setting will end up in changing Root user settings.
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1224199 Bug ID: 1224199 Summary: [Build 20240512] Unlock Users setting will end up in changing Root user settings. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4182899/modules/logi n_test/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: xiaoguang.wang(a)suse.com Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: yfjiang(a)suse.com, zcjia(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Steps: 1. Install a fresh Tumbleweed and the System Role is "Desktop with GNOME" 2. Boot to desktop and login with a non-root user which was created during installation -> Launch gnome-control-center -> Navigate to System and then Users -> Click Unlock and input Administrator password to Authenticate 3. Observe the Users Actual Result: The Users panel shows "Root" instead of the non-root user we used for login. This issue can only be reproduced on a fresh installed system. That mean if you reproduced this issue for one time and you might now be able to reproduced this one more time in this particular environment. So, be sure to take a snapshot before trying to reproduce this issue one your side. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-gnome@64bit fails in [login_test](https://openqa.opensuse.org/tests/4182899/modules/login_test/st… ## Test suite description ## Reproducible Fails since (at least) Build [20240320](https://openqa.opensuse.org/tests/4028599) ## Expected result Last good: [20240319](https://openqa.opensuse.org/tests/4026004) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222211] New: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329)
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1222211 Bug ID: 1222211 Summary: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ingo.strauch(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've recently updated to version 20240329 of Tumbleweed which for me was the upgrade of KDE Plasma 5 to 6. Since then, forgetting files via the start menu does not work as expected anymore. Steps to reproduce * open the "Application Menu" starter * click "Recent Files" at the top to show the list of recent files * right-click on one of the files and select "Forget File" from the context menu Expected behavior * the file gets removed from the list immediately (just like it did with KDE Plasma 5) Actual behavior * the file is still shown in the list As it turns out the file does get forgotten because it is removed from the list in a fresh login session, so it seems to me it's just a UI refresh problem. I still find it quite annoying because my use case often is to open files from the "Recent Files" list where I first have to remove several (to me) irrelevant entries before the document I'm looking for is shown. I've also tested this with a fresh user account and the problem exists there as well. Forgetting files does work as expected in "Application Starter" but not with "Application Menu". -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213156] New: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213156 Bug ID: 1213156 Summary: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This report is created in order to summarize related report caused by the same issues of systemd-xdg-autostart-generator in 15.5. systemd-xdg-autostart-generator is a mechanism to start XDG autostart (e.g., /etc/xdg/autostart) instead of desktop environments. In Leap 15.5, KDE plasma started to use this mechanism. However, due to the following problems, xdg-autostart-generator cannot start desktop files derived from Leap 15.4. Some essential services including IBus does not work in 15.5 (#1211977). * systemd-xdg-autostart-generator inappropriately ignores desktop files with X-GNOME-Autostart-Phase (#1201728) [1] * systemd-xdg-autostart-generator cannot start process that forks another process [2, 3, 4] [1] https://github.com/systemd/systemd/issues/18791 (resolved) [2] https://bugs.kde.org/show_bug.cgi?id=433299 [3] https://github.com/systemd/systemd/pull/20813 (merged) [4] https://github.com/systemd/systemd/issues/27919 (unresolved) FYI: Upstream bug tracker related xdg-autostart https://github.com/systemd/systemd/labels/xdg-autostart Some other fixes also might be necessary for 15.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1220260] New: qBittorrent freezes after opening and closing preferences
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220260 Bug ID: 1220260 Summary: qBittorrent freezes after opening and closing preferences Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240221 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Steps to reproduce: 1. Open qbittorrent 2. Open qbittorrent preferences 3. Close preferences window Observed result: qbittorrent freezes. Expected result: qbittorrent doesn't freeze. Additional information: qbittorrent unfreezes after a short time and seems to work properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218101] New: qBittorrent blurry fonts on kde wayland
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218101 Bug ID: 1218101 Summary: qBittorrent blurry fonts on kde wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871385 --> https://bugzilla.suse.com/attachment.cgi?id=871385&action=edit Compare the fonts in qBittorrent to the right click menu on the app's titlebar Operating System: openSUSE Tumbleweed 20231213 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Issue: qBittorrent fonts are a bit blurry under wayland on kde. Steps to reproduce: Launch qBittorrent and see that the fonts aren't as sharp as other programs. Observed behavior: Fonts are blurrier than other programs. Expected behavior: Fonts are sharp just like every other app. Additional information: I'm not sure if it's related, but right now scaling in kde wayland on tumbleweed is a bit broken, because user has to set scaling by force font dpi and not by display scaling. Scaling works when screen scaling is at 100% and force font dpi is set to apply actual scaling (120dpi in my case for effective 125% scaling). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215865] New: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215865 Bug ID: 1215865 Summary: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-0809 Fix excessive memory being allocated based on malicious initial packets that are not CONNECT packets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215864] New: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215864 Bug ID: 1215864 Summary: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-3592 Fix memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218784] New: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc
by bugzilla_noreply＠suse.com 03 Nov '24

03 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218784 Bug ID: 1218784 Summary: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: otto47(a)bk13.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- create two files bla.txt and test-ö.txt, then put them into a new tar achive. Opening this archive by ark throws a message "The archive you're trying to open is corrupt. Some files may be missing or damaged." It offers two buttons "Open as Read-Only" plus " Don't Open". Opening as Read-Only displays only one file bla.txt in the archive -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221250] New: glibc-locale-base missing locale() provides
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221250 Bug ID: 1221250 Summary: glibc-locale-base missing locale() provides Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, the glibc-locale package ships with "Provide"s for the different locales it ships: ``` $ rpm -q --provides glibc-locale|head glibc-locale = 2.38-6.1 glibc-locale(x86-64) = 2.38-6.1 locale(glibc:aa_DJ) locale(glibc:aa_DJ.utf8) locale(glibc:aa_ER) locale(glibc:aa_ER@saaho) locale(glibc:aa_ET) locale(glibc:af_ZA) locale(glibc:af_ZA.utf8) locale(glibc:agr_PE) ``` There are two locales which are shipped in glibc-locale-base - en_US.utf8 and C.utf8. Upon packaging something which requires one of them, I noticed that glibc-locale-base is not shipping any `locale()` "Provide"s. ``` $ rpm -q --provides glibc-locale-base glibc-locale-base = 2.38-6.1 glibc-locale-base(x86-64) = 2.38-6.1 libCNS.so()(64bit) libGB.so()(64bit) libISOIR165.so()(64bit) libJIS.so()(64bit) libJISX0213.so()(64bit) libKSC.so()(64bit) ``` I would expect glibc-locale-base to Provide `locale(glibc:C.utf8)` and `locale(glibc:en_US.utf8)` - both to have providers for all locales in the distribution and to make packaging easier. Unfortunately I could not figure out how the "Provide"s in glibc.spec are generated myself, hence I am opening this report instead. Cheers, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213339] New: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213339 Bug ID: 1213339 Summary: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: vojta.kottas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: When setting up a sqlite database using gda-control-center-6.0 as a test in a folder (/tmp/test_db in my case), the gui crashed and the command line showed that a segmentation fault had occurred. This issue does not happen on other distros. Reproducible: Always Steps to Reproduce: 1. Run gda-control-center-6.0 2. Set up database with sqlite Actual Results: Segmentation fault Expected Results: A database is set up in the specified folder. This all came from me trying to install the Pano extension, which upon install crashed the gnome-shell. I tracked the issue to this github issue: https://github.com/oae/gnome-shell-pano/issues/178 Which further tracks the issue down to a problem with the sqlite3 package on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219526] New: Update Definitions in MicroOS ISO Installer to reflect Aeon and Kalpa branding
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219526 Bug ID: 1219526 Summary: Update Definitions in MicroOS ISO Installer to reflect Aeon and Kalpa branding Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Update the wording in the MicroOS ISO and Yast based installer, to reflect the Aeon and Kalpa branding, for the Gnome and KDE desktop variants, respectively. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219884] New: Adapt package libzrtpcpp to build with OpenSSL 3
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219884 Bug ID: 1219884 Summary: Adapt package libzrtpcpp to build with OpenSSL 3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Package libzrtpcpp requires openssl 1.0.0 that is EOL and we would like to remove it from Factory. > BuildRequires: libopenssl-1_0_0-devel Please check tracker bug 1219879 for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1223454] New: Update nvidia driver to version 550.78
by bugzilla_noreply＠suse.com 28 Oct '24

28 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223454 Bug ID: 1223454 Summary: Update nvidia driver to version 550.78 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to version 550.78 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217749] New: No bass in built-in speakers on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 26 Oct '24

26 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217749 Bug ID: 1217749 Summary: No bass in built-in speakers on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871116 --> https://bugzilla.suse.com/attachment.cgi?id=871116&action=edit Output of "hwinfo --sound" for Lenovo 16ARH7 It seems the bass speakers do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). This issue appears to be similar to that of the wide range of recently released laptops that have the CS35L41 and TAS2781 amps, however I cannot find that hardware listed in any of my logs or online spec sheets for this laptop. The closest I can find is that is has a Realtek ALC3287 codec. Attached is the output of "hwinfo --sound" Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225352] New: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 25 Oct '24

25 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 Bug ID: 1225352 Summary: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://openqa.opensuse.org/tests/4217406/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: --- The Leap 15.5 JeOS image fails to boot in openQA for some time now. Initially it looked to me like an issue with the test infra, but the TW and 15.6 images boot while 15.5 fails consistently. I tried to reproduce the issue locally and except for a slow boot due to no ethernet cable it worked. The package diff between last working and latest build shows changes in aaa_base, coreutils, kernel, less, protobuf, libsemanage, perl, rpm and yast. Could be a kernel issue? ## Observation openQA test in scenario opensuse-15.5-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4217406/modules/prepar… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [13.183](https://openqa.opensuse.org/tests/4120363) ## Expected result Last good: [13.182](https://openqa.opensuse.org/tests/4119085) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 48

[Bug 1218682] New: EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 Bug ID: 1218682 Summary: EFI aarch64 boot failure on honeycomb lx2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We are running micro os (tumbleweed) on two build servers. Two nights ago, these failed to boot after an upgrade, same thing happened last night. The hardware is the honeycomb lx2, the boot log is: Booting `openSUSE MicroOS' Loading Linux 6.6.9-1-default ... Loading initial ramdisk ... [ 0.687447][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000140, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.699962][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.712472][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.724981][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.737490][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.749998][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.762507][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.775015][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.787522][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 0.800030][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 1.187743][ T99] fsl_mc_bus NXP0008:00: mc_get_version() failed with error -110 [ 5.689703][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.702224][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.714736][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.727248][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.739760][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.752271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.764783][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.777294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.789805][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 5.802316][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.693031][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.705546][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.718058][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.730569][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.743080][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.755592][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.768102][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.780613][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.793124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 10.805635][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.696364][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.708881][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.721393][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.733904][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.746416][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.758927][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.771438][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.783949][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.796460][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 15.808971][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.699708][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.712228][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.724743][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.737256][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.749770][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.762283][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.774797][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.787311][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.799824][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 20.812337][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.703043][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.715557][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.728071][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.740585][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.753098][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.765611][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.778124][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.790637][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.803150][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 25.815663][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.706370][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.718885][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.731398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.743911][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.756424][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.768937][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.781450][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.793964][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.806477][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 30.818990][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.709704][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.722219][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.734732][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.747245][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.759758][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.772271][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.784785][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.797298][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.809811][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 35.822325][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.713036][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.725551][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.738064][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.750578][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.763090][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.775603][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.788117][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.800630][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.813143][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 40.825656][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 44.003022][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [swapper/0:0] [ 45.716367][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.728884][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.741398][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.753912][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.766425][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.778939][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.791452][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.803965][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.816479][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 45.828992][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.719700][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.732214][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.744728][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.757240][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.769754][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.782267][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.794780][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.807294][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.819807][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 [ 50.832320][ C0] arm-smmu arm-smmu.0.auto: Unhandled context fault: fsr=0x402, iova=0x2080000100, fsynr=0x100040, cbfrsynra=0x4000, cb=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223436] New: cannot login without password set
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223436 Bug ID: 1223436 Summary: cannot login without password set Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After updating a Tumbleweed VM without any password set either on the user account, or on root, it has locked me out — i can login neither from SDDM, nor from the kernel console. The previous update of that machine was about a month ago (after the lzma backdoor rebuild). -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217774] New: qt6-webengine qtpdf.index reproducible builds
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217774 Bug ID: 1217774 Summary: qt6-webengine qtpdf.index reproducible builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our qt6-webengine / qt6-webengine-docs-html subpackage varied between builds in /usr/share/doc/qt6/qtpdf/qtpdf.index See diff at https://rb.zq1.de/compare.factory-20230830/diffs/qt6-webengine-compare.out You probably need to build with osc build -M docs -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221890] New: Audacious crashes when opening file dialog since Plasma 6
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221890 Bug ID: 1221890 Summary: Audacious crashes when opening file dialog since Plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: foss(a)grueninger.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After I installed Plasma and KF 6, the media player crashes when opening the file dialog (to open or append tracks). Steps to reproduce: 1. Open Audacious 2. Press Ctrl + o to open a audio file. 3. Dialog flashes and Audacious is terminated It seems to be a packaging issue, upstream has no idea. See the according issue: https://github.com/orgs/audacious-media-player/discussions/122 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219031] New: Multiple cross-arm-none-gcc13 bugs
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219031 Bug ID: 1219031 Summary: Multiple cross-arm-none-gcc13 bugs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: rguenther(a)suse.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 1. the package does not require libisl23 libmpc3 so the binary does not run. 2. package not required to provide required headers: ``` Compiling: keyboards/moonlander/matrix.c In file included from ./lib/chibios/os/hal/osal/rt-nil/osal.h:29, from ./lib/chibios/os/hal/include/hal.h:30, from platforms/chibios/platform_deps.h:18, from quantum/quantum.h:18, from keyboards/moonlander/moonlander.h:21, from keyboards/moonlander/matrix.c:19: /usr/lib64/gcc/arm-none-eabi/13/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory 9 | # include_next <stdint.h> | ^~~~~~~~~~ compilation terminated. [ERRORS] | | | gmake[1]: *** [builddefs/common_rules.mk:361: .build/obj_moonlander_darix-v3/matrix.o] Error 1 Make finished with errors gmake: *** [Makefile:392: moonlander:darix-v3] Error 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214915] New: Please build Qt5 with configure option -xcb-native-painting
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214915 Bug ID: 1214915 Summary: Please build Qt5 with configure option -xcb-native-painting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Woebbeking(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, this is an experimental feature to let Qt5 paint as Qt4 did. This improves performance of Qt5 applications under X2Go a lot. First this option was enabled by default but some years later it was disabled to reduce the size of the platform plugin libqxcb.so a little bit. You don't have to worry that you brake something if you enable this option as the user also have to set the environment variable QT_XCB_NATIVE_PAINTING to make it work. Thanks in advance! Cheers, André -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1223134] New: Disable N_GSM
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223134 Bug ID: 1223134 Summary: Disable N_GSM 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- N_GSM is almost unmaintained and full of bugs: https://lore.kernel.org/all/DB9PR10MB5881D2170678C169FB42A423E0082@DB9PR10M… Esp. the 0day reported recently (bug 1222619). It is supposed to be used on special embedded devices only. So let's disable the line discipline. There is jsc#PED-8240 about the same for SLE. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215851] New: code generated by swig < 4.0.0 is incompatible with Python 3.12
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215851 Bug ID: 1215851 Summary: code generated by swig < 4.0.0 is incompatible with Python 3.12 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869858 --> https://bugzilla.suse.com/attachment.cgi?id=869858&action=edit _log.txt Code generated by swig < 4.0.0 (all Leap and SLE) generates code importing `imp` module, which has been deprecated in 3.4 (i.e., in all our supported Pythons 3) and removed in 3.12. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221108] New: bmap-tools: FTBFS-2024-06-12
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221108 Bug ID: 1221108 Summary: bmap-tools: FTBFS-2024-06-12 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adam(a)mizerski.pl, code(a)bnavigator.de Blocks: 1102840 Target Milestone: --- Found By: --- Blocker: --- I had previously filed this at https://github.com/intel/bmap-tools/issues/116 but then I noticed that * we have a custom patch in that region * we are only at 3.6 while there is already a 3.7 upstream release Please work with the new upstream at Yoctoproject as appropriate. This bug was found while working on reproducible builds for openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225776] New: Flavor addons of package graphviz does not build with gcc14
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225776 Bug ID: 1225776 Summary: Flavor addons of package graphviz does not build with gcc14 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Gcc 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, flavor addons of package graphviz fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc The error (that halts the build) is: [ 79s] tbl.c:173:15: error: assignment to ‘char *’ from incompatible pointer type ‘char (*)[1]’ [-Wincompatible-pointer-types] [ 79s] 173 | s = &cp[i].u.s; [ 79s] | ^ -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221714] New: GCC 14: fipscheck package fails
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221714 Bug ID: 1221714 Summary: GCC 14: fipscheck package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building fipscheck with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): filehmac.c: In function ‘compute_file_hmac’: filehmac.c:219:24: error: implicit declaration of function ‘OSSL_PROVIDER_load’ [-Wimplicit-function-declaration] 219 | fips = OSSL_PROVIDER_load(NULL, "fips"); | ^~~~~~~~~~~~~~~~~~ filehmac.c:219:22: error: assignment to ‘OSSL_PROVIDER *’ {aka ‘struct ossl_provider_st *’} from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 219 | fips = OSSL_PROVIDER_load(NULL, "fips"); | ^ filehmac.c:265:32: error: passing argument 3 of ‘EVP_MAC_final’ from incompatible pointer type [-Wincompatible-pointer-types] 265 | EVP_MAC_final(c, rbuf, &hlen, sizeof(rbuf)); | ^~~~~ | | | unsigned int * /usr/include/openssl/evp.h:1228:47: note: expected ‘size_t *’ {aka ‘long unsigned int *’} but argument is of type ‘unsigned int *’ 1228 | unsigned char *out, size_t *outl, size_t outsize); | ~~~~~~~~^~~~ See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223466] New: Mnemosyne failed to start on the latest Tumbleweed snapshot
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223466 Bug ID: 1223466 Summary: Mnemosyne failed to start on the latest Tumbleweed snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ecsos(a)schirra.net Reporter: wire.a3n6s(a)simplelogin.com QA Contact: qa-bugs(a)suse.de CC: lars.vogdt(a)suse.com Target Milestone: --- Found By: --- Blocker: --- mnemosyne was installed from the Education repository. It used to work fine but now failed to start since the OS was rolled to the latest snapshot. Environment: * openSUSE Tumbleweed snapshot version 20240426 * mnemosyne version 2.11 from the Education repository (mnemosyne-2.11-3.6.noarch) Reproduce Steps: Start mnemosyne from the commandline: # mnemosyne /usr/lib/python3.11/site-packages/mnemosyne/libmnemosyne/__init__.py:377: UserWarning: google_trans_new package is not installed. Google translate feature will not be available. warnings.warn("google_trans_new package is not installed. Google translate feature will not be available.") QGuiApplication::setDesktopFileName: the specified desktop file name ends with .desktop. For compatibility reasons, the .desktop suffix will be removed. Please specify a desktop file name without .desktop suffix Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' The application won't start. Ctrl-C to stop it, then got following debug information: An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/lib/python3.11/site-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 449, in restore_focus def restore_focus(self): Since it worked fine in March before some OS upgradings (rollings), it may has something to do with the dependencies (maybe some Qt6 libraries). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219866] New: install guix complains about non-existent group and fails
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219866 Bug ID: 1219866 Summary: install guix complains about non-existent group and fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I attempt to install guix via 'zypper in guix' on opensuse tw 20240211-2738.1 Problem: nothing provides 'group(guixbuild)' needed by the to be installed guix-1.4.0-1.6.x86_64 Solution 1: do not install guix-1.4.0-1.6.x86_64 Solution 2: break guix-1.4.0-1.6.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213446] New: connecting dock station network enables wifi - reverse behaviour
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213446 Bug ID: 1213446 Summary: connecting dock station network enables wifi - reverse behaviour Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Dell XPS 9700 I have a Dell WD19 dock. It used to work fine. Now when I have e dock station connected with the cable there WIFI is disabled as it should When I unplug Ethernet cable from the dock the wifi remains OFF and RFKILL shows hard block. When I plug the Ethernet cable back to the dock the wifi comes up for 2-3 seconds and sets up a connection and then I get e message that wifi gets disabled and connection is switched back to Ethernet. It used to work fine that unplugging the cable from dock would bring the wifi up. So having a dock station it is not possible to disconnect its ethernet and have laptop enable Wifi. It works ok in Ubuntu. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224070] New: Missing Ark context menu in dolphin
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224070 Bug ID: 1224070 Summary: Missing Ark context menu in dolphin Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: mh306602(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Because Dolphin is installed through rpm and ark through flatpak, the integration is flawed between the 2. Could be fixed by either having both be installed through rpm's or both through flatpak. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1218125] New: cmake outdated
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1218125 Bug ID: 1218125 Summary: cmake outdated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All SLE service packs have a cmake except SP5, current version in Leap is 3.20, some projects insist on more recent version like 3.23, Factory has 3.27. Sounds like it's time to upgrade cmake again. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1219525] New: Notification on successful transactional-update is not persistent
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219525 Bug ID: 1219525 Summary: Notification on successful transactional-update is not persistent Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: sfalken(a)cloverleaf-linux.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Kalpa, transactional-update-notifier does operate correctly on Kalpa, but it pops up when run, and only survives as long as the delay set in `System Settings->Notifications->Hide After` is set to. This isn't the intended behavior, the notification should be persistent, so the user is aware that an update has been applied, and can choose whether to reboot or not -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219803] New: Lenovo Yoga 14APH8 headphones jack requires bass speaker to be full volume
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219803 Bug ID: 1219803 Summary: Lenovo Yoga 14APH8 headphones jack requires bass speaker to be full volume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pinchon.guillaume(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Symptoms : When connecting headphones to the laptop's jack it's required to set the Bass Speaker to full volume through alsamixer otherwise we get no sound. Either that or replacing in /usr/share/alsa-card-profile/mixer/paths/analog-output-headphones.conf : [Element Bass Speaker] switch = off volume = off with : [Element Bass Speaker] switch = off volume = merge System info : Operating System: openSUSE Tumbleweed 20240209 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.8.0-rc3-3.g7450939-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7840HS with Radeon 780M Graphics Memory: 27.1 Gio of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82Y8 System Version: Yoga Pro 7 14APH8 hwinfo --sound : 12: PCI 6300.1: 0403 Audio device [Created at pci.386] Unique ID: UGCg.OQPqPLYNCh0 Parent ID: JZZT.maS73mB38XF SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:63:00.1 SysFS BusID: 0000:63:00.1 Hardware Class: sound Model: "ATI Audio device" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1640 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x3824 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x785c8000-0x785cbfff (rw,non-prefetchable) IRQ: 90 (no events) Module Alias: "pci:v00001002d00001640sv000017AAsd00003824bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #27 (PCI bridge) 22: PCI 6300.6: 0403 Audio device [Created at pci.386] Unique ID: puer.m6xb4yIjnP9 Parent ID: JZZT.maS73mB38XF SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:63:00.6 SysFS BusID: 0000:63:00.6 Hardware Class: sound Model: "AMD Family 17h (Models 10h-1fh) HD Audio Controller" Vendor: pci 0x1022 "AMD" Device: pci 0x15e3 "Family 17h (Models 10h-1fh) HD Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x3882 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x785c0000-0x785c7fff (rw,non-prefetchable) IRQ: 43 (327 events) Module Alias: "pci:v00001022d000015E3sv000017AAsd00003882bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #27 (PCI bridge) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224068] New: Budgie crashes session if it crashes twice
by bugzilla_noreply＠suse.com 05 Oct '24

05 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224068 Bug ID: 1224068 Summary: Budgie crashes session if it crashes twice Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: asdhio(a)tuta.io QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874777 --> https://bugzilla.suse.com/attachment.cgi?id=874777&action=edit A screen saying "Oh no! Something has gone wrong." Budgie will throw a screen "Oh no! Something has gone wrong." if Budgie crashes more than one time. A common case of it happening is if Bugdie panel crashes more than once. The likelihood of such crashes can be increased if budgie-appmenu-applet or any applets from budgie-extras are applied. The problem is that Budgie won't just restart its panels and let the user do their job (like XFCE and MATE would). Budgie will stop after second crash even though those applications are still running. But Budgie gives no option other than to log out. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223269] New: VUL-0: CVE-2023-51791: ffmpeg: buffer overflow via function gen_alias_map in libavcodec/jpegxl_parser.c
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223269 Bug ID: 1223269 Summary: VUL-0: CVE-2023-51791: ffmpeg: buffer overflow via function gen_alias_map in libavcodec/jpegxl_parser.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/402764/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Buffer Overflow vulenrability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavcodec/jpegxl_parser.c in gen_alias_map. References: https://ffmpeg.org/ http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51791 https://www.cve.org/CVERecord?id=CVE-2023-51791 https://trac.ffmpeg.org/ticket/10738 https://bugzilla.redhat.com/show_bug.cgi?id=2276114 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223276] New: VUL-0: CVE-2023-51797: ffmpeg: buffer overflow in the showwaves_filter_frame function in libavfilter/avf_showwaves.c
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223276 Bug ID: 1223276 Summary: VUL-0: CVE-2023-51797: ffmpeg: buffer overflow in the showwaves_filter_frame function in libavfilter/avf_showwaves.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/402769/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Buffer Overflow vulnerability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavfilter/avf_showwaves.c:722:24 in showwaves_filter_frame References: https://github.com/FFmpeg/FFmpeg https://ffmpeg.org/ http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51797 https://www.cve.org/CVERecord?id=CVE-2023-51797 https://trac.ffmpeg.org/ticket/10756 https://bugzilla.redhat.com/show_bug.cgi?id=2276120 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1224233] New: VUL-0: CVE-2024-30268: cacti: reflected cross-site scripting vulnerability in display_settings
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224233 Bug ID: 1224233 Summary: VUL-0: CVE-2024-30268: cacti: reflected cross-site scripting vulnerability in display_settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/405121/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: Andreas.Stieger(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Cacti provides an operational monitoring and fault management framework. A reflected cross-site scripting vulnerability on the 1.3.x DEV branch allows attackers to obtain cookies of administrator and other users and fake their login using obtained cookies. This issue is fixed in commit a38b9046e9772612fda847b46308f9391a49891e. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-30268 https://www.cve.org/CVERecord?id=CVE-2024-30268 https://github.com/Cacti/cacti/blob/08497b8bcc6a6037f7b1aae303ad8f7dfaf7364… https://github.com/Cacti/cacti/commit/a38b9046e9772612fda847b46308f9391a498… https://github.com/Cacti/cacti/security/advisories/GHSA-9m3v-whmr-pc2q -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224232] New: VUL-0: CVE-2024-29895: cacti: command injection in cmd_realtime.php
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224232 Bug ID: 1224232 Summary: VUL-0: CVE-2024-29895: cacti: command injection in cmd_realtime.php Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/405105/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: Andreas.Stieger(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Cacti provides an operational monitoring and fault management framework. A command injection vulnerability on the 1.3.x DEV branch allows any unauthenticated user to execute arbitrary command on the server when `register_argc_argv` option of PHP is `On`. In `cmd_realtime.php` line 119, the `$poller_id` used as part of the command execution is sourced from `$_SERVER['argv']`, which can be controlled by URL when `register_argc_argv` option of PHP is `On`. And this option is `On` by default in many environments such as the main PHP Docker image for PHP. Commit 53e8014d1f082034e0646edc6286cde3800c683d contains a patch for the issue, but this commit was reverted in commit 99633903cad0de5ace636249de16f77e57a3c8fc. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-29895 https://www.cve.org/CVERecord?id=CVE-2024-29895 https://github.com/Cacti/cacti/blob/501712998589763d411a68d35e3cda98fd9cfd1… https://github.com/Cacti/cacti/commit/53e8014d1f082034e0646edc6286cde3800c6… https://github.com/Cacti/cacti/commit/99633903cad0de5ace636249de16f77e57a3c… https://github.com/Cacti/cacti/security/advisories/GHSA-cr28-x256-xf5m -- You are receiving this mail because: You are on the CC list for the bug.

1 2