I guess we should close this, then? "reset" works for me. Increasing the amount of concurrency (the "range" values in the script) seems to increase the repro chance. I guess it's some race condition in how ffmpeg cleans up after itself.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1756952 Title: Text invisible after concurrent ffmpeg invocations Status in gnome-terminal package in Ubuntu: New Bug description: Repro steps: Run the attached script in gnome-terminal. (Requires Python and ffmpeg.) After the script finishes, try typing in the same terminal. No text will appear. (The repro is not 100% reliable, so you may have to try the script multiple times.) The script spawns a couple of concurrent ffmpeg processes. Their stdin must be connected to the terminal for the bug to repro. I've tried other programs in place of ffmpeg which also use stdin, but haven't found any other repro. Observed behavior: Typed text doesn't appear after running the script. However, the terminal still seems to receive commands. Ctrl+C still works, but doesn't fix the problem. I have to restart gnome-terminal to fix it. Expected behavior: Text input should work normally after the script exits. Versions: Ubuntu 14.04.1 LTS gnome-terminal 3.26.0 Python 3.5.3 ffmpeg 3.4.1-1 x86_64 I also repro'd in gnome-terminal under Arch Linux. (But the Gnome bug tracker said to file with Ubuntu first, so here we are.) I wasn't able to repro when using xterm in place of gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1756952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
