May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171137] New: KIWI, during OEM install udev can't find devices like keyboard, mouse etc.
by bugzilla_noreply＠novell.com 05 May '20

05 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171137 Bug ID: 1171137 Summary: KIWI, during OEM install udev can't find devices like keyboard, mouse etc. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: psarnack(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: this maybe kiwi bug. happend after upgrade of systemd from release version systemd-234-lp151.25.7 to update version systemd-234-lp151.26.13.1. actual culprit is udev-234-lp151.26.13.1 once OEM image using KIWI is created and booted , during boot initial/installer initrd cannot find devices , i.e do load drivers modules.. cannot accept licence etc, cannot continue. the workaround it to put initial release version of 80-drivers.rules in initrd directory /etc/udev.rules.d/ the change is the first line, where new version is executed on "add" event , but old (working) version on "add" and "change" event. new: not working : ACTION!="add", GOTO="drivers_end" old: working : ACTION=="remove", GOTO="drivers_end" that indicate kernel generate "change" event ? kernel-default-4.12.140lp151.28.48.1 kiwi version 9.18.16-lp151.2.6.1 udev-234-lp151.26.13.1 Reproducible: Always Steps to Reproduce: 1. create OEM image using KIWI with inirtd version mentioned and licence screen 2. boot , once booted and license screen appear .. keyboard,mouse (both USB) doesn't work. also screen resolution doesn't change. Actual Results: drivers are not loaded, keyboard, mouse doesn't work Expected Results: keyboard, mouse work, screen change resolution -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1171132] can't install broadcom-wl from packman
by bugzilla_noreply＠novell.com 05 May '20

05 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171132 http://bugzilla.suse.com/show_bug.cgi?id=1171132#c2 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Maintenance |Kernel Assignee|maintenance(a)opensuse.org |kernel-maintainers(a)forge.pr | |ovo.novell.com --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- i dont think the leap 15.2 kabi is frozen yet -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170842] On aarch64, using dracut 050, only one interface gets ifup during the pxe boot first stage
by bugzilla_noreply＠novell.com 05 May '20

05 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1170842 http://bugzilla.suse.com/show_bug.cgi?id=1170842#c1 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas(a)suse.com, | |thomas.blume(a)suse.com Flags| |needinfo?(aplanas(a)suse.com) --- Comment #1 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Alberto Planas Dominguez from comment #0) > Created attachment 837097 [details] > Dracut logs > > When booting a OEM Kiwi via PXE boot, the download of the second kernel, > initrd and image fails. > > Inside the dracut shell we can see that the device have two interfaces, but > only the first interface gets up. The second one can be manually up via > "ifup enp0s2" > > The logs shows that indeed, there is only one call to ifup, that correspond > to the first interface. If not explicitly given at the command line, dracut will only set up one interface and just continue if this is successfull, which is the case here: --> 39.785787] localhost dracut-initqueue[575]: + ip -4 addr add 10.0.3.101/24 broadcast 10.0.3.255 dev enp0s1 [ 39.856029] localhost dracut-initqueue[575]: + route=() [ 39.858205] localhost dracut-initqueue[575]: + local r route [ 39.858205] localhost dracut-initqueue[575]: + '[' -n '' ']' [ 39.858205] localhost dracut-initqueue[575]: + local g [ 39.858205] localhost dracut-initqueue[575]: + '[' -n 10.0.3.101 ']' [ 39.858205] localhost dracut-initqueue[575]: + for g in ${GATEWAYS} [ 39.858205] localhost dracut-initqueue[575]: + ip -4 route add default via 10.0.3.101 dev enp0s1 [ 39.898801] localhost dracut-initqueue[575]: + break [ 39.901409] worker dracut-initqueue[575]: + '[' -n '' ']' [ 39.901409] worker dracut-initqueue[575]: + '[' -n worker ']' [ 39.901409] worker dracut-initqueue[575]: + echo worker [ 39.901409] worker dracut-initqueue[575]: + '[' '!' -s /tmp/net.enp0s1.resolv.conf.ipv4 ']' [ 39.907099] worker dracut-initqueue[575]: + '[' -n '' ']' [ 39.907099] worker dracut-initqueue[575]: + '[' -n '' ']' [ 39.907099] worker dracut-initqueue[575]: + '[' -n 10.0.3.1 ']' [ 39.907099] worker dracut-initqueue[575]: + for s in ${DNSSERVERS} [ 39.907099] worker dracut-initqueue[575]: + echo nameserver 10.0.3.1 [ 39.907099] worker dracut-initqueue[575]: + '[' -e /tmp/net.enp0s1.resolv.conf.ipv4 ']' [ 39.907099] worker dracut-initqueue[575]: + '[' '!' -e /etc/resolv.conf ']' [ 39.907099] worker dracut-initqueue[575]: + cp -f /tmp/net.enp0s1.resolv.conf.ipv4 /etc/resolv.conf [ 39.945505] worker systemd[1]: inotify event for /etc/localtime [ 39.949340] worker systemd[1]: Failed to stat /etc/localtime, ignoring: No such file or directory [ 39.951267] worker dracut-initqueue[575]: + info 'DHCP is finished successfully' [ 39.953333] worker dracut-initqueue[575]: + echo 'DHCP is finished successfully' --< The root cause visible in the logs is that the device for installation isn't found: --> [ 48.582317] worker dracut-pre-mount[719]: /////lib/dracut/hooks/pre-mount/30-kiwi-dump-image.sh@15(report_and_quit): die 'No device(s) for installation found' [ 48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@460(die): echo '<24>dracut: FATAL: No device(s) for installation found' [ 48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@461(die): echo '<24>dracut: Refusing to continue' [ 48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@465(die): echo 'warn dracut: FATAL: "No device(s) for installation found"' [ 48.582317] worker dracut-pre-mount[719]: ////lib/dracut-lib.sh@466(die): echo 'warn dracut: Refusing to continue' --< Still, I can see that a device gets plugged: --> [ 36.297674] localhost systemd[1]: dev-vda.device: Changed dead -> plugged [ 36.298760] localhost systemd[1]: sys-devices-platform-LNRO0005:1f-virtio2-block-vda.device: Changed dead -> plugged --< Is vda the device configured for installation? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171123] New: GCC 10: qemu build fails on i586
by bugzilla_noreply＠novell.com 05 May '20

05 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171123 Bug ID: 1171123 Summary: GCC 10: qemu build fails on i586 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.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… with: [ 861s] drivers/net/intelvf.c: In function 'intelvf_mbox_poll': [ 861s] drivers/net/intelvf.c:80:13: error: array subscript i is outside array bounds of 'uint32_t[0]' {aka 'unsigned int[]'} [-Werror=array-bounds] [ 861s] 80 | msg->dword[i] = readl ( intel->regs + intel->mbox.mem + [ 861s] | ~~~~~~~~~~^~~ [ 861s] In file included from drivers/net/intelvf.c:32: [ 861s] drivers/net/intelvf.h:135:11: note: while referencing 'dword' [ 861s] 135 | uint32_t dword[0]; [ 861s] | ^~~~~ [ 861s] drivers/net/intelvf.c:98:20: note: defined here 'msg' [ 861s] 98 | union intelvf_msg msg; [ 861s] | ^~~ It's analyzed in GCC bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94940#c4 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1166404] Pan not able to post to any newsgroups
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.novell.com/show_bug.cgi?id=1166404 http://bugzilla.novell.com/show_bug.cgi?id=1166404#c6 --- Comment #6 from Atri Bhattacharya <badshah400(a)gmail.com> --- I am a little confused: your initial complaint said that the problem exists on TW with pan version 0.146 and not on Leap 15.1 (with pan v 0.145). This tallies in with the upstream report, also against version 0.146. Are you saying that it is indeed working on TW now, still with version 0.146? That would indicate that some underlying dependency and not pan itself is to blame. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171132] New: can't install broadcom-wl from packman
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171132 Bug ID: 1171132 Summary: can't install broadcom-wl from packman Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: boodyeltrqawy(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: trying to install broadcom-wl doesn't work, with the error: Problem: nothing provides ksym(preempt:dev_driver_string) = 61e2d92c needed by broadcom-wl-kmp-preempt-6.30.223.271_k5.3.18_lp152.12-pm152.12.6.x86_64 Solution 1: do not install broadcom-wl-6.30.223.271-pm152.12.6.x86_64 Solution 2: break broadcom-wl-kmp-preempt-6.30.223.271_k5.3.18_lp152.12-pm152.12.6.x86_64 by ignoring some of its dependencies Reproducible: Always Steps to Reproduce: sudo zypper in broadcom-wl Actual Results: Problem: nothing provides ksym(preempt:dev_driver_string) = 61e2d92c needed by broadcom-wl-kmp-preempt-6.30.223.271_k5.3.18_lp152.12-pm152.12.6.x86_64 Solution 1: do not install broadcom-wl-6.30.223.271-pm152.12.6.x86_64 Solution 2: break broadcom-wl-kmp-preempt-6.30.223.271_k5.3.18_lp152.12-pm152.12.6.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): Expected Results: to install broadcom-wl -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1171045] New: Mesa-drivers build failure ppc64le "error: ‘std::index_sequence’ has not been declared"
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171045 Bug ID: 1171045 Summary: Mesa-drivers build failure ppc64le "error: ‘std::index_sequence’ has not been declared" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 837313 --> http://bugzilla.opensuse.org/attachment.cgi?id=837313&action=edit Mesa_drivers_standard_ppc64le_202005040925.log Mesa-drivers build failure ppc64le "error: ‘std::index_sequence’ has not been declared" as reported in attached Mesa_drivers_standard_ppc64le_202005040925.log extract: === [ 483s] In file included from /usr/include/llvm/IR/Module.h:19, [ 483s] from ../src/gallium/state_trackers/clover/llvm/codegen.hpp:35, [ 483s] from ../src/gallium/state_trackers/clover/llvm/codegen/bitcode.cpp:34: [ 483s] /usr/include/llvm/ADT/STLExtras.h:559:49: error: ‘std::index_sequence’ has not been declared ... [ 485s] /usr/include/llvm/IR/PassInstrumentation.h:85:34: required from here [ 485s] /usr/include/llvm/ADT/PointerIntPair.h:148:25: error: static assertion failed: PointerIntPair with integer size too large for pointer [ 485s] 148 | static_assert(IntBits <= PtrTraits::NumLowBitsAvailable, [ 485s] | ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 485s] /usr/include/llvm/ADT/PointerIntPair.h:163:42: error: right operand of shift expression ‘(1 << 18446744073709551615)’ is >= than the precision of the left operand [-fpermissive] === As per osc jobhist failure is not directly related to a source code change of Mesa-drivers. === $osc jobhist -l10 openSUSE:Factory:PowerPC/Mesa-drivers standard ppc64le time package reason code build time worker 2020-02-22 20:03:38 Mesa-drivers source change succeeded 30m 55s obs-power8-02:15 2020-02-26 14:57:01 Mesa-drivers source change succeeded 34m 21s obs-power8-02:20 2020-03-03 10:02:50 Mesa-drivers source change succeeded 32m 14s obs-power8-04:19 2020-03-11 18:57:41 Mesa-drivers source change succeeded 31m 15s obs-power8-02:3 2020-03-26 02:04:06 Mesa-drivers source change succeeded 21m 14s obs-power8-01:12 2020-04-05 19:46:58 Mesa-drivers source change succeeded 21m 28s obs-power8-01:12 2020-04-07 09:10:54 Mesa-drivers source change succeeded 31m 12s obs-power8-04:14 2020-04-10 02:20:43 Mesa-drivers new build failed 7m 42s obs-power8-01:8 2020-04-27 22:21:44 Mesa-drivers source change failed 14m 15s obs-power8-03:12 2020-05-02 20:47:49 Mesa-drivers source change failed 11m 35s obs-power8-02:3 === -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1170998] yast2-aduc produces a lot of ldap traffic
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170998 http://bugzilla.opensuse.org/show_bug.cgi?id=1170998#c1 David Mulder <david.mulder(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from David Mulder <david.mulder(a)suse.com> --- Merged fixes upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1166537] osc rq accept - forwarding request causes backtrace
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1166537 http://bugzilla.suse.com/show_bug.cgi?id=1166537#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:1172-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1160446,1166537,1168862 CVE References: Sources used: SUSE Linux Enterprise Module for Development Tools 15-SP1 (src): osc-0.168.2-3.15.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156202] New: nginx: GeoIP support is discontinued
by bugzilla_noreply＠novell.com 04 May '20

04 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1156202 Bug ID: 1156202 Summary: nginx: GeoIP support is discontinued Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: achernikov(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: schubi(a)suse.com, suse(a)ammler.ch Blocks: 1156194 Found By: --- Blocker: --- GeoIP has been discontinued by Maxmind. Please see https://support.maxmind.com/geolite-legacy-discontinuation-notice/ for details. Without the database GeoIP is useless. Therefore all users of GeoIP have to either migrate to libmaxminddb or remove GeoIP support. The GeoIP package itself will be dropped from Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5