Nested mutter makes sway exit on ctrl-c

[krobelus]

• sway.log

• Configuration file: none

Steps to reproduce:

0. install mutter
1. run sway from the Linux console
   • alternatively, run weston
2. type super-enter to spawn a terminal (i.e. foot)
3. run mutter --nested and close it with super-shift-q or (ctrl-c in the terminal)
   • alternatively, run mutter --nested foot and run exit to close mutter
   • alternatively, run mutter -- it will fail to start but trigger the same symptoms
4. press ctrl-c anywhere

This makes sway/weston exit unexpectedly.
It does not happen when running mutter --nested inside a Gnome session.

[emersion]

Sounds like Sway is explicitly asked to exit (perhaps via a signal):

00:00:13.100 [INFO] [sway/main.c:377] Shutting down sway

[krobelus]

yeah gdb shows sway gets SIGINT from ctrl-c (even if I press ctrl-c when there is no graphical terminal etc.).
Feels like mutter gives ownership of the PTY back to the Linux Console instead of Sway.

Likely a mutter issue ( https://gitlab.gnome.org/GNOME/mutter/-/issues/4020 ),
I'll dig some more and close this. I assume it's easily reproducible

[krobelus]

one workaround is setsid sway

$ ps -eo comm,args,pid,pgid,sid | grep -E 33605
sway            sway                          33605   33605   33605

Whereas with the original reproduction (sway in the interactive shell) it looks like

$ ps -eo comm,args,pid,pgid,sid | grep -E '34429|791'
sway            sway                          34429   34429     791
bash            -bash                           791     791     791

I'll try to find out why sway (launched from an interactive shell in the Linux TTY) doesn't get killed by ctrl-c. Maybe the same mechanism can be used here.