July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213578] New: OOPS in amdgpu
by bugzilla_noreply＠suse.com 22 Aug '23

22 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213578 Bug ID: 1213578 Summary: OOPS in amdgpu Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aj(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I get an OOPs with both 5.14.21-150500.55.7-default and also with Takachi's 5.14.21-150500.3.g62ee467-default -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1212853] New: GRUB2 asking for passphrase twice again
by bugzilla_noreply＠suse.com 18 Aug '23

18 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212853 Bug ID: 1212853 Summary: GRUB2 asking for passphrase twice again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: eyadlorenzo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday I reinstalled my Tumbleweed system, with crypted root and crypted swap. I now get again asked twice for my passphrase. I could follow what described in https://en.opensuse.org/SDB:Encrypted_root_file_system#Avoiding_to_type_the…, but last time I installed Tumbleweed there was no need (see https://bugzilla.opensuse.org/show_bug.cgi?id=1206710) for details. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213489] New: GTK2 apps (and the other toolkits) don't apply dark mode GNOME Adwaita
by bugzilla_noreply＠suse.com 17 Aug '23

17 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213489 Bug ID: 1213489 Summary: GTK2 apps (and the other toolkits) don't apply dark mode GNOME Adwaita Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: soymilkriceyuriz(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868325 --> https://bugzilla.suse.com/attachment.cgi?id=868325&action=edit White on white theme+font on the IBUS IME (+ It rendering at the upper left corner on LibreOFFICE but I might do a bug report for that too) GTK2 and Legacy applications are not applying the dark theme, while having set "adwaita-dark" in Legacy themes, GNOME-Tweaks. While it can be a minor issue, it can be really critical, since, some apps are not so usable. SUCH as my main point, an IME, especially the Japanese one provided by Ibus-Mozc. What it does is that because the dark theme is not applied, GTK2 toolkits thinks that the theme is black and so, the font is white. BUT, no, it is white on white theme (white font, white theme) not readable, so because of that, it is impossible to propely select the correct word according to the sentence (IME) and this is really incovinient. There might be something wrong with the "adwaita-dark" package, because it is not the only application that has that behaviour, all of the softwares don't follow the dark theme as default? I can't figure it out. Packages related: gnome-themes, gnome-themes-extra, adwaita-dark, ibus-mozc, firefox etc. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1213224] New: illegal instruction while building ppc64le
by bugzilla_noreply＠suse.com 17 Aug '23

17 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213224 Bug ID: 1213224 Summary: illegal instruction while building ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Visit https://build.opensuse.org/package/live_build_log/hardware/libplist/openSUS… Package hardware/libplist failed to build in openSUSE_Factory_PPC/ppc64le Check out the package for editing: osc checkout hardware libplist Last lines of build log: [ 37s] post-build-checks-84.87+git20230328.de######################################## [ 37s] attr-2.5.1-1.23 ######################################## [ 37s] build-mkbaselibs-20230628-1.1 ######################################## [ 38s] kernel-obs-build-6.3.9-1.1 ######################################## [ 39s] now finalizing build dir... [ 39s] ... running 01-add_abuild_user_to_trusted_group [ 39s] ... running 02-set_timezone_to_utc [ 39s] ... running 03-set-permissions-secure [ 39s] ... running 11-hack_uname_version_to_kernel_version [ 40s] ----------------------------------------------------------------- [ 40s] I have the following modifications for libplist.spec: [ 40s] 23c23 [ 40s] < Release: 0 [ 40s] --- [ 40s] > Release: 2.5 [ 42s] ----------------------------------------------------------------- [ 42s] ----- building libplist.spec (user abuild) [ 42s] ----------------------------------------------------------------- [ 42s] ----------------------------------------------------------------- [ 42s] /.build/build-recipe-spec: line 170: 1079 Illegal instruction chroot $BUILD_ROOT $rpmbuild --undefine --help >&/dev/null [ 42s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/hardware/openSUSE_Factory_PPC/7934553a10bfea6c1c50…' /home/abuild/rpmbuild/SOURCES/libplist.spec [ 42s] Illegal instruction [ 42s] ### VM INTERACTION START ### [ 42s] [ 28.122495][ T1] sysrq: Power Off [ 42s] [ 28.123277][ T55] reboot: Power down [ 42s] ### VM INTERACTION END ### [ 42s] [ 42s] obs-power8-05 failed "build libplist.spec" at Tue Jul 11 16:48:09 UTC 2023. [ 42s] -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213178] New: lddtree fails to run
by bugzilla_noreply＠suse.com 15 Aug '23

15 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213178 Bug ID: 1213178 Summary: lddtree fails to run Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bugzilla.opensuse.org(a)urbanec.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Leap 15.5 system with * pax-utils-1.3.7-bp155.1.5.x86_64 * python3-pyelftools-0.29-150500.1.4.noarch $ lddtree /lib64/libc.so.6 File "/usr/bin/lddtree", line 53 assert sys.version_info >= (3, 6), f"Python 3.6+ required, but found {sys.version}" ^ SyntaxError: invalid syntax Attempt a workaround by specifying a python3 interpreter: $ python3 /usr/bin/lddtree /lib64/libc.so.6 Traceback (most recent call last): File "/usr/bin/lddtree", line 128, in <module> def dedupe(items: list[str]) -> list[str]: TypeError: 'type' object is not subscriptable This is a regression from Leap 15.4, where `lddtree` used to work without issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212926] New: tmpfiles suse.conf conflicts with lockdev.conf
by bugzilla_noreply＠suse.com 15 Aug '23

15 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212926 Bug ID: 1212926 Summary: tmpfiles suse.conf conflicts with lockdev.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- /usr/lib/tmpfiles.d/suse.conf:10: Duplicate line for path "/run/lock", ignoring. (26/49) Installing: systemd-253.5-4.1.x86_64 ..................................................[done] /usr/lib/tmpfiles.d/suse.conf:10: Duplicate line for path "/run/lock", ignoring. (27/49) Installing: systemd-network-253.5-4.1.x86_64 ..........................................[done] user@uefi:~> grep -r /run/lock /usr/lib/tmpfiles.d /usr/lib/tmpfiles.d/dmraid.conf:d /run/lock/dmraid 0700 root root - /usr/lib/tmpfiles.d/lvm2.conf:d /run/lock/lvm 0700 root root - /usr/lib/tmpfiles.d/lockdev.conf:d /run/lock 0775 root lock - /usr/lib/tmpfiles.d/lockdev.conf:L /var/lock - - - - ../run/lock /usr/lib/tmpfiles.d/suse.conf:d /run/lock 0775 root root - user@uefi:~> user@uefi:~> rpm -qif /usr/lib/tmpfiles.d/lockdev.conf Name : lockdev Version : 1.0.3_git201003141408 Release : 32.1 I see that lockedv gets dropped (https://bugzilla.opensuse.org/show_bug.cgi?id=1212801) but it does not help users that already have it installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212906] New: fanotify23 randomly fails on Tumbleweed when run more times
by bugzilla_noreply＠suse.com 14 Aug '23

14 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212906 Bug ID: 1212906 Summary: fanotify23 randomly fails on Tumbleweed when run more times Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jack(a)suse.com Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP fanotify23 test (test for FAN_MARK_EVICTABLE from 5.19) fails, when run more times. I tested it on all archs on the current Tumbleweed kernel [2], it fails everywhere. It also fails when tested on VM with older 6.2.8-1-default kernel (where it mostly fails, I guess the behavior is the same on all recent version): # /opt/ltp/testcases/bin/fanotify23 -i5 tst_device.c:97: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1094: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:81: TFAIL: FAN_MARK_REMOVE did not fail with ENOENT as expected after drop_caches: SUCCESS (0) fanotify23.c:175: TBROK: read(3,0x5598cbfafc54,24524) failed, returned -1: EAGAIN/EWOULDBLOCK (11) Summary: passed 27 failed 1 broken 1 skipped 0 warnings 0 dmesg: [ 371.377308][T29983] loop: module loaded [ 371.380510][T29982] loop0: detected capacity change from 0 to 614400 [ 371.441931][ C1] clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large: [ 371.443816][ C1] clocksource: 'kvm-clock' wd_nsec: 515886747 wd_now: 5749149153 wd_last: 572a54c2b8 mask: ffffffffffffffff [ 371.445730][ C1] clocksource: 'tsc' cs_nsec: 30542623402 cs_now: cff3ae7e60 cs_last: c057e04270 mask: ffffffffffffffff [ 371.447768][ C1] clocksource: Clocksource 'tsc' skewed 30026736655 ns (30026 ms) over watchdog 'kvm-clock' interval of 515886747 ns (515 ms) [ 371.449822][ C1] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 371.451068][ C1] tsc: Marking TSC unstable due to clocksource watchdog [ 371.499239][ C1] operation not supported error, dev loop0, sector 614272 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.501256][ C0] operation not supported error, dev loop0, sector 524 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.503893][ C1] operation not supported error, dev loop0, sector 16908 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.506135][ C0] operation not supported error, dev loop0, sector 32774 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.508716][ C1] operation not supported error, dev loop0, sector 49676 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.511513][ C0] operation not supported error, dev loop0, sector 65542 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.514038][ C0] operation not supported error, dev loop0, sector 82444 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.516522][ C1] operation not supported error, dev loop0, sector 98310 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.519263][ C0] operation not supported error, dev loop0, sector 115212 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.521950][ C1] operation not supported error, dev loop0, sector 131078 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.545611][T29982] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.548719][T29982] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.787570][T30005] fanotify23 (30005): drop_caches: 3 [ 371.804729][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.810253][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.812114][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.820273][T30005] fanotify23 (30005): drop_caches: 3 [ 371.828227][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.830160][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.831957][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.841016][T30005] fanotify23 (30005): drop_caches: 3 [ 371.862288][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.864165][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.866232][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.872592][T30005] fanotify23 (30005): drop_caches: 3 [ 371.890441][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.892294][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.894159][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.900270][T30005] fanotify23 (30005): drop_caches: 3 [ 371.919626][T29982] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. When running on Debian 6.3.0-1-amd64 test does not fail and dmesg does not contain clocksource and tsc, therefore I suspect it's something our kernel specific (our configuration specific? We don't have any fanotify related patch, only something old patches.suse/vfs-add-super_operations-get_inode_dev, which is IMHO unrelated). I can report it to linux-fsdevel ML if it's a general problem. [1] https://github.com/linux-test-project/ltp/blob/353f0e4203139f3fc02fa2beb67c… [2] https://openqa.opensuse.org/tests/overview?build=fanotify23-10x -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213788] New: systemd units under /usr/local don't work properly
by bugzilla_noreply＠suse.com 13 Aug '23

13 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213788 Bug ID: 1213788 Summary: systemd units under /usr/local don't work properly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- /usr/local/lib/systemd/system is a location where systemd sources system units, as stated in systemd.unit(5). On a default install of openSUSE Tumbleweed, with a root filesystem of type btrfs, and with snapshots, /usr/local is mounted as a subvolume to avoid it being modified in case of an OS rollback. This combination causes systemd units under /usr/local/lib/systemd/system to not work properly. Service and timer units stored there are found, and can be enabled, but they don't actually run as expected on reboot. If ext4 is used as root filesystem, it works as expected. Tested on Tumbleweed 20230728. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213787] New: Plasma desktop is entirely grey with 64+GB of RAM
by bugzilla_noreply＠suse.com 12 Aug '23

12 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213787 Bug ID: 1213787 Summary: Plasma desktop is entirely grey with 64+GB of RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse-bugs(a)mkwsystems.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868516 --> https://bugzilla.suse.com/attachment.cgi?id=868516&action=edit Photo of the screen when bug occurs Problem: OpenSuse Tumbleweed boots to an entirely grey desktop when using KDE Plasma with 64GB or more of RAM. How to reproduce: Install 64GB or more of RAM, boot normally. What I expect to happen: the normal KDE Plasma desktop displays. What happens: other than the cursor, which appears normal, the entire screen displays grey. The cursor will change to, e.g., the text entry cursor when over the location of a text entry field, but that field will not be visible. It's like everything loads properly, then is covered with a layer of grey. When using ctrl-alt-F1/F2 to switch to and from a GUI, the correct desktop will display briefly. Other notes: - Problem occurs with 64 or 96GB of RAM installed. - Problem occurs both with the version of KDE installed from the installation media snapshot from July 14, 2023, as well as the version of KDE installed after running sudo zypper update today (July 30, 2023). - System is AMD-based, and using the integrated GPU of a Ryzen 9 7900. - The console works as expected. - Problem does not occur with XFCE as the desktop environment. - Problem does not occur when using Manjaro's KDE Plasma installation. - Problem does not occur with 16, 32, or 48GB of memory installed in the same system, using any combination of modules available to me. - There are no errors (lines with EE) in Xorg.0.log Screenshot attached is from when Night Mode is on. During the day the red tint is gone and it is grey. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1212824] New: [Build 20230627] apptainer: Write failed because no space left on device
by bugzilla_noreply＠suse.com 10 Aug '23

10 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212824 Bug ID: 1212824 Summary: [Build 20230627] apptainer: Write failed because no space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3390518/modules/appt ainer/steps/42 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Since today, the hpc_apptainer test is failing with 'no space on device' df shows sufficient space left: Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 728M 0 728M 0% /dev/shm tmpfs 292M 4.9M 287M 2% /run /dev/vda2 28G 2.3G 26G 9% / tmpfs 728M 24K 728M 1% /tmp /dev/vda2 28G 2.3G 26G 9% /.snapshots /dev/vda2 28G 2.3G 26G 9% /home /dev/vda2 28G 2.3G 26G 9% /var /dev/vda2 28G 2.3G 26G 9% /boot/grub2/i386-pc /dev/vda2 28G 2.3G 26G 9% /boot/grub2/x86_64-efi /dev/vda2 28G 2.3G 26G 9% /usr/local /dev/vda2 28G 2.3G 26G 9% /opt /dev/vda2 28G 2.3G 26G 9% /root /dev/vda2 28G 2.3G 26G 9% /srv tmpfs 146M 0 146M 0% /run/user/0 openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_hpc_apptainer@64bit fails in [apptainer](https://openqa.opensuse.org/tests/3390518/modules/apptainer/step… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module ## Reproducible Fails since (at least) Build [20230627](https://openqa.opensuse.org/tests/3389026) ## Expected result Last good: [20230626](https://openqa.opensuse.org/tests/3383456) (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 3