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