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 334942 - Visual formatting sequences appear to be unhandled
Visual formatting sequences appear to be unhandled
Status: RESOLVED DUPLICATE of bug 400072
Product: vte
Classification: Core
Component: general
0.12.x
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-17 23:32 UTC by greg
Modified: 2007-05-21 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
Screen shot of the rendering in Gnome Terminal and In XTerm (269.03 KB, image/png)
2006-03-17 23:33 UTC, greg 		Details

Description greg 2006-03-17 23:32:27 UTC 
Please describe the problem:
When I try using gnome-terminal to administer my Meridian Mail system through
the conserver client, I see what appears to be formatting codes like "[;1;4m
" on the forms instead of normal fields. 

Steps to reproduce:
I don't know any way to reproduce this without accessing this system, but I'd be
glad to assist developers in getting access for testing.

1) run the conserver ( http://www.conserver.com/ ) client to connect to
appropriate system
2) Enter voicemail administration

Actual results:
I can see the prompts for the voice mail system, but there are what appear to be
formatting codes garbling the output. 

Expected results:
I should be seeing the dialogs for the voice mail system with the proper formatting.

Does this happen every time?
Yes

Other information:
While this may not be relevant, the output being generated appears to work in
both XTerm and Konsole.
Comment 1 greg 2006-03-17 23:33:42 UTC 
Created attachment 61466 [details]
Screen shot of the rendering in Gnome Terminal and In XTerm

I'm having a difficult time actually describing the issue, so I hope this image will help clear up what I'm actually seeing.
Comment 2 Chris Wilson 2007-01-31 23:40:12 UTC 

*** This bug has been marked as a duplicate of 400072 ***
Comment 3 greg 2007-05-21 12:14:47 UTC 
I can confirm that I no longer have this problem as of 0.16.1 and gnome-terminal 2.18.0. Thank you for your work on this issue.