By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1717 - [stdout/stderr] Konsole: undecodable token: \001b(hex)[?1015h
Summary: [stdout/stderr] Konsole: undecodable token: \001b(hex)[?1015h
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-11-18 20:54 CST by Darrell
Modified: 2018-05-27 10:48 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-11-18 20:54:16 CST 
This error/warning message was first reported in bug 1655. To facilitate tracking and debugging, this message has been moved to this new report.

A patch was pushed to git in commit 6409e490 to clarify the source of the message, which is Konsole.

Some effort was made to resolve this message as seen in bug 1655 comment 39 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=1655#c39).

How to specificaly trigger these type of messages is not yet confirmed.
Comment 1 Darrell 2013-11-20 17:40:53 CST 
I found a way to trigger the message.

Ensure the Terminal Sessions applet is in the panel.

Select Root Midnight Commander.

No need to do anything special. After mc starts, exit mc, which will close the konsole session. The warning message should appear.
Comment 2 Timothy Pearson 2013-11-20 23:23:03 CST 
The quick fix for this is to compile Konsole in release mode (-NDEBUG), which will shut off the debugging messages you are currently seeing.

The general response I have gotten thus far is that four-character terminal control sequences are illegal, so Konsole is doing the right thing by complaining to developers (i.e. those using software not compiled in release mode).
Comment 3 Darrell 2013-11-21 00:26:12 CST 
Okay.

* Is compiling with -NDEBUG desirable or overall, do we prefer konsole to spew debug messages? Seems debug mode is more helpful.

* Should we expand the printf statement to include verbiage that four-character escape sequences are illegal?

* Is there a way to trap which software app is using four-character escape sequences such that the xsession-error log is more useful to users? (In my use case I'm running a watchdog script to alert me when various error messages occur. That is how I knew mc was a trigger. Other users will not have a watchdog script running and won't know the cause of the 'undecodable' messages.)