February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1145745] New: umoci fails to build with go1.11
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1145745 Bug ID: 1145745 Summary: umoci fails to build with go1.11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With go update via SP1:Update, it change to go1.11 as the default one, however umoci fails to build with go1.11. [ 42s] + go test -v -cover -covermode=count -coverprofile=/tmp/umoci-coverage.rijr0s/cov.opgda -coverpkg=github.com/openSUSE/umoci/... github.com/openSUSE/umoci/cmd/umoci [ 46s] FAIL github.com/openSUSE/umoci/cmd/umoci [build failed] [ 46s] error: Bad exit status from /var/tmp/rpm-tmp.FoT1oN (%check) Build log: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2:Stagin… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1145616] [Build 483.2] gnome session crashes after starting gimp in openQA test
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1145616 http://bugzilla.suse.com/show_bug.cgi?id=1145616#c2 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(yfjiang(a)suse.com) --- Comment #2 from Lubos Kocman <lubos.kocman(a)suse.com> --- Hello Yifan, so do I read you correctly that this might be a test suite issue? Also I feel like this issue happened randomly especially in case that previous test failed. Lubos -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159999] New: go1.9 build failed (excluded) at armv7l
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159999 Bug ID: 1159999 Summary: go1.9 build failed (excluded) at armv7l Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, Currently, go1.9 build is excluded for armv7l architecture at Leap 15.2. The build is known to be failed previously. However, go1.9 build is fixed for arvm7l in openSUSE:Factory [1]. Could this fix be backported to Leap 15.2? go1.9 is required for go1.12, and go1.12 is required for docker. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/go1.… -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1156920] wpa_supplicant-2.9 is broken with wicked
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1156920 http://bugzilla.opensuse.org/show_bug.cgi?id=1156920#c15 Anatol Belski <ab(a)php.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ab(a)php.net --- Comment #15 from Anatol Belski <ab(a)php.net> --- Based on the previous suggestion from Bernhard, i was able to fix this issue on the current Tumbleweed aarch64 as well. Eg. zypper in libopenssl1_0_0 rpm -U --oldpackage https://rpmfind.net/linux/opensuse/ports/update/leap/42.3/oss/aarch64/wpa_s… zypper al --type package wpa_supplicant Using the latest leap package seems to be suitable for now, so it seems to be a worky trick. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162498] New: yast lan needs quite some time to start
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162498 Bug ID: 1162498 Summary: yast lan needs quite some time to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In openQA tests recurrently fail as yast lan needs more than 30 seconds to start: 30 seconds until initial screen: https://openqa.opensuse.org/tests/1162799#step/yast2_lan/12 ~35 seconds to complete: https://openqa.opensuse.org/tests/1163348#step/yast2_lan/16 Is this expected (i.e. the timeout should be extended to ~60 seconds) or is this considered a bug? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161232] kernel stack trace on resume
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161232 http://bugzilla.suse.com/show_bug.cgi?id=1161232#c10 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse(a)mike.franken.de Flags|needinfo?(oneukum(a)suse.com) |needinfo?(opensuse(a)mike.fra | |nken.de) --- Comment #10 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Jiri Slaby from comment #6) > Oliver, any idea why this happens? > > > usb usb1: root hub lost power or was reset > > usb usb2: root hub lost power or was reset > > ACPI: EC: event unblocked > > usb usb3: root hub lost power or was reset > > usb usb4: root hub lost power or was reset > > xhci_hcd 0000:3c:00.0: Host halt failed, -19 > > xhci_hcd 0000:3c:00.0: Host not accessible, reset failed. > > usb usb5: root hub lost power or was reset > > usb usb6: root hub lost power or was reset > > xhci_hcd 0000:3d:00.0: Host halt failed, -19 > > usb usb7: root hub lost power or was reset > > usb usb8: root hub lost power or was reset > > xhci_hcd 0000:3d:00.0: Host not accessible, reset failed. > > xhci_hcd 0000:3e:00.0: Host halt failed, -19 > > xhci_hcd 0000:3e:00.0: Host not accessible, reset failed. [ 5390.147140] pcieport 0000:03:00.0: Refused to change power state, currently in D3 [ 5390.150504] pcieport 0000:04:01.0: Refused to change power state, currently in D3 [ 5390.150505] pcieport 0000:04:00.0: Refused to change power state, currently in D3 [ 5390.150506] pcieport 0000:04:02.0: Refused to change power state, currently in D3 [ 5390.150507] pcieport 0000:04:04.0: Refused to change power state, currently in D3 [ 5390.156540] pcieport 0000:3a:00.0: Refused to change power state, currently in D3 [ 5390.156545] thunderbolt 0000:05:00.0: Refused to change power state, currently in D3 [ 5390.159558] pcieport 0000:3b:00.0: Refused to change power state, currently in D3 [ 5390.159559] pcieport 0000:3b:01.0: Refused to change power state, currently in D3 [ 5390.159560] pcieport 0000:3b:02.0: Refused to change power state, currently in D3 This is basically a PCI issue, which in turn crashes USB. But the second dmesg is inconsistent with that. Could we have two or three crashes with the same kernel as dmesg, so we can be sure that we are not seeing memory corruption? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162471] [Build 20200131] Kernel 5.5/btrfs 'eats' disk space
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162471 http://bugzilla.suse.com/show_bug.cgi?id=1162471#c5 Wenruo Qu <wqu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wqu(a)suse.com) | --- Comment #5 from Wenruo Qu <wqu(a)suse.com> --- (In reply to Dominique Leuenberger from comment #3) > (In reply to Wenruo Qu from comment #2) > > A known bug, caused by v5.4 kernel where metadata over-commit behavior > > changed. > > Caused by 5.4 kernel? How come we only see this with 5.5? (or was that a > typo?) > > (all in all: glad we had openQA catch it) It's v5.4. We had reported since v5.4. We knew it, tried several ways to fix it, but none of them was good enough for backport, until recent days. (In reply to Jiri Slaby from comment #4) > (In reply to Wenruo Qu from comment #2) > > The fix is already in David's tree, would be sent to upstream in next pull > > request. > > Could you be more specific? For example a subject or SHA? Commit 86e7e13f738e ("btrfs: do not zero f_bavail if we have available space") in David's misc-next branch will fix it. Although that "Fixes:" tag mentions it's a v4.5 commit, it's really Josef's metadata space overcommit patches changing the behavior and caused the problem. (Too many patches in that series, thus I failed to pin to exact commit) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162426] lxd-bash-completion doesn't work
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1162426 http://bugzilla.suse.com/show_bug.cgi?id=1162426#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1162426) was mentioned in https://build.opensuse.org/request/show/769535 15.1 / lxc https://build.opensuse.org/request/show/769536 15.2 / lxc -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156920] wpa_supplicant-2.9 is broken with wicked
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1156920 http://bugzilla.opensuse.org/show_bug.cgi?id=1156920#c14 Victor Zhestkov <victor.zhestkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victor.zhestkov(a)suse.com --- Comment #14 from Victor Zhestkov <victor.zhestkov(a)suse.com> --- Yes, it breaks NET installation over WIFI -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162497] New: Not show any more a wifi device
by bugzilla_noreply＠novell.com 03 Feb '20

03 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162497 Bug ID: 1162497 Summary: Not show any more a wifi device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: obarrios(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 828916 --> http://bugzilla.opensuse.org/attachment.cgi?id=828916&action=edit dmesg I have a laptop Dell Inc. Precision 5530/0NFGCT, BIOS 1.15.0 12/25/2019, and after upgrade to the latest version TW, the Network Manager doesn't show any Wifi device. I then tried starting with the previous kernel 5.4.13-1-default, and the wifi device is there and works all fine. So it might be some problem with the firmware and the latest kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 1