May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1170063] New: podman 1.9.0 is unable to download opensuse/leap image for aarch64
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1170063 Bug ID: 1170063 Summary: podman 1.9.0 is unable to download opensuse/leap image for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, rbrown(a)suse.com, sgrunert(a)suse.com Found By: --- Blocker: --- Since podman update from 1.8.2 to 1.9.0 [0], podman tests in openQA for Kubic/MicroOS [1] are unable to download the opensuse/leap image for aarch64 with the following error: no image found in manifest list for architecture arm64, variant v8, OS Linux But "hello-world" and "Alpine:3.6" images are fine. [0]: https://build.opensuse.org/request/show/794479 [1]: https://openqa.opensuse.org/tests/1241153#step/podman/11 -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1134788] New: HiKey960 not booting into EDK2 after edk2 and arm-trusted-firmware updates
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134788 Bug ID: 1134788 Summary: HiKey960 not booting into EDK2 after edk2 and arm-trusted-firmware updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: All Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: guillaume.gardet(a)arm.com Reporter: afaerber(a)suse.com QA Contact: jsrain(a)suse.com CC: dmueller(a)suse.com Found By: --- Blocker: --- hardware:boot/{l-loader,arm-trusted-firmware}-hikey960 are no longer properly booting after Guillaume's replacement of my downstream edk2-hikey960 package and update of arm-trusted-firmware package. New serial output: NOTICE: BL2: v2.1(debug): NOTICE: BL2: Built : 13:51:40OURCE, Apr 9 2019 INFO: BL2: Doing platform setup INFO: UFS LUN0 contains 1024 blocks with 4096-byte size INFO: UFS LUN1 contains 1024 blocks with 4096-byte size INFO: UFS LUN2 contains 2048 blocks with 4096-byte size INFO: UFS LUN3 contains 7805952 blocks with 4096-byte size INFO: ufs: change power mode success INFO: BL2: Loading image id 2 INFO: Loading image id=2 at address 0x89c80000 INFO: Image id=2 loaded: 0x89c80000 - 0x89cb5100 INFO: BL2: Initiating SCP_BL2 transfer to SCP INFO: BL2: SCP_BL2: 0x89c80000@0x35100 INFO: BL2: SCP_BL2 HEAD: INFO: BL2: SCP_BL2 0x7000 0x179 0x159 0x149 INFO: BL2: SCP_BL2 0x189 0x18b 0x18d 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x18f INFO: BL2: SCP_BL2 0x191 0x0 0x193 0x195 INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x4d454355 0x43494741 0x424d554e 0x21215245 INFO: BL2: SCP_BL2 0x4a054904 0x42912000 0xf841bfbc 0xe7fa0b04 INFO: BL2: SCP_BL2 0xb88cf000 0x3b18 0x3d1c 0x6809493e INFO: BL2: SCP_BL2 0x4613680a 0x201f102 0xf0002a04 0x600a804c INFO: BL2: SCP_BL2 0x204f04f 0xf203fb02 0xf102440a 0x60100204 INFO: BL2: SCP_BL2 0x160f04f 0xf103fb01 0x68004834 0x61044408 INFO: BL2: SCP_BL2 0x61866145 0xf8c061c7 0xf8c08020 0xf8c09024 INFO: BL2: SCP_BL2 0xf8c0a028 0xf3efb02c 0xf3ef8208 0x68118309 INFO: BL2: SCP_BL2 0xf1026401 0xf0110204 0xbf070f04 0x46113220 INFO: BL2: SCP_BL2 TAIL: INFO: BL2: SCP_BL2 0x19cad091 0x19cad091 0x19cad5a9 0x19cad0ed INFO: BL2: SCP_BL2 0x19cad195 0x19cad1cd 0x19cad001 0x19cad2e5 INFO: BL2: SCP_BL2 0x19cad003 0x19cad209 0x0 0x19cad6a9 INFO: BL2: SCP_BL2 0x19cad469 0x19cad27d 0x19cad2b9 0x19cad005 INFO: BL2: SCP_BL2 0x19cad17d 0x19cad7e9 0x19cad809 0x19cad9a5 INFO: BL2: SCP_BL2 0x19cad015 0x19cad049 0x19b80040 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 transferred to SCP INFO: start fw loading INFO: fw load success WARNING: BL2: Platform setup already done!! INFO: BL2: Loading image id 3 INFO: Loading image id=3 at address 0x1ac58000 INFO: Image id=3 loaded: 0x1ac58000 - 0x1ac63024 INFO: BL2: Loading image id 4 INFO: Loading image id=4 at address 0x3f000000 INFO: Image id=4 loaded: 0x3f000000 - 0x3f00001c INFO: OPTEE ep=0x3f000000 INFO: OPTEE header info: INFO: magic=0x4554504f INFO: version=0x2 INFO: arch=0x1 INFO: flags=0x0 INFO: nb_images=0x1 INFO: BL2: Loading image id 21 INFO: Loading image id=21 at address 0x3f000000 INFO: Image id=21 loaded: 0x3f000000 - 0x3f044270 INFO: BL2: Skip loading image id 22 INFO: BL2: Loading image id 5 INFO: Loading image id=5 at address 0x1ac98000 INFO: Image id=5 loaded: 0x1ac98000 - 0x1ad88000 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0x1ac58000 INFO: SPSR = 0x3cd NOTICE: BL31: v2.1(debug): NOTICE: BL31: Built : 13:51:40OURCE, Apr 9 2019 INFO: ARM GICv2 driver initialized Previous output: NOTICE: BL2: v1.5(debug): NOTICE: BL2: Built : 18:48:01OURCE, Jun 3 2018 INFO: BL2: Doing platform setup INFO: UFS LUN0 contains 1024 blocks with 4096-byte size INFO: UFS LUN1 contains 1024 blocks with 4096-byte size INFO: UFS LUN2 contains 2048 blocks with 4096-byte size INFO: UFS LUN3 contains 7805952 blocks with 4096-byte size INFO: ufs: change power mode success INFO: BL2: Loading image id 2 INFO: Loading image id=2 at address 0x89c80000 INFO: Image id=2 loaded: 0x89c80000 - 0x89cb5100 INFO: BL2: Initiating SCP_BL2 transfer to SCP INFO: BL2: SCP_BL2: 0x89c80000@0x35100 INFO: BL2: SCP_BL2 HEAD: INFO: BL2: SCP_BL2 0x7000 0x179 0x159 0x149 INFO: BL2: SCP_BL2 0x189 0x18b 0x18d 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x18f INFO: BL2: SCP_BL2 0x191 0x0 0x193 0x195 INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x18fd 0x18fd 0x18fd 0x18fd INFO: BL2: SCP_BL2 0x4d454355 0x43494741 0x424d554e 0x21215245 INFO: BL2: SCP_BL2 0x4a054904 0x42912000 0xf841bfbc 0xe7fa0b04 INFO: BL2: SCP_BL2 0xb88cf000 0x3b18 0x3d1c 0x6809493e INFO: BL2: SCP_BL2 0x4613680a 0x201f102 0xf0002a04 0x600a804c INFO: BL2: SCP_BL2 0x204f04f 0xf203fb02 0xf102440a 0x60100204 INFO: BL2: SCP_BL2 0x160f04f 0xf103fb01 0x68004834 0x61044408 INFO: BL2: SCP_BL2 0x61866145 0xf8c061c7 0xf8c08020 0xf8c09024 INFO: BL2: SCP_BL2 0xf8c0a028 0xf3efb02c 0xf3ef8208 0x68118309 INFO: BL2: SCP_BL2 0xf1026401 0xf0110204 0xbf070f04 0x46113220 INFO: BL2: SCP_BL2 TAIL: INFO: BL2: SCP_BL2 0x19cad091 0x19cad091 0x19cad5a9 0x19cad0ed INFO: BL2: SCP_BL2 0x19cad195 0x19cad1cd 0x19cad001 0x19cad2e5 INFO: BL2: SCP_BL2 0x19cad003 0x19cad209 0x0 0x19cad6a9 INFO: BL2: SCP_BL2 0x19cad469 0x19cad27d 0x19cad2b9 0x19cad005 INFO: BL2: SCP_BL2 0x19cad17d 0x19cad7e9 0x19cad809 0x19cad9a5 INFO: BL2: SCP_BL2 0x19cad015 0x19cad049 0x19b80040 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 0x0 0x0 0x0 0x0 INFO: BL2: SCP_BL2 transferred to SCP INFO: start fw loading INFO: fw load success WARNING: BL2: Platform setup already done!! INFO: BL2: Loading image id 3 INFO: Loading image id=3 at address 0x1ac58000 INFO: Image id=3 loaded: 0x1ac58000 - 0x1ac63028 INFO: BL2: Loading image id 4 INFO: Loading image id=4 at address 0x3f000000 INFO: Image id=4 loaded: 0x3f000000 - 0x3f00001c INFO: OPTEE ep=0x3f000000 INFO: OPTEE header info: INFO: magic=0x4554504f INFO: version=0x2 INFO: arch=0x1 INFO: flags=0x0 INFO: nb_images=0x1 INFO: BL2: Loading image id 21 INFO: Loading image id=21 at address 0x3f000000 INFO: Image id=21 loaded: 0x3f000000 - 0x3f045270 INFO: BL2: Skip loading image id 22 INFO: BL2: Loading image id 5 INFO: Loading image id=5 at address 0x1ac98000 INFO: Image id=5 loaded: 0x1ac98000 - 0x1ad88000 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0x1ac58000 INFO: SPSR = 0x3cd NOTICE: BL31: v1.5(debug): NOTICE: BL31: Built : 18:48:01OURCE, Jun 3 2018 WARNING: Using deprecated integer interrupt array in gicv2_driver_data_t WARNING: Please migrate to using an interrupt_prop_t array INFO: ARM GICv2 driver initialized INFO: BL31: Initializing runtime services WARNING: BL31: cortex_a53: CPU workaround for 835769 was missing! INFO: BL31: cortex_a53: CPU workaround for 843419 was applied INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: plat_setup_psci_ops: INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x1ac98000 INFO: SPSR = 0x3c9 UEFI firmware (version Alpha built at 12:00:00 on May 31 2018) -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1134533] New: The emergency shell does not show the "Welcome" message
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134533 Bug ID: 1134533 Summary: The emergency shell does not show the "Welcome" message Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In openQA, when 'systemctl rescue' is executed, the emergency shell does not show the "Welcome" message: "You are in Rescue mode. After login..." Before "Give root password for maintenance" message. See https://openqa.opensuse.org/tests/928446#step/snapper_undochange/23 and https://openqa.opensuse.org/tests/928446#step/snapper_thin_lvm/58 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1157755] New: LD from binutils 2.33.1 is broken on aarch64
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1157755 Bug ID: 1157755 Summary: LD from binutils 2.33.1 is broken on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 824949 --> http://bugzilla.opensuse.org/attachment.cgi?id=824949&action=edit tensorflow full build log While building Tensorflow for Factory:ARM we get the following error: [20116s] /usr/bin/gcc -shared -o bazel-out/aarch64-opt/bin/tensorflow/python/_pywrap_tensorflow_internal.so '-Wl,-rpath,$ORIGIN/../../_solib_aarch64/_U_S_Stensorflow_Spython_C_Upywrap_Utensorflow_Uinternal.so___Utensorflow' -Lbazel-out/aarch64-opt/bin/_solib_aarch64/_U_S_Stensorflow_Spython_C_Upywrap_Utensorflow_Uinternal.so___Utensorflow -Wl,--version-script bazel-out/aarch64-opt/bin/tensorflow/python/pywrap_tensorflow_internal_versionscript.lds '-Wl,-rpath,$ORIGIN/,-rpath,$ORIGIN/..' -Wl,-soname,_pywrap_tensorflow_internal.so -Wl,-no-as-needed -Wl,-z,relro,-z,now -B/usr/bin -B/usr/bin -pass-exit-codes -Wl,--gc-sections -Wl,@bazel-out/aarch64-opt/bin/tensorflow/python/_pywrap_tensorflow_internal.so-2.params) [20116s] /usr/bin/ld: can not size stub section: invalid operation [20116s] /usr/bin/ld: linker stubs: file class ELFCLASSNONE incompatible with ELFCLASS64 [20116s] /usr/bin/ld: final link failed: file in wrong format [20116s] collect2: error: ld returned 1 exit status Building for released Tumbleweed is fine. Major diffs are: * binutils 2.32 > 2.33.1: https://build.opensuse.org/request/show/748099 * kernel 5.3.8 > 5.3.12 * java-1_8_0-openjdk 1.8.0.222 > 1.8.0.232 binutils 2.33 got lots of aarch64 update and the error is from ld, so this is where my suspicions go. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1124940] New: ghc-bootstrap fails to build for Leap 15.x for ARM
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1124940 Bug ID: 1124940 Summary: ghc-bootstrap fails to build for Leap 15.x for ARM Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Check 15.1:ARM (armv7 and aarch64) build failures on: https://build.opensuse.org/package/show/openSUSE:Leap:15.1:ARM/ghc-bootstrap The problem is that pre-built binaries require glibc 2.27 and Leap 15.x has only glibc 2.26 So, ghc is now unresolvable on Leap 15.1:ARM -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1151462] New: Leap 15.2 ports (ARM + PowerPC) are missing update repo on download.o.o
by bugzilla_noreply＠novell.com 19 Oct '21

19 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1151462 Bug ID: 1151462 Summary: Leap 15.2 ports (ARM + PowerPC) are missing update repo on download.o.o Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap 15.2 ports (ARM + PowerPC) are missing update repo on download.o.o: http://download.opensuse.org/ports/update/leap/15.2/oss/ Moreover, there is no binaries available on https://build.opensuse.org/project/show/openSUSE:Leap:15.2:Update for ports. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1144793] New: libdlm: upgrade libdlm package to include some fixes for dlm_controld
by bugzilla_noreply＠novell.com 18 Oct '21

18 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1144793 Bug ID: 1144793 Summary: libdlm: upgrade libdlm package to include some fixes for dlm_controld Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: ghe(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libdlm in the upstream has release v4.0.9 tag, there are some fixes and enhancements for dlm_controld between v4.0.9 and v4.0.7. second, libdlm project was moved to https://pagure.io/dlm, we also need to update the related items in the spec file. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1112433] New: file /usr/bin/embedspu conflicts between attempted installs of sdcc-3.6.0-lp151.3.2.ppc64le and binutils-2.29.1-lp151.5.2.ppc64le
by bugzilla_noreply＠novell.com 17 Oct '21

17 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1112433 Bug ID: 1112433 Summary: file /usr/bin/embedspu conflicts between attempted installs of sdcc-3.6.0-lp151.3.2.ppc64le and binutils-2.29.1-lp151.5.2.ppc64le Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Is the embedspu from binutils sufficient or is the one from sdcc different? -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1104462] New: annoying kwallet setup dialog
by bugzilla_noreply＠novell.com 17 Oct '21

17 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1104462 Bug ID: 1104462 Summary: annoying kwallet setup dialog Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- whenever an application, like the network settings or chromium, want to store passwords a dialog to set up kwallet appears. It has two options, to use blowfish or to use GPG. GPG is default. Both are not very understandable to non technical users. Clicking cancel just leads to the dialog appearing next time again. The default option leads to an error message that no GPG key is available. Can we have that more user friendly please? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1166669] New: susepaste command from openSUSE shell logins is failing with "Paste failed :-("
by bugzilla_noreply＠novell.com 16 Oct '21

16 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1166669 Bug ID: 1166669 Summary: susepaste command from openSUSE shell logins is failing with "Paste failed :-(" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://progress.opensuse.org/issues/56189 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initial Summary: susepaste command from openSUSE shell logins is failing with "Paste failed :-(" To reproduce: 1-login to shell or xterm or konsole or or or or... 2-susepaste -n mynick -e 10080 /var/log/Xorg.0.log Actual results: 1-paste quickly appears on https://paste.opensuse.org/lists 2-shell reports "Paste failed :-(" Expected results: 1-paste quickly appears on https://paste.opensuse.org/lists 2-shell reports the URL of the successful paste Notes: 1-https://lists.opensuse.org/opensuse/2020-01/msg00429.html has an ostensibly fixed script. 2-https://progress.opensuse.org/issues/56189 was reported in August. 3-Issues began last June: https://lists.opensuse.org/opensuse/2019-06/msg00050.html 4-September thread reporting failure: https://lists.opensuse.org/opensuse/2019-09/msg00350.html 5-This creates obstacle for helping people reporting trouble in the forums -- You are receiving this mail because: You are on the CC list for the bug.

2 6