With a bit more testing I have one other issue related to the
enhancement -- when I add a secondary monitory and I adjust the scaling
from one of the two options on a 2560x1550 monitor (100% or 200%) the
apply button is not visible anywhere to actually set the setting.
--
You received this bug no
The new implementation does work for updating the settings; however,
it's glitchy.
What I mean by that is when one has the settings set for 200% scaling,
reboots the VM and then logs back in (at least in VMWare -- haven't
tested elsewhere) the scaling for text is at 100%; however, icons appear
to
I can confirm that using X11 as you suggested instead of Wayland is a
viable workaround and that both multi-monitor support and resolution re-
scaling work when moving VMWare Workstation around.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
At first I thought this bug was caused with the recent changes in open-
vm-tools 10.1.10; however, after restoring my VM to the snapshot that
had 17.04 and re-performing the dist-upgrade with open-vm-tools and
open-vm-tools-desktop held at 10.1.5 I am experiencing the same iss
additional information about when one doesn't hold the package back
(note the error from VMWare Workstation 12.5).
Same thing happens even if the open-vm-tools and open-vm-tools-desktop
are held at 10.1.5.
** Attachment added: "OS updates breaks open-vm-tools-desktop.png"
https://bugs.launchp
The workaround here is to manually execute
```gsettings set org.gnome.desktop.interface scaling-factor 2```
and then restart the system to be into a scaled (2x) mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager)
... there is no longer the ability to configure the HiDPI scaling within
the window manager. This may be an intentional regression or simply
something that got passed by. But I find this configuration opt
Cross referencing to older bug report in a different project:
https://bugs.launchpad.net/cloud-images/+bug/1569237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589721
Title:
vagrant username is in
Public bug reported:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/xenial64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: Setting the name of the VM: ###