Waiting for background jobs to finish on exit

[k561]

$ ble summary
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu) [Linux Mint 22.1]
ble.sh, version 0.4.0-devel4+8060b7a (noarch) [git 2.43.0, GNU Make 4.3, GNU Awk 5.2.1, API 3.2, PMA Avon 8-g1, (GNU MPFR 4.2.1, GNU MP 6.3.0)]
bash-completion, version 2.11 (hash:9abb523dbcb688e7fae4b87f5fc9d155b658d9ba, 76898 bytes) (noarch)
locale: LANG=en_EN.UTF-8
terminal: TERM=xterm wcwidth=15.0-west/16.0-2+ri, kitty:0 (1;4000;32)
options: +extglob +histappend -hostcomplete +inherit_errexit

$ echo $bleopt_allow_exit_with_jobs
yes
$ sleep 20 &
[1] 74760
$ exit

The allow_exit_with_jobs setting doesn’t work. When it’s enabled, ble.sh stops showing the message “There are remaining jobs,” but it still waits for background jobs to finish before exiting.

[akinomyoga]

The program waiting for sleep is likely the terminal, but not the shell. Even if the shell terminates immediately, the sleep prpcess remains. Then, the terminal waits for the process to terminate before closing the terminal window.

Is the problem specific to ble.sh? What is the behavior when you don't source ble.sh?

[k561]

sleep is used here as an example, since it’s the simplest one. You could run, for instance, firefox& — the reaction would be the same.
If I comment out ble.sh in .bashrc, the problem goes away.

[akinomyoga]

sleep is used here as an example, since it’s the simplest one. You could run, for instance, firefox& — the reaction would be the same.

Yes, my explanation above isn't specific to sleep. The same explanation applies to firefox, and the expected behavior should be the same with firefox. As far as the terminal waits for processes, even without ble.sh, the terminal window doesn't close until firefox & ends.

If I comment out ble.sh in .bashrc, the problem goes away.

At least, in my environment, loading or disabling ble.sh doesn't change the behavior of the terminals. There are two types of terminals; one is the type of terminals that close the window immediately when the shell process terminates. The other is the type of terminals that wait for any processes keeping file descriptors of the TTY. In the former type of terminals in my environment, even with ble.sh, the terminal closes immediately after sleep 10 & exit. In the latter type of terminals in my environment, even without ble.sh, the terminal waits for sleep 10 & to terminate.

To check the behavior in a closer environment, I installed kitty in Linux Mint 22 in my virtual machine. However, the terminal window doesn't close even without ble.sh until sleep 10 & finishes. I also checked the behavior with firefox &, but the terminal window doesn't close even without ble.sh until I close Firefox.

Maybe Firefox in Linux Mint 22 in my virtual machine is old. I only use virtual machines for testing purposes, and I usually don't use Linux Mint 22 in the virtual machine, so I haven't updated the virtual machine for a long time. I'll try again after finishing sudo apt upgrade.

[akinomyoga]

I completed the update of Linux Mint 22 in the virtual machine and tried these again.

Even without ble.sh being loaded, the reported behavior reproduces within kitty. The kitty terminal doesn't close the window until sleep 10 terminates, even without ble.sh. The behavior is the same with firefox; the kitty terminal doesn't close the window until Firefox is closed.

It should be noted that whether the terminal waits for the remaining processes depends on the terminal, so the terminal window may immediately close in another terminal (in both cases with and without ble.sh being loaded). For example, GNOME terminal immediately closes the terminal window even with remaining processes like sleep 10 or firefox, in both cases with and without ble.sh.

@k561 You've reported that the problem goes away without ble.sh, but that seems strange to me, and also, I cannot reproduce the problem in my environment, kitty with Linux Mint 22.1 in a virtual machine. I'm currently unsure about what causes the behavioral differences between yours and mine:

• One possibility could be that the software versions are different.
  • Is your system up to date? @k561 Could you update your system with sudo apt update & sudo apt upgrade to make it in the latest state?
  • Which version of kitty do you use? I'm using kitty installed with sudo apt install kitty. @k561 If you installed kitty independent of the system package, could you provide me with the details?
• Another possibility could be that you used a different terminal to check the behavior without ble.sh. @k561 Could you check if the problem really goes away without ble.sh in the kitty terminal?