[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Sorry for the late feedback, but sharing here: AWS docs regarding best practices regarding cpu-starvation [1] do not recommend disabling the irqbalance service. Quoting the doc: > "Note: we do not recommend disabling irqbalance service. ENA driver doesn’t provide affinity hints, and if device reset happens while irqbalance is disabled, this might cause undesirable IRQ distribution with multiple IRQs landing on the same CPU core." Other customers that have hit issues with irqbalance were running very specific workloads and were aware of the need to turn it off, so we would prefer to keep irqbalance. [1] https://github.com/amzn/amzn- drivers/blob/master/kernel/linux/ena/ENA_Linux_Best_Practices.rst#cpu- starvation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2049061] [NEW] adsysctl update with a domain user fails if KRB5CCNAME is not set
Public bug reported:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set,
running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update
" it works.
The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It seems
like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https://pastebin.ubuntu.com/p/FjyTWQChjM/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
[deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2049061
Title:
adsysctl update with a domain user fails if KRB5CCNAME is not set
Status in adsys package in Ubuntu:
New
Bug description:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable
set, running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update
" it works.
The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It
seems like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https://pastebin.ubuntu.com/p/FjyTWQChjM/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
[deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+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 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I've tested this in Lunar and Mantic. TL;DR: In Lunar I hit the exact same issue as in Kinetic. After installing adsys, I'm no longer able to login using a domain user. On Mantic, it works fine and I'm able to login even after installing adsys. On the other hand, both Lunar and Mantic have the same issue with the kerberos keytab / credential cache missing the service principal for ldap/ec2amaz-hg2r0q8.fabio-rg@fabio-rg.com. Details: - Lunar: https://pastebin.ubuntu.com/p/mg7xXzM79N/ - Mantic: https://pastebin.ubuntu.com/p/bfGhnCdkjJ/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Confirmed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I just tested Ubuntu 22.04 and I can confirm it fixes the issue. First, used 22.04 with the current mutter version available in jammy- updates: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And I do hit the error when trying to revert after changing the scale: Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:03:38 U-20CG3JVH1ALS3 gnome-shell[3048]: Xlib: extension "DPMS" missing on display ":1". Then, I upgraded to package from -proposed: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And now the error is no longer logged and I can successfully revert: Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 59 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 61 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 61 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 63 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 63 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 65 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 65 at 1.00 failed Scalig CRTC 65 at 1.00 failed (The errors above can be ignored for now as their are a known problem with Xdcv, which is further explained in comment #16) Marking as verification-done ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv:
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi, Thank you for the package in -proposed. I just tested Ubuntu 22.04 and I can confirm it fixes the issue. First, used 22.04 with the current mutter version available in jammy- updates: user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 mutter-common: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And I do hit the error when trying to revert after changing the scale: Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:40:40 U-2RVWD6LKXR3GE gnome-shell[3186]: Xlib: extension "DPMS" missing on display ":1". Then, I upgraded to package from -proposed: user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user0: mutter-common: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And now the error is no longer logged and I can successfully revert: Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 59 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 61 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 61 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 63 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 63 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 65 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 65 at 1.00 failed (The errors above can be ignored for now as their are a known problem with Xdcv, which is further explained in comment #16) Marking as verification-done ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2 with Jammy. I'll test again when 42.9-0ubuntu3 is available in -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] When running GNOME on the Xdcv X11 server, changing the display scale in Settings and then clicking 'Revert Settings' instead of 'Keep Changes' does not revert the settings. [ Test Plan ] Very complicated; see comment #8. [ Where problems could occur ] In the list of available graphics modes in Xorg sessions on jammy only (an equivalent fix already exists in later Ubuntu releases). [ Original Description ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I've tested the mutter packages from -proposed in an AWS Workspace: https://pastebin.ubuntu.com/p/9Yvgfs7yZr/ And I'm able to successfully change the scale to 200% and then revert the setting. The following messages are logged when changing to 200%: https://pastebin.ubuntu.com/p/Y5QdXSqcsW/ And then when you try to revert: https://pastebin.ubuntu.com/p/cYP7JKryx9/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Status in mutter source package in Lunar: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] When running GNOME on the Xdcv X11 server, changing the display scale in Settings and then clicking 'Revert Settings' instead of 'Keep Changes' does not revert the settings. [ Test Plan ] Very complicated; see comment #8. [ Where problems could occur ] In the list of available graphics modes in Xorg sessions on jammy only (an equivalent fix already exists in later Ubuntu releases). [ Original Description ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I've tested Focal and it works well with adsys from -proposed: https://pastebin.ubuntu.com/p/6RBcBpZq2T/ And also does Jammy: https://pastebin.ubuntu.com/p/pqvgSkkmcQ/ I'm having issues with Kinetic. When I install adsys, I'm no longer able to login to the instance, I'm getting the following errors when trying to login: https://pastebin.ubuntu.com/p/hh9SHB3ZXx/ It works if I purge the adsys package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Thank you very much for the great job narrowing this, Daniel! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up- installing-linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the following process being started: /usr/bin/Xdcv -output 800x600+0+0 -output
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Daniel, Regarding 3 (the blank screen issue when enabling a monitor): I can confirm that the issue happens when you're using Workspaces client 5.9.0.4129 (Windows client version) and no longer happens (even with Xdcv + Gnome) in 5.10.0.4196. And, by checking the client release notes [1]: "Resolved black screen issue when using multiple monitors with Ubuntu WorkSpaces" [1] https://docs.aws.amazon.com/workspaces/latest/userguide/amazon- workspaces-windows-client.html#windows-release-notes Regards, Fabio Martins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you will also need to look at the details shared by Daniel in his comment #16. Otherwise, even if we fix the zero hz issue, you will be able to change/revert scale, but will also need to make sure fractional scaling is disabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Daniel, A few items to make sure I'm on the same page: 1. So, IIUC, you're saying that the "final fix" should be the vv5 package, which contains the fix to the zero hz bug (loosening mutter to accept zero-Hz, as this is the bogus refresh rate being reported by Xdcv) + the caveat for AWS to either fix Xdcv or never try to enable Fractional scaling in the instance (details in your comment#16), is that so? 2. Regarding your comment on bug 1857392 and bug 2007742 being present, iiuc they do not have a noticeable impact (other than spamming the log). 3. Also, I need to mention that I went ahead and tried once more the vv5 package on a AWS Workspace, and I can no longer reproduce the blank screen. Now I see these logs [1] and the scale does get reverted from 200% to 100%. https://pastebin.ubuntu.com/p/JpVsjbQzsQ/ 4. If 1 above is correct, then where (if anywhere) we are going to investigate the situation where vv5 causes the other monitors to get automatically enabled? Regards, Fabio Martins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1 --auto" to enable another
monitor using Budgie and Xfce (I believe none of them use mutter), and I
can't reproduce the "blank screen". It doesn't really do anything, but
also doesn't reproduce the blank screen issue.
This is what I see in Xfce:
https://pastebin.ubuntu.com/p/BNs9KJqbHz/
And Budgie:
https://pastebin.ubuntu.com/p/pKTGzJb8bN/
My previous suggestion (patch with zero hz fix + no fractional scaling)
was because I thought vv1 was also exposed to the issue you mentioned on
comment #19 ("fractional scaling patch is trying to implement the revert
using fractional scaling"), but I guess not, and it still fails with the
"Invalid mode 800x600 (-nan)" errors, which is the zero hz issue, and
led us to vv2 and then vv4.
So, the current situation is that either with vv4 (zero hz patch + no
fractional scaling) OR vv5 with fractional scaling disabled (zero hz
patch included) we get to the situation where the extra monitors are
automatically enabled and the resolution is changed to 800x600:
https://pastebin.ubuntu.com/p/k822YMHM5v/
And IIUC this is what needs to be investigated next.
And no need to apologize if not able to respond this daily, completely
understandable and you're already doing a lot for this bug. Thank you
very very much for that!
I'll also be OoO for the next couple of days, back on Monday anyway.
Cheers,
Fabio Martins
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782
Title:
Xdcv: Changing display scale setting and reverting it fails
Status in mutter package in Ubuntu:
In Progress
Bug description:
In Amazon Workspaces running Ubuntu 22.04, when attempting to change
the Scale in the Gnome Display settings, if you click on a different
scale (i.e. changing from 100% to 200%) and hitting apply, it will
bring up a prompt asking if you want to keep or revert the changes and
there will be a timer of 20 seconds. If you try to revert the changes
(either by letting the timer expire or by clicking the "revert"
button), we will hit one of the following two behaviors:
1 - The setting won't revert and will keep scaled
2 - gnome-shell will show some error messages in syslog and the
display will be "corrupted", where the only window you are able to
click is the display setting and if you try to drag it, it will leave
a "blur" throughout the window (per discussions, this seems to be
https://launchpad.net/bugs/1924689)
For both situations, changing the display resolution (i.e. going into
and out of full screen in the workspaces client) will fix the issue
When hitting situation 1, syslog shows:
May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
'unknown unknown'
When hitting situation 2, syslog shows:
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown
unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling
on crtc 59 to 1.00, error id 2
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS"
missing on display ":1".
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label
(0x557090d07de0), has been already disposed — impossible to access it. This
might be caused by the object having been destroyed from C code using something
such as destroy(), dispose(), or remove() vfuncs.
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context
0x557090bee180 ==
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349
(2cdac32b2e20 @ 105)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42
(2cdac32a5d80 @ 27)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError:
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
> Try logging into a non-GNOME Xorg session on Workspaces > if you can. Then use the 'xrandr' command to set a mode > to turn on one of the unused virtual monitors. If that > causes the DCV client to go blank then we have proven > it's not mutter's fault. I did test that with a Cinnamon session and confirmed it. I basically did: xrandr --output VNC-output-1 --auto and it immediately goes to a blank screen OK, so saying out loud my understanding of this issue so far, so as to check it's correct. The problems are: - Fractional scaling is supported in RandR 1.3 or newer - Xdcv reports its RandR version is 1.6, but when you try to use fraction scaling it errors (error id 2) - The corruption bug 1924689 may be caused by the fractional scaling patch (or a side effect of the "error id 2"?) - Xdcv is reporting a bogus refresh rate - There's a "config history" issue identified by Mustafa in comments #26 and #30 What we've been doing now to try to narrow it down is: A - The "Zero Hz" fix is basically loosening mutter to accept zero-Hz, as this is the bogus refresh rate being reported by Xdcv B - vv4 fix = no fractional scaling + "zero Hz" fix C - vv5 fix = re-adds fractional scaling + "zero Hz" fix And out of it, we've confirmed in local VM / Workspaces tests that 1 - Without fractional scaling patch (vv4) / with fractional scaling disabled, we can't reproduce the "Failed to restore previous configuration: Invalid mode" / "Impossible to set scaling on crtc" errors 2 - The "Zero Hz" fix causes a side-effect of enabling the unused monitors (tbd if this is a bug) 2a. If you manually disable 3 monitors (keeping only one) and then try to apply / revert 200% scale, it errors [1] and sets resolution back to 800x600 3 - When enabling unused monitors in Workspaces, we get a blank screen (which I've confirmed through cinnamon / xrandr that it must be a problem with the Workspaces client when enabling a monitor) For the "zero Hz" problem, if I understand correctly, it is a bogus issue without a noticeable impact in usage. On the other hand, due to the "zero Hz" fix introducing problems 2 and 2a above, I'm skeptical on validating that avoiding fractional scaling fixes our issue (item 1 above). If the "zero hz" issue is really just bogus, should we try a "vv6" build completely disabling fractional scaling for the Xdcv use case (on apply and revert), but not including the "zero hz" fix? This way we would be able to validate item 1 above (even if we see the zero hz bogus messages, which we can ignore for now). If this succeeds, we can investigate the item 3 above separately, so we can then re-introduce the "zero hz" fix. [1] https://pastebin.ubuntu.com/p/Xtyfvb3CV2/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Although Mustafa says he's not well-versed, he's way smarter than me :) So his comment#26 seems to be much more relevant than what I have to say, but I'd like to reply to Daniel's comment#24/25 anyway: I saw the details you mentioned on comment #16, and I also have fractional scaling turned off. By "having it off" I'm assuming this [1] is enough, right? Also, I noticed that by previous pasteboard wasn't too clear in showing the problem when I use 42.5-0ubuntu1vv5. I want to clarify that I get a screen as if I had 3 monitors side by side, but all in the same "client monitor". If you try to maximize the application, it picks one of the "screens" and maximizes to it, as we can see here [2]. Even without changing the fractional scale or scale setting, just by having the 42.5-0ubuntu1vv5 packages installed, I get this "triple monitor in 1" situation when I boot my VM. I had to reinstall the original packages from our archives in order to fix this. Also, I just want to make sure you're aware that these are the *mutter* packages that I have installed: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1 amd64GObject introspection data for Mutter ii libmutter-10-0:amd6442.5-0ubuntu1 amd64window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1 all shared files for the Mutter window manager i.e. Just want to make clear that I don't have the "mutter" package installed, but the ones above. Back to your comment, iiuc, the "Impossible to set scaling on crtc 65 to 1.00, error id 2" means that we're trying to use some incomplete RandR implementation in Xdcv. Isn't it the fractional scaling, that was effectively removed from your 42.5-0ubuntu1vv5 package? In this case, doesn't the errors showing up means that we're still trying to use something that isn't properly implemented in Xdcv? Just for my own information, what's the difference between the vv5 and vv4 builds? Tested with vv4 in a VM: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1vv4 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.5-0ubuntu1vv4 amd64window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1vv4 all shared files for the Mutter window manager As soon as I installed it in my VM, I got that "triple monitor" situation again, and then I realized it's really just what you had described, that it automatically enables these other monitors. I can disable them and get back to 1 single monitor. With vv4, I can apply the scale 200% [3] and then revert it, but then it changes my resolution to 800x600. After realizing that, I went back to the vv5 package and re-tested and I notice it's the same behavior as in vv4. After installing it automatically enables all 4 monitors, I have to manually disable them and keep just 1. Then I test the scale to 200% + revert and it does revert, but also changes my resolution to 800x600. I can't really test that in Workspaces, because when it enables the extra monitors, I'm no longer able to access the Workspace with the AWS Workspaces client. If I try to change the scale in Workspaces, I believe it tries to enable the other monitors, and then all I get is a blank screen. And here's the output of "xrandr --verbose" from the VM [5] and the Workspace [6] [1] https://pasteboard.co/qEbvvwijUW2F.png [2] https://pasteboard.co/K9Oh9nZ8wqNk.png [3] https://pastebin.ubuntu.com/p/xkcFScZv5c/ [4] https://pastebin.ubuntu.com/p/mVwWt4Rzsr/ [5] https://pastebin.ubuntu.com/p/JC4PXwdv55/ [6] https://pastebin.ubuntu.com/p/S5bXz975Nn/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi Daniel, Thanks again. Tested 42.5-0ubuntu1vv5 When I apply the 200% scale: https://pastebin.ubuntu.com/p/MfS9vpT6KB/ When I revert it: https://pastebin.ubuntu.com/p/SHtvrXyPkY/ And then I get this situation (possibly due to what you mentioned on the settings app attempting to enable the 4 monitors): https://pasteboard.co/kLUbb5XWlwAQ.png The tests above were in a qemu VM in my laptop + DCV. I also tested it in an AWS Workspace and I believe the situation is similar. When I change scale to 200%: https://pastebin.ubuntu.com/p/DgkB3rngvj/ When I revert it: https://pastebin.ubuntu.com/p/H4nJC4MmKW/ And the screen in the Workspaces client gets all blank and there's no place to click. Even if I try to resize the client screen (which would force Xdcv to change the resolution) I can't get back to the workspace. Only way to fix it is to close and reopen the client. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I was getting some inconsistent and confusing results on my tests, so I decided to start from scratch with a fresh VM (qemu) and also a fresh Workspace (AWS). In a freshly installed Jammy VM (on qemu, not AWS), out of the box we have factional scaling disabled, so I tried changing scale to 200% and I do hit the error (but the scale DOES change): https://pastebin.ubuntu.com/p/yVwnmqbTTJ/ When I try to revert, I hit the error again and gnome freezes: https://pastebin.ubuntu.com/p/nYpqJDmr5x/ I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the VM When I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/V7MmKCjc4W/ And also when trying to revert it (gnome freezes): https://pastebin.ubuntu.com/p/dbWZFQGr9t/ Package versions: https://pastebin.ubuntu.com/p/c4WsgPVnxr/ Also did the same tests with a fresh Workspace: Tested the very same thing in a Workspace: Out of the box fractional scaling is disabled, so I tried changing scale to 200% and I hit the error (but it does change): https://pastebin.ubuntu.com/p/gSZ5rfm7vF/ When I try to revert, I hit the error and then it causes the problem reported in https://launchpad.net/bugs/1924689: https://pastebin.ubuntu.com/p/NHY62YvxCG/ (So both Workspaces and local VM hit the same problem, but when reverting Workspaces will hit LP#1924689 and the local VM will freeze gnome) I then rebooted the Workspace without upgrading any package and tried the same steps again, and I still have the same problem. I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the Workspace, and I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/977wzx6sxW/ And when I try to revert: https://pastebin.ubuntu.com/p/D2VZv2J7QV/ Packages: https://pastebin.ubuntu.com/p/mDKy4wWyWZ/ So, unless I'm missing something, apparently the same problem happens with fractional scaling disabled and also with the packages from the PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Thanks for the investigation Daniel. Indeed my inability to change the scale with the first patch was due to low resolution in my client machine. Interesting enough, I tried reproducing this in a Local VM with Xdcv (with just regular mutter packages, straight from our archives, no PPA), and I'm unable to reproduce the problem when I disable fractional scaling. I'm able to change to 200% and then revert properly. Given that I'm unable to reproduce there, I went back to an AWS Workspace and installed your new 42.5-0ubuntu1vv2 package and I'm still able to reproduce the problem when reverting it: May 31 20:17:42 U-3JQHCWI1WR5QW geoclue[2660]: Service not used for 60 seconds. Shutting down.. May 31 20:17:42 U-3JQHCWI1WR5QW systemd[1]: geoclue.service: Deactivated successfully. May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Xlib: extension "DPMS" missing on display ":1". May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something
[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
I also tested Daniel's mutter package with: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade And rebooted the Workspace just in case. I know Mustafa mentioned he was still able to reproduce the issue. In my case, I wasn't but on the other hand, I can't do the action that would allow me to reproduce it. When I go to display settings, I don't have an option to change the scale, but I do have the option to enable "Fractional Scaling", but if I enable it, I don't have an apply button to enable it, so this never gets enabled and doesn't get to a situation where I can change/revert the scale to see if I would be able to reproduce the issue or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39
[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Hi Daniel, I'm not with the SEG team and I would need assistance from someone building that and providing the debs or a ppa. I've also subscribed Mustafa, from SEG, to this bug, as he's assisting me investigating this issue. Regards, Fabio Martins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy):
[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell 42.5-0ubuntu1: fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common [sudo] password for fabiomirmar: mutter-common: Installed: 42.5-0ubuntu1 Candidate: 42.5-0ubuntu1 Version table: *** 42.5-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy gnome-shell gnome-shell: Installed: 42.5-0ubuntu1 Candidate: 42.5-0ubuntu1 Version table: *** 42.5-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And I have the same issue. When I apply the scale change I see: May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: vte-spawn-11c0b6cb-a094-4eee-9cbf-7a694348f00a.scope: Consumed 1.272s CPU time. May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: gnome-terminal-server.service: Consumed 1.231s CPU time. May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Impossible to set scaling on crtc 59 to 0.615385, error id 2 May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Scalig CRTC 59 at 0.615385 failed May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS" missing on display ":1". May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, using scale 1 May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS" missing on display ":1". May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, using scale 1 May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Spurious clutter_actor_allocate called for actor 0x55a6ef3a4ba0/[:0x55a6ef3a4ba0] which isn't a descendent of the stage! May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6f04896e0] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6f048ca30] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]:
[Desktop-packages] [Bug 2020782] [NEW] Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Public bug reported: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing- linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the following process being started: /usr/bin/Xdcv -output 800x600+0+0 -output 800x600+800+0 -output 800x600+1600+0 -output 800x600+2400+0 -enabledoutputs 1 vt2 -displayfd 3 -auth /run/user/541001128/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 I'm also unable to reproduce the problem using xrdp + Xorg. While discussing this with the desktop crew, it was mentioned that we see the same problems in Xorg. And to a much lesser extent some issues in Wayland too when changing scales.
[Desktop-packages] [Bug 2019751] Re: Shell startup animation may not complete on early resolution changes
@Daniel, My understanding is that bug 2019751 is the same as bug 1989170, but public. Since the fix was not released to Jammy, bug 2019751 aims to address that (although your question might be targeted to Lunar, since I see bug 1989170 was released to Kinetic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Shell startup animation may not complete on early resolution changes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Committed Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2019751/+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 683725] Re: When I format an usb key, after remount it opens the empty device twice.
Thank you for filing this bug. I tried to reproduce it in Xenial, but it seems this behavior is no longer happening and very likely is already fixed, so I'm closing this bug as invalid. This is also a duplicate of 686780. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/683725 Title: When I format an usb key, after remount it opens the empty device twice. Status in One Hundred Papercuts: Confirmed Status in nautilus package in Ubuntu: Invalid Status in parted package in Ubuntu: Invalid Bug description: When I plug an usb device and I format it through right click format, after the task is done, it remounts the device and open the empty device in nautilus twice. It should open only once. It could not open at all because if we want to use the usb key to run "create a startup disk" it is no use and if we need to put files in it, we only have to double click the icon on the desktop to open the device. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/683725/+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 686780] Re: USB format opens two nautilus windows
Thank you for filing this bug. I tried to reproduce it in Xenial, but it seems this behavior is no longer happening and very likely is already fixed, so I'm closing this bug as invalid. This is also a duplicate of 683725. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/686780 Title: USB format opens two nautilus windows Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: parted Sorry that i reported this to parted, i don't know even if this is "parted" related. This is a general error which is present for a long time. When you format USB (the one that displays in desktop) with Right Click , Format, after format it opens two nautilus windows. Sorry if this is duplicate but i couldn't find it. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: parted 2.2-5ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Tue Dec 7 23:05:36 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: parted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/686780/+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 334806] Re: nautilus disappear desktop icons and freeze open folders on jaunty
We are closing this bug report as it is related to a no longer supported version of Ubuntu + Kernel + Nautilus and this issue has not been observed in any recent and supported releases. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/334806 Title: nautilus disappear desktop icons and freeze open folders on jaunty Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus This happens a few seconds after startup. When I kill de process the problem appears again 3-5 seconds after nautilus reboot. When I open nautilus for the terminal I get: " franciscocosta@franciscocosta-desktop:~$ nautilus (nautilus:9651): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nautilus:9651): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. " I'm using the latest x64 Jaunty ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: fglrx Package: nautilus 1:2.25.91-0ubuntu1 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: nautilus Uname: Linux 2.6.28-7-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/334806/+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
