GNOME Bugzilla – Bug 121894
garbled title: don't use the DEC special character set when parsing window/icon title text
Last modified: 2008-12-12 12:41:39 UTC
I'm using mc 4.6.0, standing in /x/UB/gnome2-terminal/sources directory, the other panel is /tmp. Standard settings, 80x24 size etc., mc is configured to display the current directory in its title. Here I have the gnome-terminal .tar.gz source. I tap enter on it, the window title becomes: mc - /x/UB/gnome2-terminal/sources/gnome-terminal-2.4.0.tar.gz#utar I use F5 to copy (untar) the source to /tmp. After the end of this operation, the window title becomes totally screwed up. Uppercase letters ("UB"), slashes and digits ("2.4.0") are recognizeable, others are replaced by "LF", "FF", plus-minus, box-drawing etc. characters. The bug doesn't occur with regular xterm, neither did with gnome-terminal 2.2.x.
Created attachment 19840 [details] Screenshot
Sorry, it's a vte bug...
So far the title only changed when mc has finished copying. Now it happened to me that the title changed during copying, and immediately after this (still when I saw mc's copy progress bars) gnome-terminal has exited with segfault. Must be some dirty buffer overrun bug, which occasionally might lead to segfault...
It seems to me now that the segfault issue is not related. The garbled title is caused by the terminal being in 'tput smacs' mode (I don't know what it's officially called) when changing the title. Try this: echo $'\033]0;Normal Window Title\007' echo $'\016\033]0;Garbled Window Title\007'
*** This bug has been marked as a duplicate of 107262 ***
Bug 107262 talks about a segfault case. It redirects me in turn to bug 120891 where I can find the CVS commit that fixes it. I've recompiled pango 1.2.5 with that small patch and the segfault described there is really gone. But here in this bugreport I'm not talking about segfault, I'm talking about incorrect title. This bug is still present, and is not mentioned at all in bug 107262, so I can't see any reason marking it as either resolved or duplicate of that bug. It's a different (although maybe related) issue.
Updated the summary to point to a solution.
*** Bug 136438 has been marked as a duplicate of this bug. ***
*** Bug 137026 has been marked as a duplicate of this bug. ***
Egmont, any docs showing that the title should not be interpreted in alternate charset?
I'm not aware of any relevant docs, I just saw that vte behaved differently than other terminal emulators.
See bug 112172. It's not limited to the title string. Investigating.
Ok, since there is no evidence that the title should be interpretted differently, I'm dupping this. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 127870 ***
Actually I confirmed using xterm that the title is always in the default encoding.
I'm not sure how to cleanly implement this. Since the original issue (garbling) is fixed now, I'm closing this bug until someone actually using alternate charsets reports it.
Actually I now see how to implement it.
Humm, actually I was wrong :(.