SUMMARY It frustates with logs of processes which have been backgrounded already. I have tried checking `jobs` and `bg 1` that job and it says `bash: bg: job 1 already in background` as expected. STEPS TO REPRODUCE 1. Start any program by backgrounding it. for example `gedit foo.txt &` 2. Start using that program. for example - typing anything into it. 3. Open the yakuake terminal. for example - press F12. OBSERVED RESULT There should be all the logs generating in it like when it is launched in foreground. I tried similar thing with konsole and it was showing expected behaviour. EXPECTED RESULT After backgrounding a process , a person assumes their terminal will not be filled with so many logs so everytime after switching between a text editor and terminal I have to press CTRL + C to exit that and to continue what I was doing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-arch1-1(64-bit) ADDITIONAL INFORMATION I have arch and I use Gnome on X11(generally and at that time also) but I like KDE Applications too. I still gave above version informations if it may be helpful.
Unless I'm misunderstanding something, not a konsole/yakuake issue. Backgrounding doesn't prevent a process from printing to the terminal (unless tostop is set, but it typically isn't set. See the output of "stty -a"). To prevent logs from getting printed, they should be redirected, e.g: gedit foo.txt >/dev/null 2>&1 & or gedit foo.txt >& /dev/null & # (if your shell supports that) or gedit foo.txt 2> /dev/null & # (if you only want stderr redirected)