Dialog formatting issues after recent '-current' updates
3 Attachment(s)
There have been a number of recent changes to ncurses and terminfo files that I believe are causing the slackpkg+ dialogs/UI to have formatting issues. For ex. a character appears and repeats a number of times in place of line drawing characters, some lines are not properly drawn. The dialogs are still perfectly usable - no functionality issues.
The regular slackpkg dialogs are fine (i.e. when turning slackpkg+ 'off'). My term setting (ssh'ing from MacOS): declare -x TERM="xterm-256color" Screenshots attached: 1 - Slackpkg - looks fine, no problems 2 - Slackpkg+ - reinstall dialog formatting issues 3 - Slackpkg+ - upgrade dialog formatting issues |
Thankyou to reporting.
I have to update my -current to replicate the problem. Which is your current update? latest changelog is (now) Wed Apr 4 00:16:40 UTC 2018 also try to run VERBOSE=3 slackpkg reinstall kernel at the end of execution, the temporary directory /tmp/slackpkg.XXXX will be not removed. attach the generated file 'dialog.tmp' from that directory thankyou. |
I'm on Wed Apr 4 00:16:40 UTC 2018, attaching log
Thanks for looking into this.
My dialog.tmp contains just one line: kernel-generic-4.14.32-x86_64-1.txz "slackware64" on |
Have you a way to access the machine in ssh from a linux machine and/or from the console (monitor attached) or just from mac?
Please give me echo $TERM before ssh, after ssh and after the 'su' command (before declare -x ... ) Edit: which character encoding are you using? (UTF-8 and so on). |
Direct terminal access: dialog looks perfect.
echo $TERM shows 'linux' Also, direct terminal access -> run xfce (TERM=xterm-256color): perfect The problem appears tied to the use of xterm-xxxx on Mac. I don't know why slackpkg+ specifically is affected - I suspect won't be easy to figure out. These are the results from trying all the possibilities for MacOS Term settings with slackpkg+ dialogs: xterm: problems xterm-16color: problems xterm-256color: problems ansi: terrible dtterm: perfect nsterm: perfect rxvt: perfect vt52: doesn't work properly for anything vt100: perfect (black & white) vt102: perfect (black & white) |
Actually noticed one other thing: with xterm (-256color), on both direct terminal > xfce, and MacOS ssh, after exiting from slackpkg+ the screen doesn't get cleared - the dialog UI remains on screen, and the prompt appears in the middle of it. So xterm has problems of some kind with slackpkg+ even on direct linux console.
|
2 Attachment(s)
Found issues with one screen in Slackware installer, and with the iptraf utility, all on Mac Terminal. Seems like an issue with dialog, which may not be fixable by slackpkg+. I'll probably need to file a slackware current bug, or dialog bug, but because it affects the Mac there will be little interest in fixing it I suspect.
|
To fastest tests run
dialog --msgbox test 10 30 and dialog --clear Also run VERBOSE=3 bash -x slackpkg upgrade kernel 2>slackpkg.trace grep dialog slackpkg.trace|grep reinstall You will find the exact command that slackpkg+ runs Always annotate the $TERM before you run it. |
This may solve..
Quote:
|
dialog/ncurses issues solved by recent slackware -current
Thanks zerouno, those recent slackware -current changes fixed xterm connecting from MacOS.
Since the default MacOS term is actually xterm-256color, I had to apply a similar fix and build a custom ncurses (maybe slackware -current will also make this change in a future update). $ vim <ncurses src slackbuild dir>/ncurses/terminfo/xterm.terminfo ~~~~~~ Original: xterm-256color|xterm with 256 colors, use=xterm+256color, use=xterm-new, ~~~~~~ Modified: xterm-256color|xterm with 256 colors, use=xterm+256color, use=xterm, ~~~~~~ I could make the same change to other xterm-XXcolor such as xterm-16color, but for me at least xterm-256color is the one I use so I only changed that one. |
1 Attachment(s)
EXPERIMENTAL FEATURE!!! -> Duplicate packages allowed in install dialog box
Apply patch to slackpkgplus.sh from slackpkg+-1.7.0d1-noarch-3mt.txz Add in slackpkgplus.conf: DIALOG=full This patch add a version of the dialogbox in the install mode where the packages will be shown from all repositories, not just from the repository in configuration priority order, so I do not need to add single packages in PKGS_PRIORITY every time (and search in which repository is it) By default the dialog mark as selected only the package in priority as from configuration. Then you can select the package you want. (dangerous note: in that first draft slackpkg does not check if you have selected more than one package with the same name) May be most useful to enable TAG_PRIORITY=on where do you set DIALOG=full, otherwise at the first slackpkg upgrade-all it will be replaced with the one in standard priority order. This may replace slackpkg install repo:package where I don't know where to find the package (yes, I can run slackpkg search package, but this is another way) NOTE: it is a MOST EXPERIMENTAL FEATURE, just to know if it may be useful/wanted. Someone asked for it in past. know bug: if two different repositories have the SAME full-package-name (for example one in the -stable and one in -current), just one will be shown, the first in standard priority order. test it with DOWNLOADONLY=on slackpkg install package Code:
--- slackpkgplus.sh 2018-05-21 22:39:12.493106875 +0200 |
IMPORTANT
slackware current introduce slackpkg-2.83.0 that broke slackpkg+-1.7.0-x86_64-5mt You should upgrade to slackpkg+-1.7.0-x86_64-6mt BEFORE upgrade slackpkg, otherwise you need to upgrade it by downloading it manually. (slackpkg+ development release already works with slackpkg-2.83) Code:
Thu May 31 09:39:12 CEST 2018 It broke the $ROOT compatibility even in slackpkg-2.82.2 If you use slackware-stable and need $ROOT do NOT upgrade slackpkg+ This is a workaround. I will work for a better fix when I'll a lot of time. |
Upgrade manually slackpkg+: http://www.slakfinder.org/slackpkg+/pkg/
|
I think it broke more than $ROOT.
I installed new Slackpkg+ on 14.2, I have "TAG_PRIORITY=on" and "PKGS_PRIORITY=( multilib: )" set. New version ignored it altogether offering me to upgrade bunch of multilib, SBo and my custom packages with original Slackware versions. |
the correct syntax is
PKGS_PRIORITY=( multilib ) or PKGS_PRIORITY=( multilib:.* ) and tell me if it works however if slackpkg+-1.7.0-noarch-5mt did work with ( multilib: ) I need to investigate (but I use slackware-current). You can find the older versions here: http://slakfinder.org/slackpkg+all/ (do not use the older version with slackware-current) |
All times are GMT -5. The time now is 11:45 AM. |