https://bugs.kde.org/show_bug.cgi?id=401898
--- Comment #12 from gr...@kde.org --- FWIW, I tested the scenario Ahmed describes in the linked bug, on FreeBSD: - start xterm - start konsole from xterm - in konsole, type "kwrite &" (enter), wait for kwrite to come up, then: - close konsole with ^D (terminating the shell in konsole); kwrite stays running - close konsole with Ctrl-Shift-W (terminating konsole); error messages about shell not closing, followed by kwrite dying (after a short delay) - start xterm - start another xterm from xterm - in xterm, type "kwrite &" (enter), wait for kwrite to come up, then: - close xterm with ^D (terminating the shell in xterm); write stays running - close xterm with the close-window button (the red X, upper-right in the kwin decoration); kwrite is killed quickly So the two are consistent (and frankly, the inconsistency of what-happens-to-gui-applications-launched-from-the-shell depending on how the terminal emulator is closed, would cause me to file a bug report claiming that backgrounded processes should be left alone). -- You are receiving this mail because: You are watching all bug changes.
