[Touch-packages] [Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
I did not reproduce this issue with ubuntu 22.04 desktop beta image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Hi Christian Ehrhardt, Would you kindly please help ask somebody to take care of this issue ? Thanks very much. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
I can reproduce the issue with jammy-desktop-amd64.iso daily build 20/Mar/2022 from https://cdimage.ubuntu.com/daily-live/current/jammy- desktop-amd64.iso -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Any updates for this issue ? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1850775] Re: DNS info is not loaded by dhclient
DNS setting is correct with updated systemd package 242-7ubuntu3 from -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1838525] Re: LVM setup fails to install grub on virtio storage
Verified: this issue is fixed in GA iso -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Invalid Status in debian-installer package in Debian: New Bug description: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian-installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is visible both in the d-i screen and by running `ps` on a different console. Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/ It's interesting how this doesn't happen when not using virtio. If from the commands above the "if=virtio" option is dropped then everything works as expected. In this case the target block device is called /dev/sda instead of /dev/vda. To manage notifications about this bug go to:
[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
No file /etc/network/interfaces in ubuntu-19.10-beta-desktop-amd64.iso. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1805953] Re: perl is not installed correctly ubuntu-18.10-server-amd64.iso
VMware PR https://bugzilla.eng.vmware.com/show_bug.cgi?id=919 ** Bug watch added: bugzilla.eng.vmware.com/ #919 https://bugzilla.eng.vmware.com/show_bug.cgi?id=919 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1805953 Title: perl is not installed correctly ubuntu-18.10-server-amd64.iso Status in perl package in Ubuntu: Invalid Bug description: perl is not installed correctly in ubuntu-18.10-server-amd64.iso. It can be fixed when reinstall perl with command "apt install perl" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1805953/+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 1805953] Re: perl is not installed correctly ubuntu-18.10-server-amd64.iso
I install OS with iso ubuntu-18.10-server-amd64.iso. After installation, the perl exists. But it lacks file /usr/share/perl/5.26/File/stat.pm when comparing to the installed OS system with ISO ubuntu-18.10-live- server-amd64.iso/ubuntu-18.10-desktop-amd64.iso/ubuntu-18.04-server- amd64.iso. So it's strange why this file is missing after I installed OS with ubuntu-18.10-server-amd64.iso. I change the issue's status for your confirmation. Thanks. ** Changed in: perl (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1805953 Title: perl is not installed correctly ubuntu-18.10-server-amd64.iso Status in perl package in Ubuntu: Confirmed Bug description: perl is not installed correctly in ubuntu-18.10-server-amd64.iso. It can be fixed when reinstall perl with command "apt install perl" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1805953/+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 1805953] Re: perl is not installed correctly ubuntu-18.10-server-amd64.iso
Missing perl module File::stat.pm on ubuntu-18.10-server-amd64.iso Is the "/usr/share/perl/5.26/File/stat.pm" existing? ubuntu-18.10-server-amd64.isoNO ubuntu-18.10-live-server-amd64.iso YES ubuntu-18.10-desktop-amd64.iso YES ubuntu-18.04-server-amd64.isoYES ** Changed in: perl (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1805953 Title: perl is not installed correctly ubuntu-18.10-server-amd64.iso Status in perl package in Ubuntu: New Bug description: perl is not installed correctly in ubuntu-18.10-server-amd64.iso. It can be fixed when reinstall perl with command "apt install perl" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1805953/+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 1796438] [NEW] cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd
Public bug reported: In ubuntu 18.10, error message is displayed at initramfs stage when cryptsetup is not included to the initrd. vmware@ubuntu-18.10:~$ sudo update-initramfs -u [sudo] password for vmware: update-initramfs: Generating /boot/initrd.img-4.18.0-8-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. rmdir: failed to remove '/var/tmp/mkinitramfs_mxUIaj/var/cache/ldconfig': No such file or directory vmware@ubuntu-1810:~$ There is a bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Package changed: cloud-init (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1796438 Title: cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd Status in initramfs-tools package in Ubuntu: New Bug description: In ubuntu 18.10, error message is displayed at initramfs stage when cryptsetup is not included to the initrd. vmware@ubuntu-18.10:~$ sudo update-initramfs -u [sudo] password for vmware: update-initramfs: Generating /boot/initrd.img-4.18.0-8-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. rmdir: failed to remove '/var/tmp/mkinitramfs_mxUIaj/var/cache/ldconfig': No such file or directory vmware@ubuntu-1810:~$ There is a bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796438/+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 1722897] Re: Unexpected behavior with Wayland desktop
This is urgent issue because ubuntu will GA on Oct/19/17. Is it possible to be get fixed in GA ? thanks very much! -- 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/1722897 Title: Unexpected behavior with Wayland desktop Status in xorg package in Ubuntu: Confirmed 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :