After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 308970 - gnome-terminal corrupts display when using curses application
gnome-terminal corrupts display when using curses application
Status: RESOLVED DUPLICATE of bug 305507
Product: gnome-terminal
Classification: Core
Component: general
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-24 21:12 UTC by Marc Jacobsen
Modified: 2005-07-04 19:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Attachment of the above uuencoded file (1.85 KB, text/plain)
2005-07-02 20:13 UTC, Michele Baldessari
Details

Description Marc Jacobsen 2005-06-24 21:12:14 UTC
Distribution/Version: Ubuntu 5.04

When using a curses application that normally bolds some text and
inverses some other text, gnome-terminal displays the escape sequence 
characters instead of making the text bold or inverse.

This only happens with gnome-terminal 2.10.0 (on Ubuntu 5.04 and Fedora
Core 4), an older version of gnome-terminal (from Fedora Core 2/3) didn't
have this problem.  Also, xterm on the same systems, with the same
fonts, correctly displays the same curses application with bold and
inverse text where it is supposed to be.

Lastly, bold and inverse text is correctly displayed in gnome-terminal
2.10.0 when displaying man pages, using "less", etc.  Seems to be
specific to the curses application.  Maybe it only happens right after
the cursor is repositioned.
Comment 1 Michele Baldessari 2005-06-25 18:49:41 UTC
Hi Marc,

thanks for the report. Could you let me know if this is related to:
http://bugzilla.gnome.org/show_bug.cgi?id=305507 ?
There's a bug in new vte's where we ignore some probably valid sequences.

Also is this curses app you're referring to available somwhere? So I can
play with it?
Comment 2 Michele Baldessari 2005-06-27 09:14:02 UTC
Let me know if recompiling with the patch in the above link is trouble for you and
I'll provide you with a patched deb for your Ubuntu 5.04 distro.

Thanks
Comment 3 Marc Jacobsen 2005-06-27 18:32:25 UTC
Thanks for the quick response.

The curses app is some in-house front end to pick a source version to use cscope
on.  I couldn't find anything on it in google, which is why I assume it is
in-house, sorry.

Actually, I just realized that the problem also shows up in cscope itself, at
least to some degree.  You can find cscope in sourceforge.  When you search for
a symbol it displays a line like this: "Lines 1-9 of 4231, press the space bar
to display next lines".  That should be in inverse, but I just get the escape
codes displayed at the beginning.

If it helps, what I see specifically is "[;7m" where inverse text should
start and "[;1m" where bold text should start.  That first character is
displayed as a '>' with a line under it.

I spent quite a bit of time downloading source, gcc, dependent libraries for
vte, applying the patch, and finally got a libvte.so.4.4.0 that doesn't fix the
problem, but sure did break the backspace functionality.  Sorry, I am not
confident that I proved anything, since I just did a configure and make and
didn't read through all the gnome and vte specific documentation.  The fact that
backspace is broken tells me that I probably missed several details when I did
it.  The curses apps also have even more problems with the libvte that I
compiled.  But I don't have more time to spend on it right now.  Sorry.

If you want to give me a patched deb, or just a libvte.so.4.4.0, I'll try it.

Thanks again.
Comment 4 Michele Baldessari 2005-06-27 18:56:35 UTC
Hi Marc,

thanks much for following up on this. As soon as I'm able to reproduce it I'll
try to fix it. On my cscope here I only get:
* 39744 more lines - press the space bar to display more *

Do I have to use a particular version/options etc.?

You're using Ubuntu Hoary on UTF-8 and pretty much standard settings, correct?
(I'll try tomorrow to reproduce it on such a system)
Comment 5 Marc Jacobsen 2005-06-27 20:59:35 UTC
Hi Michele,

Yeah, that is what I see using cscope locally on my Ubuntu system also.  That is
cscope version 15.5.  But where I really use cscope is on an HP-UX system that
is running cscope version 13.7.  I telnet into that system.  I looked at the
cscope options and didn't see a way to get it to behave like the 13.7 version
(using inverse on the text).

Is there a reasonable way I can "cheat" to get you a text file or something that
will allow you to reproduce the problem?  Would redirecting the std out to a
text file, or even capturing a network trace (of the telnet session) work?  Or
can you think of any way to work around you not having access to the program?

Thanks.
Comment 6 Marc Jacobsen 2005-06-27 21:22:09 UTC
Hi Michele,

I tried cheating by redirecting std out and it worked.  If I cat the file in
xterm it displays right, in gnome-terminal it doesn't.

Since I can't paste in the entire text file with non-printing characters, I
uuencoded the file.  Here it is, just uudecode it, then cat the file.  You will
see what is wrong in gnome-terminal and can cat it in an xterm or an old version
of gnome-terminal to see the desired output.

Let me know if this doesn't work as expected.

Thanks.

begin 644 ns.out
M&UMM&UM(&ULR2BLM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TK
M#0I\&ULR.S@P2'P-"BLM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TK#0H;6S$[,4@;6S0[,4@K+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM*PT*?!M;-3LX,$A\#0I\&ULV.S@P2'P-"GP;6S<[.#!(?`T*?!M;
M.#LX,$A\#0I\&ULY.S@P2'P-"GP;6S$P.S@P2'P-"GP;6S$Q.S@P2'P-"GP;
M6S$R.S@P2'P-"BLM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TK
M#0H;6S0[,4@;6S$T.S%(&ULQ.#LQ2"LM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TK#0I\&ULQ.3LX,$A\#0HK+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM*PT*&ULQ.#LQ2!M;,C$[,4@K+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM*PT*?!M;,C([.#!(?`T**RTM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2L-"AM;,C$[,4@;6S$Y.S-(,3$N
M,C`;6S$Y.SE(0F%S96QI;F4;6S$Y.S$X2$)A8VMU<!M;,3D[,C5(0VUN9',;
M6S$Y.S,Q2"@Q,1M;,3D[,S5(3F]V&ULQ.3LS.4A`&ULQ.3LT,4@P,CHS-3HR
M,2D;6S$Y.S4Q2!M;-3LU2#$;6S4[-T@;6SLW;2]S8V]P92]S8R]C=7`Q,2XR
M,%]B;#(P,#-?,#<Q-R]C;6YD<R]B86-K=7`@&UMM&ULV.S5(,AM;-CLW2"]S
M8V]P92]S8R]C=7`Q,2XR,%]B;#(P,#-?,#<Q-R]C;6YD<R]P<F]C97-S;6=M
M=!M;-SLU2#,;6S<[-T@O<V-O<&4O<V,O8W5P,3$N,C!?8FPR,#`S7S`W,3<O
M8VUN9',O=GAF<QM;.#LU2#0;6S@[-T@O<V-O<&4O<V,O8W5P,3$N,C!?8FPR
M,#`S7S`W,3<O8VUN9',O=GAV;1M;.3LU2#4;6SD[-T@O<V-O<&4O<V,O8W5P
M,3$N,C!?8FPR,#`S7S`W,3<O:V5R;AM;,3`[-4@V&ULQ,#LW2"]S8V]P92]S
M8R]C=7`Q,2XR,%]B;#(P,#-?,#<Q-R]L:6)R87)I97,O;&EB9G,;6S$Q.S5(
M-QM;,3$[-T@O<V-O<&4O<V,O8W5P,3$N,C!?8FPR,#`S7S`W,3<O;&EB<F%R
M:65S+VQI8G9X9G,;6S$R.S5(.!M;,3([-T@O<V-O<&4O<V,O8W5P,3$N,C!?
M8FPR,#`S7S`W,3<O;&EB<F%R:65S+VQI8G9X=FT;6S$S.S,R2!M;.S=M($9/
M4E=!4D0@,C$W(&UO<F4@&UMM&ULQ-#LU2!M;;2`@("`@("`@4T5,14-4(!M;
M.S%M,2TX+"!34$%#12`@("`@&UMM&ULQ-#LT-D@;6VT@("`@("`@("`@455)
M5"`;6SLQ;7$L42Q>1"`@("`@("`@(!M;;1M;,34[-4@;6VT@(%!!1T4@1D]2
M5T%21"`;6SLQ;68L2BQ>1BP]("`@("`@(!M;;1M;,34[-#9(&UMM("`@("!0
M04=%($)!0TL@&UL[,6UB+$LL7D(L+2`@("`@("`;6VT;6S$V.S5(&UMM("!,
M24Y%($9/4E=!4D0@&UL[,6T\0U(^+&H@("`@("`@("`;6VT;6S$V.S0V2!M;
M;2`@("`@3$E.12!"04-+(!M;.S%M:R`@("`@("`@("`@("`@&UMM&ULQ-SLU
M2!M;;5!!5%1%4DX@4T5!4D-((!M;.S%M+RQP+%`@("`@("`@("`@&UMM($A%
M3%`@&UL[,6UM+&@L/QM;;2`@("`@("`@(%-(14Q,(!M;.S%M?BPA("`@("`@
M("`@("`@&UMM&ULQ-#LW-D@;6S\Q:!M;/S(U21M;,3D[-3%(&ULR-#LQ2!M;
)/S%L&UL_,C5H
`
end
Comment 7 Michele Baldessari 2005-06-27 21:38:26 UTC
Hi Marc,

thanks _a lot_ for giving this info. I can reproduce the issue now. 
I'll look into it :)
Comment 8 Olav Vitters 2005-06-27 21:39:02 UTC
Marc: Please do not use uuencode, just attach such files to the bugreport.
Comment 9 Marc Jacobsen 2005-06-27 21:48:32 UTC
Sorry, I didn't look very hard for a way to attach files.

Michele, glad it worked, and thanks for your help.  Is this bug report
"CONFIRMED" now?  :-)

-Marc
Comment 10 Michele Baldessari 2005-07-02 17:36:52 UTC
Surely :)
Comment 11 Michele Baldessari 2005-07-02 20:13:12 UTC
Created attachment 48567 [details]
Attachment of the above uuencoded file

I'll attach the above uuencoded file to make it easier for people to test it
Comment 12 Michele Baldessari 2005-07-04 19:08:13 UTC

*** This bug has been marked as a duplicate of 305507 ***