Bug 191158 - dialog4ports only shows empty terminal for most ports
Summary: dialog4ports only shows empty terminal for most ports
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 10.0-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bartek Rutkowski
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-18 13:45 UTC by Thomas Schweikle
Modified: 2014-06-24 10:01 UTC (History)
3 users (show)

See Also:

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 Thomas Schweikle 2014-06-18 13:45:56 UTC 
dialog4ports only displays an empty terminal window for various ports:

cd /usr/ports/lang/clang33
make config

-> empty xterm or console.

Environment:
FreeBSD fbsd10-64.bfs.de 10.0-STABLE FreeBSD 10.0-STABLE #26 r266805: Wed May 28 20:40:18 CEST 2014     root@fbsd10-64.bfs.de:/usr/obj/usr/src/sys/FBSD10-64  amd64

How-To-Repeat:
cd /usr/ports/lang/clang33
make config
Comment 1 Arnaud Bergeron 2014-06-18 14:43:05 UTC 
I am encountering the exact same problem (with the devel/nasm port and several others, in fact I can't find a port where dialog4ports is working).  I am having this problem through an SSH connection from Terminal on OS X as well as the native console.

I should note that if you press the arrow down key you see the message:

===> Options unchanged

and dialog4ports exits.


Here are the steps I've tried to resolve the problem:

- Change TERM to: xterm, cons25, xterm-color, vt220, vt100 xterm-256color, xterm-old

- Rebuild dialog4ports from the newest sources available.

Also, I remember this working on 10.0-RELEASE.  I personally encountered the problem with 10.0-p5.  I can't say if any of the intervening patch releases have the same problem.
Comment 2 ru_M1cRO 2014-06-19 10:11:51 UTC 
Hi, just update you ports tree, it should fix the problem.
Comment 3 Arnaud Bergeron 2014-06-19 13:44:41 UTC 
I can confirm that the latest port tree fixes the problem for me.
Comment 4 Baptiste Daroussin freebsd_committer freebsd_triage 2014-06-24 10:01:04 UTC 
Close this was not a dialog4ports bug and the issue has been fixed in the ports tree framework