August 2022 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1200457] New: iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200457 Bug ID: 1200457 Summary: iscsi.service cannot start at microos Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running microOS 20220611 with open-iscsi-2.1.7-90.1.x86_64. When I try to start iscsi.service the following error appears: Jun 12 19:16:09 localhost.localdomain systemd[1]: Starting Login and scanning of iSCSI devices... Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1018]: iscsiadm: Could not get list of targets from firmware. (err 21) Jun 12 19:16:09 localhost.localdomain systemd[1]: Finished Login and scanning of iSCSI devices. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1167780] New: MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1167780 Bug ID: 1167780 Summary: MicroOS images don't update grub if booted without EFI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- The .qcow2 images are meant to work fine on systems with EFI (optionally secure boot) and without, so they have both i386-pc and x86_64-efi targets of grub2 installed by kiwi during image building. Kiwi sets LOADER_TYPE="grub2-efi" for this. When booting the image without EFI though, this is not changed by anything and so update-bootloader only manages the x86_64-efi target of grub2. As the grub.cfg file is in the same location, there aren't any immediate issues, but it means that grub is never updated in those deployments. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1202875] New: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202875 Bug ID: 1202875 Summary: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: michal.vyskocil(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- packagekitd won't start on my MicroOS GNOME Desktop and produces error messages in Gnome Software. NAME="openSUSE Tumbleweed" # VERSION="20220827" packagekitd[28073]: what(): Can't load plugin "txnupd.so": Can't load shared library "/usr/lib64/libdnf/plugins/txnupd.so": /usr/lib64/libdnf/plugins/txnupd.so: undefined symbol: _ZN19TransactionalUpdate11Transaction4initENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE It looks like this commit https://github.com/openSUSE/transactional-update/commit/2a2117d15a87dfbedea… broke the ABI. Not sure why BuildService haven't solved the problem by rebuilding the package. What libtukit.so.4 provides (I run my setup inside distrobox, hence /run/host paths poiting to the "host" - the MicroOS itself) objdump -C -T /run/host/lib64/libtukit.so.4.0.0 | grep 'Transaction::init' 0000000000020010 g DF .text 0000000000000c7f Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >) What txnupd requires objdump -C -T /run/host/lib64/libdnf/plugins/txnupd.so | grep 'Transaction::init' 0000000000000000 DF *UND* 0000000000000000 Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) $ rpm -qf /lib64/libdnf/plugins/txnupd.so /lib64/libtukit.so.4.0.0 libdnf-plugin-txnupd-0.1.3-1.10.x86_64 libtukit4-4.0.1-1.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1202290] New: Unable to update system using GNOME Software
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202290 Bug ID: 1202290 Summary: Unable to update system using GNOME Software Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: songchuan.kang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0 Build Identifier: In GNOME Software, when clicking "Restart & Update" button in updates tab, an error messages pops up saying: > Unable to update "System Updates": Failed to create symlink: Read-only file system This is due to GNOME Software trying to call pk-trigger-offline-update which creates /system-update. However, this won't succeed because of the read-only file system. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1201566] New: setroubleshoot packages in repositories bundle a broken version of setroubleshootd
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201566 Bug ID: 1201566 Summary: setroubleshoot packages in repositories bundle a broken version of setroubleshootd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: systemtool.exe(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The setroubleshoot-server 3.3.26 package bundles a version of setroubleshootd that requires a python2 module but is executed with python3 (as the shebang in the executable is /usr/bin/python3). The issue has been resolved in later versions. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202983] New: simple-framebuffer error -16 on raspberry pi 4 using latest openSUSE MicroOS RaspberryPi image
by bugzilla_noreply＠suse.com 27 Nov '22

27 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202983 Bug ID: 1202983 Summary: simple-framebuffer error -16 on raspberry pi 4 using latest openSUSE MicroOS RaspberryPi image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: proprietaer1(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I wanted to test MicroOS on my RaspberryPi 4. Unfortunately, the display output stopped during the boot process, with the error: simple-framebuffer.0: [drm] ERROR could not acquire memory range [mem 0x3e3cf000-0x3ebb7fff flags 0x200]: error -16 Steps to reproduce: 1.Download latest MicroOS for RaspberryPi & flash it to sd card. 2.Try to boot the system -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1195878] New: [Build 20220211] openQA test fails in disk_boot
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195878 Bug ID: 1195878 Summary: [Build 20220211] openQA test fails in disk_boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2186742/modules/disk _boot/steps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos@64bit fails in [disk_boot](https://openqa.opensuse.org/tests/2186742/modules/disk_boot/step… Feb 13 08:01:56.395743 localhost dracut-initqueue[502]: /sbin/ifup: line 135: dhclient: command not found ## Test suite description ## Reproducible Fails since (at least) Build [20220211](https://openqa.opensuse.org/tests/2186317) ## Expected result Last good: [20220210](https://openqa.opensuse.org/tests/2184227) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202852] New: Installation of MicroOS Desktop KDE Fails on Latest image.
by bugzilla_noreply＠suse.com 28 Aug '22

28 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202852 Bug ID: 1202852 Summary: Installation of MicroOS Desktop KDE Fails on Latest image. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861152 --> https://bugzilla.suse.com/attachment.cgi?id=861152&action=edit Screenshot of Error in Question When installing MicroOS Desktop KDE from current DVD image, the installation fails, with the error in the attached screenshot. Possibly connected to: https://bugzilla.suse.com/show_bug.cgi?id=1202067 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1186158] [SELinux] blocking podman socket access to /var/run/podman/podman.sock
by bugzilla_noreply＠suse.com 24 Aug '22

24 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1186158 https://bugzilla.suse.com/show_bug.cgi?id=1186158#c15 Gayane Osipyan <gayane.osipyan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #15 from Gayane Osipyan <gayane.osipyan(a)suse.com> --- Please reopen if needed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 16 Aug '22

16 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c20 --- Comment #20 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Richard Brown from comment #19) > PR merged, bug fixed Thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186158] [SELinux] blocking podman socket access to /var/run/podman/podman.sock
by bugzilla_noreply＠suse.com 15 Aug '22

15 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1186158 Robert Simai <robert.simai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.simai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202126] New: GParted doesn't work because pkexec doesn't exist
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202126 Bug ID: 1202126 Summary: GParted doesn't work because pkexec doesn't exist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: khanich.opensource(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- So, as it turns out, since pkexec was split out of the polkit package, some software like GParted breaks, because they don't depend on it. It is not the only one, but a more major one since it doesn't even start without it. Grsync for example can't run as the super user (a setting under advanced) either. Installing the pkexec package helped in both cases tho. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200457] iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200457 https://bugzilla.suse.com/show_bug.cgi?id=1200457#c4 --- Comment #4 from Matwey Kornilov <matwey.kornilov(a)gmail.com> --- You are right, I see the following: overlay on /etc type overlay (rw,relatime,seclabel,lowerdir=/sysroot/var/lib/overlay/3/etc:/sysroot/etc,upperdir=/sysroot/var/lib/overlay/4/etc,workdir=/sysroot/var/lib/overlay/4/work-etc) However, iscsi doesn't start. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200457] iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200457 https://bugzilla.suse.com/show_bug.cgi?id=1200457#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- /etc is mounted writeable already in the initrd and iscsi.service runs after systemd-remount-fs.service This should work, but could be that there are still some races somewhere... Or it's bsc#1156421 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200457] iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200457 https://bugzilla.suse.com/show_bug.cgi?id=1200457#c2 Matwey Kornilov <matwey.kornilov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(matwey.kornilov@g | |mail.com) | --- Comment #2 from Matwey Kornilov <matwey.kornilov(a)gmail.com> --- /etc/iscsi exists It still doesn't work with open-iscsi-2.1.7-92.1.x86_64 I think that the reason is that /etc is read-only in microOS and iscsi wants to create new file lock.write -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183582] New: transactional server role has very inconsistent package selection (TW, SLE, Leap)
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1183582 Bug ID: 1183582 Summary: transactional server role has very inconsistent package selection (TW, SLE, Leap) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Selecting the transactional server role results in a very different selection of patterns and packages. On Tumbleweed: https://openqa.opensuse.org/tests/1667896#step/disable_grub_timeout/13 Documentation, Minimal Base, Enhanced Base, AppArmor, YaST Base, Software Management, Minimal Appliance Base On SLE 15 SP3: https://openqa.suse.de/tests/5670408#step/disable_grub_timeout/14 Minimal Base, Enhanced Base, AppArmor, 32-Bit Runtime Environment On Leap 15.3: https://openqa.opensuse.org/tests/1667171#step/disable_grub_timeout/13 Minimal Base, Minimal Appliance Base -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1185463] kdump fails on microos
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1185463 https://bugzilla.suse.com/show_bug.cgi?id=1185463#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Apparently fixed https://github.com/yast/skelcd-control-MicroOS/pull/56 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185801] Kubelet/CRI-O/CA-Advisor is not reporting memory
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1185801 https://bugzilla.suse.com/show_bug.cgi?id=1185801#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- Memory cgroup is now enabled -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186125] MicroOS snapshot 20210515 CoreDNS fails to resolve external addresses
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1186125 https://bugzilla.suse.com/show_bug.cgi?id=1186125#c24 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #24 from Richard Brown <rbrown(a)suse.com> --- Was fixed, forgot to close the bug -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187897] Running kubelet1.21 on MicroOS Kubic crashes with Bus error
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1187897 https://bugzilla.suse.com/show_bug.cgi?id=1187897#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Assumed fixed now Kubic no longer exists -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193588] MicroOS will not complete boot on Raspberry Pi 3 (and more)
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1193588 https://bugzilla.suse.com/show_bug.cgi?id=1193588#c4 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- Can't reproduce the issue and have enough other bugs related to MicroOS on Pi 3's to suggest others don't have this issue also -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200182] systemd-resolved cannot bind port 53
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200182 https://bugzilla.suse.com/show_bug.cgi?id=1200182#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Component|MicroOS |Security Assignee|kubic-bugs(a)opensuse.org |security-team(a)suse.de --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- SELinux issue, assigning to correct componant -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200457] iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200457 https://bugzilla.suse.com/show_bug.cgi?id=1200457#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matwey.kornilov(a)gmail.com, | |rbrown(a)suse.com Flags| |needinfo?(matwey.kornilov@g | |mail.com) --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- So, does /etc/iscsi exist? Does it work if you create it? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201049] Make MicroOS GNOME Desktop RC/Released
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201049 https://bugzilla.suse.com/show_bug.cgi?id=1201049#c1 --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- MOD GNOME is at RC phase Blockers to Release at time of comment - https://bugzilla.suse.com/show_bug.cgi?id=1202290 - openQA Testing -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1196547] New: MicroOS Desktop GNOME system role doesn't preinstall language subpackages
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1196547 Bug ID: 1196547 Summary: MicroOS Desktop GNOME system role doesn't preinstall language subpackages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Follow-up of https://github.com/yast/skelcd-control-MicroOS/pull/51 Installing MicroOS Desktop (GNOME system role) doesn't install the language subpackages for the select language on the installer. Languages subpackages are currently handled as soft dependencies, which doesn't mix well with MicroOS relying only on requires. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c19 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #19 from Richard Brown <rbrown(a)suse.com> --- PR merged, bug fixed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c18 --- Comment #18 from Richard Brown <rbrown(a)suse.com> --- https://github.com/yast/skelcd-control-MicroOS/pull/57 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c17 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rbrown(a)suse.com) | --- Comment #17 from Richard Brown <rbrown(a)suse.com> --- (In reply to David Diaz from comment #16) > (In reply to Jan Zerebecki from comment #13) > > I don't think anyone reachable via microos-bugs knows enough about yast or > > the skelcd control file. CC-ing the relevant bugowner instead: > > > osc bugowner -A yast2-caasp > > Defined in project: YaST:Head > > bugowner of yast2-caasp : > > yast2-maintainers > > > osc bugowner -A skelcd-control-MicroOS > > Defined in project: YaST:Head > > bugowner of skelcd-control-MicroOS : > > yast2-maintainers > > Probably by accident because of the module name. > > Asking Richard Brown, who created and updated the skelcd. See output from > git blame > https://github.com/yast/skelcd-control-MicroOS/blame/ > 509289c27796cbbdaa7cbfad8b93fdcd618469cf/control/control.MicroOS.xml#L257 Hi all, The problem we face with the MicroOS Desktop is as follows - We _cannot_ have YaST produce a user account, because we need the gnome initial setup tool to do that - YaST does so on regular MicroOS as part of the inst_user_first module - Therefore the inst_user_first module must not be run when installing the MicroOS Desktop, which is why it was removed - When removing inst_user_first I didn't add back the inst_microos_role we use elsewhere I don't really care for the RPi as a desktop platform but I'll fix this as it will make the Desktop more in sync with what we have on regular MicroOS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202290] Unable to update system using GNOME Software in MicroOS Desktop
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202290 https://bugzilla.suse.com/show_bug.cgi?id=1202290#c4 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- (In reply to Jonathan Kang from comment #3) > (In reply to Thorsten Kukuk from comment #2) > > (In reply to Jonathan Kang from comment #1) > > > Created attachment 860723 [details] > > > Failed offline update in GNOME Software > > > > It doesn't make any sense to use "GNOME offline update", since > > transactional-update is doing an offline update itself in a much better and > > more robust way. > > No idea if this GNOME functionality can be disabled in the MicroOS Gnome > > Desktop, but should be. > > Or integrated with the way how transactional-update works so that users have > a > graphical interface to update MicroOS Desktop? it could, that was attempted with the Packagekit/microdnf backend It failed, it was not reliable enough/at all The plan for the MicroOS Desktop is to disable/hide that function in GNOME software and rely on the "traditional" transactional-update automatic timers, with some kind of notification showing when a reboot is needed to activate an automatically installed update -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202290] Unable to update system using GNOME Software in MicroOS Desktop
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202290 https://bugzilla.suse.com/show_bug.cgi?id=1202290#c3 --- Comment #3 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Thorsten Kukuk from comment #2) > (In reply to Jonathan Kang from comment #1) > > Created attachment 860723 [details] > > Failed offline update in GNOME Software > > It doesn't make any sense to use "GNOME offline update", since > transactional-update is doing an offline update itself in a much better and > more robust way. > No idea if this GNOME functionality can be disabled in the MicroOS Gnome > Desktop, but should be. Or integrated with the way how transactional-update works so that users have a graphical interface to update MicroOS Desktop? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c16 David Diaz <dgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(yast2-maintainers |needinfo?(rbrown(a)suse.com) |(a)suse.de) | --- Comment #16 from David Diaz <dgonzalez(a)suse.com> --- (In reply to Jan Zerebecki from comment #13) > I don't think anyone reachable via microos-bugs knows enough about yast or > the skelcd control file. CC-ing the relevant bugowner instead: > > osc bugowner -A yast2-caasp > Defined in project: YaST:Head > bugowner of yast2-caasp : > yast2-maintainers > > osc bugowner -A skelcd-control-MicroOS > Defined in project: YaST:Head > bugowner of skelcd-control-MicroOS : > yast2-maintainers Probably by accident because of the module name. Asking Richard Brown, who created and updated the skelcd. See output from git blame https://github.com/yast/skelcd-control-MicroOS/blame/509289c27796cbbdaa7cbf… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202287] Cannot add a printer in CUPS on MicroOS
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

1 0

[Bug 1202290] Unable to update system using GNOME Software in MicroOS Desktop
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202290 https://bugzilla.suse.com/show_bug.cgi?id=1202290#c2 --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Jonathan Kang from comment #1) > Created attachment 860723 [details] > Failed offline update in GNOME Software It doesn't make any sense to use "GNOME offline update", since transactional-update is doing an offline update itself in a much better and more robust way. No idea if this GNOME functionality can be disabled in the MicroOS Gnome Desktop, but should be. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202287] New: Cannot add a printer in CUPS
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202287 Bug ID: 1202287 Summary: Cannot add a printer in CUPS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: caleb(a)candj.us QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0 Build Identifier: CUPS appears to be unusable on MicroOS Reproducible: Always Steps to Reproduce: 1.Install cups and associated packages with transactional-update, reboot 2.Allow remote access to web interface by editing the config 3.enable and start cups service 4.From web interface try to add printer or find printer 5.Receive error: Request Entity Too Large -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c15 Axel Braun <axel.braun(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(axel.braun(a)gmx.de | |) | --- Comment #15 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Thorsten Kukuk from comment #14) > (In reply to Jan Zerebecki from comment #13) > > I don't think anyone reachable via microos-bugs knows enough about yast or > > the skelcd control file. CC-ing the relevant bugowner instead: > > That's per se not a YaST problem, but it looks like the MicroOS Desktop > system role was choosen? Axel, would be nice if you would explain what you > did install and not let others guess or make wrong assumptions. Because it > looks like this is not "MicroOs" as you claims but "MicroOS Desktop"? Thats right, as the headline says, I have chosen MicroOS Desktop for installation. As the Raspi does not have a Real-time-Clock, its date and time settings are inaccurate unless it gets a date/time from NTP...but that is not active by default > Richard, who is responsible for the GNOME Desktop case to setup the time > correct? > > (In reply to Axel Braun from comment #5) > > Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well. > > How to proceed? > > This is not correct or a bug in the Desktop selection, MicroOS comes with > save_y2logs. It's an extra package for that reason. ..but it is not installed by default.... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c14 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Flags| |needinfo?(axel.braun(a)gmx.de | |) --- Comment #14 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Jan Zerebecki from comment #13) > I don't think anyone reachable via microos-bugs knows enough about yast or > the skelcd control file. CC-ing the relevant bugowner instead: That's per se not a YaST problem, but it looks like the MicroOS Desktop system role was choosen? Axel, would be nice if you would explain what you did install and not let others guess or make wrong assumptions. Because it looks like this is not "MicroOs" as you claims but "MicroOS Desktop"? Richard, who is responsible for the GNOME Desktop case to setup the time correct? (In reply to Axel Braun from comment #5) > Problem is that MicroOS comes w/o YaST, and by this w/o save_y2logs as well. > How to proceed? This is not correct or a bug in the Desktop selection, MicroOS comes with save_y2logs. It's an extra package for that reason. Richard? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c13 Jan Zerebecki <jzerebecki(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzerebecki(a)suse.com, | |yast2-maintainers(a)suse.de Flags|needinfo?(microos-bugs@suse |needinfo?(yast2-maintainers |.de) |(a)suse.de) --- Comment #13 from Jan Zerebecki <jzerebecki(a)suse.com> --- I don't think anyone reachable via microos-bugs knows enough about yast or the skelcd control file. CC-ing the relevant bugowner instead: > osc bugowner -A yast2-caasp Defined in project: YaST:Head bugowner of yast2-caasp : yast2-maintainers > osc bugowner -A skelcd-control-MicroOS Defined in project: YaST:Head bugowner of skelcd-control-MicroOS : yast2-maintainers -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202000] [Build 20220729] openQA test fails in transactional_update: read-only file system
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202000 https://bugzilla.suse.com/show_bug.cgi?id=1202000#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Fabian Vogt from comment #2) > Not sure what to do about this. Make the ordering dependency more extreme by > having boot-writable.mount Requires=systemd-mount-fs.service? Next try, closer to the root cause which is systemd-remount-fs.service: https://build.opensuse.org/request/show/993307 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202000] [Build 20220729] openQA test fails in transactional_update: read-only file system
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202000 https://bugzilla.suse.com/show_bug.cgi?id=1202000#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- Didn't help, openQA is still unhappy. The journal shows: Aug 05 05:37:34.280907 susetest systemd[1]: Starting Remount Root and Kernel File Systems... ... Aug 05 05:37:34.281179 susetest systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Aug 05 05:37:34.281193 susetest systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. Aug 05 05:37:34.281207 susetest systemd[1]: Failed to start Remount Root and Kernel File Systems. ... Aug 05 05:37:34.247313 susetest systemd-remount-fs[444]: /usr/bin/mount for / exited with exit status 32. Aug 05 05:37:34.282334 susetest apparmor.systemd[435]: Restarting AppArmor Aug 05 05:37:34.282334 susetest apparmor.systemd[435]: Reloading AppArmor profiles Aug 05 05:37:34.283671 susetest systemd-remount-fs[448]: mount: /: mount point is busy. ... Aug 05 05:37:34.984770 susetest systemd[1]: Mounting /boot/writable... ... Aug 05 05:37:35.246908 susetest systemd[1]: Mounted /boot/writable. ... Aug 05 05:37:35.331954 susetest systemd[1]: Starting Remount Root and Kernel File Systems... ... Aug 05 05:37:35.500468 susetest systemd[1]: Finished Remount Root and Kernel File Systems. The first attempt to systemd-remount-fs.service fails because something has a file opened in RW mode, so it's attempted again later, when it's already too late. Not sure what to do about this. Make the ordering dependency more extreme by having boot-writable.mount Requires=systemd-mount-fs.service? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c12 --- Comment #12 from David Diaz <dgonzalez(a)suse.com> --- (In reply to Knut Alejandro Anderssen Gonz�lez from comment #9) > > The desktop role executes the gnome-initial-setup for configuring the > timezone. See comment #10 and comment #11 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c11 --- Comment #11 from David Diaz <dgonzalez(a)suse.com> --- Created attachment 860632 --> https://bugzilla.suse.com/attachment.cgi?id=860632&action=edit Status of NTP service As it can be seen, none NTP service is active after gnome-initial-setup despite it shown its timezone page. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c10 --- Comment #10 from David Diaz <dgonzalez(a)suse.com> --- Created attachment 860631 --> https://bugzilla.suse.com/attachment.cgi?id=860631&action=edit gnome-initial-setup timezone page During the gnome-initial-setup, a timezone selector is displayed. BTW, it seems to be a little buggy. When I typed "Canary" it allows me to select "Gran Canaria, Canary Islands" but it selects Madrid timezone instead. Anyway, something to report in another bug tracker ;) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202067] MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202067 https://bugzilla.suse.com/show_bug.cgi?id=1202067#c9 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |kanderssen(a)suse.com, | |microos-bugs(a)suse.de Component|Installation |MicroOS Assignee|yast2-maintainers(a)suse.de |kubic-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Flags| |needinfo?(microos-bugs@suse | |.de) --- Comment #9 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- It is related to https://bugzilla.suse.com/show_bug.cgi?id=1135342. Basically the NTP configuration is not written at the end of the installation because it is not modified and no one is taking care of enabling chrony or systemd-timesync. When the micro_os_role is selected it runs an additional dialog (see https://github.com/yast/skelcd-control-MicroOS/blob/master/control/control.…) for configuring the ntp-servers and therefore the configuration is modified and written at the end of the installation but this is not the case of the micro_os_gnome_desktop_role. The current clients are in caasp module (see https://github.com/yast/yast-caasp/tree/master/src/clients) The desktop role executes the gnome-initial-setup for configuring the timezone. Assigning the bug to microos-bugs. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202122] New: MicroOS Snapshot20220801 KDE System Settings / Audio Test produces File or data not found error
by bugzilla_noreply＠suse.com 04 Aug '22

04 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202122 Bug ID: 1202122 Summary: MicroOS Snapshot20220801 KDE System Settings / Audio Test produces File or data not found error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: jared.hudson(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed MicroOS Snapshot20220801 as a KVM VM and picked the KDE Desktop installation pattern. When opening KDE's System Settings, clicking Audio, clicking Test, clicking "Front Left" it produces the error: Error trying to play a test sound. The system said: "File or data not found" Running the following and rebooting supplied the file that was missing: sudo transactional-update pkg install sound-theme-freedesktop -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202147] New: tukit D-Bus API can't parse fields with comma
by bugzilla_noreply＠suse.com 04 Aug '22

04 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202147 Bug ID: 1202147 Summary: tukit D-Bus API can't parse fields with comma Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using the Snapshot.List D-Bus API call from the prerelease version of transactional-update (4.0.0~rc4) reveals that the interface is designed improperly: The queried fields must not contain any comma, otherwise the returned string can't be parsed correctly any more. Example: busctl call org.opensuse.tukit /org/opensuse/tukit/Snapshot org.opensuse.tukit.Snapshot List "s" "number,description,default" would return a list such as "2334,Hello, this is a test!,no" -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202120] New: Can't update my MicroOS as shim post-install script fails with "mokutil: unrecognized option '--set-sbat-policy'"
by bugzilla_noreply＠suse.com 04 Aug '22

04 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202120 Bug ID: 1202120 Summary: Can't update my MicroOS as shim post-install script fails with "mokutil: unrecognized option '--set-sbat-policy'" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fx.houard(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 Safari/537.36 Build Identifier: I try to upgrade my microOS with "transactional-update dup", and it fails every time with code 107. Apparently the problem is that shim post-install script try to launch mokutil with the option '--set-sbat-policy' which is not available with my installation. "mokutil: unrecognized option '--set-sbat-policy'" My version of mokutil is : S | Name | Type | Version | Arch | Repository ---+---------+---------+-----------+---------+------------------------ i+ | mokutil | package | 0.5.0-1.5 | aarch64 | openSUSE-Tumbleweed-Oss I think it is the latest The upgrade is openSUSE MicroOS 20220207-0 -> 20220731-0 BTW I get the same error when trying to upgrade the shim package only (transactional-update pkg update shim). My version of shim is 15.4-7.4, I can't update it to the suggested version (15.6-3.1) Reproducible: Always Steps to Reproduce: 1.transactional-update pkg update shim or transactional-update dup 2. 3. Actual Results: Retrieving: shim-15.6-3.1.aarch64.rpm [.done (1.5 KiB/s)] (1/1) Installing: shim-15.6-3.1.aarch64 [........ mokutil: unrecognized option '--set-sbat-policy' Usage: mokutil OPTIONS [ARGS...] Options: --help Show help --list-enrolled List the enrolled keys --list-new List the keys to be enrolled --list-delete List the keys to be deleted --import <der file...> Import keys --delete <der file...> Delete specific keys --revoke-import Revoke the import request --revoke-delete Revoke the delete request --export Export keys to files --password Set MOK password --clear-password Clear MOK password --disable-validation Disable signature validation --enable-validation Enable signature validation --sb-state Show SecureBoot State --test-key <der file> Test if the key is enrolled or not --reset Reset MOK list --generate-hash[=password] Generate the password hash --ignore-db Ignore DB for validation --use-db Use DB for validation --import-hash <hash> Import a hash into MOK or MOKX --delete-hash <hash> Delete a hash in MOK or MOKX --set-verbosity <true/false> Set the verbosity bit for shim --pk List the keys in PK --kek List the keys in KEK --db List the keys in db --dbx List the keys in dbx --timeout <-1,0..0x7fff> Set the timeout for MOK prompt --sbat List the entries in SBAT Supplimentary Options: --hash-file <hash file> Use the specific password hash --root-pw Use the root password --mokx Manipulate the MOK blacklist --ca-check Check if CA of the key is enrolled/blocked --ignore-keyring Don't check if the key is the kernel keyring warning: %post(shim-15.6-3.1.aarch64) scriptlet failed, exit status 255 ........done] Executing %posttrans script 'shim-15.6-3.1.aarch64.rpm' [....done] 2022-08-03 21:19:37 Application returned with exit status 107. Expected Results: Exit with status 0 :) My system is a raspberry pi 4b. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202121] New: MicroOS Snapshot20220801 kwrite missing KDE-specific features and icons when ran from Toolbox or Flatpak
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202121 Bug ID: 1202121 Summary: MicroOS Snapshot20220801 kwrite missing KDE-specific features and icons when ran from Toolbox or Flatpak Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: jared.hudson(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860587 --> http://bugzilla.opensuse.org/attachment.cgi?id=860587&action=edit Comparing kwrite in toolbox vs kwrite on MicroOS host I installed MicroOS Snapshot20220801 as a KVM VM and picked the KDE Desktop installation pattern. kwrite was not installed by default so I went looking for what my options are. I could run sudo transactional-update pkg install kwrite but that would require a reboot which seems quite extreme just to get an editor. I referred to the documentation https://en.opensuse.org/Portal:MicroOS/Desktop#Installation:_KDE which recommends flatpak or Toolbox or Distrbox. I ran toolbox enter. This required downloading several container blobs which could be an issue for air-gapped systems or people with constrained bandwidth. This is a negative compared to traditional Leap or even Tumbleweed ISO which includes most required packaged on the ISO. I ran sudo zypper ref && sudo zypper dup - No additional packages downloaded. I ran sudo zypper install adwaita-icon-theme xorg-x11-fonts libX11-xcb1 gsettings-desktop-schemas gdk-pixbuf-query-loaders which required installing 17 packages. (from https://en.opensuse.org/Portal:MicroOS/Desktop#Installation:_KDE) I ran sudo gdk-pixbuf-query-loaders-64 --update-cache as instructed from https://en.opensuse.org/Portal:MicroOS/Desktop#Installation:_KDE which produced the error "Failed to create file ��/usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache.3JKAQ1��: No such file or directory" /usr/lib64/gdk-pixbuf-2.0 is not included in the "toolbox enter" container. I then ran sudo zypper -n in kwrite which wanted to install 177 new packages. All of those packages were already installed on my MicroOS host. Re-downloading these packages wastes disk space and bandwidth. Once done I ran kwrite. It doesn't look or behave like a normal KDE Kwrite does from Leap, Tumbleweed or even if I had installed Kwrite in the MicroOS host and rebooted. Here's a list of differences: There are no icons for menu items. I'll attach a screenshot illustrating the difference between toolbox vs MicroOS host version. I did eventually install on the host and reboot in order to write this bug report and compare/contrast differences. The open dialog is missing KDE features. I'll attach screenshot to illustrate. On the left of the Open Dialog there's only Computer and jhhudso, it looks like a KDE application from several years ago. Whereas a modern KDE application has a set of "Places" like Home, Desktop, Documents, Downloads. It also normally has a set of Devices such as your disk, USB devices plugged, etc. The toolbox version of kwrite is missing all of this. I have no way to mount or unmount a USB stick via the Open dialog of the toolbox kwrite. The Kwrite Settings/Configure menu is missing icons above the words Appearance, Color Themes, Editing and Open/Save. The Save/Save As dialog is missing the KDE ability to save to a Network share. When Kwrite is run from the host instead of toolbox, it has the ability to utilize Network resources such as Bluetooth, MTP Devices and Shared Folders (SMB). You can save to a URL in the host-based version such as smb://192.168.1.7/username/ but that functionality is missing from toolbox version. The toolbox version uses a lot more memory than the host based version. As reported by pmap -X, the toolbox version uses 133 MiB (PSS) out of 138 MiB (RSS). Whereas the host version, uses only 33 MiB (PSS) out of 122 MiB (RSS). Most libraries kwrite depends on are already loaded in memory. To try flatpak I ran flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo flatpak search kwrite flatpak install kwrite It gives the error: F: An error was encountered searching remote ��flathub�� for ��kwrite��: Unable to load summary from remote flathub: GPG verification enabled, but no summary found (check that the configured URL in remote config is correct) Found ref ��app/org.kde.kwrite/x86_64/stable�� in remote ��flathub�� (system). Use this ref? [Y/n]: y After installing I ran with flatpak run org.kde.kwrite. Visually the flatpak version looks the same as the host based version which is good. There are icons, theme is correct, Settings/Configure has icons as well. The Host and Flatpak versions are not able to open the Kwrite Handbook, Report Bug Wizard or Donate (options from Help) without being told who handles https. The toolbox version doesn't give a pop-up option of who handles https and only prints to the console "Unable to detect a web browser to launch 'https://docs.kde.org.....' The flatpak version of kwrite uses more memory than the host similar to this issue in the Toolbox. As reported by pmap -X, the flatpak version uses 137 MiB (PSS) out of 218 MiB (RSS). -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1202000] [Build 20220729] openQA test fails in transactional_update: read-only file system
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202000 https://bugzilla.suse.com/show_bug.cgi?id=1202000#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Hopefully fixed with https://github.com/openSUSE/read-only-root-fs/pull/12. -- You are receiving this mail because: You are the assignee for the bug.

1 0