Hi Guardfather, (Mainstream gnome-terminal/vte developer/contributor speaking here. I myself sometimes felt that the output was stopped for longer than desired, although never could reliable reproduce to track it down.)
How reproducible is this behavior using the python script? (Being able to take a screenshots suggests that you could reproduce this.) Could you record the session with script(1) using the -t flag to record timings as well, and then replay with scriptreplay(1) with timings? Does the bug occur when you replay it? Is there any chance you could reproduce with a different tree structure or a modified script log that doesn't contain sensitive information (that you'd need to blur out on a screenshot) and you could attach publicly? When it gets stuck (either with the original python script, or with scriptreplay), could you please do other irrelevant stuff with gnome- terminal (open a new tab or window, produce some output there, switch focus to a completely different app etc.) for about a minute or two? Does this seemingly stuck output continue at one point? Does it continue if you type a regular key into this particular terminal? Or does it freeze until you press ^C? What's the character encoding of your terminal, and what are the exact bytes printed by your python script? If your encoding is UTF-8 then is it really an "a with circumflex" U+E2 (0xC3 0xA2) followed by a "question mark" U+3F (0x3F) and then the "euro sign" U+20AC (0xE2 0x82 0xAC)? What's the desired look of the filename? I suspect there is some charset problem, probably your terminal is set to some 8-bit encoding, and seeing "MACOSX" in the filename I suspect there might easily be a combining accent there as well. Could you please try with another emulator that's also based on vte's gtk3 version? You can test it by the command «echo -ne '\e[>3c'» producing the same numbers as gnome-terminal (the middle one being the version of libvte-2.91) (they're inserted as if you typed them). In Ununtu Xenial, roxterm is such a choice, or you might e.g. get terminator-1.90 manually (not from the distro's repo, there's an older version there). You do not have screen or tmux running, do you? Also: Could we please move this discussion upstream where gnome- terminal/vte development is happening and where the main developer also sees it; that is, could you please file a new bugreport at https://bugzilla.gnome.org/, component vte? Thanks! -- 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/1653420 Title: gnome-terminal output locks up on special character Status in gnome-terminal package in Ubuntu: New Bug description: I wrote a Python 3 script which scans directory trees, and outputs various filenames (with path) to the terminal, as the files are being hashed. When the following filename was to be printed, gnome-terminal stopped printing output with the cursor where the question mark would have been printed out: ._13 Trapezoid singâ?€.mp3 When I interrupted the program using keyboard interrupt, much more output was displayed, indicating the script had continued to run, despite the output stopping after "â". I navigated to the directory and tried using ls, which was able to print the filename without issue. I tried using: find `pwd` -name *Trapezoid* This also displayed the filename, with full path, correctly. I tried running the script with terminator, which had no problem printing the filename and continuing on with the rest of the output as expected. Terminal output at freeze, and after keyboard interrupt shown in the cropped/pixelized screenshots here: http://imgur.com/a/D0XRK Gnome Terminal version: 3.18.3 Ubuntu 64 Gnome Edition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1653420/+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
