October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1229594] Agama installation test stops at preparing page on ppc64le
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229594 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |yast2-maintainers(a)suse.de Component|Other |Installation QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231843] AUDIT-0: GDM login without auth
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231843 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|GDM login without auth |AUDIT-0: GDM login without | |auth -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231843] New: GDM login without auth
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231843 Bug ID: 1231843 Summary: GDM login without auth Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dleuenberger(a)suse.com Target Milestone: --- Found By: --- Blocker: --- a few weeks ago gdm started to act weird. the login page no longer listed any users. when i tried entering an username and tried to get to a password prompt nothing happened. This weekend i had my yubikey removed for some testing and the GDM looked normal again which brought me to do some testing. But before I tested starting gdm without my yubikey, I entered an username and without doing anything else, it logged me in. o.O which lead me to dig deeper. 1. if a pkcs11 device (like my yubikey) is attached accountsservice ListsCachedUsers only returns users with a pkcs11 key set up for them apparently. This explains why the "recent user list" in gdm was suddenly empty. 2. to make some progress with debugging why gdm no longer works I reinstalled all gnome patterns with recommends enabled. this pulled in pam_pkcs11. This allowed /usr/lib/pam.d/gdm-smartcard to load, before it failed because of the missing module. 3. lets test this: ``` cp /usr/lib/pam.d/gdm-smartcard sudo-i-pam_gdm-reproduce ln -s sudo-i-pam_gdm-reproduce sudo-i sudo -i ERROR:pam_pkcs11.c:313: Failed to initialize crypto root@fortress ~ # ``` yup got right in. ``` rpm -e --nodeps pam_pkcs11 ``` and ``` sudo -i sudo: PAM authentication error: Module is unknown sudo: a password is required ``` commenting out the pam_pkcs11 ``` sudo -i root@fortress ~ # ``` all the potentially affected pam files: ``` grep pam_gdm * gdm-autologin:auth optional pam_gdm.so gdm-fingerprint:auth [success=ok default=1] pam_gdm.so gdm-smartcard:auth [success=ok default=1] pam_gdm.so ``` I am not sure if totally related ... but the shadowing of the i variable here looks broken: https://gitlab.gnome.org/GNOME/gdm/-/commit/f365ba1d55c186e2aa93ecf2c897af2… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231494] New: [Build 20241008-SELinux] openQA test fails in rsync_server: rsyncd cant start
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231494 Bug ID: 1231494 Summary: [Build 20241008-SELinux] openQA test fails in rsync_server: rsyncd cant start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4548658/modules/rsyn c_server/steps/24 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1231483 Target Milestone: --- Found By: openQA Blocker: Yes Tumbleweed iso test with SELinux enabled by default, see tracker bsc#1230118 rsyncd cant start probably policy issue type=AVC msg=audit(1728547661.441:148): avc: denied { execute } for pid=1700 comm="rsyncd" path="/usr/bin/bash" dev="vda2" ino=15343 scontext=system_u:system_r:rsync_t:s0 tcontext=system_u:object_r:shell_exec_t:s0 tclass=file permissive=0 ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-rsync-server@64bit fails in [rsync_server](https://openqa.opensuse.org/tests/4548658/modules/rsync_serve… ## Test suite description Maintainer: zluo(a)suse.de install and test rsync server ## Reproducible Fails since (at least) Build [20241008-SELinux](https://openqa.opensuse.org/tests/4548658) (current job) ## Expected result Last good: [20241009](https://openqa.opensuse.org/tests/4547293) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231489] New: [Build 20241008-SELinux] openQA test fails in snapper_thin_lvm
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231489 Bug ID: 1231489 Summary: [Build 20241008-SELinux] openQA test fails in snapper_thin_lvm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4548535/modules/snap per_thin_lvm/steps/71 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1230118 Target Milestone: --- Found By: openQA Blocker: Yes Tumbleweed iso test with SELinux enabled by default, see tracker bsc#1230118 probably policy issue, avc: type=AVC msg=audit(1728548238.401:476): avc: denied { execute } for pid=79659 comm="snapperd" name="systemctl" dev="vda2" ino=37890 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=0 ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in [snapper_thin_lvm](https://openqa.opensuse.org/tests/4548535/modules/snapper… ## Test suite description Maintainer: QE Core Filesystem related tests, for example snapper and btrfs features. ## Reproducible Fails since (at least) Build [20241008-SELinux](https://openqa.opensuse.org/tests/4548535) (current job) ## Expected result Last good: [20241009](https://openqa.opensuse.org/tests/4547883) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231773] dracut cannot create initrd & initramfs on initrd-6.11.2-1-default
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231773 https://bugzilla.suse.com/show_bug.cgi?id=1231773#c23 --- Comment #23 from Thomas Blume <thomas.blume(a)suse.com> --- Ok, so they are indeed not there. Can you now try to copy the missing files manually with the same command that dracut is using, e.g.: sudo cp '/usr/lib/dracut/modules.d/98dracut-systemd/parse-root.sh' '/var/tmp/dracut.uJvS7n/initramfs/var/lib/dracut/hooks/cmdline/00-parse-root.sh' and afterwards verify that they are there? The 2 slashes (//) should be irrelevant. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231590] subversion:testsuite fails to build with Swig 4.3.0
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231590 https://bugzilla.suse.com/show_bug.cgi?id=1231590#c4 --- Comment #4 from Antonio Teixeira <antonio.teixeira(a)suse.com> --- I don't object to adding the uncommitted patches if they test fine. Just add a commented link to the mailing list thread in the spec file so I can quickly know where to look to find out if the patches were merged later on. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231826] New: open-vm-tools 12.5.0 was released - please rebase
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231826 Bug ID: 1231826 Summary: open-vm-tools 12.5.0 was released - please rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: john.wolfe(a)broadcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- open-vm-tools 12.5.0 was released on Oct 08, 2024 - based on build 24276846. There are no new features in the open-vm-tools 12.5.0 release. This is primarily a maintenance release that addresses a few issues, including: - A Github pull request. Please see the Resolved Issues section of the Release Notes. - Avoid deprecated function warnings if using libxml2 version 2.13.0 or later. For a more complete list of issues resolved in this release, see the Resolved Issues section of the Release Notes. For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.5.0 Release Notes are available at: https://github.com/vmware/open-vm-tools/blob/stable-12.5.0/ReleaseNotes.md The granular changes that have gone into the 12.5.0 release are in the ChangeLog at: https://github.com/vmware/open-vm-tools/blob/stable-12.5.0/open-vm-tools/Ch… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1229757] New: Package conflict in libsemanage (shadow) update
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229757 Bug ID: 1229757 Summary: Package conflict in libsemanage (shadow) update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com, mvetter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This is what I get with the latest MU: + zypper patch --with-optional Problem: 1: the to be installed libsemanage2-3.5-150600.1.48.x86_64 requires 'libsemanage-conf >= 3.5', but this requirement cannot be provided not installable providers: libsemanage-conf-3.5-150600.1.48.x86_64[repo-oss] Solution 1: Following actions will be done: do not install patch:openSUSE-SLE-15.6-2024-2808-1.noarch do not install patch:openSUSE-SLE-15.6-2024-2630-1.noarch Solution 2: deinstallation of libsemanage1-3.1-150400.1.65.x86_64 Solution 3: deinstallation of shadow-4.8.1-150400.8.57.x86_64 Solution 4: break libsemanage2-3.5-150600.1.48.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1231830] New: golang get target info not working via `go tool dist list`
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231830 Bug ID: 1231830 Summary: golang get target info not working via `go tool dist list` Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: initd(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 Build Identifier: go build cross-platform will need some target info from the current go version, I do local developing on my os runing on VMware, so I into this problem Reproducible: Always Steps to Reproduce: 1. sudo zypper in go 2. go tool dist list Actual Results: go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT Expected Results: aix/ppc64 android/386 android/amd64 android/arm android/arm64 darwin/amd64 darwin/arm64 dragonfly/amd64 freebsd/386 freebsd/amd64 freebsd/arm freebsd/arm64 freebsd/riscv64 illumos/amd64 ios/amd64 ios/arm64 js/wasm linux/386 linux/amd64 linux/arm linux/arm64 linux/loong64 linux/mips linux/mips64 linux/mips64le linux/mipsle linux/ppc64 linux/ppc64le linux/riscv64 linux/s390x netbsd/386 netbsd/amd64 netbsd/arm netbsd/arm64 openbsd/386 openbsd/amd64 openbsd/arm openbsd/arm64 openbsd/ppc64 openbsd/riscv64 plan9/386 plan9/amd64 plan9/arm solaris/amd64 wasip1/wasm windows/386 windows/amd64 windows/arm windows/arm64 I found the same issue on stackoverflow, someone said "When the package are installed on your computer via the package manager, it does not create the git repository associated with those sources." I think so, I think we should solve the problem, I choose the openSUSE because its pkg management edge. https://stackoverflow.com/questions/62498725/go-tool-dist-failed-not-a-git-… https://github.com/initdc/golang-project-workflow/blob/master/get-go-target… -- You are receiving this mail because: You are on the CC list for the bug.

1 2