May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171573] python-typed-ast build failed for ppc64 (BE)
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171573 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com Assignee|screening-team-bugs(a)suse.de |sebix+novell.com(a)sebix.at -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127794] NetworkManager keeps OpenVPN processes running
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1127794 http://bugzilla.suse.com/show_bug.cgi?id=1127794#c20 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #20 from Jonathan Kang <songchuan.kang(a)suse.com> --- The fix should be available as an update soon. RESOLVED FIXED. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171587] Tumbleweed on s390x fails to start network on installation initrd
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171587 http://bugzilla.opensuse.org/show_bug.cgi?id=1171587#c4 --- Comment #4 from Berthold Gunreben <azouhr(a)opensuse.org> --- I had a look in linuxrc.log and probably found the reason: sh: /sbin/udevadm: No such file or directory It looks like udevadm is called from /sbin/udevadm, but it is installed to /usr/bin/udevadm -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171587] Tumbleweed on s390x fails to start network on installation initrd
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171587 http://bugzilla.opensuse.org/show_bug.cgi?id=1171587#c3 --- Comment #3 from Berthold Gunreben <azouhr(a)opensuse.org> --- (In reply to Mark Post from comment #2) > (In reply to Berthold Gunreben from comment #0) > > [ 17.450295] qeth 0.0.0800 enc800: renamed from eth0 > > [ 17.462449] udevd[1158]: Using default interface naming scheme > > 'v245'. > > This would appear to be at least part of the problem, if not entirely. Do > things get better if you add "netdev=enc800" to the kernel parameters? The interface naming has been the same for quite some time. However, I tried to boot with netdev=enc800, but the behavior is identical. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171505] [staging][bison3.6] yast2-core does not cope with the new, improved syntax error output
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171505 http://bugzilla.suse.com/show_bug.cgi?id=1171505#c2 --- Comment #2 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Andreas Stieger from comment #1) > https://github.com/yast/yast-core/commit/ > 9c78f956973c1fb7e902da1bddeb4b73902fc772 > https://build.opensuse.org/request/show/803200 Thanks for closing it, I did fix and forgot to close the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 690867] Consider to DNSSEC sign the opensuse.org domain
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.suse.com/show_bug.cgi?id=690867 http://bugzilla.suse.com/show_bug.cgi?id=690867#c20 Lars Vogdt <lars.vogdt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Flags|needinfo?(achernikov(a)suse.c | |om) | --- Comment #20 from Lars Vogdt <lars.vogdt(a)suse.com> --- I got some internal answers back, which make me hope that we can start with this at the end of 2020. Sounds like a long time to wait, but what are a few months after 9 years? ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171289] Kernel 5.6+ breaks KVM passthrough
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171289 http://bugzilla.suse.com/show_bug.cgi?id=1171289#c6 Joerg Roedel <jroedel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Joerg Roedel <jroedel(a)suse.com> --- Change merged. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171633] New: clang9 update failure
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171633 Bug ID: 1171633 Summary: clang9 update failure 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: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- today I did an upgrade but the package clang9-9.0.1-10.3 failed to install with many errors like: File /usr/bin/clang from install of clang9-9.0.1-10.3.x86_64 (openSUSE-20190726-0) conflicts with file from package clang10-10.0.0-1.2.x86_64 (@System) File /usr/bin/clang from install of clang9-9.0.1-10.3.x86_64 (openSUSE-20190726-0) conflicts with file from package clang8-8.0.1-8.3.x86_64 (@System) Because I didn't have problems with the last upgrade to clang9-9.0.1-10.1, I checked if there where any difference in the spec file for llvm9-9.0.1-10.1 and llvm9-9.0.1-10.3. The spec files are essentially the same, therefore the issue has to be related to some change introduced in the build system. The output of: rpm -qlpv clang9-9.0.1-10.1.x86_64.rpm | grep '/usr/bin/clang ' is: lrwxrwxrwx 1 root root 23 Apr 9 21:10 /usr/bin/clang -> /etc/alternatives/clang and the output of: rpm -qlpv clang9-9.0.1-10.3.x86_64.rpm | grep '/usr/bin/clang ' is: lrwxrwxrwx 1 root root 28 May 11 12:11 /usr/bin/clang -> ../../etc/alternatives/clang As you can see the build system was creating /usr/bin/clang as a link to /etc/alternatives/clang before, but now the link point to ../../etc/alternatives/clang. This difference is causing the update failure. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171568] Error installing proprietary NVIDIA drivers on openSUSE Leap 15.2
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171568 http://bugzilla.opensuse.org/show_bug.cgi?id=1171568#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. My test builds against kernel::stable work. So I would say you can ignore the missing ksym and install the package. The kernel module itself gets rebuild during installation anyway ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171568] Error installing proprietary NVIDIA drivers on openSUSE Leap 15.2
by bugzilla_noreply＠suse.com 13 May '20

13 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171568 http://bugzilla.opensuse.org/show_bug.cgi?id=1171568#c5 --- Comment #5 from Dead Mozay <dead_mozay(a)opensuse.org> --- (In reply to Stephan Hemeier from comment #4) > The driver in the Nvidia Repo is build only for the kernel delivered by the > Leap Version the Repo is build for. > > Example: > The Nvidia driver from the Nvidia Repo for Leap 15.2 is only working with > the kernel 5.3 delivered by the OSS Repo for Leap 15.2 > > There is no Repo for kernel:stable, you have to build it from the > Installtion file delivered from Nvidia: > http://www.nvidia.de/Download/index.aspx?lang=en https://bugzilla.opensuse.org/show_bug.cgi?id=1171568#c3 > for the 5.3.18 kernel that driver doesn’t work either In the first message > The standard kernel 5.3.18 provides ksym(default:set_page_dirty_lock) = aad1d01a driver requires > nothing provides ksym(default:set_page_dirty_lock) = f9bf7120 -- You are receiving this mail because: You are on the CC list for the bug.

1 0