July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201483] New: upstream fixes for multipath-tools 0.9.0
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1201483 Bug ID: 1201483 Summary: upstream fixes for multipath-tools 0.9.0 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- * Fix multipath -ll output for foreign nvme (https://github.com/openSUSE/multipath-tools/commit/2306efa4de4f60e9ffca3bdf…) * fix find_multipaths_timeout for "unkown" arrays (https://github.com/openSUSE/multipath-tools/commit/8efb4f93f295406b865e0b36…) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1199080] New: Vorta fails to read borg archive and make new snapshot
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199080 Bug ID: 1199080 Summary: Vorta fails to read borg archive and make new snapshot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: suse(a)gerrit-heim.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Vorta can be connected to Borg Repo and the backup runs through seemingly normally, but is not completed. The list of archives is not displayed. Refresh runs dead. On the command line with borg there are no problems. So the problem is with vorta. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1177461] New: [Build 20201007] openQA test fails in journal_check: dracut is missing /usr/etc/{services,nsswitch.conf,protocols}
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1177461 Bug ID: 1177461 Summary: [Build 20201007] openQA test fails in journal_check: dracut is missing /usr/etc/{services,nsswitch.conf,protocols} Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1423381/modules/jour nal_check/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: daniel.molkentin(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: --- [ 188s] dracut-install: ERROR: installing '/etc/services' [ 188s] dracut-install: ERROR: installing '/etc/nsswitch.conf' [ 188s] dracut-install: ERROR: installing '/etc/protocols' [ 188s] dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.81Rh4v/initramfs -a /etc/services /etc/nsswitch.conf /etc/rpc /etc/protocols /etc/idmapd.conf [ 188s] sed: can't read /etc/nsswitch.conf: No such file or directory This leads to issues like Oct 08 03:09:49.976326 localhost rpcbind[326]: cannot get local address for udp: Servname not supported for ai_socktype in the initrd. ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-Kubic-kubeadm-x86_64-kubeadm@64bit-2G fails in [journal_check](https://openqa.opensuse.org/tests/1423381/modules/journal_ch… ## Test suite description ## Reproducible Fails since (at least) Build [20201006](https://openqa.opensuse.org/tests/1421922) ## Expected result Last good: [20201005](https://openqa.opensuse.org/tests/1421204) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 48

[Bug 1200255] New: cool-retro-term broken
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200255 Bug ID: 1200255 Summary: cool-retro-term broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: rs.opensuse(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (1/3) Installing: int10h-oldschoolpc-fonts-2.2-1.6.noarch (2/3) Installing: qmltermwidget-0.2.0-2.14.x86_64 (3/3) Installing: cool-retro-term-1.2.0-1.2.x86_64 robert@linux-1p8x ~> cool-retro-term QQmlApplicationEngine failed to load component qrc:/main.qml:143:5: Type TerminalContainer unavailable qrc:/TerminalContainer.qml:47:5: Type PreprocessedTerminal unavailable qrc:/PreprocessedTerminal.qml:123:9: Cannot assign to non-existent property "blinkingCursor" Cannot load QML interface -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1171368] New: [Build 20200506] openQA ppc64 test fails with new ruby 2.7
by bugzilla_noreply＠novell.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1171368 Bug ID: 1171368 Summary: [Build 20200506] openQA ppc64 test fails with new ruby 2.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1258904/modules/welc ome/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [Build 20200506] openQA ppc64 test fails with new ruby 2.7 ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64-gpt@ppc64 fails in [welcome](https://openqa.opensuse.org/tests/1258904/modules/welcome/steps/7) This is the first openQA tests for TW PowerPC since new ruby 2.7 reported message: === YaST2 ... internal error Caller: /mounts/mp_0001/usr/lib64/ruby/2.7.0/rubygems/core_ext/kernel_requires.rb:92:in `require' Details: cannot load such file -- storage ... === no data reported by openQA env, I will do a manual trial. ## Test suite description ## Reproducible Fails since (at least) Build [20200506](https://openqa.opensuse.org/tests/1258904) (current job) ## Expected result Last good: [20200501](https://openqa.opensuse.org/tests/1251875) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1180615] New: [Package request] asciidoctor-pdf extension
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180615 Bug ID: 1180615 Summary: [Package request] asciidoctor-pdf extension Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, would it be possible to package the asciidoctor-pdf extension to complement the main asciidoctor package? - https://build.opensuse.org/package/show/openSUSE%3AFactory/rubygem-asciidoc… - https://github.com/asciidoctor/asciidoctor-pdf/releases Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1197931] New: [Build 20220331] Kernel 5.17 / fanotify22 time out
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197931 Bug ID: 1197931 Summary: [Build 20220331] Kernel 5.17 / fanotify22 time out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2276368/modules/fano tify22/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fanotify22](https://openqa.opensuse.org/tests/2276368/modules/fanotify22/st… tst_device.c:88: TINFO: Found free device 0 '/dev/loop0' tst_test.c:999: TINFO: Formatting /dev/loop0 with ext4 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1459: TINFO: Timeout per run is 0h 00m 10s fanotify.h:277: TINFO: fid(test_mnt/internal_dir/bad_dir) = 73fe5178.f4546ba9.8002.6b9ac421.0... debugfs 1.46.5 (30-Dec-2021) fanotify.h:277: TINFO: fid(test_mnt) = 73fe5178.f4546ba9.2.0.0... Test timeouted, sending SIGKILL! tst_test.c:1509: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1511: TBROK: Test killed! (timeout?) ## Reproducible Fails since (at least) Build [20220331](https://openqa.opensuse.org/tests/2276368) (current job) ## Expected result Last good: [20220330](https://openqa.opensuse.org/tests/2273631) (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 4

[Bug 1180681] New: perf does not resolve plt symbols from libstdc++ right
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1180681 Bug ID: 1180681 Summary: perf does not resolve plt symbols from libstdc++ right 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: martin.liska(a)suse.com, matz(a)suse.com, mliska(a)suse.cz, rguenther(a)suse.com, tonyj(a)suse.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1180610 +++ There is a problem with *@plt symbols in some libraries, they are unresolved by perf (memcmp@plt in this case): > 0.26% main2 /usr/lib64/libstdc++.so.6.0.28 0xa51a0 l [.] 0x00000000000a51a0 On the other hand, plt symbols in other libraries are fine (memset@plt in this case): > 0.17% main2 /usr/lib64/libantlr4-runtime.so.4.8 0x4ed10 l [.] memset@plt Dump of memcmp's nth .plt.rela entry: /usr/lib64/libantlr4-runtime.so.4.8: 154th addr=4e9d0 plt_off=4e020 hdr=10 entry=10 /usr/lib64/libstdc++.so.6.0.28: 772th addr=a1070 plt_off=9e020 hdr=10 entry=10 The difference (offset) of stdc++'s memcmp is 0xa51a0 (correct) - 0xa1070 (perf's computed) = 0x4130. The problem is perf assumes nth entry of .plt.rela to correspond to nth function in .plt, but memcmp is in .plt.sec in libstdc++.so: > Relocation section '.rela.plt' at offset 0x97900 contains 1018 entries: > Offset Info Type Symbol's Value Symbol's Name + Addend > ... > 00000000001dc838 0000007800000007 R_X86_64_JUMP_SLOT 0000000000000000 memcmp(a)GLIBC_2.2.5 + 0 See: https://github.com/torvalds/linux/blob/f5e6c330254ae691f6d7befe61c786eb5056… It takes symbol index from sym.r_info. Then it resolves its name from .dynsym, appending @plt to it. Then this name is added to symbol table along with address which is computed as .rela.plt index multiplied by entry size (shdr_plt.sh_entsize) plus plt header (shdr_plt.sh_entsize on x86_64 too). And from this comes (almost) the offset above: > $ objdump -h /usr/lib64/libstdc++.so.6|grep -E ' .plt(\.sec)? ' > 12 .plt 00003fb0 000000000009e020 000000000009e020 0009e020 2**4 > 14 .plt.sec 00003fa0 00000000000a2160 00000000000a2160 000a2160 2**4 0xa2160-0x9e020 = 0x4140. I assume the 0x10 difference is that perf adds shdr_plt.sh_entsize (0x10) to the offset to skip the first .plt entry (header). Now, what is .plt.sec? And how should perf find out whether to consider .plt or .plt.sec? Or generally, how to properly find an address of *@plt like memcmp@plt above? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1177956] New: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1177956 Bug ID: 1177956 Summary: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1443345/modules/awai t_install/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mchang(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: --- With this fairly standard and simple ext4 setup (see https://openqa.opensuse.org/tests/1443345#step/partitioning_filesystem/9 for the YaST view), the installation fails with grub2-install complaining: "failed to get canonical path of `/boot/grub2/i386-pc'." This failure also happens in lvm-encrypt-separate-boot and autoyast_multi_btrfs tests, but doesn't appear to affect standard cryptlvm or btrfs setups. My guess ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ext4_textmode@64bit fails in [await_install](https://openqa.opensuse.org/tests/1443345/modules/await_inst… ## Test suite description Mantainer: jeriveramoya Test selection of file system ext4 for / partition in textmode for openSUSE distributions ## Reproducible Fails since (at least) Build [20201020](https://openqa.opensuse.org/tests/1443345) (current job) ## Expected result Last good: [20201019](https://openqa.opensuse.org/tests/1441513) (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 2

[Bug 1177957] New: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1177957 Bug ID: 1177957 Summary: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1443345/modules/awai t_install/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mchang(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: --- With this fairly standard and simple ext4 setup (see https://openqa.opensuse.org/tests/1443345#step/partitioning_filesystem/9 for the YaST view), the installation fails with grub2-install complaining: "failed to get canonical path of `/boot/grub2/i386-pc'." This failure also happens in lvm-encrypt-separate-boot and autoyast_multi_btrfs tests, but doesn't appear to affect standard cryptlvm or btrfs setups. My guess ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ext4_textmode@64bit fails in [await_install](https://openqa.opensuse.org/tests/1443345/modules/await_inst… ## Test suite description Mantainer: jeriveramoya Test selection of file system ext4 for / partition in textmode for openSUSE distributions ## Reproducible Fails since (at least) Build [20201020](https://openqa.opensuse.org/tests/1443345) (current job) ## Expected result Last good: [20201019](https://openqa.opensuse.org/tests/1441513) (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 8