March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208808] New: hotspot: review dbus / polkit rules
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208808 Bug ID: 1208808 Summary: hotspot: review dbus / polkit rules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The last hotspot release installs the following files in order to run the `perf` utility with elevated privileges: /usr/share/dbus-1/system.d/com.kdab.hotspot.perf.conf /usr/share/dbus-1/system-services/com.kdab.hotspot.perf.service /usr/share/polkit-1/actions/com.kdab.hotspot.perf.policy Sources URL: https://github.com/KDAB/hotspot/tree/1.4 and notably https://github.com/KDAB/hotspot/blob/master/src/hotspot-perf-authhelper.act… which is processed by kauth. The package update is currently available in a branch: https://build.opensuse.org/package/show/home:krop:branches:devel:tools/hots… # cat com.kdab.hotspot.perf.conf <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig>  <policy user="root"> <allow own="com.kdab.hotspot.perf"/> </policy> </busconfig> --- # cat com.kdab.hotspot.perf.service [D-BUS Service] Name=com.kdab.hotspot.perf Exec=/usr/libexec/kauth/hotspot-auth-helper User=root --- # cat com.kdab.hotspot.perf.policy <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE policyconfig PUBLIC "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN" "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd"> <policyconfig> <action id="com.kdab.hotspot.perf.elevate" > <description>Elevate Privileges</description> <message>allows to run perf as root</message> <defaults> <allow_inactive>no</allow_inactive> <allow_active>auth_admin_keep</allow_active> </defaults> </action> </policyconfig> -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1209729] New: After update system no longer able to boo because mount sysroot unknown filesystem type jfs
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209729 Bug ID: 1209729 Summary: After update system no longer able to boo because mount sysroot unknown filesystem type jfs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: sachse(a)gmx.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 865835 --> http://bugzilla.opensuse.org/attachment.cgi?id=865835&action=edit Bootlog After Update with "zypper dup" which was running fine the system no longer able to boot because filesystem driver not included into kernel or initrd. Error message: "mount: /sysroot: unknown filesystem type 'jfs'" Starting system with a rescue system and check installed modules there is a jfs kernel module available but not included into initrd by dracut. To solve the problem: - dracut have to check if filesystem of the root partition into the kernel or if it exists as module - if it exists as module it must be included into initrd - if no driver is found then dracut must abort and complain that the system is not able to boot after this update NOGO: run silent and leave system in non bootable state -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1209338] AUDIT-0: mumble: review of D-Bus service net.sourceforge.mumble.murmur
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209338 https://bugzilla.suse.com/show_bug.cgi?id=1209338#c2 --- Comment #2 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- We currently experience a higher load of reviews and it will take a bit longer before we can work on your package. Mumble is written in C++ and has ~80.000 lines of code so it might be a bigger effort. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209818] Slow startup of evolution and other applications on i3
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209818 https://bugzilla.suse.com/show_bug.cgi?id=1209818#c3 --- Comment #3 from Martin Sirringhaus <martin.sirringhaus(a)suse.com> --- (In reply to Martin Sirringhaus from comment #2) > After doing > > ~ �� systemctl --user stop xdg-desktop-portal-wlr > > applications seem to start fine on sway. > > But starting xdg-desktop-portal and xdg-desktop-portal-gnome still fails > with a timeout. Correction: That above is NOT true. It just happened in parallel with this: Mar 31 10:43:49 suse-laptop dbus-daemon[4714]: [session uid=1000 pid=4714] Failed to activate service 'org.freedesktop.impl.portal.desktop.gnome': timed out (service_start_timeout=120000ms) Mar 31 10:43:49 suse-laptop dbus-daemon[4714]: [session uid=1000 pid=4714] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gnome' unit='xdg-desktop-portal-gnome.service' requested by ':1.174' (uid=1000 pid=6162 comm="/usr/libexec/xdg-desktop-portal") Mar 31 10:43:49 suse-laptop systemd[4531]: Starting Portal service (GNOME implementation)... Mar 31 10:43:50 suse-laptop dbus-daemon[4714]: [session uid=1000 pid=4714] Failed to activate service 'org.freedesktop.portal.Desktop': timed out (service_start_timeout=120000ms) Once I run in this final timeout (when running `/usr/libexec/xdg-desktop-portal-gnome` and `/usr/libexec/xdg-desktop-portal` manually), apps start normally. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209983] Tumbleweed CD has Rock Ridge errors
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209983 https://bugzilla.suse.com/show_bug.cgi?id=1209983#c1 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com Component|Installation |Other Assignee|yast2-maintainers(a)suse.de |screening-team-bugs(a)suse.de QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Joshua Kugler from comment #0) > Please pardon me if this is the wrong category. I did not see a "build farm" > category similar. As you suspected, "Installation" is not the right component because it ends up assigned to the YaST Team, that is not involved in building the image. I was also not able to find the right component so I moved this to "Other" and will leave the screening team do their job. :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195391] New: identify and declare bash dependencies explicitly
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1195391 Bug ID: 1195391 Summary: identify and declare bash dependencies explicitly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a lot of fear that the openSUSE and SUSE distributions are, due to historic reason alone always assuming that /bin/sh is a symlink to bash, so that scripts executed with /bin/sh are actually only executable with bash. in order to explore that dependency, we need to figure out how many scripts actually use bash specifics when being invoked for /bin/sh and then fix these to declare the bash dependency if they have it. this bug is a tracker issue for fixes related to that. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1207784] New: [spack, podman] Spack generated Dockerfile fails due to not sourcing setup-env.sh
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207784 Bug ID: 1207784 Summary: [spack, podman] Spack generated Dockerfile fails due to not sourcing setup-env.sh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hpc-bugs(a)suse.de Found By: Development Blocker: --- Created attachment 864634 --> https://bugzilla.suse.com/attachment.cgi?id=864634&action=edit Fix Building a container from a Spack-generated Dockerfile fails with the error message: [1/2] STEP 3/5: RUN cd /opt/spack-environment && spack env activate . && spack install --fail-fast && spack gc -y /bin/sh: spack: command not found Error: building at STEP "RUN cd /opt/spack-environment && spack env activate . && spack install --fail-fast && spack gc -y": while running runtime: exit status 127 Reason: The 'RUN' command does not source /opt/spack/share/spack/setup-env.sh before calling spack which conveniently sets up PATH (among other things) to include the spack binary. Even with spack in the search path, `spack env activate .` would fail without the environment set up. There are two locations in the Dockerfile-template where this needs to be added. The singularityfile template does this correctly already. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1207053] New: [HPC, Spack] 'var_path' set incorrectly
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207053 Bug ID: 1207053 Summary: [HPC, Spack] 'var_path' set incorrectly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- Spack cannot find its repos since var_path is set incorrectly since release of version 0.19.0: it points to /var/spack instead of /var/lib/spack. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209548] New: [hdf5] timestamp/buildhost/kernel data makes build not reproducible
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209548 Bug ID: 1209548 Summary: [hdf5] timestamp/buildhost/kernel data makes build not reproducible Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: stefan.bruens(a)rwth-aachen.de Found By: Development Blocker: --- The build of hdf5 is not reproducible as information on timestamp/buildhost/kernel is kept. This has been fixed for TW but the fix is still missing from Leap/SLE. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208808] AUDIT-0: hotspot: review dbus / polkit rules
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208808 https://bugzilla.suse.com/show_bug.cgi?id=1208808#c15 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #15 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- The package is now in Factory using the privilege escalation disable patch from upstream. Therefore I'm closing this bug as WONTFIX. Once there is an improved upstream version you can reenable the D-Bus and Polkit components and open a follow-up review bug. Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0