Open Apteryks opened 1 year ago
Can you test whether this happens with a minimal wxWidgets (C++) application (e.g., the minimal sample)?
Yes, it happens as well with wxWidgets:
~/src/wxWidgets/mybuild$ guix shell --container --network --preserve=XAUTHORITY --expose=/gnu --expose=$XAUTHORITY --preserve=DISPLAY -- samples/minimal/minimal
(minimal:1): dbind-WARNING **: 20:42:25.343: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: No such file or directory
^C
^C^C^C
^C^C
^C^C
[frame still displayed]
Describe the bug: A minimal application (the hello world one from https://wiki.wxpython.org/Getting%20Started#A_First_Application:_.22Hello.2C_World.22 will suffice) cannot be interrupted via SIGINT (Ctrl-C from the parent process) when launched non-interactively in a containerized environment.
Expected vs observed behaviour: When not using a container, the application can be interrupted just fine with CTRL-C (later abbreviated C-c), as shown in this example:
When ran inside a Linux container though, it doesn't work anymore:
It hangs up until the main application window is closed via the window manager.
I'd expect C-c to be able to interrupt the application in both situations, as it works with other applications.
Platform and version information
Tested with Guix at commit deda3cc9057f20b1e3d34d63a64da0bdd6ca1998 which has
python-wxpython
at version 4.2.0 andpython
at version 3.10.7 on my Guix System GNU/Linux distribution.