July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226823] bluetooth earphones fail
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226823 https://bugzilla.suse.com/show_bug.cgi?id=1226823#c12 --- Comment #12 from Antonio Larrosa <alarrosa(a)suse.com> --- What version of pipewire and wireplumber are you using? There was a bluetooth related fix in wireplumber 0.5.5 which was submitted 3 days ago to TW. If you're not using that version, can you update and test it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218788] sdl_bomber package broken installation.
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1218788 https://bugzilla.suse.com/show_bug.cgi?id=1218788#c2 hui <sturm-fr(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from hui <sturm-fr(a)web.de> --- Fixed with sdl_bomber-1.0.4-2.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226829] New: gzdoom segmentation fault
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226829 Bug ID: 1226829 Summary: gzdoom segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: epg(a)pretzelnet.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0 Build Identifier: Run gzdoom without arguments or with any normal arguments as I normally would, e.g. 'gzdoom -iwad ~/doom/DOOM2.WAD -skill 3 -file Utopia.wad -record Utopia'. Reproducible: Always Steps to Reproduce: 1. gzdoom Actual Results: *** Fatal Error *** !!! Failed to exec debug process zsh: segmentation fault (core dumped) gzdoom % gdb /usr/bin/gzdoom gzdoom-16267-1719180269.core (gdb) bt #0 0x00007fcaba0949dc in __pthread_kill_implementation () at /lib64/libc.so.6 #1 0x00007fcaba041176 in raise () at /lib64/libc.so.6 #2 0x000055fafe140ca7 in crash_catcher (signum=11, siginfo=<optimized out>, context=<optimized out>) at /usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/crashcatcher.c:254 #3 0x00007fcaba041240 in <signal handler called> () at /lib64/libc.so.6 #4 0x00007fcaba17ff6c in __strlen_evex () at /lib64/libc.so.6 #5 0x00007fcaba0643e1 in __printf_buffer () at /lib64/libc.so.6 #6 0x00007fcaba0649f9 in __vfprintf_internal () at /lib64/libc.so.6 #7 0x00007fcaba059ecf in printf () at /lib64/libc.so.6 #8 0x000055fafe118899 in main (argc=1, argv=0x7ffcaeb7df68) at /usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/i_main.cpp:158 (gdb) frame 8 #8 0x000055fafe118899 in main (argc=1, argv=0x7ffcaeb7df68) at /usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/i_main.cpp:158 158 printf(GAMENAME" %s - %s - SDL version\nCompiled on %s\n", Expected Results: gzdoom runs % rpm -qi gzdoom Name : gzdoom Version : 4.12.2 Release : 3.1 Architecture: x86_64 Install Date: Mon Jun 3 18:40:25 2024 Group : Amusements/Games/3D/Shoot Size : 28312984 License : GPL-3.0-only Signature : RSA/SHA512, Mon May 27 05:09:27 2024, Key ID 35a2f86e29b700a4 Source RPM : gzdoom-4.12.2-3.1.src.rpm Build Date : Fri May 17 17:04:47 2024 Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://zdoom.org/ Summary : A DOOM source port with graphic and modding extensions Description : GZDoom is a port (a modification) of the original Doom source code, featuring: * an OpenGL renderer, HQnX/xBRZ rescaling, 3D floor and model support * Truecolor software rendering, extending the classic 8-bit palette * Heretic, Hexen and Strife game modes and support for a lot of additional IWADs. * Boom and Hexen map extension support, scriptability with ACS and ZScript, and various modding features regarding actors and scenery. * Demo record/playback of classic and Boom demos is not supported. Distribution: openSUSE Tumbleweed % rpm -qi openSUSE-release Name : openSUSE-release Version : 20240621 Release : 2966.1 Architecture: x86_64 Install Date: Sat Jun 22 09:32:45 2024 -- 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 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c10 --- Comment #10 from Enzo Matsumiya <ematsumiya(a)suse.com> --- I've pushed the fix to our internal branches, Leap 15.6 should get it on next maintenance update. If anyone wants to build + test the fixed kernel, please let me know so I push it to a public branch. Meanwhile use the 'nohandlecache' mount option as a workaround, which should have little to no side effects (aside from some performance loss). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220520] New: Configure remote printer: does not disable local cups entirely
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220520 Bug ID: 1220520 Summary: Configure remote printer: does not disable local cups entirely Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: All Status: NEW Severity: Minor Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: bnacht(a)web.de QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Fresh installed Leap; Configure a remote printer; Get the message that the local cups will be disabled -> OK; But after that I get the message that the local cups is running again. It looks like YaST does only disable cups.service; cups.socket and cups.path, but not stop them (missing --now ?) After I stop the three units the config was successful. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1187317] libssh2_org build failed with autoconf 2.71
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1187317 https://bugzilla.suse.com/show_bug.cgi?id=1187317#c3 Holger Bruenjes <holgerbruenjes(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #3 from Holger Bruenjes <holgerbruenjes(a)gmx.net> --- resolved upstream years ago -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187317] libssh2_org build failed with autoconf 2.71
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1187317 https://bugzilla.suse.com/show_bug.cgi?id=1187317#c2 --- Comment #2 from Holger Bruenjes <holgerbruenjes(a)gmx.net> --- I wrote this bug report 3 years ago for version 1.9.0, now there is version 1.11.0. I also write that the fix is upstream. Thanks Holger -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c9 --- Comment #9 from Jonas Groß <gross.jonas(a)gmail.com> --- I don't know the other side - it's in a corporate environment and my google-foo would not let me find how to find that information client side. But I tried adding 'nohandlecache' to the mount options and it didn't lock up since then. If you can point me to some tutorial or some other guidance I am happy to provide further info. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227393] New: VUL-0: CVE-2024-39844: znc: arbitrary code embedded into the kick reason executed while kicking someone on a channel
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227393 Bug ID: 1227393 Summary: VUL-0: CVE-2024-39844: znc: arbitrary code embedded into the kick reason executed while kicking someone on a channel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412810/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mpluskal(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: --- In ZNC before 1.9.1, remote code execution can occur in modtcl via a KICK. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39844 https://seclists.org/oss-sec/2024/q3/23 https://github.com/znc/znc/commit/8cbf8d628174ddf23da680f3f117dc54da0eb06e https://www.cve.org/CVERecord?id=CVE-2024-39844 https://github.com/znc/znc/releases/tag/znc-1.9.1 https://wiki.znc.in/Category:ChangeLog https://wiki.znc.in/ChangeLog/1.9.1 http://www.openwall.com/lists/oss-security/2024/07/03/9 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c8 --- Comment #8 from Enzo Matsumiya <ematsumiya(a)suse.com> --- Thanks for confirming. I checked if I was using 'nohandlecache' on my test systems and I wasn't. So the problem is in my build system, that I'm still puzzled as I can't reproduce the bug with my self-built kernel. I'm suspecting probably some kernel config, but will update the bug once I get the fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0