Your message dated Tue, 2 Jun 2015 12:43:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#787490: curl: VMWare doesn't start anymore
has caused the Debian Bug report #787490,
regarding libcurl3: VMWare doesn't start anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
787490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787490
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: curl
Version: 7.42.1-1
Severity: important

Dear Maintainer,

since upgrade of curl from 7.42.1-1 to 7.42.1-2 vmware stopps with signal 11
during start.
Is there a problem with libcurl3-gnutls (#342719)?

$ vmware --version
VMware Workstation 11.1.0 build-2496824

Bye



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages curl depends on:
ii  libc6     2.19-18
ii  libcurl3  7.42.1-1
ii  zlib1g    1:1.2.8.dfsg-2+b1

curl recommends no packages.

curl suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On mar, giu 02, 2015 at 09:56:09 +0200, Daniel Schröter wrote:
> Package: curl
> Version: 7.42.1-1
> Severity: important
> 
> Dear Maintainer,
> 
> since upgrade of curl from 7.42.1-1 to 7.42.1-2 vmware stopps with signal 11
> during start (if you switch the vm-windows):
> $ vmware
> Unexpected signal: 11.
> 
> [...]
> 
> 2015-06-02T09:52:53+02:00[+0.180]| vmui| I120: SymBacktrace[5]
> 00007ffd3bf27b80 rip=00007f75752d3e1a in function SSL_CTX_free in object
> /usr/lib/vmware/lib/libssl.so.1.0.1/libssl.so.1.0.1 loaded
> at 00007f7575291000
> 2015-06-02T09:52:53+02:00[+0.180]| vmui| I120: SymBacktrace[6]
> 00007ffd3bf27ba0 rip=00007f756b274c3f in function (null) in object
> /usr/lib/x86_64-linux-gnu/libcurl.so.4 loaded at 00007f756b21c000

I think the problem is in the above two log entries. The system libcurl library
is used, but vmware embeds its own libssl version. The libcurl3 package since
version 7.42.1-2 requires libssl version 1.0.2 or above, but the embedded libssl
in vmware is only 1.0.1. If this is indeed the problem, there isn't anything I
can do about it.

I think vmware also embeds its own libcurl.so.4 in /usr/lib/vmware/lib so you
may want to try to uninstall the libcurl3 package (if possible) and see if
vmware picks its own libcurl version.

In short, this isn't really a bug in the Debian package, so I'm closing it.

Cheers

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to