Bug 11021 - Terminology software emits debug tracing statements
Summary: Terminology software emits debug tracing statements
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: has_procedure mga3-32-ok mga3-64-ok
Keywords: Triaged, validated_update
Depends on:
Blocks:
 
Reported: 2013-08-16 19:46 CEST by bozonius
Modified: 2013-08-22 20:29 CEST (History)
5 users (show)

See Also:
Source RPM: terminology
CVE:
Status comment:


Attachments

Description bozonius 2013-08-16 19:46:49 CEST
Description of problem:
Although the testing repo updates do allow Terminology (version 0.2.0) to run, it is spitting out trace statements as it runs.  It appears to do this for every mouse movement and keyboard click.  While this does not impair operation of the program, it might be wise to investigate why this is happening and hopefully clean up this output.

The i586 version spits out messages that seem to refer to (a bug or changeset) number 8786 in the Terminology software tracking system, whereas the x86_64 version indicates 4433, but I could not seem to get a fix on exactly what these were.  The Enlightenment project's bug numbers do not even run that high; they stop around 2000 or so it looks like, based on the widest bug search I could list.

This problem was discovered while validating 10312.

Version-Release number of selected component (if applicable):
terminology 0.2.0 for both i586 and x86_64 versions.

How reproducible:
very.

Steps to Reproduce:
1.  Install terminology 0.2.0
2.  Invoke "terminology" from a command line window
3.  Type any key or move mouse in the terminology program window


Reproducible: 

Steps to Reproduce:
Comment 1 William Kenney 2013-08-16 21:06:23 CEST
(In reply to bozonius from comment #0)

> This problem was discovered while validating 10312.

And I think this is the right thing to do as this is
an entirely different function then the original bug.

CC: (none) => wilcal.int

Manuel Hiebel 2013-08-17 17:23:52 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => tremyfr
Source RPM: (none) => terminology

Comment 2 trem 2013-08-17 19:58:26 CEST
I have uploaded a patched/updated package for Mageia 3.

You can test it with the following command :
- urpmi terminology (install terminology)
- open a terminal
- run terminology from the terminal
Then check that the terminal isn't flooded with message like this :
ERR<7878>:termpty termptyesc.c:1318 _termpty_handle_seq() o



Updated packages in core/updates_testing:
========================
terminology-0.2.0-4.mga3
terminology-debuginfo-0.2.0-4.mga3

Source RPMs: 
terminology-0.2.0-4.mga3
trem 2013-08-17 19:59:12 CEST

Assignee: tremyfr => qa-bugs

trem 2013-08-17 20:02:32 CEST

CC: (none) => tremyfr

David Walser 2013-08-17 22:26:00 CEST

Version: Cauldron => 3

Comment 3 William Kenney 2013-08-18 17:55:06 CEST
MGA3-32 not ok

in VirtualBox

default install terminology-0.2.0-3.mga3.i586 from core release
[root@localhost wilcal]# urpmi terminology
Package terminology-0.2.0-3.mga3.i586 is already installed

Relaunch terminology from Menu, launched ok
Launch from terminal and recreated error messages referred to in Description ie:
ERR<2999>:elementary elm_scroller.c:734 elm_scroller_policy_set() Passing object (0x81c7858)..........
ERR<2999>:termpty termptyesc.c:1034 _handle_esc() ESC: '['
ERR<2999>:termpty termptyesc.c:765 _handle_esc_csi() unhandled screen non-priv mode arg 36, mode 0, ch 'l'
ERR<2999>:termpty termptyesc.c:769 _handle_esc_csi() unhandled 'l'
ERR<2999>:termpty termptyesc.c:1034 _handle_esc() ESC: '>'
ERR<2999>:termpty termptyesc.c:1034 _handle_esc() ESC: ']'
ERR<2999>:termpty termptyesc.c:1315 _termpty_handle_seq() txt: [
ERR<2999>:termpty termptyesc.c:1318 _termpty_handle_seq() [
ERR<2999>:termpty termptyesc.c:1318 _termpty_handle_seq() w
ERR<2999>:termpty termptyesc.c:1318 _termpty_handle_seq() i
ERR<2999>:termpty termptyesc.c:1318 _termpty_handle_seq() l
ERR<2999>:termpty termptyesc.c:1318 _termpty_handle_seq() c
..........

install terminology-0.2.0-4.mga3.i586 from core updates_testing
[root@localhost wilcal]# urpmi terminology
Package terminology-0.2.0-4.mga3.i586 is already installed
Relaunch terminology from Menu, launched ok
Launch terminology from a terminal and results are as follows:
[wilcal@localhost ~]$ terminology
ERR<3563>:elementary elm_scroller.c:734 elm_scroller_policy_set() Passing object (0x8aaa1e8)..........
ERR<3563>:termpty termptyesc.c:765 _handle_esc_csi() unhandled screen non-priv mode arg 36, mode 0, ch 'l'
ERR<3563>:termpty termptyesc.c:769 _handle_esc_csi() unhandled 'l'
no additional errors reported

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
VirtualBox 4.2.16-1.mga3.x86_64.rpm
Comment 4 William Kenney 2013-08-18 17:55:35 CEST
MGA3-64 not ok

in VirtualBox

default install terminology-0.2.0-3.mga3.x86_64 from core release
[root@localhost wilcal]# urpmi terminology
Package terminology-0.2.0-3.mga3.x86_64 is already installed

Relaunch terminology from Menu, launched ok
Launch from terminal and recreated error messages referred to in Description ie:
[wilcal@localhost ~]$ terminology
ERR<2211>:elementary elm_scroller.c:734 elm_scroller_policy_set() Passing object (0x9eb230)..........
ERR<2211>:termpty termptyesc.c:1034 _handle_esc() ESC: '['
ERR<2211>:termpty termptyesc.c:765 _handle_esc_csi() unhandled screen non-priv mode arg 36, mode 0, ch 'l'
ERR<2211>:termpty termptyesc.c:769 _handle_esc_csi() unhandled 'l'
ERR<2211>:termpty termptyesc.c:1034 _handle_esc() ESC: '>'
ERR<2211>:termpty termptyesc.c:1034 _handle_esc() ESC: ']'
ERR<2211>:termpty termptyesc.c:1315 _termpty_handle_seq() txt: [
ERR<2211>:termpty termptyesc.c:1318 _termpty_handle_seq() [
ERR<2211>:termpty termptyesc.c:1318 _termpty_handle_seq() w
ERR<2211>:termpty termptyesc.c:1318 _termpty_handle_seq() i
ERR<2211>:termpty termptyesc.c:1318 _termpty_handle_seq() l
ERR<2211>:termpty termptyesc.c:1318 _termpty_handle_seq() c
..........


install terminology-0.2.0-4.mga3.x86_64 from core updates_testing
[root@localhost wilcal]# urpmi terminology
Package terminology-0.2.0-4.mga3.x86_64 is already installed
Relaunch terminology from Menu, launched ok
Launch terminology from a terminal and results are as follows:
[wilcal@localhost ~]$ terminology
ERR<2796>:elementary elm_scroller.c:734 elm_scroller_policy_set() Passing object (0x19baed0)..........
ERR<2796>:termpty termptyesc.c:765 _handle_esc_csi() unhandled screen non-priv mode arg 36, mode 0, ch 'l'
ERR<2796>:termpty termptyesc.c:769 _handle_esc_csi() unhandled 'l'
no additional errors reported

Test platform:
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
VirtualBox 4.2.16-1.mga3.x86_64.rpm
Comment 5 trem 2013-08-18 18:08:32 CEST
As the console isn't flooded with debug messages, I thin this is OK.
Comment 6 William Kenney 2013-08-18 19:00:20 CEST
What'a ya think David & bozonius
Comment 7 bozonius 2013-08-19 00:51:12 CEST
It generates output that ends up going to ... the null device?   I agree it is harmless, but it isn't "clean" and it does make work for the system that is of no use to the user.  I just wanted to point these out, but I am open to whatever you want to do with it.   I don't use Terminology anyway; it looks like a partially-completed work-in-progress not ready for primetime.

CC: (none) => bozonius
Version: 3 => Cauldron

Comment 8 claire robinson 2013-08-19 08:11:17 CEST
Validating. Thanks guys, and trem for the quick fix.

Advisory uploaded as..

+description: |
+If started from another terminal, Terminology would flood it with error
+messages for each character displayed such as below.
+
+ERR<7878>:termpty termptyesc.c:1318 _termpty_handle_seq() o
+
+This should not now happen.


If there is a better description please let us know.

Could sysadmin please push from 3 core/updates_testing to core/updates

Thanks!

Keywords: (none) => validated_update
Whiteboard: (none) => has_procedure mga3-32-ok mga3-64-ok
CC: (none) => sysadmin-bugs

claire robinson 2013-08-19 08:12:33 CEST

Version: Cauldron => 3

Comment 9 Thomas Backlund 2013-08-22 20:29:49 CEST
Update pushed:
http://advisories.mageia.org/MGAA-2013-0090.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.