Bug 467792 – app-portage/elogv on ARM - _curses.error: use_default_colors() returned ERR

• Status: RESOLVED FIXED
• Product: Portage Development

[Description A. Person 2013-04-28 21:03:36 UTC]

I get the following on ARM (beaglebone) over a serial console:

# elogv
Traceback (most recent call last):
  File "/usr/bin/elogv", line 561, in <module>
    curses.wrapper(ElogViewer)
  File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/bin/elogv", line 99, in __init__
    curses.use_default_colors()
_curses.error: use_default_colors() returned ERR
#

[Comment 1 Sebastian Pipping 2013-05-01 23:46:21 UTC]

Hello Grant,

we can definitely use your help with debugging the problem!

The same crash with another piece of software:
https://github.com/nicolargo/glances/issues/31
https://github.com/nicolargo/glances/issues/32#issuecomment-3719531
https://github.com/nicolargo/glances/commit/2c0a31855c94b8feabf0b692a40fde051e12669b

Could you check your $TERM variable?  For me it's set to "xterm".

[Comment 2 A. Person 2013-05-02 18:47:39 UTC]

I get "vt100" when connected via the USB serial port.  When connected via SSH, elogv works fine and $TERM is "xterm".

[Comment 3 Sebastian Pipping 2013-05-02 21:44:57 UTC]

(In reply to comment #2)
> I get "vt100" when connected via the USB serial port.  When connected via
> SSH, elogv works fine and $TERM is "xterm".

Excellent, with command

  $ TERM=vt100 elogv

it crashed with the same error on amd64, too.


+*elogv-0.7.5-r2 (02 May 2013)
+
+  02 May 2013; Sebastian Pipping <[e-mail]> +elogv-0.7.5-r2.ebuild,
+  +files/elogv-0.7.5-vt100.patch:
+  Fix crash with TERM=vt100 (bug #467792)
+


Please give 0.7.5-r2 a try and re-open if necessary.