Package: doomsday
Version: 2.3.1+ds1-1+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,


* What led up to the situation?

loading  wad file (doom /doom2/heretic/...)

* What exactly did you do (or not do) that was effective (or

ineffective)?

upgraded libsdl2-2.0-0 (2.28.5+dfsg-3 to 2.30.0+dfsg-1) before spawning doomsday.

* What was the outcome of this action?

segmentation fault :

févr. 04 08:54:11 jupiter kernel: Code: 1d df b0 17 00 48 89 df 48 83 ec
08 e8 ff b8 fc ff 48 8b 3d d0 b0 17 00 e8 23 61 0e 00 48 89 df be ff ff
ff ff e8 e6 b8 fc ff <8b> 7d 08 83 05 ac b0 17 00 01 e8 f7 fd ff ff 48
89 c3 48 85 c0 74
févr. 04 08:54:11 jupiter kernel: doomsday[4521]: segfault at 8 ip 00007fd6534a268a sp 00007ffe8e89e7d0 error 4 in libSDL2-2.0.so.0.3000.0[7fd65346a000+12c000] likely on CPU 0 (core 0,
socket 0)

* What outcome did you expect instead?

start of game.

NB: Downgrading libsdl2-2.0-0 to 2.28.5+dfsg-3 solves issue.



-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages doomsday depends on:
ii doomsday-common 2.3.1+ds1-1+b2
ii doomsday-data 2.3.1+ds1-1
ii libc6 2.37-15
ii libgcc-s1 14-20240201-3
ii libqt5core5a 5.15.10+dfsg-6
ii libqt5gui5 5.15.10+dfsg-6
ii libqt5network5 5.15.10+dfsg-6
ii libqt5widgets5 5.15.10+dfsg-6
ii libsdl2-2.0-0 2.30.0+dfsg-1
ii libsdl2-mixer-2.0-0 2.8.0+dfsg-1
ii libstdc++6 14-20240201-3

Versions of packages doomsday recommends:
ii fluid-soundfont-gm 3.1-5.3

doomsday suggests no packages.

-- no debconf information

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

reassign -1 doomsday,src:libsdl2

Bug #1062969 [doomsday] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Bug reassigned from package 'doomsday' to 'doomsday,src:libsdl2'.
No longer marked as found in versions doomsday/2.3.1+ds1-1.
Ignoring request to alter fixed versions of bug #1062969 to the same values previously set

found -1 doomsday/2.3.1+ds1-1

Bug #1062969 [doomsday,src:libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Marked as found in versions doomsday/2.3.1+ds1-1.

found -1 libsdl2/2.30.0+dfsg-1

Bug #1062969 [doomsday,src:libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Marked as found in versions libsdl2/2.30.0+dfsg-1.

--
1062969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062969
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

clone -1 -2

Bug #1062969 [doomsday,src:libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Bug 1062969 cloned as bug 1065714

reassign -1 libsdl2 2.30.0+dfsg-1

Bug #1062969 [doomsday,src:libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Bug reassigned from package 'doomsday,src:libsdl2' to 'libsdl2'.
No longer marked as found in versions doomsday/2.3.1+ds1-1 and libsdl2/2.30.0+dfsg-1.
Ignoring request to alter fixed versions of bug #1062969 to the same values previously set
Bug #1062969 [libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
There is no source info for the package 'libsdl2' at version '2.30.0+dfsg-1' with architecture ''
Unable to make a source version for version '2.30.0+dfsg-1'
Marked as found in versions 2.30.0+dfsg-1.

reassign -2 doomsday 2.3.1+ds1-1

Bug #1065714 [doomsday,src:libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Bug reassigned from package 'doomsday,src:libsdl2' to 'doomsday'.
No longer marked as found in versions libsdl2/2.30.0+dfsg-1 and doomsday/2.3.1+ds1-1.
Ignoring request to alter fixed versions of bug #1065714 to the same values previously set
Bug #1065714 [doomsday] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Marked as found in versions doomsday/2.3.1+ds1-1.

retitle -1 libsdl2: SDL_JoystickName() doesn't tolerate NULL joystick object since 2.30

Bug #1062969 [libsdl2] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Changed Bug title to 'libsdl2: SDL_JoystickName() doesn't tolerate NULL joystick object since 2.30' from 'doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)'.

retitle -2 doomsday: shouldn't rely on being able to call methods on a NULL SDL object

Bug #1065714 [doomsday] doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)
Changed Bug title to 'doomsday: shouldn't rely on being able to call methods on a NULL SDL object' from 'doomsday: launching doomsday (2.3.1+ds1-1+b2) causes segfault in libsdl2-2.0-0 (2.30.0+dfsg-1)'.

--
1062969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062969
1065714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065714
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Sat, 09 Mar 2024 12:58:23 +0000
with message-id <E1riwHP-005V37-BP@fasolo.debian.org>
and subject line Bug#1062969: fixed in libsdl2 2.30.1+dfsg-2
has caused the Debian Bug report #1062969,
regarding libsdl2: SDL_JoystickName() doesn't tolerate NULL joystick object since 2.30
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1062969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062969
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 4 Feb 2024 08:27:11 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-12.1 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
DKIM_VALID_EF,FOURLA,FREEMAIL_FROM,HAS_PACKAGE,RCVD_IN_DNSWL_NONE,
RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE
autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 32; hammy, 150; neutral, 111; spammy,
0. spammytokens: hammytokens:0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O,
0.000-+--trixie, 0.000-+--sk:taint_u, 0.000-+--sk:TAINT_U
Return-path: <yves.le_berre@orange.fr>
Received: from smtp-22.smtpout.orange.fr ([80.12.242.22]:50319 helo=smtp.smtpout.orange.fr)
by