[Touch-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 Ubuntu
Touch seeded 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.vendo
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m
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, &data, GBM_BO_USE_RENDERING);
}
/Thomas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-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/EnableProposed&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0A&m=6i%2FG3qEpVSz8wL%2FaiY%2Fao74%2BAoL8VMn%2FCrCnQHHkDGo%3D%0A&s=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/PerformingSRUVerification&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0A&m=6i%2FG3qEpVSz8wL%2FaiY%2Fao74%2BAoL8VMn%2FCrCnQHHkDGo%3D%0A&s=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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370386] Re: libmirclient7 hang on client startup
OK, so from within 14.10 things appear to work OK. XMir fires up as well, so feel free to close this bug if desired. Thanks, Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1370386 Title: libmirclient7 hang on client startup Status in Mir: New Status in “mir” package in Ubuntu: New Bug description: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1370386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370386] Re: libmirclient7 hang on client startup
Sure, I'll try that, although I thought Ubuntu 14.04 had some sort of "stable mir 7" environment shipped with it. BTW is XMir still alive with 14.10? /Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1370386 Title: libmirclient7 hang on client startup Status in Mir: New Status in “mir” package in Ubuntu: New Bug description: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1370386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370386] [NEW] libmirclient7 hang on client startup
Public bug reported: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas ** Affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1370386 Title: libmirclient7 hang on client startup Status in “mir” package in Ubuntu: New Bug description: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1370386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #11 0x7fd23c5f944f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #12 0x7fd23c5fcaf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so ---Type to continue, or q 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 Ubuntu Touch seeded 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::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #11 0x7fd23c5f944f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #12 0x7fd23c5fcaf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so ---Type to continue, or q 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
