How recover from damage from slackpkg 'upgrade' (scilab) ?
 

6/23/2019 ...

Well, I did an 'update' which I thought was 'safe':
#slackpkg update
#slackpkg install-new
#slackpkg upgrade-all

Now at least one program (scilab, an SBo) will not run, won't start - at all.

I have 14.2, 64-bit, with Alien's multilib. Following his advice, and advice within /etc/slackpkg/blacklist, I uncommented all 'SBo', and two lines for blacklisting Alien's stuff. Also, comments near top of 'blacklist' advise uncommenting all those 'kernel' entries (9 lines, including 'Huge', which I still have), so I did that.

Now 'scilab', an SBo which has run perfectly, will not start at all. I get this message,

-------------------------------
get chip id failed: -1 [13]
param 4, val: 0
[Intel_init_bufmgr: 1091] Error Initializing Buffer Manager.
Cannot find this look and feel:
[GTK look and feel - com.sun.java.swing.plaf.gtk.GTKLookAndFeel] not supported on this platform
/opt/scilab/bin/scilab: line 972: 1698 Segmentation fault "SCILABBIN" "$@"
--------------------------------------------------
note, the first line in above was always there, but not the rest.

I've 'removepkg(d)' scilab*, rebuilt the package (v 6.0.1) and reinstalled (twice). The rebuilt, reinstalled pkg then DOES show up in /var/log/packages. But still same thing - bombs as above.

I have not the slightest idea how to recover from this situation, but I don't relish reinstalling Slack 14.2/64/multilib/, all the SBo's, recompiling ad infinitum.

I would deeply appreciate any suggestions.
Unless I can somehow learn what went wrong, and what not do do in future, I will never, ever use slackpkg 'upgrade' again.

Needless to say, the package works excellently and smoothly on Windows (7).

jrc

Why aren't you using the 64 bit version of scilab (which appears to be available from Slackbuilds.org) instead?

Actually I am using the 64-bit version. /var/log/packages has:

"scilab-6.0.1-x86-64_64-1_SBo"..

I also had updated to the 6.0.2 version with the help of the
scilab SBo package maintainer.

Rebuilt them both; neither works now after the
'slackpkg upgrade-all' earlier.

Thanks Richard, anyway, for your comment.
--------------
Edit: Richard, maybe I'm missing something - is there a
'clue' in my post that indicates my slack64 thinks the
scilab pkg is a 32-bit version?
Thanks,

jrc

Edit: I originally responded thinking you were running -current.

The type of breakage you are experiencing on a stable release is not common, but unfortunately it can still happen with 3rd-party packages. Reinstalling is less likely to help for repackaged binaries like scilab, since you are not actually rebuilding anything. Maybe you can track down the upgrade that broke scilab. Can you do `ls -lrt /var/log/packages`?

I will try installing scilab later to see if I can reproduce your error. I also have Slackware64-14.2 and multilib.

You rebuilt but there is a broken link after the update. You may want to find the broken link reinstall that program. Or programs that are dependent to that GTK failure. the doinst.sh will fix that link. This happens to me many times through the years and slackware 14.1 14.2 and SBO builds

rebuild what?
 

Not sure what you mean by 'rebuild it after update'...

I completely rebuilt the SBo package for scilab 6.0.1 TWICE,
using 'installpkg' /tmp/... each time. Still bombs.

?
jrc

sorry read back had a edit the error shows your missing dependency seems newer 6.0.2 needs
check this out

How to UNDO 'slackpkg upgrade-all'
 

I confess I'm VERY CONFUSED over the man pages for 'slackpkg' and its options, along with the file '/etc/slackpkg/blacklist'.

The comments in 'blacklist' say that,

'Automated upgrade of kernel packages aren't a good idea ... if you think the same, uncomment the lines below...' (I take the advice here, to NOT automatically upgrade kernels...is this somehow wrong??) ..

This advice is followed by a (originally commented) list of 9 kernels, including 'huge', which is the default and which I still have (at least I have NOT personally changed it...). So I uncommented all 9. The instructions say this will 'blacklist' all 9, ie prevent 'automatic upgrade' (by 'slackpkg upgrade-all'). I've always done it this way.

I also uncommented all the SBo pkges per Alien Bob advice; also added uncommented lines to blacklist all the 'alien' stuff - 2 lines. All of these are in his 'multilib' instructions.

So that's how I've always run it. After the sequence,

#slackpkg update
#slackpkg install-new
#slackpkg upgrade-all

I get a list of packages to be upgraded and a list of commands. I always pick the'O' command, which carries a reminded that the previous package will be retained (with a 'suffix' ? cannot remember).

So, is there a way to step BACK to the previous configuration using the original (saved) packages? Or to reinstall one of them? I don't easily find any reference to how to do this, either online or in the man pages, or in the 'slack book'.

If there is a file which shows the list (which quickly flashed by) of which packages were upgraded, where they are, etc I'd sure like to know how to find it. Then maybe I could start trying to find which step messed up my previously working 'scilab' installation.

I'd very much appreciated any insight in how to go about this - undoing one or more 'upgrade-all' packages. Thanks for comments.

jrc

to 'Slackware Current' -

Actually I have the same problem, same diagnostics, with EITHER vesion of scilab, 6.0.1 OR 6.0.2.

I'll check your reference, thanks.

jrc

I know nothing about scilab, but I find many reports about this problem, under multiple Linux distros.

As far as I can tell, the only suggestion that resolves the issue for now, is to use the Oracle JDK, instead of OpenJDK.

However, the Oracle JDK is less freely and easily downloadable these days, though it can still be done.

UPDATE: It seems that Debian and/or Ubuntu have a fixed scilab package in their repositories.

I would revert to the original build figure out the broken link or why GTK Java are broken. install latest openjdk =< 8
rebuild. I do know GTK on 14.2 has been rebuilt a few times.
You may have to rebuild stuff from SlackBuilds. your gtk theme not working it will segfault and not create the window.
Like you! For my slackpkg/blacklist I would leave the +_SBo +_alien uncommented and upgrade them through SlackBuilds and alien.
I recommend this only on stable 14.2 this will keep slackpkg from breaking things.
Little note when uncommenting
No space from the left
wrong way
why because awk is setup that way or what ever they use in slackpkg
This will cause slackpkg to use default

Result of 'ls -lrt /var/log/packages' ..
 

to montagdude..
Using your suggestion, I entered 'ls -lrt /var/log/packages', and got a list of upgrades.
Previously, the most recent upgrade was in March 2019.
The upgrades in question, June 23, 2019, are listed as 18 pkgs, as follows:
bind, ca-certs, curl, ghostscript, glibc-zoneinfo, gnutils,
httpd, libpng, libssh2, mariadb, moz-firefox, moz-Tbird,
ntp, openjpeg, openssl-1, openssl-so..., rdesktop, wget.

I don't quickly see ANY of these directly involved in scilab.
glibc-* might impact multilib, but 'glibc-zoneinfo' is only timezones.

To the person wondering about use of jdk, I AM using Oracle jdk 8u202, an SBo pkg. This has not changed during the update, worked just fine before the general upgrade, which did not involve jdk at all.

So i'm not sure how to proceed.

If I could just undo them all somehow, that would surely fix the problem. If it didn't, it would have to be 'aliens' (i.e., nothing else has changed).

jrc

You need to install openjdk 8 or higher get it from alien
then
Scalib is a prebuilt program then repackaged most of all the libraries are static. Runs fine in slackware64.14.2 and Current tested both.
Install openjdk then reboot or open a terminl type like this
note the dot and space.
now run
have fun

Have you tried it with Oracle JDK to confirm that that is the problem?

I never use the Sun Version I would uninstall and you will need to delete the /etc/profile.d/jdk.sh and /etc/profile.d/jdk.csh
for some reason slackpkg never removes them from openjdk or Sun oracle jdk for me.
do as above