Bug#1123953: angband: SDL2 frontend won't start with sdl2-compat: This process is currently running setuid or setgid

[Simon McVittie]

Package: angband,libsdl2-compat
Control: found -1 angband/1:4.2.5+dfsg1-3
Severity: normal
Tags: forky sid
User: sdl2-compat at packages.debian.org
Usertags: regression setgid
Forwarded: https://github.com/libsdl-org/sdl2-compat/issues/564

sdl2-compat is a reimplementation of the SDL 2 API using SDL 3. 
It can be tested by installing the libsdl2-compat-shim and 
libsdl2-compat-dev packages from testing/unstable, or by installing the 
libsdl2-2.0-0 and libsdl2-dev packages built by src:sdl2-compat in 
experimental.

After discussion with SDL upstream, I'm looking into what needs to 
happen for Debian (and indirectly Ubuntu) to replace "classic" SDL2 
(src:libsdl2) with sdl2-compat, following in the footsteps of other 
distros like Arch and Fedora that have already done this transition.

When using sdl2-compat, angband doesn't start, because angband is 
setgid, SDL 3 uses GTK for "tray icon" support, and GTK specifically 
doesn't support being run setuid/setgid:

>$ angband -msdl2
>
>(process:624673): Gtk-WARNING **: 18:12:37.294: This process is currently running setuid or setgid.
>This is not a supported use of GTK+. You must create a helper
>program instead. For further details, see:
>
>    http://www.gtk.org/setuid.html
>
>Refusing to initialize GTK+.

A workaround is to depend on libsdl2-classic and run as:

    SDL_DYNAMIC_API='/usr/$LIB/sdl2-classic/libSDL2-2.0.so.0' angband -msdl2

although I've confirmed that this still suffers from #1121870 (not a 
regression, it seems that bug was already present with "classic" SDL2).

I've raised this with SDL upstream in 
https://github.com/libsdl-org/sdl2-compat/issues/564 and will see what 
they say.

    smcv