July 2023 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1212959] SelfInstall Image - Failed to create partition table
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212959 https://bugzilla.suse.com/show_bug.cgi?id=1212959#c5 --- Comment #5 from Malcolm Lewis <malcolmlewis(a)linuxmail.org> --- @All, thanks for fixing this issue, will wait for the next snapshot release and re-test to confirm. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212959] New: SelfInstall Image - Failed to create partition table
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212959 Bug ID: 1212959 Summary: SelfInstall Image - Failed to create partition table 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: malcolmlewis(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi The latest SelfInstall Image 20230701; (607aaefe2caf487834659f95e59ee7c2adff4f4c6ae69906c5b2746d3f359dd0 openSUSE-MicroOS.x86_64-SelfInstall.raw.xz) Install fails with the following error with Combustion; dracut [676]: Created symlink /etc/systemd/system/systemd-fsck-root.service -> /dev/null dracut-pre-mount[1070]: Warning! Unable to generate a proper UUID! Creating an improper one as a last dracut-pre-mount[1070]: resort! Windows 7 may crash if you save this partition table! dracut-pre-mount(1073]: /lib/kiwi-partitions-lib.sh: line 25: partprobe: command not found dracut: FATAL: Failed to create partition table dracut: Refusing to continue dracut-pre-mount[1079]: Failed to get properties: Transport endpoint is not connected Screen blanks, no signal! Force power off, then Power On. Install completes, system reboots and arrive at login prompt. Login as root user and / is only 1.3GB and almost full, run transactional-update shell, then run btrfs fi resize max / exit and reboot. All is fine, the combustion scripts have run and everything populated as expected. However due to this I cannot install my Combustion additional packages, this has to be done after the NVMe is resized. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1213704] New: openSUSE-MicroOS.aarch64-16.0.0-Rock64-Build61.54.raw: FATAL: Failed to create partition table
by bugzilla_noreply＠suse.com 27 Jul '23

27 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213704 Bug ID: 1213704 Summary: openSUSE-MicroOS.aarch64-16.0.0-Rock64-Build61.54.raw: FATAL: Failed to create partition table Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 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 Target Milestone: --- Found By: --- Blocker: --- Hello, I am running the lates MicroOS image openSUSE-MicroOS.aarch64-16.0.0-Rock64-Build61.54.raw on Rock64 aarch64 SBC. At the first boot I see the following fatal log: [ OK ] Reached target Initrd Root Device. [ 38.711894] dracut-pre-mount[554]: Created symlink /etc/systemd/system/systemd-fsck-root.service → /dev/null. [ 46.392681] dracut-pre-mount[863]: Warning! Unable to generate a proper UUID! Creating an improper one as a last [ 46.407449] dracut-pre-mount[863]: resort! Windows 7 may crash if you save this partition table! [ 48.527503] dracut-pre-mount[866]: /lib/kiwi-partitions-lib.sh: line 25: partprobe: command not found [ 48.537810][ T536] dracut: FATAL: Failed to create partition table [ 48.538506][ T536] dracut: Refusing to continue [ 48.708785] dracut-pre-mount[871]: Failed to get properties: Transport endpoint is not connected [ 49.103915][ T1] reboot: System halted It seems that the reason is that partprobe is missed from dracut initrd image. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203393] microOS cloud-init (OpenStack variant) fails due to attempting systemd-network over NetworkManager
by bugzilla_noreply＠suse.com 26 Jul '23

26 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1203393 https://bugzilla.suse.com/show_bug.cgi?id=1203393#c19 Aleksandr Zubkov <i(a)verschworer.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i(a)verschworer.ru --- Comment #19 from Aleksandr Zubkov <i(a)verschworer.ru> --- Greetings! in my case I'm using thumbleweed cloudinit qcow2 as a template for my proxmox VMs. After investigating, I found out that there is nothing at all either for the network. A quick solution would be to use virt-customize -a <your_qcow2> --run-command 'zypper in -y wicked' attempt to virt-customize -a <your_qcow2> --run-command 'zypper in -y NetworkManager' don't fix error -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1209716] Add additional packages to enhance GNOME experience for MicroOS Desktop
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

1 0

[Bug 1208869] MicroOS - Urdu Lanuage (Pakistan) Keyboard,Formats, Language and Region Support, Arabic Keyboard (Pakistan) layout support
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1208869 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Patterns Assignee|kubic-bugs(a)opensuse.org |rbrown(a)suse.com Product|openSUSE Tumbleweed |openSUSE Aeon -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210492] Gnome Settings -> Color option is not available in the default install
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

1 0

[Bug 1210710] Including `inxi` in default MicroOS installation
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210710 https://bugzilla.suse.com/show_bug.cgi?id=1210710#c5 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #5 from Richard Brown <rbrown(a)suse.com> --- Assuming fixed by SR#1084824 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210483] RTL8821CE Firmware not installed on MicroOS
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210483 https://bugzilla.suse.com/show_bug.cgi?id=1210483#c4 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- Assuming fixed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212071] New: Aeon: Fingerprint reader not supported out of the box
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212071 Bug ID: 1212071 Summary: Aeon: Fingerprint reader not supported out of the box 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: 0xdopice(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've seen this being discussed briefly in Matrix/Telegram (Telegram link: https://t.me/openSUSE_Aeon/31932) but can't find any "this is how we'll do it", so hence this report. Summary Packages fprintd and fprintd-pam are "missing" in a default install of Aeon. Why would we include it? - Since we install all kernel firmware packages the fingerprint readers are there and ready to be used. The only thing missing is the two above packages. This give the option Fingerprint Login under Settings > User. - It improves the user friendliness which allows the user to enroll fingerprints out of the box without adding extra packages. Why wouldn't we include it? - Not all systems have fingerprint readers - Users don't want to use biometric auth even if it's available -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1212671] New: Gnome desktop first time setup script tries to download Firefox flatpak
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212671 Bug ID: 1212671 Summary: Gnome desktop first time setup script tries to download Firefox flatpak Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: wolfram.fischer1979+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: The Gnome desktop first time setup script tries to download Firefox flatpak on the AARCH64 platform. Because Mozilla does _not_ provide a Firefox flatpak for AARCH64, the first time setup script fails reproducible every time a user logins to the desktop. Reproducible: Always Steps to Reproduce: 1.Install MicroOS and check the Gnome Desktop setup 2.Boot into desktop Actual Results: For Gnome, the first time setup script is executed and fails because there is no Firefox AARCH64 flatpak Expected Results: Try not to download Firefox AARCH64 flatpak so the first time setup script runs successfully and the user doesn't see an error message This bug is easily fixed by removing the first time setup desktop file in ~/.config/autostart . -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201049] Make MicroOS GNOME Desktop RC/Released
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1201049 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Base Product|openSUSE Tumbleweed |openSUSE Aeon Assignee|kubic-bugs(a)opensuse.org |rbrown(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1213499] New: libvirtd: When adding a host USB device & Start: "usb-host' is not a valid device model name"
by bugzilla_noreply＠suse.com 20 Jul '23

20 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213499 Bug ID: 1213499 Summary: libvirtd: When adding a host USB device & Start: "usb-host' is not a valid device model name" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: colony.three(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: Unable to add any host USB devices to a KVM VM due to the above error, on the current MicroOS. Add any USB device, Run the VM, and immediately a window pops up with: Error starting domain: internal error: QEMU unexpectedly closed the monitor (vm='cygnus-old'): 2023-07-20T00:13:42.182489Z qemu-system-x86_64: -device {"driver":"usb-host","hostbus":3,"hostaddr":2,"id":"hostdev2","bus":"usb.0","port":"2"}: 'usb-host' is not a valid device model name Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1425, in startup self._backend.create() File "/usr/lib64/python3.11/site-packages/libvirt.py", line 1373, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor (vm='cygnus-old'): 2023-07-20T00:13:42.182489Z qemu-system-x86_64: -device {"driver":"usb-host","hostbus":3,"hostaddr":2,"id":"hostdev2","bus":"usb.0","port":"2"}: 'usb-host' is not a valid device model name Reproducible: Always Steps to Reproduce: 1. In virt-manager add any host USB device. 2. Run the VM. 3. Profit with error. Actual Results: Error starting domain: internal error: QEMU unexpectedly closed the monitor (vm='cygnus-old'): 2023-07-20T00:13:42.182489Z qemu-system-x86_64: -device {"driver":"usb-host","hostbus":3,"hostaddr":2,"id":"hostdev2","bus":"usb.0","port":"2"}: 'usb-host' is not a valid device model name Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1425, in startup self._backend.create() File "/usr/lib64/python3.11/site-packages/libvirt.py", line 1373, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor (vm='cygnus-old'): 2023-07-20T00:13:42.182489Z qemu-system-x86_64: -device {"driver":"usb-host","hostbus":3,"hostaddr":2,"id":"hostdev2","bus":"usb.0","port":"2"}: 'usb-host' is not a valid device model name Expected Results: Add the host USB device and start the VM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1213490] New: security enhancement: no setuid
by bugzilla_noreply＠suse.com 19 Jul '23

19 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213490 Bug ID: 1213490 Summary: security enhancement: no setuid Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: ALP Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootable Images Assignee: fcrozat(a)suse.com Reporter: gmoro(a)suse.com QA Contact: jsrain(a)suse.com CC: georg.pfuetzenreuter(a)suse.com, gmoro(a)suse.com, kubic-bugs(a)opensuse.org, lnussel(a)suse.com, qa-bugs(a)suse.de Depends on: 1171174 Target Milestone: --- Found By: --- Blocker: --- The way ALP is setting this in the config.sh is still broken, need to investigate consequences and if this is still the case. +++ This bug was initially created as a clone of Bug #1171174 +++ setuid binaries are a potential attack vector for privilege escalation. MicroOS with it's limited scope has chance to close that hole by default and not ship any binaries with elevated privileges by default. Ie set the default level to "paranoid". This will prevent unprivileged (system) users from potentially exploiting - shadow suite tools like passwd, chsh etc - pam helpers unix{,2}_chkpwd - wall, write - clockdiff, ping - dbus-daemon-launch-helper - su - sudo - mount -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171174] security enhancement: no setuid
by bugzilla_noreply＠suse.com 19 Jul '23

19 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1171174 Guilherme Moro <gmoro(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1213490 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211868] New: distro-export-ed cannot be selected as "default" apps
by bugzilla_noreply＠suse.com 15 Jul '23

15 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211868 Bug ID: 1211868 Summary: distro-export-ed cannot be selected as "default" apps Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sjaniska(a)atmarama.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, all the distrobox-export-ed applications on Aeon (MicroOS), although being visible/searchable on the desktop, can't be selected as "default" apps for the GNOME DE. For instance, Claws-mail flatpak does not contain "fancy" plugin, so I had to install it and exported, but then it's viable option for "default" mail client. Similarly to Firefox - my eID could not work with flatpak version, so I have to keep twp versions – one which can understand e.g. links from other flatpak applications like Element and another for eID feature. I know that Aeon/MicroOS is a new thing, but I like it a lot. Still, wondering whether the above issues are due to Flatpak packaging, distrobox limitations or Aeon/MicroOS bugs? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212672] New: Gnome desktop: Cannot enable auto login for user via settings
by bugzilla_noreply＠suse.com 15 Jul '23

15 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212672 Bug ID: 1212672 Summary: Gnome desktop: Cannot enable auto login for user via settings 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: wolfram.fischer1979+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: I cannot enable auto login for the user in the Gnome settings (application) which makes GDM login the user automatically. Reproducible: Always Steps to Reproduce: 1.Open Gnome settings 2.Navigate to Users 3.Enter root password to be able to toggle auto login for the user 4.Toggle auto login for the user Actual Results: The auto login setting for the user _seems_ to be activated, as long as one is on the user settings page. If the settings page is changed away from user settings and returned to the user settings, the auto login setting for the user is _not_ activated. The auto login is not activated, which can be checked with a simple reboot. Expected Results: The setting to automate auto login should be enabled -- You are receiving this mail because: You are the assignee for the bug.

1 3