October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224773] New: Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 12 Dec '24

12 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Bug ID: 1224773 Summary: Cannot install NVIDIA drivers in latest Aeon RC2 Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sunscape1(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installing NVIDIA drivers in Aeon RC2 (https://en.opensuse.org/SDB:NVIDIA_drivers) fails because the MOK cannot be enrolled after boot. Error during installation using pkg is: SKIP: /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.78-22.1-default.der is not in MokList Without the nvidia-pubkeys folder it is impossible to enroll the MOK or try to enable it after reboot. The key doesn't exist :( -- You are receiving this mail because: You are on the CC list for the bug.

1 38

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

11 Dec '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 6

[Bug 1231795] New: python3-config contains some garbage flags
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231795 Bug ID: 1231795 Summary: python3-config contains some garbage flags Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- OS: openSUSE Tumbleweed 20241016 Version: python311-devel-3.11.10-1.2.x86_64 Observed: $ >x.c; gcc `python3-config --cflags` -c x.c -Wmissing-include-dirs cc1: warning: Vendor/: No such file or directory [-Wmissing-include-dirs] Expected: Don't let -IVendor escape from the python internal build into the python3-config script. Since python3.pc does not have the problem, I wonder if anyone should even ever use python3-config to begin with. Opinions? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1231836] New: [MicroOS]: emergency mode after attempting to mount /.snapshots
by bugzilla_noreply＠suse.com 11 Dec '24

11 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231836 Bug ID: 1231836 Summary: [MicroOS]: emergency mode after attempting to mount /.snapshots Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878122 --> https://bugzilla.suse.com/attachment.cgi?id=878122&action=edit Failing boot During the nightly reboot of one of my MicroOS systems, I am getting intermittent drops into the emergency shell. Rebooting the device helps in most cases, in other cases, a second reboot is needed. I am using /etc/fstab with the following content [1]. In the attachments, one of those failing boots can be observed. The community it seems has this issue also for a good while - https://forums.opensuse.org/t/random-boot-failures-in-microos/176605 [1]: /etc/fstab UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 / btrfs ro 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /usr/local btrfs subvol=/@/usr/local 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /srv btrfs subvol=/@/srv 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /root btrfs subvol=/(a)/root,x-initrd.mount 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /opt btrfs subvol=/@/opt 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /home btrfs subvol=/@/home 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/writable btrfs subvol=/@/boot/writable 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0 UUID=2e79ec65-78e5-4ba4-b549-cc97117e0954 /.snapshots btrfs subvol=/(a)/.snapshots 0 0 UUID=83c66cbc-e40b-4b67-987f-3b41f613932c /var btrfs defaults,x-initrd.mount 0 0 UUID=EEE3-4BD4 /boot/efi vfat utf8 0 2 UUID=1c5adbee-7e1a-471e-9d04-0e583d29d8ec /var/data auto nofail,subvol=/,x-parent=8d06eb2d:af57615e:15d28725:65d23c58 0 0 overlay /etc overlay defaults,lowerdir=/sysroot/var/lib/overlay/168/etc:/sysroot/etc,upperdir=/sysroot/var/lib/overlay/169/etc,workdir=/sysroot/var/lib/overlay/169/work-etc,x-systemd.requires-mounts-for=/var,x-systemd.requires-mounts-for=/sysroot/var,x-initrd.mount 0 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1231566] New: Base:System/dbus-1: Bug Resplit the dbus package.
by bugzilla_noreply＠suse.com 10 Dec '24

10 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231566 Bug ID: 1231566 Summary: Base:System/dbus-1: Bug Resplit the dbus package. Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: simonf.lees(a)suse.com Reporter: fxzxmic(a)hotmail.com QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am curious if there are still wayland software using dbus-launch now. In Fedora, if I execute the following command "dnf provides /usr/bin/dbus-launch", I will only get: "dbus-x11". On Fedora, the dbus package no longer contains any content. So I propose to completely move dbus-launch to dbus-x11. Also, for the dbus-daemon-launch-helper, I think it should be a part of the dbus-daemon. As for rcdbus, it said: "The service command and the rc* symlinks have been deprecated and will be removed in a future release." -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230361] New: scap-security-guide: reproducible builds issue (date)
by bugzilla_noreply＠suse.com 10 Dec '24

10 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230361 Bug ID: 1230361 Summary: scap-security-guide: reproducible builds issue (date) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: rumen.chikov(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com Blocks: 1047218 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our scap-security-guide varied in each build, even when varying as little as possible. This is because, there is a build date+time embedded in the output: --- old//usr/share/scap-security-guide/tailoring/rhel8_stig_delta_tailoring.xml 2024-09-02 13:58:51.000000000 +0000 +++ new//usr/share/scap-security-guide/tailoring/rhel8_stig_delta_tailoring.xml 2024-09-02 13:58:51.000000000 +0000 @@ -1,4 +1,4 @@ -<xccdf-1.2:Tailoring xmlns:xccdf-1.2="http://checklists.nist.gov/xccdf/1.2" id="xccdf_content-disa-delta_tailoring_default"><xccdf-1.2:version time="2024-09-06T15:14:18.947277+00:00">1</xccdf-1.2:version><xccdf-1.2:Profile id="xccdf_org.ssgproject.content_profile_stig_delta_tailoring" extends="xccdf_org.ssgproject.content_profile_stig"><xccdf-1.2:title override="true">DISA STIG for Red Hat Enterprise Linux 8</xccdf-1.2:title> +<xccdf-1.2:Tailoring xmlns:xccdf-1.2="http://checklists.nist.gov/xccdf/1.2" id="xccdf_content-disa-delta_tailoring_default"><xccdf-1.2:version time="2024-09-06T15:15:45.696526+00:00">1</xccdf-1.2:version><xccdf-1.2:Profile id="xccdf_org.ssgproject.content_profile_stig_delta_tailoring" extends="xccdf_org.ssgproject.content_profile_stig"><xccdf-1.2:title override="true">DISA STIG for Red Hat Enterprise Linux 8</xccdf-1.2:title> If timestamps cannot be dropped, they should use $SOURCE_DATE_EPOCH https://reproducible-builds.org/docs/source-date-epoch/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226763] New: Missing non-oss source repo for aarch64
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226763 Bug ID: 1226763 Summary: Missing non-oss source repo for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We have a source repo for non-oss ports on s390x and ppc but not on arm we can either add it for Arm, or drop it for others guillaume_g As it exists for x86_64, I guess we should publish it for :ARM as well https://download.opensuse.org/source/tumbleweed/repo/non-oss/ (using patterns component so it ends on rel-eng) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223794] New: VUL-0: CVE-2023-46565: TRACKERBUG: gobgp: buffer overflow via handlingError() function in pkg/server/fsm.go
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223794 Bug ID: 1223794 Summary: VUL-0: CVE-2023-46565: TRACKERBUG: gobgp: buffer overflow via handlingError() function in pkg/server/fsm.go Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/403566/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: asarai(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, qa-bugs(a)suse.de, screening-team-bugs(a)suse.de, smash_bz(a)suse.de Blocks: 1223793 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1223793 +++ Buffer Overflow vulnerability in osrg gobgp commit 419c50dfac578daa4d11256904d0dc182f1a9b22 allows a remote attacker to cause a denial of service via the handlingError function in pkg/server/fsm.go. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-46565 https://www.cve.org/CVERecord?id=CVE-2023-46565 https://github.com/osrg/gobgp/issues/2725 https://bugzilla.redhat.com/show_bug.cgi?id=2278569 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1230496] New: Intel Tiger Lake-H HD Audio - no sound from laptop speakers
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230496 Bug ID: 1230496 Summary: Intel Tiger Lake-H HD Audio - no sound from laptop speakers Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: alisia.prince(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877303 --> https://bugzilla.suse.com/attachment.cgi?id=877303&action=edit alsa-info with legacy driver loaded No sound on fresh install of Slowroll: System Dell x15r1 laptop with NVIDIA and Intel GPUs. There is a known issue with the NVIDIA drivers and sound and I made those adjustments based on the following instructions: https://www.reddit.com/r/openSUSE/comments/1aklnpe/no_audio_after_installin… This did not resolve my issue. I installed the upstream firmware and it didn't resolve my issue. http://download.opensuse.org/repositories/multimedia:/libs/15.6/noarch/ I configured for the legacy sound card and I have sound now. Bluetooth earbuds work. Attached is my inxi -Aa output and the alsa-info file. I have only one file in /etc/modprobe.d and it's empty - the file is 50-yast.conf -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1216919] New: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1216919 Bug ID: 1216919 Summary: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have upgrade to Leap 15.4 to find my dkimproxy setup broken. I noticed the following things: 1. there was one dkimproxy service, now there are two dkimproxy-in and dkimproxy-out. The new services are disabled even though the old one was enabled 2. The dkimproxy_in.service file references the /run/sysconfig/dkimproxy environment file 2a. The dkimproxy_env.sh script is supposed to create that file, but /run/sysconfig is not created at all to that script fails 2b. The dkimproxy_env.sh sets "HFQHN=$( hostname -f )" dkimproxy-in.service uses --hostname=${FQHN} While problem 1 is a one-time fix, the problems from 2 are more persistent and are ideally solved in the package. Note: systemd integration was contributed in bug #1116007 -- You are receiving this mail because: You are on the CC list for the bug.

1 6