September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190421] Nouveau prevents the start on X11
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190421 https://bugzilla.suse.com/show_bug.cgi?id=1190421#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. There is no nouveau-related changes between those kernel versions, but one of major differences is that the recent kernel was switched to UsrMerge, i.e. the modules are put in /usr/lib/modules/*, and the firmware is looked from /usr/lib/firmware/*. Could you give the kernel log from the working version, too? I'm not sure whether the errors in the report are the culprit or not: set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: vp: unable to load firmware nouveau/nv84_xuc00f set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: vp: init failed, -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: bsp: unable to load firmware nouveau/nv84_xuc103 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: bsp: init failed, -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: vp: unable to load firmware nouveau/nv84_xuc00f set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: vp: init failed, -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: bsp: unable to load firmware nouveau/nv84_xuc103 set 12 16:05:50 tw-molino kernel: nouveau 0000:08:00.0: bsp: init failed, -2 If 5.13.12 also showed those errors but works, they are irrelevant. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190431] New: bsdtar man pages show incorrect command names
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190431 Bug ID: 1190431 Summary: bsdtar man pages show incorrect command names 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: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The bsdtar package contains the three commands /usr/bin/bsdcat /usr/bin/bsdcpio /usr/bin/bsdtar and the four pages /usr/share/man/man1/bsdcat.1.gz /usr/share/man/man1/bsdcpio.1.gz /usr/share/man/man1/bsdtar.1.gz /usr/share/man/man5/libarchive-formats.5.gz The man pages bsdcpio and bsdtar show the standard command names cpio and tar. This is confusing, because cpio and tar belong to the packages cpio and tar. Please rename the command names in man pages bsdtar and bsdcpio. E.g. Rename (*) in man bsdcpio TAR(1)* BSD General Commands Manual TAR(1)* NAME tar* �� manipulate tape archives SYNOPSIS tar* [bundled-flags ��args��] [��file�� | ��pattern�� ...] tar* {-c} [options] [files | directories] tar* {-r | -u} -f archive-file [options] [files | directories] tar* {-t | -x} [options] [patterns] The Fedora RPM package uses a shell script for renaming. See https://fedora.pkgs.org/34/fedora-updates-x86_64/bsdtar-3.5.2-2.fc34.x86_64… Tumbleweed and Leap 15.2 are affected, 15.3 probably too. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1189885] DRBD doesn't connect after Update from Leap 15.2 to 15.3
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189885 https://bugzilla.suse.com/show_bug.cgi?id=1189885#c1 nick wang <nwang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(E.Kuemmerle@fz-ju | |elich.de) --- Comment #1 from nick wang <nwang(a)suse.com> --- Hi Eberhard, Could you please enclose the output of DRBD rpms and version information before/after upgrade? `hb_report` logs (including upgrade before/after timestamps) are even better. # rpm -qa|grep drbd and # cat /proc/drbd (before and after upgrade Leap/packages) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185518] Consider building Linux 5.12+ with PREEMPT flag on arches with STATIC_CALL
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1185518 Vlastimil Babka <vbabka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbabka(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190407] kubelet failed to create pod network sandbox: unable to set hairpin mode
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190407 https://bugzilla.suse.com/show_bug.cgi?id=1190407#c1 --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- We don't test with systemd-networkd, only wicked. Could be very well that some of the involved tools don't work together with systemd-networkd. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190197] [Build 20210903] python-ldap fails to build
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190197 https://bugzilla.suse.com/show_bug.cgi?id=1190197#c3 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #3 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to William Brown from comment #1) > I can't reproduce this: > > Doing an osc build of python-ldap passes all tests, and the library builds > cleanly. > > Doing the following steps I can't reproduce: > > docker pull opensuse/tumbleweed:latest > docker run -i -t opensuse/tumbleweed:latest > > zypper ref --force > zypper dup > zypper in -y 389-ds sssd sssd-ldap openssl > > > 389 installs properly and correctly. > > What am I missing here to reproduce this issue? I should have been more explicit what 'update of openldap2' means: That would be openldap 2.5.7 (as is currently in the devel project) To reproduce: osc branch network:ldap openldap2 home:$oscusername:boo1190197 osc branch openSUSE:Factory python-ldap home:$oscusername:boo1190197 With this, you get openldap2 2.5.7 plus the current python-ldap devel branch into an own branch, and should be able to reproduce the failure -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123699] libvirt does not start default network automatically
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1123699 https://bugzilla.suse.com/show_bug.cgi?id=1123699#c124 --- Comment #124 from Oliver Kurz <okurz(a)suse.com> --- Opened https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13239 to remove the soft-fail reference. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181155] [Build 20210118] openQA test fails in aa_notify
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1181155 https://bugzilla.suse.com/show_bug.cgi?id=1181155#c25 --- Comment #25 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: apparmor https://openqa.opensuse.org/tests/1898110 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179395] [Build 20201129] Chromium: rendering error
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1179395 https://bugzilla.suse.com/show_bug.cgi?id=1179395#c22 --- Comment #22 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: gnome https://openqa.opensuse.org/tests/1898437 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174164] [Build 20200710] nfs server log messages have too high log level and break ncurses apps
by bugzilla_noreply＠suse.com 13 Sep '21

13 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1174164 https://bugzilla.suse.com/show_bug.cgi?id=1174164#c26 --- Comment #26 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: yast2_nfs_v4_client https://openqa.opensuse.org/tests/1911966 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0