July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189003] New: Yast is unable to handle encrypted disk
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 Bug ID: 1189003 Summary: Yast is unable to handle encrypted disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 851486 --> http://bugzilla.opensuse.org/attachment.cgi?id=851486&action=edit Screenshot showing problem and details When trying an update or installation, Yast detects an encrypted disk, asks for the password, and unlocks it, but then is unable to continue (see attachment). The device /dev/mapper/cr-auto-1 is there when Yast claims it is not. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1179492] New: Test grub booting using pe/coff boot entry to support shim and MOK
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1179492 Bug ID: 1179492 Summary: Test grub booting using pe/coff boot entry to support shim and MOK Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: mchang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To support shim lock protocol and use MOK (Machine Owner Key), grub has to load and boot the kernel on it's own without resorting to firmware protocols, namely UEFI LoadImage and StartImage protocols, which would only know about keys in db and dbx and thus would reject image with signature of MOK. To finalize UEFI Secure Boot to fully utilize the capability of shim, the grub package with needed implementation to achieve that is available here. https://build.opensuse.org/package/show/home:michael-chang:arm64-linuxefi/g… In a nut shell, it will call out shim_lock protocol to verify the image, and then jump directly to the PE/COFF entry to boot the image if preceding verification goes successfully. This ticket is opened to track any issue in grub with respect to needed change to adopt shim and MOK on aarch64. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1201529] New: VUL-0: CVE-2022-32323: autotrace: Heap overflow in AutoTrace v0.40.0
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1201529 Bug ID: 1201529 Summary: VUL-0: CVE-2022-32323: autotrace: Heap overflow in AutoTrace v0.40.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/337313/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-32323 AutoTrace v0.40.0 was discovered to contain a heap overflow via the ReadImage function at input-bmp.c:660. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32323 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32323 https://github.com/autotrace/autotrace/commit/2b44c173027736c64b3f379bd154c… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1188363] New: windows:mingw:win{32|64}/mingw{32|64}-python3 missing
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188363 Bug ID: 1188363 Summary: windows:mingw:win{32|64}/mingw{32|64}-python3 missing Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- It would be nice to have a mingw build for Python3 that can be used by mingwxx-gdb and other packages wanting Python3 support. There could be two sources for such a package: 1. https://build.opensuse.org/package/show/home%3Ajayvdb%3Awine-python3%3Apy37… 2. https://github.com/python-cmake-buildsystem/python-cmake-buildsystem The first one uses a custom python build system that is native to the obs project and looks like it would be a lot of work to understand and maintain. Since the build system of the second proposal is based on a known build system (cmake) and it is managed on github, it is suspected that maintenance will be easier here, but may still need adjustments to add mingw based cross-compile functionality and package that. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1191084] New: ocfs2-tools: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1191084 Bug ID: 1191084 Summary: ocfs2-tools: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: renzhengeek(a)gmail.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ghe(a)suse.com Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for ocfs2-tools. If ocfs2-tools still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1129466] New: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129466 Bug ID: 1129466 Summary: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fwdupd 1.2.3-2.1 cannot update the BIOS on my laptop because of this error: $fwupdmgr get-devices ... 20MBCTO1WW System Firmware DeviceId: 65b6a9dc7b7df18bdff003584b51bf21373e3aa6 Guid: 1e1fe415-74e8-49e1-9508-106b3d13d50d Guid: 230c8b18-8d9b-53ec-838b-6cfc0383493a Guid: 171800c9-1a51-5fd9-a32b-7b3999cb1c4e Plugin: uefi Flags: internal|require-ac|supported|registered|needs-reboot Version: 0.1.18 VersionLowest: 0.1.0 Icon: computer Created: 2019-03-15 UpdateError: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found Apparently, if Secure Boot is enabled (my case and I believe TW default on UEFI installs), it looks for /usr/lib/fwupd/efi/fwupdx64.efi.signed. This file is missing but it turns out that /usr/lib/fwupd/efi/fwupdx64.efi is present AND signed: $pesign -S -i /usr/lib/fwupd/efi/fwupdx64.efi --------------------------------------------- certificate address is 0x7f0e55679f78 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is openSUSE Secure Boot Signkey The signer's email address is build(a)opensuse.org Signing time: Tue Mar 05, 2019 There were certs or crls included. --------------------------------------------- So the fix is simply so make a symlink and restart fwupd so it sees the change: $ln -s /usr/lib/fwupd/fwupdx64.efi /usr/lib/fwupd/fwupdx64.efi.signed $systemctl restart fwupd Then the error goes away in 'fwupdmgr get-devices' and you can supposedly update with 'fwupdmgr update' (didn't try it at updating the BIOS is rather scary and I do not absolutely need this update currently). So I think the package should be updated to make the symlink (or rename the file if keeping fwupdx64.efi is unecessary). -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1161823] New: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported"
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1161823 Bug ID: 1161823 Summary: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported" 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: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 828281 --> http://bugzilla.opensuse.org/attachment.cgi?id=828281&action=edit Step 1 of installation When installing OpenSUSE TW, by adding compress=zstd in fstab arbitrary option value will result in broken grub "compression type 0x3 not supported" even it grub already support zstd compression on btrfs. Or maybe I did something wrong. Installation process photos were attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 1098360] New: aide --init gives the error DBG: md_enable: algorithm 7 not available
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098360 Bug ID: 1098360 Summary: aide --init gives the error DBG: md_enable: algorithm 7 not available Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chevy.stroker(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt:~ # aide --init DBG: md_enable: algorithm 7 not available gcry_md_enable 7 failedAIDE initialized database at /var/lib/aide/aide.db.new Number of entries: 218651virt:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1028824] New: aide looking for a removed algorithm
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028824 Bug ID: 1028824 Summary: aide looking for a removed algorithm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After starting: aide -i comes the following notice: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1139017] New: aide gcry_md_enable 7 failure
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1139017 Bug ID: 1139017 Summary: aide gcry_md_enable 7 failure Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP1 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: woe.2018(a)wizonet.ch QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- This error occurs in openSuSE Leap 15 and openSuSE Leap 15.1 (which is not available ub in OS: and Version: selector above). The output of aide shows no longer the differ files - only the summary is available: aide_2019-06-23 gcry_md_enable 7 failedAIDE found differences between database and filesystem!! Summary: Total number of entries: 103548 Added entries: 18 Removed entries: 0 Changed entries: 17 Therefore it is no longer possible to identify the files that has changed. I think the error is based on this message: In output: gcry_md_enable 7 failed When started: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3