[Bug 2028819] Re: File-Roller should depend on 7zip package instead of abandoned p7zip-full since version 43
** Summary changed: - File-Roller should depend on 7zip package instead of p7zip-full since version 43 + File-Roller should depend on 7zip package instead of abandoned p7zip-full since version 43 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2028819 Title: File-Roller should depend on 7zip package instead of abandoned p7zip- full since version 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028819] [NEW] File-Roller should depend on 7zip package instead of p7zip-full since version 43
Public bug reported: File-Roller switched from p7zip to official 7zip utility since version 43.alpha , see https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d and https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned by upstream p7zip-full, while it should depend on 7zip package instead of p7zip-full or maybe better to have "Depends: 7zip | p7zip-full" ? There are lots of bugs in p7zip, for example some large zip files cannot be extract on 16.02 but can on 9.20, see https://sourceforge.net/p/p7zip/discussion/383044/ and http://bugs.debian.org/src:p7zip also https://bugs.launchpad.net/ubuntu/+source/p7zip It seems Debian developers planing to replace p7zip-full with official 7zip package, see https://bugs.debian.org/991428 Also there is a related note in NEWS file: - Distros will want to adjust the `data/packages.match` file. Some archive managers in Ubuntu/Debian already depends on official 7zip package instead of p7zip, see arqiver for example. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2028819 Title: File-Roller should depend on 7zip package instead of p7zip-full since version 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - monitors.xml in Ubuntu 23.04: + monitors.xml in Ubuntu 23.04, and 22.04: ``` 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60.000 - - ``` - - monitors.xml in Ubuntu 22.04: - - ``` - - - - - 0 - 0 - yes - - - Virtual-1 - ??? - 0x - 0x - - - 1600 - 900 - 60 - - - - - - - 0 - 0 - 1 - yes - - - Virtual-1 - unknown - unknown - unknown - - - 1600 - 900 - 60 - - - - ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * monitors.xml in Ubuntu 22.04, and 23.04 (both version are using GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` + * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: * monitors.xml in Ubuntu 22.04, and 23.04 (GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: - * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + * monitors.xml in Ubuntu 22.04, and 23.04 (both version are using GNOME) is starting with ``, while in Ubuntu MATE 22.04, and 23.04 it is starting with `` * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` monitors.xml in Ubuntu MATE 22.04, and 23.04: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
I just filed: [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 -- I pointed out that there will certainly be times when GNOME and MATE will not be able to use the same version of monitors.xml in the future. ** Description changed: * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 - Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports + [Feature request] mate-display-properties: Please upgrade monitors.xml from to - https://bugs.launchpad.net/ubuntu/+bug/2028818 GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 Expected behaviour cinnamon is using a dedicated name,
[Bug 1859398] Re: Extracting .rar creates multi-GB file which fills up harddrive
Maybe this .rar archive extracting issue is fixed in latest File-Roller 43 release? Look at https://gitlab.gnome.org/GNOME/file-roller/-/merge_requests/87 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1859398 Title: Extracting .rar creates multi-GB file which fills up harddrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
> GNOME's monitors.xml is starting with , and that > MATE's monitors.xml is starting with So really I think this makes most sense to request support for version 2 from MATE. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: + * GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + * The monitors.xml file name is defined here for MATE: https://github.com/mate-desktop/mate-desktop/blob/master/libmate-desktop/mate-rr-config.c#L44, and here for GNOME: https://gitlab.gnome.org/GNOME/mutter/-/issues/2919#note_1799008 + + Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour - Disclaimer: GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with - GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1571806] Re: Backup files are silently ignored when using certain archive types
File-roller developers decided do not add files with a `~` on the end of their names to new archive in version 2.23.4 , see https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS#L3858 : New features and user visible changes: [...] * Do not add the backup files, that is files ending with ~, to the archive. It seems we should report this issue to the upstream: https://gitlab.gnome.org/GNOME/file-roller/-/issues -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1571806 Title: Backup files are silently ignored when using certain archive types To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1571806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
It's not mentioned in the changelog but it looks like a fix for 22.04 will arrive with: https://launchpad.net/ubuntu/+source/gtk4/4.6.9+ds-0ubuntu0.22.04.1 ** No longer affects: gnome-shell (Ubuntu) ** Changed in: gtk4 (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] Re: does not support spec 1.5
** Changed in: desktop-file-utils (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] Re: does not support spec 1.5
Thank you for the report. It would be smoothest if upstream released a version with that change. I see that is requested in https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues/69 ** Bug watch added: Debian Bug tracker #1041654 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041654 ** Also affects: desktop-file-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041654 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues #69 https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/issues/69 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
PS: Before I forget, I also tested something else, see attached screenshot. Going into nvidia-settings and manually setting the PowerMizer mode to "prefer maximum performance" makes all animations, the overview and everything related to it super smooth fps-wise. You can make this permanent by adding these changes to the startup applications / commands so that it sticks upon reboot. I opened the overview 30 times in a row right now, not a single fps-drop. However, this does not fix the low fps-rate and sluggish behaviour when trying to resize individual windows (files). The latter only gets a performance boost when turning off vsync in nvidia-settings. The downside to this is of course the higher power consumption, but it does indicate that the lag might be connected to the lower power modes. Iirc sluggish 3d animations on the desktop with Nvidia was also an issue all the way back on Ubuntu during the good old Compiz days, and I remember fixing it by adjusting the PowerMizer mode to prefer a higher performance mode. ** Attachment added: "Bildschirmfoto vom 2023-07-26 17-12-03.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688578/+files/Bildschirmfoto%20vom%202023-07-26%2017-12-03.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Description changed: Expected behaviour cinnamon is using a dedicated name, cinnamon-monitors.xml. This doesn't cause the file to be overwritten by the display preferences if other desktop environment are used on the same distro. If MATE and GNOME followed the same approach, the file name would be mate-monitors.xml, and gnome-monitors.xml, respectively. Actual behaviour + Disclaimer: GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with + GNOME's monitors.xml: ``` 0 0 yes Virtual-1 ??? 0x 0x 1600 900 60 0 0 1 yes Virtual-1 unknown unknown unknown 1600 900 60 ``` MATE's monitors.xml: ``` no ??? 0x 0x 1600 900 60 0 0 normal no no yes ``` Steps to reproduce the behaviour Both GNOME and MATE can be installed on the same distro. Both DEs are installing "$HOME/.config/monitors.xml" via manually configured display GUI preferences: * GNOME via `$ gnome-control-center display` * MATE via `$ mate-display-properties` Steps I used to reproduce the issue in Ubuntu 22.04 (as a virtual machine): * Log into GNOME * Ubuntu comes with GNOME, so install MATE in addition: `sudo apt-get install mate-desktop-environment-extras mate-desktop-environment` * Run `$ gnome-control-center display`, change the "Resolution" to 1600x900, click on the "Apply": This will 1) generate "$HOME/.config/monitors.xml", 2) [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56](/uploads/dc4ba73ddfae955fcafa948e3a164581/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_43_56.png). Close the window. * Log out from GNOME. From the display manager, log into MATE. * As you can see, the [screen resolution (1600x900 configured in GNOME) not used by MATE](https://github.com/mate-desktop/mate-control-center/assets/6416073/adffa08e-cf08-499d-8dc3-9e7800e4d7e9), instead a fallback resolution is used. * Run `$ mate-display-properties`, just click on the "Apply" button (you don't have to click on the "Keep this configuration" button that pop-ups in the dialoge-box), it will overwrite "$HOME/.config/monitors.xml" * Log out from MATE. From the display manager, log into GNOME. * As you can see, [Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11](/uploads/013b2b1abf582caf7e6c4c70733ea5ac/Screenshot_ubuntu-22.04-desktop-amd64.iso-clone_2023-07-24_23_40_11.png), instead a fallback resolution is used. ## Links to bug reports GNOME https://gitlab.gnome.org/GNOME/mutter/-/issues/2919 MATE https://github.com/mate-desktop/mate-control-center/issues/712 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 01:24:22 2023 InstallationDate: Installed on 2023-04-17 (97 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
xrandrv.txt as requested by Dan ** Attachment added: "xrandrv.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688576/+files/xrandrv.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Hi Daniel, I will follow your suggestion and try to find the time to create a new bug report for the additional issues that occured. That said, since the drive on this machine suffered from what I wrote above, I decided to quickly format and perform the steps that you suggested on a fresh Ubuntu 23.04 install. First of all, I am happy to report that checking the checkbox for "additional drivers" (proprietary gpu and wifi drivers) during the installation of 23.04 did in fact successfully and flawlessly install the proprietary Nvidia drivers this time around - namely the Nvidia driver 535 that killed my 22.04 installation. This was not the case the first two times that I installed 23.04, so it seems that we have already made some progress in this regard. That said, back to the initial issue: MUTTER_DEBUG_TRIPLE_BUFFERING=always MUTTER_DEBUG_TRIPLE_BUFFERING=never CLUTTER_PAINT=disable-dynamic-max-render-time I tried all of these under 23.04 separately per reboot, sadly no change. 23.04 still shows signs of sluggish or low fps when resizing windows and also when opening the overview with a few programs open (Firefox, Software Center, text editor etc). Sometimes the overview is buttery smooth, but at some point it drops in performance and loses a few fps, just like mentioned in my initial post. For example, opening the overview while writing this text I can clearly see an fps-drop, but after repeating the process two or three times it becomes buttery smooth all of a sudden. The only thing that makes everything super fast all the time is when disabling vsync in nvidia-settings -> opengl. Doing this results in buttery smooth 60+ fps animations all the time - and no lag when resizing windows either. I attached the xrandrv.txt that you requested further below. Please note: I will be formatting this Nvidia powered machine tonight in order to install another distro onto it, so I won't be able to further test these things on this particular machine. That said, I want to reiterate that I will still continue to use Ubuntu on many of my other computers that are equipped with AMD and Intel gpu hardware. Your triple buffering vsync patches work beautifully on Amd and even on super low- end Intel igpu hardware. I love Ubuntu, and I highly appreciate your personal efforts for everything related to triple buffering / vsync and more, which is why I am going to be donating a couple of bucks to you guys this weekend in order to contribute my fair share since troubleshooting these Nvidia specific issues is too time consuming for me right now. Thanks Dan, appreciate all the help! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
> As mentioned in the other bug, I think that's more a bug in MATE if it has become incompatible. Oh, interesting! Can you please humbly ask if this is the cause in the MATE entry page that I filed for this issue: https://github.com/mate-desktop/mate-control-center/issues/712 ? But please mention that GNOME's monitors.xml is starting with , and that MATE's monitors.xml is starting with ** Bug watch added: github.com/mate-desktop/mate-control-center/issues #712 https://github.com/mate-desktop/mate-control-center/issues/712 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Is there any progress on this issue? (Progress as in: works for end- users as it did the last 20 years…) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028438] Re: gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
** Changed in: gnome-control-center Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash with assertion failure: cc-power- panel.c:1122:performance_profile_set_active: assertion failed: (button) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2028438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028438] Re: gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
Even if I remove/purge it,and install fresh... On start, it is stuck at the same point and error... It is affected by this upstream Gnome bug: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 Upon seeing that it is affected by setting the power profile to performance... I did this: Code: mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl get performance mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl set balanced mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl get balanced After that, gnome-control-center was unlocked and worked... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash with assertion failure: cc-power- panel.c:1122:performance_profile_set_active: assertion failed: (button) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2028438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942204] Re: gjs-console assert failure: double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** Changed in: gjs (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1942204 Title: gjs-console assert failure: double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1942204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1981678] Re: /usr/bin/gjs-console:double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** This bug is no longer a duplicate of bug 1942204 gjs-console assert failure: double free or corruption (out) ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1981678 Title: /usr/bin/gjs-console:double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1981678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028438] Re: gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
Thanks. That's being tracked in https://errors.ubuntu.com/problem/b5c373fef4f1e2ac4e0db303d268a4a781068cff ** Summary changed: - gnome-control-center crash + gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1504 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released ** Tags added: fixed-in-gnome-control-center-43.1 fixed-upstream ** Tags added: fixed-in-gnome-control-center-42.4 ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash with assertion failure: cc-power- panel.c:1122:performance_profile_set_active: assertion failed: (button) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2028438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028754] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:performance_profile_set_active:setup_power_profiles:cc_power_panel_init
*** This bug is a duplicate of bug 2028438 *** https://bugs.launchpad.net/bugs/2028438 ** This bug has been marked a duplicate of bug 2028438 gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028754 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:performance_profile_set_active:setup_power_profiles:cc_power_panel_init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028754] [NEW] /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:performance_profile_set_active:setup_power_profiles:cc_power_panel_init
*** This bug is a duplicate of bug 2028438 *** https://bugs.launchpad.net/bugs/2028438 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/b5c373fef4f1e2ac4e0db303d268a4a781068cff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kinetic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028754 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:performance_profile_set_active:setup_power_profiles:cc_power_panel_init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
Tested new version, it works without errors ❯ apt-cache policy libgtk-4-1 libgtk-4-1: Installed: 4.6.9+ds-0ubuntu0.22.04.1 Candidate: 4.6.9+ds-0ubuntu0.22.04.1 Version table: *** 4.6.9+ds-0ubuntu0.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.6.6+ds-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 4.6.2+ds-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages Before upgrading: ❯ gjs -m /tmp/error.js (gjs:8879): Gjs-CRITICAL **: 10:47:25.041: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. (gjs:8879): Gjs-CRITICAL **: 10:47:25.041: The offending callback was ScaleFormatValueFunc(). == Stack trace for context 0x5634d50d9180 == (gjs:8879): Pango-WARNING **: 10:47:25.041: Invalid UTF-8 string passed to pango_layout_set_text() free(): invalid pointer [1]8879 IOT instruction (core dumped) gjs -m /tmp/error.js marco-ThinkPad-X1-Carbon-7th ~ 8sSIGIOT(6) 10:47:27 ❯ apt-cache policy libgtk-4-1 libgtk-4-1: Installed: 4.6.6+ds-0ubuntu1 Candidate: 4.6.6+ds-0ubuntu1 Version table: 4.6.9+ds-0ubuntu0.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages *** 4.6.6+ds-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.6.2+ds-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** 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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028438] Re: gnome-control-center crash
Stuck on power panel: mafoelffen@Mikes-ThinkPad-T520:~$ gnome-control-center network (gnome-control-center:122922): cc-power-profile-row-CRITICAL **: 01:37:57.530: cc_power_profile_row_get_radio_button: assertion 'CC_IS_POWER_PROFILE_ROW (self)' failed ** power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Bail out! power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Aborted (core dumped) mafoelffen@Mikes-ThinkPad-T520:~$ gnome-control-center -v display (gnome-control-center:123168): cc-power-profile-row-CRITICAL **: 01:39:37.164: cc_power_profile_row_get_radio_button: assertion 'CC_IS_POWER_PROFILE_ROW (self)' failed ** power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Bail out! power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Aborted (core dumped) *** END OUTPUT *** -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
This bug was fixed in the package yaru-theme - 22.04.5 --- yaru-theme (22.04.5) jammy; urgency=medium [ Paul Kepinski ] * Add osd monitor labels theming (LP: #1979037) * Fix slider states (LP: #2019475) * Gtk3: fix marks scale visibilty on hover (LP: #2019477) * Gtk3: fix invisible check and radio in selected row (LP: #2019476) * Fix uncentered cursors (LP: #2019479) * Sync Gtk3 with upstream (only reference code, see debian/README.source) [ Marco Trevisan (Treviño) ] * dock: Fix margins making the dock show-apps clickable (LP: #1966167) * debian: Update references to ubuntu/jammy branch * nautilus: Ensure disk-space-display items are themed (LP: #2008791) * debian/README.sources: Explain better the role of the upstream folders -- Marco Trevisan (Treviño) Fri, 09 Jun 2023 21:38:14 +0200 ** Changed in: yaru-theme (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979037] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979037] Re: Monitor numbers are almost invisible in an Ubuntu/Yaru session
This bug was fixed in the package yaru-theme - 22.04.5 --- yaru-theme (22.04.5) jammy; urgency=medium [ Paul Kepinski ] * Add osd monitor labels theming (LP: #1979037) * Fix slider states (LP: #2019475) * Gtk3: fix marks scale visibilty on hover (LP: #2019477) * Gtk3: fix invisible check and radio in selected row (LP: #2019476) * Fix uncentered cursors (LP: #2019479) * Sync Gtk3 with upstream (only reference code, see debian/README.source) [ Marco Trevisan (Treviño) ] * dock: Fix margins making the dock show-apps clickable (LP: #1966167) * debian: Update references to ubuntu/jammy branch * nautilus: Ensure disk-space-display items are themed (LP: #2008791) * debian/README.sources: Explain better the role of the upstream folders -- Marco Trevisan (Treviño) Fri, 09 Jun 2023 21:38:14 +0200 ** Changed in: yaru-theme (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
As mentioned in the other bug, I think that's more a bug in MATE if it has become incompatible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: apparmor (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
