Bug 241705 - vmware segfaults after MKSHostOps XCreateImage failed
Summary: vmware segfaults after MKSHostOps XCreateImage failed
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libX11   
(Show other bugs)
Version: 6
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-29 17:54 UTC by Rasmus Ory Nielsen
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-29 20:56:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rasmus Ory Nielsen 2007-05-29 17:54:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; da-DK; rv:1.8.1.3) Gecko/20070323 BonEcho/2.0.0.3

Description of problem:
After upgrading to the latest version of libX11 vmware crashes as described on these pages:
https://bugs.launchpad.net/ubuntu/+source/vmware-player/+bug/114828
http://www.vmware.com/community/thread.jspa?messageID=630226&#630226

The solution is to install the older libX11-1.0.3-4.

Version-Release number of selected component (if applicable):
libX11-1.0.3-7.fc6

How reproducible:
Always


Steps to Reproduce:
1. Upgrade to libX11-1.0.3-7
2. Start vmware with win2k as guest
3.

Actual Results:
At the moment it changes to normal resolution it terminates with a "Signal 11" error. 

Expected Results:
Vmware should not crash.

Additional info:
I don't know if this really is a libX11 bug or a vmware bug. I chose to open a bug here, so other people could benefit from the solution (install libX11-1.0.3-4).
Comment 1 Adam Jackson 2007-05-29 20:56:47 UTC 
You are correct, this is a vmware bug.
Note You need to log in before you can comment on or make changes to this bug.