July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219829] EXT4-fs error (device dm-5) in ext4_mb_clear_bb:6517: error 95
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219829 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ada.lovelace(a)gmx.de, | |marcela.maslanova(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226823 https://bugzilla.suse.com/show_bug.cgi?id=1226823#c14 Antonio Larrosa <alarrosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(werwolf131313@gma | |il.com) --- Comment #14 from Antonio Larrosa <alarrosa(a)suse.com> --- Thanks for the confirmation. Dmitry Markov, can you confirm that the update to wireplumber 0.5.5 fixes the issue for you too? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226103] Regression: Plasma Wayland 6.0.5 panel drag'n'drop broken
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226103 https://bugzilla.suse.com/show_bug.cgi?id=1226103#c11 pallas wept <pallaswept(a)proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #11 from pallas wept <pallaswept(a)proton.me> --- See: https://bugs.kde.org/show_bug.cgi?id=489809 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226103] Regression: Plasma Wayland 6.0.5 panel drag'n'drop broken
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226103 https://bugzilla.suse.com/show_bug.cgi?id=1226103#c10 --- Comment #10 from pallas wept <pallaswept(a)proton.me> --- Great news, others have repro'd this outside of opensuse: https://old.reddit.com/r/kde/comments/1dvoadm/weird_issue_while_moving_icon… Apparently it's a widely known bug and I'm the only one bothering to report it... Closing this in lieu of raising the bug upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226829 https://bugzilla.suse.com/show_bug.cgi?id=1226829#c3 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #3 from Jan Engelhardt <jengelh(a)inai.de> --- gzdoom 4.12.2-3.1 -> 4.12.2-4.1 x86_64 base openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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#c13 --- Comment #13 from Konstantin Voinov <kv(a)kott.no-ip.biz> --- (In reply to Antonio Larrosa from comment #12) > 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? Yes, it was broken on wireplumber-0.5.4+git2.96dc045 After update to 0.5.5 the problem was fixed on my side. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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