[Bug 1709667] Re: Missing desktop scaling slider in system settings
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709667 Title: Missing desktop scaling slider in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1709667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709667] Re: Missing desktop scaling slider in system settings
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 be scaled. In order to get the whole desktop experience working correctly the following sequence needs to be followed: 1. set scaling for the display to 100%. click apply. Click keep settings. 1.a. Repeat #1 because you need to do it with more feeling. 2. set the desktop to 200%. 2.a. Repeat #2 because, once again, more feeling is required to get the setting to stick than the initial click of 'keep settings'. 3. Close and re-open any applications that utilize the DPI scaling functionality. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709667 Title: Missing desktop scaling slider in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1709667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712223] Re: performing dist-upgrade results in open-vm-tools no longer working
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 Ubuntu. https://bugs.launchpad.net/bugs/1712223 Title: performing dist-upgrade results in open-vm-tools no longer working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712223] [NEW] performing dist-upgrade results in open-vm-tools no longer working
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 issue
where VMWare Workstation no longer can interact with display resolution
detection of the host monitor(s). Multiple monitor support is also lost
in the update process.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 17:09:59 2017
DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components:
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful':
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security':
{'multiverse', 'restricted', 'universe', 'main'}}
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-11-30 (264 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
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.12.0-11-generic
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
dmi.bios.date: 07/02/2015
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/02/2015: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.13.1+17.10.20170720-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.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: Mon Aug 21 16:27:55 2017
xserver.configfile: default
xserver.devices:
inputPower Button KEYBOARD, id 6
inputAT Translated Set 2 keyboard KEYBOARD, id 7
inputVirtualPS/2 VMware VMMouse MOUSE, id 8
inputVirtualPS/2 VMware VMMouse MOUSE, id 9
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2
Virtual3Virtual4Virtual5Virtual6Virtual7
Virtual8
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: vmware
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful regression reproducible single-occurrence
third-party-packages ubuntu wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712223
Title:
performing dist-upgrade results in open-vm-tools no longer working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712223/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712223] Re: performing dist-upgrade results in open-vm-tools no longer working
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.launchpad.net/ubuntu/+source/xorg/+bug/1712223/+attachment/4936705/+files/OS%20updates%20breaks%20open-vm-tools-desktop.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712223 Title: performing dist-upgrade results in open-vm-tools no longer working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709667] Re: Regression - Loss of hiDPI configuration settings
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.launchpad.net/bugs/1709667 Title: Regression - Loss of hiDPI configuration settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1709667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709667] [NEW] Regression - Loss of hiDPI configuration settings
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 option to be very useful when working on a Lenovo P70 w/ 17" 4k monitor (which neds 2x DPI scaling) and also when switching back to my multiple-monitor configuration (which doesn't need any scaling). This is a piece of functionality I use on a regular basis that is now lost. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Aug 9 09:24:28 2017 DistUpgraded: 2017-08-07 09:44:27,630 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: 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.11.0-10-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (1 days ago) dmi.bios.date: 07/02/2015 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/02/2015: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.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.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: Mon Aug 7 08:59:11 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputVirtual2 Virtual3Virtual4Virtual5Virtual6Virtual7 Virtual8 xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: vmware ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi high-resolution scaling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709667 Title: Regression - Loss of hiDPI configuration settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1709667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589721] Re: vagrant username is incorrect
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 incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1589721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589721] [NEW] vagrant username is incorrect
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: ## ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 80 (guest) => (host) (adapter 1) default: 22 (guest) => 2322 (host) (adapter 1) default: 81 (guest) => 8889 (host) (adapter 1) default: 3306 (guest) => 3307 (host) (adapter 1) default: 15672 (guest) => 8890 (host) (adapter 1) default: 22 (guest) => (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1: default: SSH username: vagrant default: SSH auth method: password default: Warning: Remote connection disconnect. Retrying... ^C==> default: Waiting for cleanup before exiting... Specifying various forms of config.ssh.username and config.ssh.password fails to get vagrant to be able to properly authenticate. Once booted up though, one can ssh into the system with the ubuntu user. This bug breaks the default vagrant workflow. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- 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 incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1589721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
