- openSUSE Kubic Bugs

[Bug 1206199] New: udisks2 ignores fstab mount options and uses the defaults instead
by bugzilla_noreply＠suse.com 08 Dec '22

08 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206199 Bug ID: 1206199 Summary: udisks2 ignores fstab mount options and uses the defaults instead 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: alexviralata(a)posteo.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0 Build Identifier: I used KDE Partition Manager to configure fstab to automount all of my drives. I activated the users option, and added "exec" as a mount option. The "exec" option isn't working. After some discution on reddit, I found out that udisksctl is in fact reading the fstab file, but the actual mount option used are the "safe defaults", I found this by using "findmnt". Reproducible: Always Steps to Reproduce: 1.Configure fstab to automount any other drive with "exec" mount option 2.Restart computer 3.Try to execute anything on that drive Actual Results: Nothing, since the drive is mount with "safe defaults" and that includes "rw,nosuid,nodev,noexec,relatime,lazytime,etc..." Expected Results: To be able to execute programs inside my drives. All my drives have my user name as owner and group owner. I think that's the only reason why they do actually automount, but with the wrong flags. Once I have fstab configured the way I like, and I unmount and re-mount my drives with KDE Partition Manager, the fstab mount option do get used, among the "safe defaults". SELinux disabled/permissive made no change. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206087] MicroOS - autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9'
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206087 https://bugzilla.suse.com/show_bug.cgi?id=1206087#c4 --- Comment #4 from Thorsten Kukuk <kukuk(a)suse.com> --- You don't need to install autoyast on the system to install MicroOS via autoyast. Just boot the installer DVD and provide an autoyast.xml file. If it is about creating the autoyast.xml file: you need to write one, there are several examples files for MicroOS somewhere flying around. If it's not about installation, but configuration: we have ignition/combustion for exactly this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206087] New: MicroOS - autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9'
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206087 Bug ID: 1206087 Summary: MicroOS - autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9' 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: samcon(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:107.0) Gecko/20100101 Firefox/107.0 Build Identifier: When attempting to install autoyast2 on MicroOS ``` transactional-update pkg install autoyast2 Checking for newer version. transactional-update 4.1.0 started Options: pkg install autoyast2 Separate /var detected. 2022-12-06 10:18:51 tukit 4.1.0 started 2022-12-06 10:18:51 Options: -c58 open 2022-12-06 10:18:52 Using snapshot 58 as base for new snapshot 59. 2022-12-06 10:18:52 Syncing /etc of previous snapshot 57 as base into new snapshot "/.snapshots/59/snapshot" 2022-12-06 10:18:52 SELinux is enabled. ID: 59 2022-12-06 10:18:58 Transaction completed. Calling zypper install 2022-12-06 10:19:00 tukit 4.1.0 started 2022-12-06 10:19:00 Options: callext 59 zypper -R {} install autoyast2 2022-12-06 10:19:00 Executing `zypper -R /tmp/transactional-update-K8KWbl install autoyast2`: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9', but this requirement cannot be provided not installable providers: yast2-network-4.5.10-1.1.noarch[repo-oss] Solution 1: deinstallation of busybox-hostname-1.35.0-25.1.noarch Solution 2: do not install autoyast2-4.5.11-1.1.noarch Solution 3: break autoyast2-4.5.11-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c 2022-12-06 10:19:40 Application returned with exit status 4. ERROR: zypper install on /.snapshots/59/snapshot failed with exit code 4! Removing snapshot #59... 2022-12-06 10:19:41 tukit 4.1.0 started 2022-12-06 10:19:41 Options: abort 59 2022-12-06 10:19:41 Discarding snapshot 59. 2022-12-06 10:19:42 Transaction completed. transactional-update finished ``` OS info: ``` $ cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20221204" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed" VERSION_ID="20221204" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20221204" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" ``` Reproducible: Always Steps to Reproduce: 1. run latest version of MicroOS 2. transactional-update pkg install autoyast2 Actual Results: Problem: the to be installed autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9', but this requirement cannot be provided not installable providers: yast2-network-4.5.10-1.1.noarch[repo-oss] Solution 1: deinstallation of busybox-hostname-1.35.0-25.1.noarch Solution 2: do not install autoyast2-4.5.11-1.1.noarch Solution 3: break autoyast2-4.5.11-1.1.noarch by ignoring some of its dependencies Expected Results: autoyast2 is installed -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206087] MicroOS - autoyast2-4.5.11-1.1.noarch requires 'yast2-network >= 4.5.9'
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206087 https://bugzilla.suse.com/show_bug.cgi?id=1206087#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |kukuk(a)suse.com Resolution|--- |WONTFIX --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- That's normal and expected. First, YaST is not supported on MicroOS and that's why it is not installed there. Second, we have dependencies to exactly express this: to create conflicts if something should be installed which is incompatible to what is already installed, and we offer a solution to solve this conflict. So just tell zypper how you want to resolve the conflict and don't abort. There is no way to make all packages always installable on every product without ever creating a conflict. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206008] sealert - ModuleNotFoundError: No module named 'formatter'
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206008 http://bugzilla.opensuse.org/show_bug.cgi?id=1206008#c1 Torsten Behrens <torsten(a)behrens.biz> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X11 Applications |MicroOS Assignee|screening-team-bugs(a)suse.de |kubic-bugs(a)opensuse.org --- Comment #1 from Torsten Behrens <torsten(a)behrens.biz> --- changed to microos -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205997] New: SELinux policy prevents launching steam games and bottles applications
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205997 Bug ID: 1205997 Summary: SELinux policy prevents launching steam games and bottles applications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: ficous(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:107.0) Gecko/20100101 Firefox/107.0 Build Identifier: I've tested on Silverblue, MicroOS, Leap, and Tumbleweed all on fresh VMs. This issue only occurs on MicroOS. 32 bit applications launched through Steam crash instantly as both native and wine apps, and any application run through Bottles, either 32 or 64 bit, will crash instantly. Steam and Bottles programs run though wine give this error: > wine: could not load kernel32.dll, status c0000135 Native steam games give this error: > failed to dlopen /home/shaw/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Left 4 Dead 2/bin/engine.so error=/home/shaw/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Left 4 Dead 2/bin/engine.so: cannot enable executable stack as shared object requires: Permission denied failed to dlopen engine.so error=engine.so: cannot enable executable stack as shared object requires: Permission denied AppFramework : Unable to load module engine.so! Unable to load interface VCvarQuery001 from engine.so Of note, 64 bit applications through steam (like rimworld) work just fine with SELinux enabled, while 32 bit games like L4D2 crash with that second error code above. What I find interesting is in both of these failures the programs report that they aren't able to find or access libraries they need. All my searching kept turning up someone familiar, and turns out when I disable SELinux the problem vanishes entirely. I A-B tested back and forth and everytime I disable SELinux I can launch everything perfectly, but once I re-enable it's sad gamer town again. I'm 100% out of my depth when it comes to actual SELinux configuration, so I'm really at an impass. I have tried scowering wine_selinux's manpage and I applied these modifications to the system, but there was no change in behavior. >semanage permissive -a wine_t setsebool -P mmap_low_allowed 1 setsebool -P wine_mmap_zero_ignore 1 Additionally, this issue or set of issues doesn't seem to be limited to my machine. [Similar wine issue reproduced by BottlesDev](https://github.com/bottlesdevs/Bottles/issues/1968#issuecomment… [Similar native Issue](https://github.com/flathub/com.mattjakeman.ExtensionManager/issues/2… [Similar native issue](https://github.com/flathub/com.parsecgaming.parsec/issues/18) [Similar native issue](https://github.com/flathub/net.jami.Jami/issues/52#issue-1254111513) [Somewhat Similar Garry's Mod issue](https://github.com/Facepunch/garrysmod-issues/issues/5056#issue-9973… *it's always SELinux :P* Reproducible: Always Steps to Reproduce: 1. Install MicroOS 2. Install Bottles 3. Create a Gaming bottle (which partially fails silently due to this issue) 4. Install Battlenet 5. Battlenet will not be installed because the installer executable never executed During steps 3 and 4 the *wine: could not load kernel32.dll, status c0000135* error will spam every time bottles attempts to launch an executable. 1. Install MicroOS 2. Install Steam 3. Install any 32bit game. Fistful of Frags is free and affected by this 4. Launch the game natively or through proton 5. Instant crash, or if you're lucky you'll get a gui error Actual Results: N/A Expected Results: N/A MicroOS fresh install into a VM. Nothing installed, modified, or tweaked other than installing bottles. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1205862] New: Dolphin currently installed as RPM, rather than flatpak for MicroOS-KDE
by bugzilla_noreply＠suse.com 29 Nov '22

29 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205862 Bug ID: 1205862 Summary: Dolphin currently installed as RPM, rather than flatpak for MicroOS-KDE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement 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: --- Pursuant to the aims of MicroOS Desktop, now that Dolphin is available as a flatpak through Flathub, and will integrate better with the rest of the desktop, as more flatpaks become available from KDE. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205445] New: transactional-update breaks system after some time.
by bugzilla_noreply＠suse.com 28 Nov '22

28 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205445 Bug ID: 1205445 Summary: transactional-update breaks system after some time. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: samcon(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- dear experts, I've been running MicroOS headless on multiple raspberry-pi 3bs with single service (excl. system services) and/or as container host. After some time, the devices no longer boots correctly, I am unable to ssh or ping device. Since I didn't have extra monitor, I would do clean install of MicroOS (with Combustion). Doing this multiple times over the past months, I assumed maybe the SD cards were corrupt so I used another SD card, unfortunately, after sometime same happened. I got my hands on dell inspiron tower, I installed MicroOS last week. This time disabling transactional-update.timer. Everything was working fine until I enabled transactional-update.timer last week Wednesday, yesterday (Monday) I attempted to ssh into machine and found it was no longer reachable. I now have a monitor, plugged it in and am welcomed by blank screen (no login prompt). After force rebooting machine I am welcomed with: "Notice �� Hard drive self monitoring system has reported that a parameter has exceeded its normal operating range. Dell recommends that you back up your data regularly. A parameter out of range may or may not indicate a potential hard drive problem Press F2 to Resume" Pressing F2, then waiting ... I eventually I see underscore cursor flashing and nothing happens. Where do I go from here? I am unable to get to bootloader to log into device to check logs or to perform btrfs rollback. Kind regards, Sam -- You are receiving this mail because: You are the assignee for the bug.

1 3

[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 1205560] New: [Build 20221117] journal_check: Failed to adjust quota for subvolume "/var/lib/machines": Bad file descriptor
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205560 Bug ID: 1205560 Summary: [Build 20221117] journal_check: Failed to adjust quota for subvolume "/var/lib/machines": Bad file descriptor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2885705/modules/jour nal_check/steps/21 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 Since the upgrade to systemd 252.1 in Tumbleweed we see this error in the micros journals: Nov 18 10:13:10.658308 localhost systemd-tmpfiles[637]: Failed to adjust quota for subvolume "/var/lib/machines": Bad file descriptor openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos@64bit fails in [journal_check](https://openqa.opensuse.org/tests/2885705/modules/journal_ch… ## Test suite description ## Reproducible Fails since (at least) Build [20221117](https://openqa.opensuse.org/tests/2885705) (current job) ## Expected result Last good: [20221116](https://openqa.opensuse.org/tests/2883624) (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 3