August 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 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 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

[Bug 1223697] New: VUL-0: CVE-2023-26793: libmodbus: heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c.
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223697 Bug ID: 1223697 Summary: VUL-0: CVE-2023-26793: libmodbus: heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403923/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- libmodbus v3.1.10 has a heap-based buffer overflow vulnerability in read_io_status function in src/modbus.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26793 https://www.cve.org/CVERecord?id=CVE-2023-26793 https://github.com/stephane/libmodbus/issues/683 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1224062] New: VUL-0: CVE-2024-34244: libmodbus: buffer overflow via the modbus_write_bits function
by bugzilla_noreply＠suse.com 08 Dec '24

08 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224062 Bug ID: 1224062 Summary: VUL-0: CVE-2024-34244: libmodbus: buffer overflow via the modbus_write_bits function Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/404865/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- libmodbus v3.1.10 is vulnerable to Buffer Overflow via the modbus_write_bits function. This issue can be triggered when the function is fed with specially crafted input, which leads to out-of-bounds read and can potentially cause a crash or other unintended behaviors. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-34244 https://www.cve.org/CVERecord?id=CVE-2024-34244 https://github.com/stephane/libmodbus/issues/743 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226986] New: Valkey migration enables bogus valkey@basename services
by bugzilla_noreply＠suse.com 07 Dec '24

07 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226986 Bug ID: 1226986 Summary: Valkey migration enables bogus valkey@basename services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I never had a "redis@basename" instance! Yet after todays dup to 20240624 which replaced redis with valkey-7.2.5-2.1.x86_64 the migration logic enabled these bogus services, which naturally failed during boot: ``` ~> ll /etc/systemd/system/multi-user.target.wants/valkey* lrwxrwxrwx 1 root root 39 Jun 26 08:10 '/etc/systemd/system/multi-user.target.wants/valkey(a)basename.service' -> '/usr/lib/systemd/system/valkey@.service' lrwxrwxrwx 1 root root 48 Jun 26 08:10 '/etc/systemd/system/multi-user.target.wants/valkey-sentinel(a)basename.service' -> '/usr/lib/systemd/system/valkey-sentinel@.service' ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1227527] New: Failed to start Valkey Sentinel instance: basename
by bugzilla_noreply＠suse.com 07 Dec '24

07 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227527 Bug ID: 1227527 Summary: Failed to start Valkey Sentinel instance: basename Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- after update of Tumbleweed, I suddenly see following error: Starting libvirt QEMU daemon... [ OK ] Finished Permit User Sessions. Starting X Display Manager... Starting Hold until boot process finishes up... [FAILED] Failed to start Valkey Sentinel instance: basename. See 'systemctl status valkey-sentinel(a)basename.service' for details. [FAILED] Failed to start Valkey instance: basename. See 'systemctl status valkey(a)basename.service' for details. Starting Valkey Sentinel instance: basename... Starting Valkey instance: basename... [FAILED] Failed to start Valkey Sentinel instance: basename. See 'systemctl status valkey-sentinel(a)basename.service' for details. [FAILED] Failed to start Valkey instance: basename. See 'systemctl status valkey(a)basename.service' for details. [ OK ] Started NTP client/server. [ OK ] Reached target System Time Synchronized. [ OK ] Started Backup of RPM database. [ OK ] Started Backup of /etc/sysconfig. [ OK ] Started Balance block groups on a btrfs filesystem. [ OK ] Started Scrub btrfs filesystem, verify block checksums. [ OK ] Started Check if mainboard battery is Ok. [ OK ] Started Discard unused filesystem blocks once a week. [ OK ] Started Daily rotation of log files. [ OK ] Started Daily man-db regeneration. [ OK ] Started Timeline of Snapper Snapshots. [ OK ] Started daily update of the root trust anchor for DNSSEC. [ OK ] Reached target Timer Units. [ OK ] Started Command Scheduler. Starting Valkey Sentinel instance: basename... Starting Valkey instance: basename... [ OK ] Started OpenSSH Daemon.zaoliang@dell-5320:/var/log> systemctl status valkey-sentinel(a)basename.service × valkey-sentinel(a)basename.service - Valkey Sentinel instance: basename Loaded: loaded (/usr/lib/systemd/system/valkey-sentinel@.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Mon 2024-07-08 18:53:01 CEST; 1min 13s ago Process: 1449 ExecStart=/usr/bin/valkey-sentinel /etc/valkey/sentinel-basename.conf (code=exited, status=1/FAILURE) Main PID: 1449 (code=exited, status=1/FAILURE) CPU: 50ms Warning: some journal files were not opened due to insufficient permissions. zaoliang@dell-5320:/var/log> sudo systemctl status valkey-sentinel(a)basename.service × valkey-sentinel(a)basename.service - Valkey Sentinel instance: basename Loaded: loaded (/usr/lib/systemd/system/valkey-sentinel@.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Mon 2024-07-08 18:53:01 CEST; 1min 32s ago Process: 1449 ExecStart=/usr/bin/valkey-sentinel /etc/valkey/sentinel-basename.conf (code=exited, status=1/FAILURE) Main PID: 1449 (code=exited, status=1/FAILURE) CPU: 50ms Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel(a)basename.service: Scheduled restart job, restart counter is at 5. Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel(a)basename.service: Start request repeated too quickly. Jul 08 18:53:01 dell-5320 systemd[1]: valkey-sentinel(a)basename.service: Failed with result 'exit-code'. Jul 08 18:53:01 dell-5320 systemd[1]: Failed to start Valkey Sentinel instance: basename. zaoliang@dell-5320:/var/log> sudo systemctl restart valkey-sentinel(a)basename.service Job for valkey-sentinel(a)basename.service failed because the control process exited with error code. See "systemctl status valkey-sentinel(a)basename.service" and "journalctl -xeu valkey-sentinel(a)basename.service" for details. [FAILED] Failed to start Valkey Sentinel instance: basename. -- zaoliang@dell-5320:/var/log> cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240704" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240704" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240704:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240704" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 07 Dec '24

07 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed:<br/><br/>[...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1227364] New: trackerbug: packages build differently without %check
by bugzilla_noreply＠suse.com 07 Dec '24

07 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227364 Bug ID: 1227364 Summary: trackerbug: packages build differently without %check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1081754 Target Milestone: --- Found By: Development Blocker: --- The %check section in a .spec file runs scripts that may modify the package output. Some packages fail to build with osc build --nocheck and some others produce different build results. Both of these cases make reproducible-builds harder and are considered bugs. -- You are receiving this mail because: You are on the CC list for the bug.

1 3