Bug 13297 - Error message output from less or less blocking entirely due to perl Proc::ProcessTable module
Summary: Error message output from less or less blocking entirely due to perl Proc::Pr...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA4-32-OK MGA4-64-OK advisory
Keywords: Triaged, validated_update
Depends on:
Blocks:
 
Reported: 2014-05-01 17:42 CEST by Konrad Bernlöhr
Modified: 2014-06-21 00:11 CEST (History)
8 users (show)

See Also:
Source RPM: perl-Proc-ProcessTable-0.480.0-2.mga4
CVE:
Status comment:


Attachments

Description Konrad Bernlöhr 2014-05-01 17:42:48 CEST
When using the 'less' command in Mageia 4, I usually get an error message saying:

   Ran into unknown state (hex char: 29) at /usr/bin/code2color line 50.

Sometimes it would even lock up (Ctrl-C not working) and need a 
kill (-9) to get the terminal window usable again, even on simple
text files containing just a few numbers.

Lines 49-51 of at /usr/bin/code2color read:
      my $pt = new Proc::ProcessTable;
      for (@{$pt->table}) {
	next unless $_->pid eq $PPID;
and searching the internet for 'Ran into unknown state' also
points to the corresponding perl module.

As a test, I installed (with --nodeps) the Cauldron package
perl-Proc-ProcessTable-0.500.0-1.mga5.x86_64.rpm
and all problems were solved. It does not look like a problem
of 'less' but of the Proc::ProcessTable perl module.

Packages and versions used:
  less-458-2.mga4
  perl-Proc-ProcessTable-0.480.0-2.mga4





Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-05-01 19:35:09 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => jquelin

Comment 1 claire robinson 2014-05-06 11:26:18 CEST
Confirmed the problem here mga4 32

eg.

# less -M /bin/code2color 
Ran into unknown state (hex char: 29) at /bin/code2color line 50.

CC: (none) => eeeemail

Doug Laidlaw 2014-05-19 04:34:35 CEST

CC: (none) => laidlaws

Comment 2 Jerome Quelin 2014-06-02 15:52:50 CEST
perl-Proc-ProcessTable-0.500.0-1.mga4 now available in core/updates_testing.

Given https://metacpan.org/diff/file?target=JWB/Proc-ProcessTable-0.50/&source=JWB/Proc-ProcessTable-0.48/, it seems there are no new dependencies.

Proposed advisory:
=====================
code2color may break or even lock screen in some cases, thus causing common tools such as less to also break. This update prevents code2color to break and thus restores full functionality.
=====================

Please test & validate.

CC: (none) => jquelin
Assignee: jquelin => qa-bugs

Comment 3 David GEIGER 2014-06-19 19:51:55 CEST
Tested mga4_32,

Testing complete for perl-Proc-ProcessTable-0.500.0-1.mga4, bug seems now to be fixed with this update.


Before:

$ less -M /bin/code2color
Ran into unknown state (hex char: 29) at /usr/bin/code2color line 50.

-----------------------------------------------------------------------
After:

# LC_ALL=C urpmi perl-Proc-ProcessTable


    $MIRRORLIST: media/core/updates_testing/perl-Proc-ProcessTable-0.500.0-1.mga4.i586.rpm
installing perl-Proc-ProcessTable-0.500.0-1.mga4.i586.rpm from /var/cache/urpmi/rpms     
Preparing...                     #######################################################
      1/1: perl-Proc-ProcessTable
                                 #######################################################
      1/1: removing perl-Proc-ProcessTable-0.480.0-2.mga4.i586
                                 #######################################################

[david@localhost ~]$ less -M /bin/code2color
[david@localhost ~]$

CC: (none) => geiger.david68210
Whiteboard: (none) => MGA4-32-OK

Comment 4 Doug Laidlaw 2014-06-19 20:27:00 CEST
Glad to hear it.  It was only a niggle, but it was getting me frustrated.
Comment 5 user7 2014-06-20 00:02:31 CEST
Doug: The update candidate still needs to be tested on x86_64. So if you happen to be using Mageia 4 on this architecture you can install the update candidate and see if it fixes the problem for you (plus watch out for any obvious regressions) and report back here to speed up the testing process. Your help would be greatly appreciated and we could push this fix faster to all users.

If you want to help out but are unsure about how to do it, you can find detailed instructions here: https://wiki.mageia.org/en/QA_process_for_validating_updates#Test_the_update_candidate (although in this case it really just comes down to installing the update candidate and running the same test David did in Comment 3 )

CC: (none) => wassi

Comment 6 Doug Laidlaw 2014-06-20 01:33:22 CEST
I am running Mageia4 on x86_64.  As you can see, I am experiencing the bug.  I am quite happpy to test this one, but I didn't want to be a regular member of the QA team.  My health makes me too unreliable, and inclined not to finish tasks.
Comment 7 Doug Laidlaw 2014-06-20 02:06:40 CEST
Installed and tested.

Tried David's "less" command, and "less" a file of my own.

Bug gone.  I can't think of any regressions to look for.
Comment 8 Rémi Verschelde 2014-06-20 19:29:17 CEST
Thanks for your test Doug, adding the corresponding keyword.

CC: (none) => remi
Whiteboard: MGA4-32-OK => MGA4-32-OK MGA4-64-OK

Comment 9 Rémi Verschelde 2014-06-20 19:35:07 CEST
Validating update, advisory uploaded.

Please push perl-Proc-ProcessTable to 4 core/updates.

Keywords: (none) => validated_update
Whiteboard: MGA4-32-OK MGA4-64-OK => MGA4-32-OK MGA4-64-OK advisory
CC: (none) => sysadmin-bugs

Comment 10 Doug Laidlaw 2014-06-20 20:18:38 CEST
(In reply to Rémi Verschelde from comment #8)
> Thanks for your test Doug, adding the corresponding keyword.

I left that in case you wanted more results.
Comment 11 Thomas Backlund 2014-06-20 21:54:13 CEST
Update pushed:
http://advisories.mageia.org/MGAA-2014-0132.html

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

Comment 12 user7 2014-06-21 00:11:03 CEST
Doug: Thanks for your help! You don't have to be a member of the QA team to help out, I am quite an unregular tester myself - but every help is apreciated and as you can see, it does make a difference. :)

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