be sure to read also robby's solution under: upgrade libxml2, don't downgrade zlib.

---

upgraded to latest packages on 64-current multilib, but many things started to segfault: first I noticed openbox, then update-mime-database...
I reverted to the old zlib package (1.2.3 instead of 1.2.5) and now everything seem to have gone back to normal.
tried upgrading another 64-current multilib and got the same behaviour (gotta say I use custom 2.6.35 kernels on the two, but should not be related).
I thought that luckily it gets updated by slackpkg as last so update-mime-database worked for the other packages and installpkg ended without segfaulting (that's the behaviour I got after latest updates if I try to install something else that uses update-mime-database in doinst.sh)

just pointing out if anyone else has similar problems (start noticing strange segfaults on 64-current after today's updates): I suggest to grab the old zlib-1.2.3 package while it's still in non-updated mirrors.

obviously I hope it's only a personal problem.

EDIT: tried now with a 32bit vm (with stock kernel) and it works fine with the latest zlib.
but on a 64bit vm (also with stock kernel) zlib needs to be downgraded too, so it doesn't seem a problem related to multilib.

EDIT2:
tried rebuild with debug on zlib and shared-mime-info (and without stripping) but there's no more output: sorry but I'm a supernoob with gdb...
openbox gives exactly the same error in gdb.

----

btw, tnx a lot Pat and crew for the bunch of updates, much appreciated, I mean it

Hrm, I'd run into this before 13.1 was released, but I pushed it to the back burner since we didn't really have time to investigate any additional problems then. However, here's what I found today:

http://tinyurl.com/zlib-abi-break

Upgrade libxml2 to 2.7.7 and all should be fine.

(yes, it's a horrible tinyurl link name, because it was NOT an abi break by zlib)

3 members found this post helpful.

thank you a lot robby, nice catch : tried it now and with updating libxml2 to 2.7.7 I got no more segfaults on 64-current.

this solved my problem as well with VMWare Workstation

Thanks

waiting for an official update, if someone likes a prebuilt package in the meantime, you can try one x86_64 package I built with Pat's slackbuild (md5).

EDIT: packages links don't work anymore as the new libxml2 landed in -current

I built another also for ARCH=i486 (32bit, md5) in case someone needs it/want to try it with new zlib.

EDIT: packages links don't work anymore as the new libxml2 landed in -current

It wasn't needed on 32bit (for whatever reason, the segfault didn't occur there), but either way, it's upgraded in the -current tree now. Thanks for the help :-)

thanks to you for the solution

I'll remove the packages I've done to avoid duplicates with -current.

When I run VMware-Workstation-Full-7.1.4-385536.x86_64.bundle, the script dies while trying (or after?) uninstalling VMware Workstation 7.1.0:


./VMware-Workstation-Full-7.1.4-385536.x86_64.bundle --console
Extracting VMware Installer...done.
You must accept the VMware VIX API End User License Agreement to
continue. Press Enter to proceed.


VMware(R) Software Developer Kit (SDK) Agreement

<snip>

Do you agree? [yes/no]: yes


The product is ready to be installed. Press Enter to begin
installation or Ctrl-C to cancel.


Uninstalling VMware Workstation 7.1.0


[######################################################################] 100%
Installation was unsuccessful.



I have:

% gcc --version
gcc (GCC) 4.6.0 20110530 (Red Hat 4.6.0-9)

% rpm -qa | grep c++
libsigc++20-devel-2.2.9-1.fc15.x86_64
libstdc++-4.6.0-9.fc15.i686
libstdc++-devel-4.6.0-9.fc15.x86_64
ImageMagick-c++-devel-6.6.5.10-19.fc15.x86_64
libsigc++20-2.2.9-1.fc15.x86_64
libstdc++-docs-4.6.0-9.fc15.x86_64
dbus-c++-0.5.0-0.12.20090203git13281b3.fc15.x86_64
libstdc++-4.6.0-9.fc15.x86_64
ImageMagick-c++-6.6.5.10-19.fc15.x86_64
libsigc++20-2.2.9-1.fc15.i686
gcc-c++-4.6.0-9.fc15.x86_64
compat-libstdc++-33-3.2.3-68.1.x86_64

% rpm -qa | grep libxml2
libxml2-2.7.8-6.fc15.x86_64
libxml2-devel-2.7.8-6.fc15.x86_64
libxml2-python-2.7.8-6.fc15.x86_64
libxml2-2.7.8-6.fc15.i686
libxml2-debuginfo-2.7.8-6.fc15.x86_64

% rpm -qa | grep zlib | sort
jzlib-1.0.7-9.fc15.noarch
zlib-1.2.5-3.fc15.i686
zlib-1.2.5-3.fc15.x86_64
zlib-debuginfo-1.2.5-3.fc15.x86_64
zlib-devel-1.2.5-3.fc15.x86_64

Dude, you're in the Slackware forum asking about vmware on fedora. Seriously?

1 members found this post helpful.

Sorry to bother the Slackers.-) How different is Slackware from Fedora?

I'm desperate. I'll ask anyone. VMware wants money before they'll help you figure out why their software won't install.
Last year I paid them for help after experiencing a similar problem with last year's release.
I spent a dismal month bouncing questions back and forth between India and here, with a one day turn-around. They wouldn't read what I wrote. We would waste days where they would ask me to run some diagnostic which I had already run and emailed to them. They had me replace my SuSE installation with Ubuntu. THAT was a disaster. The Ubuntu community is really slow in helping even their own. Then I installed Fedora. Everything worked....until this year's Fedora upgrade to 15 and VMWare's 7.1.4 release. Fortunately, there are enough bits and pieces around the different forums that I'm making progress, but there are probably just one or two things that are keeping it from working.

Believe me, we Linux users need to support each other, because VMWare doesn't seem to make customer satisfaction a very high goal.

0 members found this post helpful.

Hmm...have you tried the following steps outlined in this document?:
http://kb.vmware.com/selfservice/mic...&externalId=38

Install Slackware, then try to install VMWare in Slackware, then we'll talk.

Eric

ok. thanks