December 2022 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[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 1206008] sealert - ModuleNotFoundError: No module named 'formatter'
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206008 http://bugzilla.opensuse.org/show_bug.cgi?id=1206008#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com, | |torsten(a)behrens.biz Flags| |needinfo?(torsten(a)behrens.b | |iz) --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- sealert is not installed on MicroOS, so why is this a MicroOS bug? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206292] New: Wine/Proton not working relaibly with default SELinux configuration
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206292 Bug ID: 1206292 Summary: Wine/Proton not working relaibly with default SELinux configuration 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: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863450 --> http://bugzilla.opensuse.org/attachment.cgi?id=863450&action=edit Proton Log file if running from a BtrFS volume Hey there, this is a bit of a wired issue I was facing and first thought Proton/Wine to be the issue if running from a BtrFS subvolume but turned out this to not be the case. So here is the situation I faced with only some games: Running a game with Proton or Wine installed in my $HOME which is a BtrFS volume by default on MicroOS caused it to sometimes fail to install some dependencies into a new prefix. Often this seemed to have been related to C++ runtime stuff Wine/Proton will install for some games. It failed to install those and the game where unable to operate properly. My first quick fix was to move Proton to an XFS drive by creating a new SteamLibrary for the Flatpak Steam Client and moving Proton there. Afterwards it operated successfully with no issues. Later on however I've read someone��s review of MicroOS mentioning he had to set: sudo setsebool -P selinuxuser_execmod 1 To make Proton work reliable. I tested this for myself with affected games and can confirm this worked. Additionally also Bottles, Lutris and Heroic Games Launcher where affected by this issue and randomly did not operate successfully when running games via their own Wine runners. The above SELinux config change fixed it also for them. Games I experienced to have issues with the missing SELinux config: - Satisfactory (Steam) - Control (Heroic Games Launcher, EGS version) - Creature in the Well /Heroic Games Launcher, EGS VVersion) - Age of Mythology: Extended Edition (Steam) In case some wants to counter test this. Would it be an issue if the above SELinux configuration could be set as it by default on MicroOS to make the gaming workload work OOTB? Or are there any reasons some should not change the above configuration. In that case I'd like to know why. Kind regards, V. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1201874] KDE pattern is using PackageKit instead of transactional-updates
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201874 http://bugzilla.opensuse.org/show_bug.cgi?id=1201874#c2 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |sfalken(a)cloverleaf-linux.or | |g Resolution|--- |FIXED --- Comment #2 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Fix has been done. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203887] New: Cannot changr auto-login settings (Gnome Settings)
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203887 Bug ID: 1203887 Summary: Cannot changr auto-login settings (Gnome Settings) 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: cutelilfroggy(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to change the auto-login settings under Gnome Settings -> Users fails. You can push the little slider to turn auto-login on, but that setting change is not respected. If you switch to a different category in the setting menu or restart the setting app, the slider is also back to its previous state. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1167780] MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1167780 http://bugzilla.opensuse.org/show_bug.cgi?id=1167780#c13 Joed L <jlopez777+opensuse(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Flags| |needinfo?(fvogt(a)suse.com) --- Comment #13 from Joed L <jlopez777+opensuse(a)gmail.com> --- Have folks landed on this? If so, should we document/close? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204792] New: Desktop-GNOME - Network Manager requires root password to change anything
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204792 Bug ID: 1204792 Summary: Desktop-GNOME - Network Manager requires root password to change anything 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: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System should be using the "Easy" polkit profile, not standard https://github.com/openSUSE/polkit-default-privs/pull/85 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1203427] New: distrobox should be installed by default for microos desktop
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203427 Bug ID: 1203427 Summary: distrobox should be installed by default for microos desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: pranav.sharma.ama(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- distrobox requires less fiddling with podman / base image, especially to get gui apps to work -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206501] New: Base:System/transactional-update: transactional-update.service forces reboot with rebootmgr disabled
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206501 Bug ID: 1206501 Summary: Base:System/transactional-update: transactional-update.service forces reboot with rebootmgr disabled 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: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've disabled rebootmgr.service After the system is triggering the transactional-update.service (via timer or I do it manually) the system updates and immediately afterwards it will force a reboot via systemd. Behavior expected: No reboot. To reproduce: switch to a (slightly) older snapshot. disable rebootmgr: systemctl disable --now rebootmgr Trigger transactional-update service: systemctl start transactional-update.service Watch it reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206502] New: Base:System/transactional-update: transactional-update.timer - Persistent attribute of timer is ignored
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206502 Bug ID: 1206502 Summary: Base:System/transactional-update: transactional-update.timer - Persistent attribute of timer is ignored 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: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The current RandomizedDelaySec=2h attribute is also applied to every boot, so users who only run their computers for a short time won't get their daily updates reliably. Normally, you'd expect that if the timer isn't run at the time (0:00 + randomized-delay) it will trigger at the next boot. However, this isn't the case at all: This behavior was changed with this merge in systemd https://github.com/systemd/systemd/pull/11608 -- You are receiving this mail because: You are the assignee for the bug.

1 3