The application is connected in two ways: to bash, and to the terminal.

The connection to the terminal is that the standard streams (stdin, stdout and stderr) of the application are connected to the terminal. Typical GUI applications don't use stdin or stdout, but they might emit error messages to stderr.

The connection to the shell is that if you started the application with foo &, it remains known to the shell as a job, as explained in Difference between nohup, disown and &. When you close the terminal, the shell receives a SIGHUP, which it propagates to its jobs. When you type exit in the shell, it disowns the jobs beforehand (this is configurable to some extent).

You can sever the shell connection with the disown built-in. You can't sever the terminal connection, at least not without underhand methods (using a debugger) that could crash the program.

The application is connected in two ways: to bash, and to the terminal.

The connection to the terminal is that the standard streams (stdin, stdout and stderr) of the application are connected to the terminal. Typical GUI applications don't use stdin or stdout, but they might emit error messages to stderr.

The connection to the shell is that if you started the application with foo &, it remains known to the shell as a job, as explained in Difference between nohup, disown and &. When you close the terminal, the shell receives a SIGHUP, which it propagates to its jobs. When you type exit in the shell, it disowns the jobs beforehand (this is configurable to some extent).

You can sever the shell connection with the disown built-in. You can't sever the terminal connection, at least not without underhand methods (using a debugger) that could crash the program.

The application is connected in two ways: to bash, and to the terminal.

The connection to the terminal is that the standard streams (stdin, stdout and stderr) of the application are connected to the terminal. Typical GUI applications don't use stdin or stdout, but they might print errors to stderr.

The connection to the shell is that if you started the application with foo &, it remains known to the shell as a job, as explained in Difference between nohup, disown and &. When you close the terminal, the shell receives a SIGHUP, which it propagates to its jobs. When you type exit in the shell, it disowns the jobs beforehand (this is configurable to some extent).

You can severe the shell connection with the disown built-in. You can't severe the terminal connection, at least not without using underhand methods (using a debugger) that could crash the program.

The application is connected in two ways: to bash, and to the terminal.

The connection to the terminal is that the standard streams (stdin, stdout and stderr) of the application are connected to the terminal. Typical GUI applications don't use stdin or stdout, but they might emit error messages to stderr.

The connection to the shell is that if you started the application with foo &, it remains known to the shell as a job, as explained in Difference between nohup, disown and &. When you close the terminal, the shell receives a SIGHUP, which it propagates to its jobs. When you type exit in the shell, it disowns the jobs beforehand (this is configurable to some extent).

You can sever the shell connection with the disown built-in. You can't sever the terminal connection, at least not without underhand methods (using a debugger) that could crash the program.