On Wed, 24 May 2017 18:39:28 -0400, Adam Carter wrote: > > [1 <text/plain; UTF-8 (7bit)>] > [2 <text/html; UTF-8 (quoted-printable)>] > On Thu, May 25, 2017 at 4:52 AM, Nikos Chantziaras <rea...@gmail.com> wrote: > > VMWare Workstation stopped working on ~amd64. And I don't know which of the > updated packages broke it. Before I start reverting all emerges I made in the > last 20 days or so (it's a BIG list according to qlop), has someone already > figured out what broke it? > > When I say "stopped working", I mean nothing happens: > > $ vmware > $ > > (No output. Doesn't start.) > > If I enable the "bundled-libs" USE flag, I get: > > $ vmware > Loop on signal 11 > > $ > > And nothing happens after that error message. > > There's two hacks i use to make workstation run on ~amd64; > cp /lib64/libz.so.1 to /opt/vmware/lib/vmware/lib/libz.so.1/ > > And > unset VMWARE_USE_SHIPPED_LIBS && vmware & > > I am under the impression that i needed +bundled-libs with the unset > VMWARE_USE_SHIPPED_LIBS.but that seems counter intuitive so would be worth > checking. >
I tried this maybe 6 months ago under kernel 4.4.39 and I got no joy. I wonder if I should try it again, or should I try to install their bundle? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com