FS#40091 - [screen] ncurses programs are broken in screen-4.2.0

Attached to Project: Arch Linux
Opened by Iru Dog (mytbk) - Friday, 25 April 2014, 15:02 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 28 April 2014, 03:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I found that some ncurses programs(e.g mocp,dialog) break in screen-4.2.0,
these programs didn't display normally.

Additional info:
* package version(s)
screen 4.2.0-1
ncurses 5.9-6
* config and/or log files etc.
I removed my .screenrc and the bug still exists.

Steps to reproduce:
Run screen and then run mocp or dialog in it, they display bad, but some programs
using ncurses(e.g htop) don't have the problem.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Monday, 28 April 2014, 03:15 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Friday, 25 April 2014, 16:25 GMT
Please elaborate on "they display bad;" I have no idea what you mean.

Over here I have not noticed any issue with ncurses programs in screen.
Comment by Iru Dog (mytbk) - Friday, 25 April 2014, 16:46 GMT
Just like the following picture when I run 'dialog --msgbox 123 20 20' in screen.
https://pbs.twimg.com/media/BmFONQOCMAIMxNF.png
Comment by Dave Reisner (falconindy) - Friday, 25 April 2014, 16:55 GMT
What is your TERM variable inside screen? I'm guessing it isn't something that looks like 'screen' or 'screen-256color'.
Comment by Iru Dog (mytbk) - Friday, 25 April 2014, 17:05 GMT
It's `screen'.
And I have another weird thing, when I remove and install screen, the post_install() script in the screen package returns error.
Comment by Dave Reisner (falconindy) - Friday, 25 April 2014, 17:11 GMT
> the post_install() script in the screen package returns error.
But you can't tell us what that error is?
Comment by Iru Dog (mytbk) - Friday, 25 April 2014, 17:20 GMT
maybe it's because of the missing of screen-info.{1..5}, pacman only said `command failed to execute correctly'.
Comment by Gaetan Bisson (vesath) - Friday, 25 April 2014, 20:57 GMT
Iru: I cannot reproduce your screen/dialog issue on my machines: everything works as expected.

So I suspect there is something fishy with your local configuration:
- is your computer fully up-to-date? (do: `pacman -Syu`)
- what is the full output of `env` inside screen?
- what is the full output of `pacman -Qi screen dialog`?
- what are the contents of your ~/.screenrc and /etc/screenrc if you have customized it?
Comment by Iru Dog (mytbk) - Saturday, 26 April 2014, 02:02 GMT
1. all packages are up-to-date
2. 3. (see the attachment)
4. I use the original configuration, but the bug still exists

And I just found that, if I use 'LANG= screen' to run screen,
and there's no such problem, and if I run screen in my locale(LANG=zh_CN.UTF-8),
then run 'LANG= dialog --msgbox 123 20 20', then the bug still exists.
   env.txt (2.1 KiB)
   pac.txt (1.3 KiB)
Comment by Gaetan Bisson (vesath) - Saturday, 26 April 2014, 05:29 GMT
Great; I can confirm that zh_CN.UTF-8 is indeed the culprit.

Would you mind reporting this regression upstream? https://savannah.gnu.org/bugs/?func=additem&group=screen

Thanks.
Comment by Iru Dog (mytbk) - Saturday, 26 April 2014, 08:34 GMT
Reported to https://savannah.gnu.org/bugs/?42198
Comment by Iru Dog (mytbk) - Monday, 28 April 2014, 01:41 GMT
https://savannah.gnu.org/bugs/?42198

closed upstream.
comment: should add 'cjkwidth off' in screenrc.

Loading...