[Desktop-packages] [Bug 1863763] [NEW] gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows
Public bug reported:
There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an incorrect
vertical offset, making the desktop largely unusable for some customers.
The bug is fixed in latest 19.3 series and 20.0 rc series, but since
Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.
Please cherry-pick mesa master commit
451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA upload")
to fix the issue, alternatively switch to mesa 19.3 series.
Thanks,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
Uname: Linux 5.5.0+ x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 05:53:02 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-02-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0+
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/30/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1863763
Title:
gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows
Status in mesa package in Ubuntu:
New
Bug description:
There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an
incorrect vertical offset, making the desktop largely unusable for
some customers.
The bug is fixed in latest 19.3 series and 20.0 rc series, but since
Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.
Please cherry-pick mesa master commit
451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA
upload") to fix the issue, alternatively switch to mesa 19.3 series.
Thanks,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
Uname: Linux 5.5.0+ x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 05:53:02 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-02-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0+
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: Phoenix
[Desktop-packages] [Bug 1690131] Re: display adapter not working with vmware
It looks like the logs you are posting are from a physical host running the modesetting driver on top of an intel kms driver. That's AFAIK not a VMware supported configuraion. Nevertheless you shouldn't see any rendering corruption caused by the VMware drivers in the guest. Could you post the vmware.log file for the VM as well as the Xorg.0.log file from the virtual machine and the output of "dmesg" from within the virtual machine. Thanks, Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1690131 Title: display adapter not working with vmware Status in xorg package in Ubuntu: New Bug description: The virtual machine colors are corrupted when logged in to virtual host. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 11 13:00:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2017-03-20 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B250M-D3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic.efi.signed root=UUID=fbf200a7-baa7-408b-8b60-06c06081cfce ro quiet splash vt.handoff=7 SourcePackage: xorg UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: Error: no composite extension UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B250M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd11/03/2016:svnGigabyteTechnologyCo.,Ltd.:pnB250M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-D3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: B250M-D3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 11 10:36:10 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputSleep Button KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 DP-2 HDMI-1 HDMI-2 HDMI-3 xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
OK, So I tried to debug this on 17.04 with the mir demos.
What happens is that while the Mir server seems to run fine,
when the EGL mir clients import a surface from the mir server (using fds /
prime) they
typecast the XRGB surface from the mir server to an ARGB surface, which the
svga gallium driver doesn't like that and it returns an error.
That error is never caught in the mir platform EGL layer and when the
corresponding "bo" is dereferenced, the mir platform EGL layer instead
dereferences NULL, which is the error code...
So I'd say this is a combination of two Mir errors: One illegal typecast and
one failure to check
for errors.
As a side note, it would be possible for the svga driver to implement a
workaround and not error
in this case, but while real hardware may be more forgiving in this case, the
surface that the
mir client thinks is an argb surface will still be an xrgb surface and any
operation involving the
alpha channel will yield unexpected results so IMHO this needs to be fixed in
the MIR EGL layer:
Offending code: (platform_mir.c)
static struct gbm_bo *create_gbm_bo_from_buffer(struct gbm_device* gbm_dev,
MirBufferPackage *package)
{
struct gbm_import_fd_data data;
data.fd = package->fd[0];
data.width = package->width;
data.height = package->height;
data.format = GBM_FORMAT_ARGB; /* TODO: Use mir surface format */ <=
HERE!
data.stride = package->stride;
return gbm_bo_import(gbm_dev, GBM_BO_IMPORT_FD, , GBM_BO_USE_RENDERING);
}
/Thomas
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
mir::graphics::nested::detail::DisplayBuffer::make_current() ->
eglMakeCurrent() -> ... -> dri2_image_get_buffers()
[platform_mir.c:138]
Status in Mir:
New
Status in mesa package in Ubuntu:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Invalid
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8. This problem was most recently seen with version
8.11+16.04.20160310.4-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
Verified that with proposed updates in Ubuntu 12.04.5, the problem is gone. /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Fix Committed Status in “mesa” source package in Trusty: Fix Released Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
Hi! I now enabled proposed in Ubuntu 14.04 and did a full update: dpkg -s libgl1-mesa-dri says Version: 10.1.3-0ubuntu0.2 No sign of the bug symptoms. Everything working as expected. I also enabled proposed in Ubuntu 12.04.5 and did a full update: dpgk -s libgl1-mesa-dri-lts-trusty says Version: 10.1.3-0ubuntu0.1~precise1 The bug is still present. so please, if possible publish a proposed package also for Ubuntu 12.04.5 Thanks, Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Confirmed Status in “mesa” source package in Trusty: Fix Committed Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
Chris, perhaps you can help me a bit by explaining here: The buggy package in Ubuntu 12.04.5 that was on the installation iso and that I rebuilt locally with the fix before filing the bug was called mesa-lts-trusty. How does that relate to this package? Thanks, Thomas On 10/01/2014 02:04 PM, Chris J Arges wrote: Hello Thomas, or anyone else affected, Accepted mesa into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mesa/10.1.3-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://urldefense.proofpoint.com/v1/url?u=https://wiki.ubuntu.com/Testing/EnableProposedk=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0Ar=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0Am=6i%2FG3qEpVSz8wL%2FaiY%2Fao74%2BAoL8VMn%2FCrCnQHHkDGo%3D%0As=58e37f56b443c106798395284093c1e9afddd26cc0cbb6e15640474c2a568035 for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://urldefense.proofpoint.com/v1/url?u=https://wiki.ubuntu.com/QATeam/PerformingSRUVerificationk=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0Ar=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0Am=6i%2FG3qEpVSz8wL%2FaiY%2Fao74%2BAoL8VMn%2FCrCnQHHkDGo%3D%0As=46ffdc6903022c90f2b6c585f15547ddcf9fc50d556dd1d691512bd9d759bd7e . Thank you in advance! ** Changed in: mesa (Ubuntu Trusty) Status: Incomplete = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Fix Committed Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
The problem is I can't verify the bug is fixed in trusty because it doesn't show any obvious symptoms. This is probably due to different stack ordering of local variables compared to the trusty stack on precise. The only way to verify the fix is in the trusty stack on precise where the bug is very obvious... /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Fix Committed Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
[Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using easy install. Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Incomplete Status in “mesa” source package in Trusty: Incomplete Bug description: Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, winsys/svga: Fix incorrect type usage in IOCTL v2, with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
OK, I did som investigation, and it seems like even for the slightest change in a window, like a cursor blink, compiz performs a fullscreen swapbuffer, and in the case of multiple monitors, compiz performs a swapbuffer that spans all the monitors. I tried to install ccsm and disable all tweaks that could trigger this behaviour and revert to use GLX_MESA_copy_sub_buffer, but that didn't help much. Except if you start on a low resolution and change resolution to something higher. THEN compiz suddenly changes update and performs updates that are not quite that large. The only drawback is that those updates seem to cover also a number of unrelated areas that are not updated. Now needless to say this becomes very suboptimal in remoted virtual environments, and also it appears very suboptimal if llvmpipe is used. Not to mention the combination of those two... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Triaged Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365403] [NEW] unity / compiz crash when switching resolution
Public bug reported: When using unity / compiz on top of llvmpipe and switching resolution from something lower to 1600x1200 (This is a virtual machine, so this happens regularly), compiz crashes. Description:Ubuntu 14.04.1 LTS Release:14.04 libgl1-mesa-dri: Installed: 10.1.3-0ubuntu0.1 Expected: compiz shouldn't crash. (gdb) bt #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 #1 0x7fd2432f991e in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x7fd2432fa412 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #3 0x7fd2432f9abe in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x7fd2432fa984 in XPutImage () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x7fd22fb8a576 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 #6 0x7fd22e5a7d5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #7 0x7fd22e5a8460 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #8 0x7fd22e5a7e48 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #9 0x7fd22fddb281 in GLXDoubleBuffer::blit(CompRegion const) const () from /usr/lib/compiz/libopengl.so #10 0x7fd22fdd94da in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #11 0x7fd23c5f944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #12 0x7fd23c5fcaf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so ---Type return to continue, or q return to quit--- #13 0x7fd2441777ed in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #14 0x7fd24417789f in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #15 0x7fd244176dfd in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #16 0x7fd24266335f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #17 0x7fd242155ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fd242156048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fd24215630a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fd24413215b in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #21 0x00401981 in main () (gdb) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365403 Title: unity / compiz crash when switching resolution Status in “mesa” package in Ubuntu: New Bug description: When using unity / compiz on top of llvmpipe and switching resolution from something lower to 1600x1200 (This is a virtual machine, so this happens regularly), compiz crashes. Description: Ubuntu 14.04.1 LTS Release: 14.04 libgl1-mesa-dri: Installed: 10.1.3-0ubuntu0.1 Expected: compiz shouldn't crash. (gdb) bt #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 #1 0x7fd2432f991e in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x7fd2432fa412 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #3 0x7fd2432f9abe in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x7fd2432fa984 in XPutImage () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x7fd22fb8a576 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 #6 0x7fd22e5a7d5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #7 0x7fd22e5a8460 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #8 0x7fd22e5a7e48 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #9 0x7fd22fddb281 in GLXDoubleBuffer::blit(CompRegion const) const () from /usr/lib/compiz/libopengl.so #10 0x7fd22fdd94da in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #11 0x7fd23c5f944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #12 0x7fd23c5fcaf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so ---Type return to continue, or q return to quit--- #13 0x7fd2441777ed in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #14 0x7fd24417789f in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #15 0x7fd244176dfd in CompTimeoutSource::dispatch(sigc::slot_base*)
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
OK, So I've finally been able to do a bit of testing with Ubuntu 14.04 If run without 3d support on llvmpipe, it's very CPU-hungry. A bit more so than Ubuntu 13.04 AFAICT. For Ubuntu on VMware this becomes troublesome primarily on ESX, but the problems were introduced with the drop of Unity 2D. I haven't dug thoroughly into why it hurts so much on ESX. Could it perhaps be that Unity / Compiz is performing full-screen flips when only a part of the screen is updated? Also we have severe performance problems when running fully 3D accelerated with workstation / fusion on multi-monitor setups. That's partly due to how the VMware device updates screens but Ubunut 14.04 stands out as particularly slow here. Also needs further investigation... /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Triaged Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Thanks. I'm still investigating the impact when run on our ESX software-based GPU. For the settings COMPIZ_CONFIG_PROFILE=ubuntu UNITY_LOW_GFX_MODE=1 compiz --replace Is it possible (for an average user) to easily make these part of the login procedure? Thanks, Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Triaged Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Hi! The 12.04 vs 14.04 compiz issue indeed seems fishy. I can't even get compiz from 12.04 to start on my 14.04 system. I'll double-check with VMware QE. However, the issue is, according to our testers present when running in 3D mode on ESX (on a slow llvmpipe-based GPU), but I guess in that case, Unity has no way of detecting that the GPU is slow, and hence runs with all effects enabled? /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: New Status in “compiz” package in Ubuntu: Confirmed Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Yes. we were aware of the Unity2D vs Unity3D difference. However, there *is* 3D support on vmware (although sometimes slow) and part of the problem is that also with 3D enabled, Ubuntu 14.04 is slower than with 3D enabled on12.04, although we haven't quantified that yet, and we assumed that any improvements here could also be applied to Unity 3D in software mode But as you mention, the problem seems to be more complex due to the fact that many effects are already disabled in software mode... Thanks, /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: New Status in “compiz” package in Ubuntu: Confirmed Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Hi! Thanks. I think we need to discuss this internally first. The reason is that sometimes the virtual GPU is backed by a fast physical GPU. Sometimes it's not, and it's only in the latter case there is a performance issue, in the fast case, we'd want all effects enabled. And also when the GPU is not enabled at all and compiz-on-llvmpipe kicks in, but as you say there's not much to be done in that case. Thanks a lot for your help. I'll get back to you next week. /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: New Status in “compiz” package in Ubuntu: Confirmed Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
I'm not sure whether there's a way to raise the importance / severity of this bug, but according to VMwre QE, this severely affects the usability of Ubuntu 14.04 on ESX. /Thomas -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: New Status in “compiz” package in Ubuntu: Confirmed Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like modesetting. Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289679] Re: Ubuntu 14.04 in VMWare: Unresponsive desktop when minimizing windows and Compiz is at 100% CPU
This bug is most likely a known TTM object regression and should be fixed in kernel Ubuntu 3.13.0-17.37. Could you please verify that that's the case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1289679 Title: Ubuntu 14.04 in VMWare: Unresponsive desktop when minimizing windows and Compiz is at 100% CPU Status in “compiz” package in Ubuntu: New Bug description: I'm running Ubuntu 14.04 in VMWare and anytime I minimize a window, the screen will freeze. When I ssh into the system, I see that compiz is taking up 100% of the CPU. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140305-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: [5.981323] intel_rapl: no valid rapl domains found in package 0 [6.890931] sda1: WRITE SAME failed. Manually zeroing. [ 15.803332] systemd-hostnamed[2798]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Fri Mar 7 20:34:37 2014 DistUpgraded: 2014-03-06 13:07:43,806 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2013-11-03 (124 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=d49ac36d-be6e-4fac-8944-7d6414e53295 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: compiz UpgradeStatus: Upgraded to trusty on 2014-03-06 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 7 20:13:45 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: No surface to present from. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1289679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
