[Desktop-packages] [Bug 1722897] [NEW] Unexpected behavior with Wayland desktop
Public bug reported: I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd like to chat with someone about how Ubuntu Wayland works. Specifically, when a VM is configured to have 4MB of GPU memory, we have trouble setting modes above 1024x768@32bpp even though there's technically enough GPU memory to handle the framebuffer. This does not happen with Ubuntu 17.10 Xorg desktop. >From what I can see there are two things: 1. Ubuntu Wayland seems to be allocated 2-3 framebuffer sized surfaces. Is it doing triple-buffering? 2. For certain modes, e.g. 1360x768 and 800x600, the pitch coming into .create_fb is greater than mode->width * bytes-per-pixel. For instance, for 800x600@32bpp, the requested pitch is 3328 instead of 3200. These two behaviors is different from what we assumed for low memory configurations, and so is causing some issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 Uname: Linux 4.13.0-syeh-v4.13 x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 12:50:08 2017 DistUpgraded: Fresh install DistroCodename: artful 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 2017-10-03 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) 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 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-username-v4.13 root=UUID=e5e24738-af43-4671-9595-cccd3f4c77b8 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet modprobe.blacklist=vmwgfx kgdboc=ttyS1,115200 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 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:bd05/19/2017: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.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 11 12:38:36 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory vmware(0): Failed to open drm. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- 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/1722897 Title: Unexpected behavior with Wayland desktop Status in xorg package in Ubuntu: New Bug description: I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd like to chat with someone about how Ubuntu Wayland works. Specifically, when a VM is configured to have 4MB of GPU memory, we have trouble setting modes above 1024x768@32bpp even though there's technically enough GPU memory to handle the framebuffer. This does not happen with Ubuntu 17.10 Xorg desktop. From what I can see there are two things: 1. Ubuntu Wayland seems to be allocated
[Desktop-packages] [Bug 1693021] Re: Need two commits cherry-picked from Mesa main into 16.10
Sorry, the title should've been "one commit" rather than "two commits" -- 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/1693021 Title: Need two commits cherry-picked from Mesa main into 16.10 Status in mesa package in Ubuntu: New Bug description: Hi, Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10? https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296 I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not there. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1693021/+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 1693021] [NEW] Need two commits cherry-picked from Mesa main into 16.10
Public bug reported: Hi, Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10? https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296 I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not there. thanks ** 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/1693021 Title: Need two commits cherry-picked from Mesa main into 16.10 Status in mesa package in Ubuntu: New Bug description: Hi, Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10? https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296 I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not there. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1693021/+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 1657296] [NEW] Need two commits cherry-picked from Mesa main into 16.04
Public bug reported: Hi, On Ubuntu 16.04, VMWare customers are running into a couple of issues: 1. Any app that uses glGenMipmap command will not work properly or crash (https://communities.vmware.com/thread/537924) 2. vmwgfx_dri.so is sending provoking vertex command when it is not supposed to. I have contacted the Mesa maintainer, but unfortunately 11.2.x is no longer being actively supported, and so I couldn't get the fixes cherry- picked over. Is there an internal process in Canonical to cherry-pick fixes over? To fix the two defects above, please cherry pick the following two commits from Mesa main: 7988513ac3d86ba367fbe44e73fe483ff96aaa29 ca531aeeb120cdd --- 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) libgl1-mesa-dri: Installed: 11.2.0-1ubuntu2.2 Candidate: 11.2.0-1ubuntu2.2 Version table: *** 11.2.0-1ubuntu2.2 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 11.2.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) Google Earth will run into the glGenMipmap issue, i.e. dmesg will show "Unsupported command" I'm not sure if the 2nd issue is observable without a debug build of VMWare software... 4) Through internal testing, the two commits above should the issues mentioned. ** 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/1657296 Title: Need two commits cherry-picked from Mesa main into 16.04 Status in mesa package in Ubuntu: New Bug description: Hi, On Ubuntu 16.04, VMWare customers are running into a couple of issues: 1. Any app that uses glGenMipmap command will not work properly or crash (https://communities.vmware.com/thread/537924) 2. vmwgfx_dri.so is sending provoking vertex command when it is not supposed to. I have contacted the Mesa maintainer, but unfortunately 11.2.x is no longer being actively supported, and so I couldn't get the fixes cherry-picked over. Is there an internal process in Canonical to cherry-pick fixes over? To fix the two defects above, please cherry pick the following two commits from Mesa main: 7988513ac3d86ba367fbe44e73fe483ff96aaa29 ca531aeeb120cdd --- 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) libgl1-mesa-dri: Installed: 11.2.0-1ubuntu2.2 Candidate: 11.2.0-1ubuntu2.2 Version table: *** 11.2.0-1ubuntu2.2 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 11.2.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) Google Earth will run into the glGenMipmap issue, i.e. dmesg will show "Unsupported command" I'm not sure if the 2nd issue is observable without a debug build of VMWare software... 4) Through internal testing, the two commits above should the issues mentioned. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296/+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 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
This also fixes a defect we are seeing in a VMWare guest with Ubuntu
16.10. The issue was wallpaper does not get resized when changing to a
higher desktop resolution, leaving a black border around the wallpaper,
and corruption occurs when when dragging a window over that black
border.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering after plugging in a
second monitor
Status in nautilus package in Ubuntu:
Fix Released
Status in nautilus source package in Yakkety:
Fix Released
Bug description:
[ Description ]
Nautilus's wallpaper drawing doesn't respond to changes in monitor
configuration. Instead of your wallpaper you see black.
[ Fix ]
Inside nautilus, the wallpaper widget connects to GTK's "monitors-
changed" signal when it is constructed. It does this only once the
widget is realized - a "realized" signal handler connects to
"monitors-changed". In Yakkety, the "realized" signal handler is
connected after the widget is already realized, meaning that the
signal handler isn't called and we don't connect to the "monitors-
changed" signal.
The proposed fix remedies this by checking if we are realized and
explicitly calling the signal handler if so.
[ QA ]
Have multiple monitors. Have only one of them connected. Log in. Plug
in one monitor. If it's autoactivated, check you see your background
on both monitors. If not, activate it ("Displays") and do the same.
[ Regression potential ]
I'm not sure why or where the order changed to make the widget be
realized earlier, if it matters or if this was always buggy and we got
lucky. I would guess a refactoring in Nautilus itself, and so the
proposed fix is safe, but watch out for other weirdness.
[ Original description ]
Using 16.04 daily image: 20160919(downloading date)
With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
Graphic chips:
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530
[8086:191b] (rev 06)
01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M]
[10de:139b] (rev ff)
Desktop wallpaper on extended display shows black background only, and
the hdmi detection is very unstable.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
Uname: Linux 4.8.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.3-0ubuntu7
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
Date: Fri Sep 23 05:30:30 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Dell HD Graphics 530 [1028:06e4]
InstallationDate: Installed on 2016-09-20 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
Bus 001 Device 004: ID 0c45:6713 Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160706-1ubuntu1
