** Changed in: linux (Ubuntu)
Assignee: Kamal Mostafa (kamalmostafa) => (unassigned)
** Changed in: linux (Ubuntu Trusty)
Assignee: Kamal Mostafa (kamalmostafa) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Utopic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
According to this thread in vmware communities
https://communities.vmware.com/thread/481038?start=15&tstart=0 the
source of the problem is that there is a clash between the X.org driver
and the vmwgfx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Saucy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Saucy)
Status: New => In Progress
** Changed in: linux (Ubuntu Precise)
Status: New =>
Thanks for testing all that Daniel. I think we've got the problem
identified now: It does revolve around the virtualHW.version specified
in the .vmx file (7 versus 10)... I find that if I edit my .vmx and
change my virtualHW.version from 10 to 7, then I do see the problem
behavior.
Thomas Hells
This problem is exactly the same as
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
vmware/+bug/1328898 and
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1331224
Should it be marked as duplicate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Creating a new VM with Player (virtualHW.version = "10") and moving over
the old virtual disk makes the problem go away.
Both 3.13.0-30.55 with and without 2a4faabafc reverted work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
According to this:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003746
The latest virtual hardware version is 10, while 7 corresponds to VMWare
Workstatio 8.x (the version I used to create the VM).
--
You received this bug notification because yo
The virtual hardware version of the VM (taken from the .vmx file) is
virtualHW.version = "7"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339768
Title:
VMWare graphics driver regression
To manag
Just tried 3.13.0-30.55 with 4e57808 applied and it makes no
difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339768
Title:
VMWare graphics driver regression
To manage notifications abou
It happens too with VMWare Player 6.0.3 build-1895310. I have both
versions, on different machines, and both exhibit the same behaviour.
Both hosts are Windows 7 machines.
The VM was copied from one machine to the other, and was created with VMWare
Workstation, not with Player.
My host is a Wind
I'm unable to reproduce this. With either Unity or XFCE desktop,
resizing the VMWare Player window works okay for me. I'm using the same
3.13.0-30.55 kernel (on both host and guest), but my VMware Player is
newer: "6.0.3 build-1895310".
Daniel, please update your VMWare Player to that version an
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Medium
Status: Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (una
The bug exists in mainline too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339768
Title:
VMWare graphics driver regression
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339768
Title:
VMWare graphics driver regression
To manage notifications about this bug go to:
https://bugs.l
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339768
Title:
VMWare graphics driver regression
To manage notifications about this bu
The regression seems to be caused by this commit:
2a4faabafcd8a1911d1dc7ae5699f2ad1103422e
I have just recompiled the kernel with this commit reverted, and now the screen
displays properly again.
This patch was included also in other kernels (Saucy and Precise for
sure).
--
You received this
19 matches
Mail list logo
