June 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185232] something has gone seriously wrong: shim_init() - system does not boot anymore after installing today's updates
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1185232 https://bugzilla.suse.com/show_bug.cgi?id=1185232#c57 --- Comment #57 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Ren� Neumaier from comment #55) > (In reply to Gary Ching-Pang Lin from comment #54) > > Did you copy grub.efi to the debug folder? I expected shim failed early as > > comment#0 so the steps doesn't copy grub.efi to the debug folder. If you > > did, it's understandable because Leap 15.3 uses grub.efi from SLE15-SP3 > > directly, so shim-opensuse.efi couldn't verify it with the built-in openSUSE > > CA. > > > > Anyway it seems your case is different from comment#0. > > I did it strictly as in your tutorial: > > > 1. Create a directory for the debug shim and copy grub.efi to that directoy: > > # cd /boot/efi/EFI > > # mkdir debug > > # cp opensuse/grub.efi debug > Oops, my bad. Anyway, the error message is caused by the change of signkey for grub.efi, so that's expected. > rene@localhost:~> ls -l /boot/efi/EFI/debug/ > total 2112 > -rwxr-xr-x 1 root root 1222656 Jun 1 15:05 grub.efi > -rwxr-xr-x 1 root root 930824 Jun 1 15:09 shim.efi > > localhost:~ # md5sum /boot/efi/EFI/debug/* > 0daa63c6a804524716fbcd4e7bf407d4 /boot/efi/EFI/debug/grub.efi > 1cf53f72d15b402924e0d7df884812f7 /boot/efi/EFI/debug/shim.efi > > localhost:~ # md5sum /boot/efi/EFI/opensuse/* > 93d0a39fa28ce160d08da037bd45f083 /boot/efi/EFI/opensuse/MokManager.efi > 1191fbb59492fedea2776dab6f7c8343 /boot/efi/EFI/opensuse/boot.csv > 91bd139eb985983650ab808809ea9656 /boot/efi/EFI/opensuse/grub.cfg > 0daa63c6a804524716fbcd4e7bf407d4 /boot/efi/EFI/opensuse/grub.efi > d6bfdc568c32902c7405b163c86b38d0 /boot/efi/EFI/opensuse/grubx64.efi > 8a1f940a8662d67482fe9f6327925f59 /boot/efi/EFI/opensuse/shim.efi > > > > ... > > You can check the system status with the following commands: > > > > # hexdump -C > > /sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c > > # hexdump -C > > /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c > > > > For a Secure Boot enabled UEFI firmware, SetupMode should be "06 00 00 00 > > 00" and SecureBoot should be "06 00 00 00 01". > > localhost:~ # hexdump -C > /sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c > 00000000 06 00 00 00 01 |.....| > 00000005 > localhost:~ # hexdump -C > /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c > 00000000 06 00 00 00 00 |.....| > 00000005 > Hmmmm, so your firmware actually doesn't enable Secure Boot. > localhost:~ # grep -i secure /etc/sysconfig/bootloader > # Enable UEFI Secure Boot support > # This setting is only relevant to UEFI which supports Secure Boot. It won't > SECURE_BOOT="yes" This just makes yast to install shim to support Secure Boot. The real status of SB is controlled by the firmware. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186668] X11:Utilities/workrave: New version available
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186668 https://bugzilla.suse.com/show_bug.cgi?id=1186668#c3 --- Comment #3 from Timo Jyrinki <tjyrinki(a)suse.com> --- I've re-added the patches and testet locally. Request https://build.opensuse.org/request/show/897101 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186668] X11:Utilities/workrave: New version available
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186668 https://bugzilla.suse.com/show_bug.cgi?id=1186668#c2 --- Comment #2 from Timo Jyrinki <tjyrinki(a)suse.com> --- Unfortunately 1.10.45 was before the GNOME Shell crasher fix and the GNOME 40 compatibility fix, so the update simply just broke workrave for now. 1.10.46 is not released so both of the patches should be put back. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186789] New: [GNOME] The right arrow button doesn't work by default when selecting folders.
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186789 Bug ID: 1186789 Summary: [GNOME] The right arrow button doesn't work by default when selecting folders. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: yfjiang(a)suse.com, zcjia(a)suse.com Found By: --- Blocker: --- openSUSE Tumbleweed 20210601 Steps: 1. Boot to desktop 2. Launch nautilus and then press the right arrow button Actual Result: No folder is selected by pressing the right arrow button no matter how many times you pressed. Additional Info: If you press the down arrow button and then the right arrow button would work. If you click the "Home" in the left panel of nautilus, the right arrow button would work. Expected Result: There should be corresponding folder selected when you pressing the right arrow button. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186621] YaST2 crashes writing network information
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186621 https://bugzilla.suse.com/show_bug.cgi?id=1186621#c7 Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- Hi Axel, I have checked the changes in the yast2-network module, and I do not see anything relevant. We did some tests and we were unable to reproduce the problem. Let's close the report by now and, please, feel free to open if you detect this problem again. Thanks for reporting! Regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185232] something has gone seriously wrong: shim_init() - system does not boot anymore after installing today's updates
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1185232 https://bugzilla.suse.com/show_bug.cgi?id=1185232#c54 --- Comment #54 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Ren� Neumaier from comment #52) > (In reply to Gary Ching-Pang Lin from comment #51) > > Could you try this to dump Boot2* and Boot3*? > > > > # for opt in /sys/firmware/efi/efivars/Boot[23]*; do echo $opt; hexdump -C > > $opt; done > > > > Boot0000 is created by openSUSE. I'm interesting in the boot options created > > by the firmware. Maybe they contain some OptionalData that shim 15.4 doesn't > > like. > > linux:~ # ls-l /sys/firmware/efi/efivars/Boot* > -rw-r--r-- 1 root root 146 Jun 1 10:36 > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c --->8--- > > linux:~ # for opt in /sys/firmware/efi/efivars/Boot[23]*; do echo $opt; > hexdump -C $opt; done > /sys/firmware/efi/efivars/Boot2001-8be4df61-93ca-11d2-aa0d-00e098032b8c > 00000000 07 00 00 00 01 00 00 00 04 00 45 00 46 00 49 00 |..........E.F.I.| > 00000010 20 00 55 00 53 00 42 00 20 00 44 00 65 00 76 00 | .U.S.B. .D.e.v.| > 00000020 69 00 63 00 65 00 00 00 7f ff 04 00 52 43 |i.c.e.......RC| > 0000002e The boot option looks a bit odd since the device path only contains the EndNode (7f ff 04 00), but it seems that shim could handle this case. I need to investigate this further. (In reply to Ren� Neumaier from comment #53) > Created attachment 849874 [details] > Verification failed - 0x1A - security violation > > Thanks for your patience. > > (In reply to Gary Ching-Pang Lin from comment #48) > > Could you try comment#27 and see if you can reproduce this bug? It'd be > > helpful to have a reliable system to reproduce the bug and verify the > > possible fix. > > I followed your tutorial from comment#27. But I felt a bit lost with point 4 > (reproduce error / collecting of information). > Which information or logfile would be helpful? > I was able to boot the "debug shim" but I got the following error: > Verification failed: (0x1A) Security Violation > After pressing 'enter' I got the messages from the attached screenshot. As I > chooses continue, the system seems to boot with the "debug shim". > Did you copy grub.efi to the debug folder? I expected shim failed early as comment#0 so the steps doesn't copy grub.efi to the debug folder. If you did, it's understandable because Leap 15.3 uses grub.efi from SLE15-SP3 directly, so shim-opensuse.efi couldn't verify it with the built-in openSUSE CA. Anyway it seems your case is different from comment#0. > After setup and before reboot: > localhost:/boot/efi/EFI/debug # efibootmgr > BootNext: 0001 > BootCurrent: 0000 > Timeout: 0 seconds > BootOrder: 0000,2001,2002,2003,3007,300E,300F,3010,3012 > Boot0000* opensuse-secureboot > Boot0001* shim debug > Boot2001* EFI USB Device > Boot2002* EFI DVD/CDROM > Boot2003* EFI Network > Boot3007* Drive0 NVMe: > Boot300E* NETWORK: > Boot300F* USB HDD: > Boot3010* USB CD/DVD: > Boot3012* Thunderbolt HDD: > > With "debug shim": > localhost:/var/log # efibootmgr > BootCurrent: 0001 > Timeout: 0 seconds > BootOrder: 0000,2001,2002,2003,3007,300E,300F,3010,3012 > Boot0000* opensuse-secureboot > Boot0001* shim debug > Boot2001* EFI USB Device > Boot2002* EFI DVD/CDROM > Boot2003* EFI Network > Boot3007* Drive0 NVMe: > Boot300E* NETWORK: > Boot300F* USB HDD: > Boot3010* USB CD/DVD: > Boot3012* Thunderbolt HDD: > > I felt I have a quite knowledge gap here (I am a bit unfamiliar with > secureboot). But the message "MokManager.efi - Not Found" made me skeptical > and led to the following command: > > localhost:/var/log # mokutil --sb-state > SecureBoot disabled > Platform is in Setup Mode > > No difference rather I boot with Boot0000 - opensuse-secureboot (as regular) > or with Boot0001 - shim debug. > That means SecureBoot doesn't work regardless of my BIOS setting? > Because in the BIOS/UEFI system it is truly activated. Actually I'm surprised that the debug shim showed "Verification failed" since it only happened when Secure Boot is on. However, the debug shim.efi is not signed by UEFI CA, the firmware is supposed to reject it when Secure Boot is on. What's more interesting is that mokutil found your system in Setup Mode which means no key enrolled for Secure Boot in the firmware, and this basically means Secure Boot is off. You can check the system status with the following commands: # hexdump -C /sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c # hexdump -C /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c For a Secure Boot enabled UEFI firmware, SetupMode should be "06 00 00 00 00" and SecureBoot should be "06 00 00 00 01". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186080] New: 'borg mount' fails due to missing python3-llfuse package
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186080 Bug ID: 1186080 Summary: 'borg mount' fails due to missing python3-llfuse package 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: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 'borg mount' fails with error: borg mount not available: loading FUSE support failed [ImportError: No module named 'llfuse'] This is caused by the python3-llfuse package (recommended by package borgbackup) not being available at all on TW: $zypper se python3-llfuse Loading repository data... Reading installed packages... No matching items found. How come package python3-llfuse has disappeared ? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1186083] [Build 20210513] remmina: unable to connect
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1186083 https://bugzilla.suse.com/show_bug.cgi?id=1186083#c2 --- Comment #2 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: desktopapps-remote-desktop-xrdp-client2@64bit_virtio https://openqa.opensuse.org/tests/1764236 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182125] [Build 20210207] no yast2 online update icon in control center
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1182125 https://bugzilla.suse.com/show_bug.cgi?id=1182125#c13 --- Comment #13 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: yast2_gui https://openqa.opensuse.org/tests/1764196 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1167589] [Build 20200322] yast2 nis and nfs clients do not find server on the same lan
by bugzilla_noreply＠suse.com 03 Jun '21

03 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1167589 https://bugzilla.suse.com/show_bug.cgi?id=1167589#c25 --- Comment #25 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: nis_client https://openqa.opensuse.org/tests/1764857 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0