I'm seeing problems also when using xterm-256color. Something changed due to aaa_terminfo-6.2_20200801-x86_64-1.txz and ncurses-6.2_20200801-x86_64-1.txz.

slackpkg with slackpkg+ enabled looks messed up:

Thanks for testing.
xterm-256color gives me the same display than xterm, but not the same than your attachment.

You're not using konsole4, I presume.

I had the same problem here and for some reason $TERM in konsole was reverted to 'xterm'.
I edited again to 'konsole' in Settings->Edit current profile->Environment->Edit then paste 'TERM=konsole' and OK.
This works for me.

Yes, but beware of other effects like vim freeze on second launch.

What I've done for now is modify my alias for slackpkg :
So, running slackpkg in a VT is still ok.

I'm using MacOS Terminal (xterm-256color) ssh to Linux.

Thanks, I wasn't remembering that. Indeed vim freezes on second launch, sometimes on first.

I had this problem long time ago and the solution was setting $TERM to konsole I think,
and I run vim a lot so at that time I think TERM=konsole was working.

https://www.linuxquestions.org/quest...kg-4175626618/


ps- I think we are off-topic, maybe a new thread would be good.

Thanks for the link. Interesting.
So, I tested quickly TERM=xterm-color and for me it solves slackpkg+ display and doesn't have effect on vim (I don't use Midnight Commander).
I'm going to try it.

Since the issue doesn't happen with SLACKPKGPLUS=off and /usr/doc/slackpkg+-1.7.0/README send users here, there are chances people with slackpkg+ 1.7 issues come here for workarounds.
Maybe zerouno prefers all versions talks on the 1.8 topic, but it's not the way I understood his announce.

Reposting/moving this to the correct place.

I am running Slackware-current with slackpkg 2.84.0_beta9 and slackpkg+ 1.7.0d1 and the functionality of both seem OK.

However, slackpkg+ (both the stable and dev version) break the dialog interface when running over mosh (https://mosh.org/), but it works fine over regular ssh. I have adjusted the TERM variable a bit, but change that only changed the amount it was broken.

For completeness I am using the st terminal, however the same behavior was encountered in xterm as well.

I had some time to do some further debugging, but I can't seem to replicate this outside of slackpkg+. I ran many of the examples that are available in the dialog source code and they all worked correctly. I then copied the dialog temp files that are created when slackpkg runs and tried to isolate it to no avail. Specifically I was running:
Which should be similar to the broken dialog command in the attachment. It appears to be some weird interaction with mosh, but I couldn't find anything on their github issue tracker or elsewhere around the web.

Attached is a screenshot of the behavior.

Testing with Konsole.

I am not seeing this on slackware64-current with Alien Bob's latest ktown installed with slackpkg - version 2.84.0_beta9 / slackpkg+ 1.7.0d1 installed.

I am not seeing this on clean slackware-current and slackware64-current installs with slackpkg version 2.84.0_beta9 or 2.84.0 installed.

I DO see this issue with slackpkg and slackpkg+ installed on the two clean installs with both slackpkg+ version 1.7.0d1 and 1.7.0

I did some more testing. Mosh seems to set the TERM variable to xterm-256color, and if I change my TERM variable (tried konsole, and st-256color and got the same result):
then I now get the first attachment.

I tried using xterm with mosh to see if that would fix it and I got the 2nd attachment.


I suspect the following is due to some incompatibilities with st as it works properly under xterm. If I set my TERM variable to xterm-256color (while using st, works fine under xterm) on my local machine (slackware64-current) I get the 3rd attachment. Obviously, it works properly when the TERM is set appropriately (st-256color).

I'm currently using slackpkg+-1.7.0 10.

slackpkg+ has some problems after the recent update to slackpkg-15.0-noarch-1.

In particular the blacklist behavior is not working as expected when using slackpkg 15 with slackpkg+. I've added:

to the blacklist - this is the new way to exclude an entire series in slackpkg 15. When slackpkg+ is enabled, `slackpkg install-new` still suggests all of the kde packages for installation despite the blacklist. Disabling slackpkg+ (chmod a-x /usr/libexec/slackpkg/functions.d/slackpkgplus.sh) fixes the blacklist behavior to make it work as expected.

The other thing I noticed when slackpkg+ is enabled is that the slackpkg indexes get updated every time it runs - it no longer says "No changes in ChangeLog.txt between your last update and now / Do you really want to download all other files (y/N)?"

Thanks for any hints if there's any quick fix for this or any slackpkg+ beta I should try.

(separately I'm still having the character set display issues mentioned in the few posts before this one when slackpkg+ is enabled but that's just cosmetic).

I should have checked the 1.8 beta - I see that the issues are discussed there, and I should try that 1.8 beta.
https://www.linuxquestions.org/quest...8-a-4175669481

Please try that:

edit /usr/libexec/slackpkg/functions.d/slackpkgplus.sh
on slackpkg+ 1.7 at line 1571
on slackpkg+ 1.7d1 at line 1735

replace "2.84" with "15.0"

if you confirm that working patch I will commit it

some fixed on
slackpkg+-1.7.0-noarch-11mt.txz
slackpkg+-1.7.0d1-noarch-13mt.txz