October 2022 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[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 1204629] New: [Build 20221023] transactional-update: munmap_chunk(): invalid pointer
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204629 Bug ID: 1204629 Summary: [Build 20221023] transactional-update: munmap_chunk(): invalid pointer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2831134/modules/tdup /steps/11 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 While testing an upgrade from the previous snapshot to 1023 (which does not have a lot of changes, so possibly this issue is not even related to the snapshot), tdup fails with: munmap_chunk(): invalid pointer Use '--interactive' for manual problem resolution. openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos-old2microosnext@64bit fails in [tdup](https://openqa.opensuse.org/tests/2831134/modules/tdup/steps/11) ## Test suite description Boot from existing, static MicroOS image and transactional-update dup to snapshot under test ## Reproducible Fails since (at least) Build [20221023](https://openqa.opensuse.org/tests/2829980) ## Expected result Last good: [20221022](https://openqa.opensuse.org/tests/2828758) (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 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 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204307 http://bugzilla.opensuse.org/show_bug.cgi?id=1204307#c16 --- Comment #16 from Richard Brown <rbrown(a)suse.com> --- (In reply to Neal Gompa from comment #15) > That said, if we're going to encourage openSUSE MicroOS to become a useful > artifact of openSUSE and not change anything about how MicroOS works, we're > going to have to change our packaging guidelines to disallow *anything* in > /srv. That will be very painful, but will likely eventually happen. > > There are two alternatives to this: > > * Exposing /srv during package management, but that adds complexity to the > snapshotting setup, since /srv is a separate subvolume > * Changing /srv to be a symlink under /var (i.e. /srv -> /var/srv), which > would make /srv work in package management properly but would add complexity > to installation to ensure that we have a partitioning scheme variant for > transactional-update systems There's a third alternative * just say that any package that installs stuff in places that it shouldn't should not be installed as an RPM on MicroOS MicroOS can be a useful artifact of openSUSE and still NOT run 100% of everything openSUSE produces After all, openSUSE can produce containers where silly nonsense exceptions too good engineering can be isolated from the host We don't need to change everything just because one package that isn't even part of openSUSE doesn't install on one base OS of openSUSE. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204307 http://bugzilla.opensuse.org/show_bug.cgi?id=1204307#c15 Neal Gompa <ngompa13(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ngompa13(a)gmail.com --- Comment #15 from Neal Gompa <ngompa13(a)gmail.com> --- (In reply to Axel Braun from comment #12) > (In reply to Richard Brown from comment #11) > > > /srv is not a valid location for an RPM to install files > > maybe not anymore. > > ... > > > As an active Board Member I expect you to be advocating for the policies and > > standards accepted by this community, not undermining them by continuing to > > push for a fix in the wrong place. > > I dont know why you are playing the board card again, or where I 'push a fix > in the wrong place'. > Fact is, the current package works in /srv. > I have encouraged the maintainer to move to a compliant location for the > installation, and that works on Leap and TW, but not on MicroOS. Reason > unclear, and in this state not a candidate for Factory > > You are more than welcome to contribute your MicroOS expertise: > https://build.opensuse.org/project/show/home:Herbster0815:Playground Packages in home projects can do whatever, including ignoring openSUSE policy (as is the case here). It doesn't mean anyone here is going to fix it. In general, the difference between /srv and /var is that the latter is exposed as a writable layer with package management and the former is not. That said, if we're going to encourage openSUSE MicroOS to become a useful artifact of openSUSE and not change anything about how MicroOS works, we're going to have to change our packaging guidelines to disallow *anything* in /srv. That will be very painful, but will likely eventually happen. There are two alternatives to this: * Exposing /srv during package management, but that adds complexity to the snapshotting setup, since /srv is a separate subvolume * Changing /srv to be a symlink under /var (i.e. /srv -> /var/srv), which would make /srv work in package management properly but would add complexity to installation to ensure that we have a partitioning scheme variant for transactional-update systems -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204307 https://bugzilla.suse.com/show_bug.cgi?id=1204307#c14 --- Comment #14 from Richard Brown <rbrown(a)suse.com> --- (In reply to Axel Braun from comment #12) > (In reply to Richard Brown from comment #11) > > > /srv is not a valid location for an RPM to install files > > maybe not anymore. > > ... > > > As an active Board Member I expect you to be advocating for the policies and > > standards accepted by this community, not undermining them by continuing to > > push for a fix in the wrong place. > > I dont know why you are playing the board card again, or where I 'push a fix > in the wrong place'. Because the facts are, the openSUSE Project prohbits the creation of content inside /srv From https://en.opensuse.org/openSUSE:Packaging_guidelines "a package must not install, remove or otherwise modify /srv content as its use is reserved to the admin according to FHS[2]. In openSUSE, it's OK to have a package create an empty directory in /srv if the default configuration of the software points there." > Fact is, the current package works in /srv. Doesn't matter, it breaks the openSUSE Project's rules, rules which you, as a Board member, have a responsibility to help enforce & communicate..not undermine. > I have encouraged the maintainer to move to a compliant location for the > installation, and that works on Leap and TW, but not on MicroOS. Reason > unclear, and in this state not a candidate for Factory Thank you, the package is the correct place to fix this, not MicroOS. > You are more than welcome to contribute your MicroOS expertise: > https://build.opensuse.org/project/show/home:Herbster0815:Playground I will not - I contribute to openSUSE, not random home: Projects -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204307 https://bugzilla.suse.com/show_bug.cgi?id=1204307#c13 --- Comment #13 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Axel Braun from comment #12) > I dont know why you are playing the board card again, or where I 'push a fix > in the wrong place'. > Fact is, the current package works in /srv. > I have encouraged the maintainer to move to a compliant location for the > installation, and that works on Leap and TW, but not on MicroOS. Reason > unclear, and in this state not a candidate for Factory /usr/srv is not really a compliant location... Wild guess: pi-hole tries to write to /usr/srv/www/... and fails on MicroOS, since this it has a read-only root filesystem. In this case it would violates all rules in TW and Leap, too, and will fail on this variants in the future (near, mid or longterm, I don't know), too. The only correct, future proof way (would mean it will also work with new features in the future like Full Disk Encryption with TPM or FIDO2 key) is, to have the static files below /usr(/share/pi-hole e.g.?) and the writeable part below /srv or /var. This is not done with changing a single configure option. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 24 Oct '22

24 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204307 https://bugzilla.suse.com/show_bug.cgi?id=1204307#c12 --- Comment #12 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Richard Brown from comment #11) > /srv is not a valid location for an RPM to install files maybe not anymore. ... > As an active Board Member I expect you to be advocating for the policies and > standards accepted by this community, not undermining them by continuing to > push for a fix in the wrong place. I dont know why you are playing the board card again, or where I 'push a fix in the wrong place'. Fact is, the current package works in /srv. I have encouraged the maintainer to move to a compliant location for the installation, and that works on Leap and TW, but not on MicroOS. Reason unclear, and in this state not a candidate for Factory You are more than welcome to contribute your MicroOS expertise: https://build.opensuse.org/project/show/home:Herbster0815:Playground -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204560] New: [MicroOS Snapshot20221019] Missing Toolbox on Default Install
by bugzilla_noreply＠suse.com 21 Oct '22

21 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204560 Bug ID: 1204560 Summary: [MicroOS Snapshot20221019] Missing Toolbox on Default Install Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fenyx(a)vivaldi.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I installed MicroOS (Gnome), updated to 20221019, and noticed that toolbox is no longer in the default install. Is this intended? This is on a vanilla install with no modifications to the base install. Version information: ``` ~> pkcon search microos-release Searching by details [=========================] Starting [=========================] Querying [=========================] Finished [=========================] Installed MicroOS-release-20221019-1887.1.x86_64 (installed:repo-oss) openSUSE MicroOS ``` Toolbox package not installed: ``` :~> toolbox bash: toolbox: command not found ``` Searching for the toolbox package will show it as Available and not Installed ``` :~> pkcon search toolbox Searching by details [=========================] Starting [=========================] Querying [=========================] Finished [=========================] ...snipped... Available toolbox-2.3+git20220622.32785f7-2.2.noarch (repo-oss) Script to start a toolbox container for system debugging ``` Thank you for the time. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1204307] [MicroOS] Package not installed correctly
by bugzilla_noreply＠suse.com 20 Oct '22

20 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204307 https://bugzilla.suse.com/show_bug.cgi?id=1204307#c11 --- Comment #11 from Richard Brown <rbrown(a)suse.com> --- (In reply to Axel Braun from comment #10) > (In reply to Richard Brown from comment #9) > > (In reply to Axel Braun from comment #6) > > > ..but still reduces the overhead.... > > > > A broken RPM does not 'reduce the overhead' for you as a user. > > The RPM is not broken. It does just not install under MicroOS without > additional activities. That was my point. The RPM installs in an invalid location /srv is not a valid location for an RPM to install files Just as an RPM should not install files in /home It is broken, and in it's current state would never be acceptable for submission to openSUSE because of such breaches of our policies. As an active Board Member I expect you to be advocating for the policies and standards accepted by this community, not undermining them by continuing to push for a fix in the wrong place. There is nothing MicroOS maintainers can, should, or will do to support the installation of invalid, poorly packaged, broken RPMs -- You are receiving this mail because: You are the assignee for the bug.

1 0