SIGUSR1 kills kitty terminal

[hafeoz]

Describe the bug
Signaling SIGUSR1 will kill kitty terminal, even with a empty config

To Reproduce
Steps to reproduce the behavior:

1. kitty --config NONE
2. killall -s SIGUSR1 kitty
3. kitty terminates with "User defined signal 1"

Environment details

kitty 0.24.1 created by Kovid Goyal
Linux rbq 5.16.4-arch1-1 #1 SMP PREEMPT Sat, 29 Jan 2022 19:08:13 +0000 x86_64
Arch Linux 5.16.4-arch1-1 (/dev/tty)

Running under:Wayland
Frozen: False
Paths:
  kitty: /usr/bin/kitty
  base dir: /usr/lib/kitty
  extensions dir: /usr/lib/kitty/kitty
  system shell: /bin/bash

Config options different from defaults:

[kovidgoyal]

Does not reproduce for me on Linux, with current kitty.

[hafeoz]

I did some testing and it seems to be related to wayland: when running unset WAYLAND_DISPLAY before starting kitty, kitty will capture SIGUSR1 and behave normally. If started using WAYLAND_DISPLAY="wayland-1" kitty, then kitty will exit when SIGUSR1 is received.

[hafeoz]

If specifying linux_display_server x11 in the configuration file, then the kitty will run normally. It's definitely caused by some code specific to wayland.

[hafeoz]

Strange... I used this script to check which the signal is captured (blocked) and it indicates that SIGUSR1 is actually used by kitty under wayland but somehow it's still triggering a exit.

Output of bash check_sig.sh PID_OF_KITTY_UNDER_WAYLAND:

SigPnd:
SigBlk: INT(2) USR1(10) TERM(15) CHLD(17)
SigIgn: PIPE(13) XFSZ(25)
SigCgt: INT(2) (32) (33)

[hafeoz]

It's now getting even more strange... the build I downloaded from github release page works, but the binary distributed by Arch Linux doesn't.

[kovidgoyal]

Report it to arch then. SIGUSR1 is used by kitty to reload its config
file.

[cenunix]

I'm still noticing this issue on Wayland , was wondering if there is a possible workaround? SIGUSR1 signal just kills kitty, I tried one of the releases on github instead of installing kitty with pacman. However still ran into the same issue.

[kovidgoyal]

Does not replicate for me with

kill -SIGUSR1 $KITTY_PID

in wayland or x11.

[cenunix]

I'm using Hyprland on wayland, this is the only message I see when running the above command "kill -SIGUSR1 $KITTY_PID"

zsh: user-defined signal 1 kitty

here is my kitty config:
window_padding_width 30
font_size 14
font_family JetBrainsMono Nerd Font
bold_font auto
italic_font auto
bold_italic_font auto
confirm_os_window_close 1
enable_audio_bell no
allow_remote_control yes

[kovidgoyal]

Yes, works fine for me on Hyprland. In any case the window manager has
no effect on how kityt handles SIGUSR1

[cenunix]

what distribution are you currently running? I'm on arch personally

[kovidgoyal]

So am I.

[cenunix]

What would be the next step for me to understand if there is a possible error on my end? is there a logfile I could attach here after sending SIGUSR1 signal?