July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227116] New: osinfo still uses deprecated SL-Micro name
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227116 Bug ID: 1227116 Summary: osinfo still uses deprecated SL-Micro name 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The osinfo-query os programm still uses the deprecated SL-Micro nomenclature > osinfo-query os | grep -i slm6 > slm6.0 | SUSE Linux Micro 6.0 | 6.0 | http://suse.com/slm/6.0 This affects then also applications like virt-manager. Since the name of SL-Micro 6.0 has been renamed back to SLEM 6.0, this should also display it similar to previous SLEM versions: > slem5.0 | SUSE Linux Enterprise Micro | 5.0 | http://suse.com/slem/5.0 > slem5.1 | SUSE Linux Enterprise Micro 5.1 | 5.1 | http://suse.com/slem/5.1 > slem5.2 | SUSE Linux Enterprise Micro 5.2 | 5.2 | http://suse.com/slem/5.2 > slem5.3 | SUSE Linux Enterprise Micro 5.3 | 5.3 | http://suse.com/slem/5.3 > slem5.4 | SUSE Linux Enterprise Micro 5.4 | 5.4 | http://suse.com/slem/5.4 > slem5.5 | SUSE Linux Enterprise Micro 5.5 | 5.5 | http://suse.com/slem/5.5 Here it should be listed als `slem6.0`. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227194] ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|palcantara(a)suse.com | Assignee|kernel-bugs(a)opensuse.org |ematsumiya(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227312] New: LUKS disk decryption fails
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227312 Bug ID: 1227312 Summary: LUKS disk decryption fails Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875840 --> https://bugzilla.suse.com/attachment.cgi?id=875840&action=edit Log of the failure I selected an existing LUKS encrypted disk for installing Aeon, and received an error that the decryption failed. Works fine to decrypt on startup, etc. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218458] New: zombie process "nvidia-settings" generated by the file .nvidia-settings-rc
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1218458 Bug ID: 1218458 Summary: zombie process "nvidia-settings" generated by the file .nvidia-settings-rc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: H.H.Albert(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- .nvidia-settings-rc creates a zombie process on opensuse leap 15.5. If the .nvidia-settings-rc file is located in the $HOME directory of the user, the process table contains a zombie process. 16912 ? Z 0:00 [*nvidia*-settings] <defunct> Harware: *~ #* lspci | grep VGA 01:00.0 *VGA* compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] (rev a1) *~ #* lscpu | grep Arch Architecture: x86_64 *~ #* hwinfo --gfxcard | grep Model *Model*: "nVidia TU116 [GeForce GTX 1660 Ti]" *~ #* hwinfo --arch Arch: X86_64/grub Desktop Environment KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.39-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227309] New: VUL-0: CVE-2024-37298: distrobuilder: gorilla/schema: potential memory exhaustion due to sparse slice deserialization
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227309 Bug ID: 1227309 Summary: VUL-0: CVE-2024-37298: distrobuilder: gorilla/schema: potential memory exhaustion due to sparse slice deserialization Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412571/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: containers-bugowner(a)suse.de 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: --- gorilla/schema converts structs to and from form values. Prior to version 1.4.1 Running `schema.Decoder.Decode()` on a struct that has a field of type `[]struct{...}` opens it up to malicious attacks regarding memory allocations, taking advantage of the sparse slice functionality. Any use of `schema.Decoder.Decode()` on a struct with arrays of other structs could be vulnerable to this memory exhaustion vulnerability. Version 1.4.1 contains a patch for the issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-37298 https://www.cve.org/CVERecord?id=CVE-2024-37298 https://github.com/gorilla/schema/blob/main/decoder.go#L223 https://github.com/gorilla/schema/commit/cd59f2f12cbdfa9c06aa63e425d1fe4a80… https://github.com/gorilla/schema/security/advisories/GHSA-3669-72x9-r9p3 https://bugzilla.redhat.com/show_bug.cgi?id=2295010 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223989] New: Please update out-of-date cyrus IMAP
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223989 Bug ID: 1223989 Summary: Please update out-of-date cyrus IMAP Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently, it looks like Cyrus IMAP is stuck on version 2.4. The current stable version is 3.10. Version 2.4 is left over from when development was done at CMU, which has not been the case for quite a while. Is it possible to offer version 3.10? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214373] Network installer image's "Loading Installation System" does atrocious job at loading it for me
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1214373 https://bugzilla.suse.com/show_bug.cgi?id=1214373#c5 --- Comment #5 from ell1e <el(a)horse64.org> --- That sounds promising, I'm curious if that one will cover this use case better. I'm hoping you're not dropping the network installer altogether, it is useful. I'd be interested in testing once a new network installer is available. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226676] Installation: kdump reports an error if systemd-boot has been selected for bootloader
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226676 https://bugzilla.suse.com/show_bug.cgi?id=1226676#c6 Jiri Bohac <jbohac(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Jiri Bohac <jbohac(a)suse.com> --- (In reply to Stefan Hundhammer from comment #3) > AFAICS /etc/sysconfig/kdump is generated with some fillup-template. In this > case, obviously this does not work. "obviously" meaning you understand why? Or you just see it didn't? :) Because I don't understand why it does not work. > So the first thing to do would be to > ensure that there is ALWAYS an /etc/sysconfig/kdump if the kdump package > needs it so desperately. It doesn't need it. If it does not exist, it still works, using default values. The error message "/usr/lib/kdump/kdump-read-config.sh: line 144: /etc/sysconfig/kdump: No such file or directory" is misleading and I just fixed it: https://github.com/openSUSE/kdump/commit/0d1cd2c6b21f875d6ad9c6a97df20ff946… The real problem is the other error message: "Kernel not found." By deafult kdump expects a /boot/vmlinuz symlink to exist, seems to not be the case here... investigating why. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227304] open build service raises 'Failed build dependencies' when new BuildRequires tag added to the .spec file by the _service during runtime, instead installing build requirements
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227304 https://bugzilla.suse.com/show_bug.cgi?id=1227304#c2 Adrian Schröter <adrian.schroeter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Adrian Schröter <adrian.schroeter(a)suse.com> --- yes, it is too late to do that at build time. The VM has no network and the dependencies can not pre-calculated. Either do that in default mode, so the change gets commited to the source. Alternative is to use dynamic build dependency implementation where another build job gets started in case dependencies are changing. That is a generic rpm feature, supported by OBS by respawning a new job. https://fedoraproject.org/wiki/Changes/DynamicBuildRequires closing as works as designed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201784] switch_to_fb linuxrc option duplicates kernel functionality
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1201784 https://bugzilla.suse.com/show_bug.cgi?id=1201784#c10 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|CONFIRMED |RESOLVED --- Comment #10 from Steffen Winterfeldt <snwint(a)suse.com> --- I've only seen reports where people expect the option to be there (in SLE15 it's not on per default). So, I will keep it as is. Also, in view that Agama is the future, optimizing for corner cases of the old linuxrc/YaST combo is maybe not worth the effort. -- You are receiving this mail because: You are on the CC list for the bug.

1 0