[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Thank you Mr. Eickmeyer for your fix in 23.04. > notice how the askubuntu question was closed? That's because it was offtopic/for an unsupported release AskUbuntu closes questions as off-topic *because* they want those questions to be *posted here* instead. It says "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." Anyway, this bug doesn't affect me, and I might as well treat the Invalid as Fix Committed but not released. > won't be supported until August 2024 (upon release of 24.04.1) Interesting! You helped me learn something today after reading https://ubuntu.com/server/docs/upgrade-introduction . I never noticed this as I personally upgrade to either latest or dev, never LTS specifically. I will post a comment on AskUbuntu to relay this information -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: Invalid Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be
[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Yeah, ok. Ubuntu Studio lead here. This bug is invalid for two reasons: 1) Upgrades to 24.04 aren't even supported yet and won't be supported until August 2024 (upon release of 24.04.1) 2) The exact bug was caught before the release of Lunar Lobster (23.04) and the fix is included in that release, but no bug was filed because I was the one who found it and didn't need to file it. (see https://git.launchpad.net/ubuntustudio-default-settings/commit/?id=7de146f7c74f8c5d73e401513500c700f38f5acf if you don't believe me) Long-story short, NOBODY should be testing upgrades from 22.04 to 24.04 right now, and NOBODY should be expecting support for this. That said, there *will* be a Conflicts: line in place before 24.04's release, but this is not something anybody should be expecting now. Furthermore, notice how the askubuntu question was closed? That's because it was offtopic/for an unsupported release. I'm treating it the same here. ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: Confirmed => Invalid ** Changed in: fontconfig (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: Invalid Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i
[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Thank you for taking the time to report this bug and helping to make Ubuntu (Studio) better. @Bluesbrother (or the original posted to askubu..) Can you please add what your installation media was, ie. `cat /var/log/installer/media-info` as your original post on askubu implies you release-upgraded to noble, and thus this issue may only occur on upgrades, rather than fresh installs. Ideally an `apport-collect` would gather this (& more details), but you aren't the original report of this bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2051315] [NEW] syslog filling up
Public bug reported: ─| lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 └─| apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages No gnome extensions installed. very limited use of the desktop as most everything is manages thru ssh remotely. The error causes /var/log/syslog file to rapidly grow until the disk is full. The following line are repeated thousands and thousands of times in the syslog file. z440 gnome-shell: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. z440 gnome-shell: The offending signal was notify on GnomeWallClock 0x55c4f6b7d830. z440 nxpreload.sh: == Stack trace for context 0x55c4f52f64a0 == ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 [modified: usr/share/applications/org.gnome.Shell.desktop] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 25 21:07:01 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-29 (89 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051315 Title: syslog filling up Status in gnome-shell package in Ubuntu: New Bug description: ─| lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 └─| apt-cache policy gnome-shell gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages No gnome extensions installed. very limited use of the desktop as most everything is manages thru ssh remotely. The error causes /var/log/syslog file to rapidly grow until the disk is full. The following line are repeated thousands and thousands of times in the syslog file. z440 gnome-shell: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. z440 gnome-shell: The offending signal was notify on GnomeWallClock 0x55c4f6b7d830. z440 nxpreload.sh: == Stack trace for context 0x55c4f52f64a0 == ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 [modified: usr/share/applications/org.gnome.Shell.desktop] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 25 21:07:01 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-29 (89 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051315/+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 2051313] [NEW] font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Public bug reported: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: ubuntustudio-default-settings (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my
[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Marked as confirmed as the real reporter is the asker on AskUbuntu, and after my investigation, I confirm that this bug is reasonable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+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 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
** Description changed:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
- I accept updates when they arrive. Recently it's been telling me to do
- firmware updates, too.
+ Other context:
+ I accept OS updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
- virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
+ virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
+ virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
- Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
+ Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
+ Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
** Summary changed:
- T14s Gen4 Intel under 23.10 started locking up hard
+ T14s Gen4 Intel under 23.10 started freezing / locking up hard
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2051303
Title:
T14s Gen4 Intel under 23.10 started freezing / locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
Other context:
I accept OS updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
[Desktop-packages] [Bug 2013107] Re: [lunar] GNOME does not display high contrast app icons
This is not fixed in Noble yet. ** No longer affects: gnome-themes-extra (Ubuntu Lunar) ** No longer affects: yaru-theme (Ubuntu Lunar) ** No longer affects: yaru-theme (Ubuntu Mantic) ** No longer affects: yaru-theme (Ubuntu Noble) ** No longer affects: gnome-themes-extra (Ubuntu Mantic) ** Changed in: gnome-themes-extra (Ubuntu Noble) Status: New => Invalid ** No longer affects: gnome-themes-extra (Ubuntu Noble) ** No longer affects: gnome-shell (Ubuntu Lunar) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2013107 Title: [lunar] GNOME does not display high contrast app icons Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Won't Fix Status in gnome-shell source package in Mantic: Triaged Status in gnome-shell source package in Noble: Triaged Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+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 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
The last crash before I reported this was just before hard-rebooting
around time 2024-01-25 19:30
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2051303
Title:
T14s Gen4 Intel under 23.10 started locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051303/+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 2051303] [NEW] T14s Gen4 Intel under 23.10 started locking up hard
Public bug reported:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously, without
high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything much
on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2051303
Title:
T14s Gen4 Intel under 23.10 started locking up hard
Status in xorg package in Ubuntu:
New
Bug description:
Everything's been great for a couple of months on this new machine
Yesterday or the day before it started locking up hard, spontaneously,
without high load.
X11 freezes. Keyboard is unresponsive. Sound still worked for a while once.
I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.
It's happening frequently enough that it's not safe for me to do anything
much on the computer.
I normally use this machine ~14 hours per day.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse:
[Desktop-packages] [Bug 2051292] Re: blutooth
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2051292 Title: blutooth Status in bluez package in Ubuntu: New Bug description: when I connect to my headset it's work couple of seconds or minutes then disconnect alone ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 22:15:26 2024 InstallationDate: Installed on 2023-06-27 (211 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. Inspiron 3721 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 044D20 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3721 dmi.product.sku: Inspiron 3721 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:2A:70:BE:D0:62 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:5227 acl:60 sco:0 events:440 errors:0 TX bytes:36549 acl:67 sco:0 commands:391 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051292/+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 2051292] [NEW] blutooth
You have been subscribed to a public bug: when I connect to my headset it's work couple of seconds or minutes then disconnect alone ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 22:15:26 2024 InstallationDate: Installed on 2023-06-27 (211 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. Inspiron 3721 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 044D20 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3721 dmi.product.sku: Inspiron 3721 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:2A:70:BE:D0:62 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:5227 acl:60 sco:0 events:440 errors:0 TX bytes:36549 acl:67 sco:0 commands:391 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- blutooth https://bugs.launchpad.net/bugs/2051292 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. -- 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 2043000] Re: Update mutter to 45.2
** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update landed in mantic-updates just before the end of year holidays but was reverted with https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 Compared to mutter 45.2-0ubuntu1, this changes or adds about 3 lines of code in the triple buffering patch to avoid the regression reported in LP: #2046360 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
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/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
Fix Released
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku:
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: broadcom-sta (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in broadcom-sta source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Triaged Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Fix Released Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mesa (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-hwe-6.2 source package in Jammy: Invalid Status in mesa source package in Jammy: New Status in linux-hwe-6.2 source package in Lunar: Invalid Status in mesa source package in Lunar: Won't Fix Status in linux-hwe-6.2 source package in Mantic: Invalid Status in mesa source package in Mantic: Fix Released Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4
[Desktop-packages] [Bug 2037115] Re: Focus is not given when a new window is launched from overview
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- 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/2037115 Title: Focus is not given when a new window is launched from overview Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Won't Fix Status in mutter source package in Mantic: Fix Released Bug description: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037115/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: tracker-miners (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in tracker-miners package in Ubuntu: Fix Committed Status in tracker-miners source package in Bionic: Won't Fix Status in tracker-miners source package in Focal: In Progress Status in tracker-miners source package in Jammy: In Progress Status in tracker-miners source package in Lunar: Won't Fix Status in tracker-miners source package in Mantic: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve the issue, namely: commit 8065985c8d818414a36fe151862afdf42c5eda8a Author: Laurent Bigonville Date: Sat, 4 Apr 2020 19:18:00 +0200 Subject: Move the Install section to the systemd .service file instead of the udev one Link:
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: xdg-desktop-portal-gnome (Ubuntu Lunar) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Won't Fix Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1995349] Re: [goodix] The enrolled finger is unknown to device
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libfprint (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1995349 Title: [goodix] The enrolled finger is unknown to device Status in libfprint: Fix Released Status in OEM Priority Project: Confirmed Status in libfprint package in Ubuntu: New Status in libfprint source package in Jammy: New Status in libfprint source package in Lunar: Won't Fix Bug description: [Impact] * The enrolled finger is unknown to device [Test Plan] * Find a machine with Goodix fingerprint device * Clean up the storage of fp device by `manage-prints` * Launch `settings` and enable `Fingerprint Login` * Enroll left index finger and right index finger * Login with right index finger [Where problems could occur] * This is only affected goodix fingerprint device To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1995349/+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 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: adsys (Ubuntu Lunar) Status: New => Won't Fix -- 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/2012371 Title: [FFe] ubuntu-proxy-manager and adsys Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: Won't Fix Bug description: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. Installing the ubuntu-proxy-manager package on its own has no impact to the system. To benefit from its functionality adsys has to be upgraded and correctly configured. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+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 2013107] Re: [lunar] GNOME does not display high contrast app icons
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell (Ubuntu Lunar) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2013107 Title: [lunar] GNOME does not display high contrast app icons Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: New Status in yaru-theme package in Ubuntu: Won't Fix Status in gnome-shell source package in Lunar: Won't Fix Status in gnome-themes-extra source package in Lunar: New Status in yaru-theme source package in Lunar: New Status in gnome-shell source package in Mantic: Triaged Status in gnome-themes-extra source package in Mantic: Invalid Status in yaru-theme source package in Mantic: Won't Fix Status in gnome-shell source package in Noble: Triaged Status in gnome-themes-extra source package in Noble: New Status in yaru-theme source package in Noble: Won't Fix Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libmbim (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Won't Fix Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: Won't Fix Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM 7560), and Lenovo are struggling to give a decent way to run the FCC unlock service without this. Until the device is unlocked, the end users are not able to use the SIM cards, and some of the affected devices have already been shipped. The end users now have to go to the Lenovo support website and download a few scripts and binaries to unlock the device to make their SIM cards work. The Lenovo wants this patch to be included in jammy, then they can provide the FCC unlock service and manage it in OEM-archive, so the end users can use SIM cards as soon as they receive the laptop. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2016990] Re: Irregular frame rate in some fullscreen games
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- 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/2016990 Title: Irregular frame rate in some fullscreen games Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Won't Fix Status in mutter source package in Lunar: Won't Fix Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. [ Test Plan ] None known, other than the OP to run the game. [ Where problems could occur ] In rendering performance of fullscreen apps/games. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time [ Other Info ] Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016990/+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 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell (Ubuntu Lunar) Status: Triaged => Won't Fix -- 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: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in gnome-shell source package in Lunar: Won't Fix Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released 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/+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 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Won't Fix Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+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 2020682] Re: Release adsys 0.12.0
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: adsys (Ubuntu Lunar) Status: New => Won't Fix -- 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/2020682 Title: Release adsys 0.12.0 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: Won't Fix Bug description: ADSys is part of the enterprise desktop offerings and customers are requesting the new version to be released for 22.04 LTS. [Impact] * ADSys depends on Go 1.20, so the golang-1.20 package must be backported to 22.04 as well. * The new version has some features that are heavily requested by enterprise customers running the LTS. [Test Plan] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5. AD user should be able to log in (https://github.com/ubuntu/adsys/wiki/2.-Prerequisites); 2. Install admx and adml files on your AD controller (https://github.com/ubuntu/adsys/wiki/3.-AD-Setup); 3. Configure some Group Policies in the AD server (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO); 4. Install ADSys, reboot the machine and login in as an AD user; 5. Ensure that the configuration done in the AD server is reflected on the Ubuntu machine; [Where problems could occur] * ADSys can prevent authentication of AD users if some policies can't be applied; * For local users, no impact will occur; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020682/+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 2025150] Re: SRU: add two symbols for riscv64 to the symbols file
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libcupsfilters (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcupsfilters in Ubuntu. https://bugs.launchpad.net/bugs/2025150 Title: SRU: add two symbols for riscv64 to the symbols file Status in libcupsfilters package in Ubuntu: Fix Released Status in libcupsfilters source package in Lunar: Won't Fix Bug description: This is seen with the planned backport of GCC 12.3 to lunar. It's already fixed in mantic [1]. The added symbols don't belong to the ABI, however the build fails because dh_makeshlibs is called with -c4, and two more template instantiations show up on riscv64. [ Impact ] Without the two added symbols, the build will fail with the updated GCC 12.3 as seen in mantic. [ Test plan ] The package builds. There are no code changes in this patch [ Where problems could occur ] The patch is small and doesn't touch code. [1] http://launchpadlibrarian.net/670755843/libcupsfilters_2.0~rc1-0ubuntu2_2.0~rc1-0ubuntu3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcupsfilters/+bug/2025150/+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 2029413] Re: Tapping the top bar with the touchscreen crashes GNOME on Xorg
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- 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/2029413 Title: Tapping the top bar with the touchscreen crashes GNOME on Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: Won't Fix Status in mutter source package in Mantic: Fix Released Bug description: Tap the current time = Immediate crash. Tap the wifi/power combo menu = Immediate crash. Tap the top bar by itself = Immediate crash. Tap the activities button = No crash? Having the GNOME shell completely crash immediately after touching the top bar is really annoying. Especially since a lot of the functionality in the top bar is pretty important. This was previously reported as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160, but that got closed because of inactivity. This is the crash report Ubuntu generated: https://errors.ubuntu.com/oops/413de504-30f9-11ee-b2c2-fa163e55efd0. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 2 15:15:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.3-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2029413/+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 2042394] Re: Support goodix fingerprint [27c6:6582]
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libfprint (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2042394 Title: Support goodix fingerprint [27c6:6582] Status in OEM Priority Project: Triaged Status in libfprint package in Ubuntu: New Status in libfprint source package in Jammy: New Status in libfprint source package in Lunar: Won't Fix Status in libfprint source package in Mantic: New Status in libfprint source package in Noble: New Bug description: [27c6:6582] include in https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/447 [Impact] * Support goodix [27c6:6582] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042394/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gtk+3.0 (Ubuntu Lunar) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in apport source package in Focal: Invalid Status in gtk+3.0 source package in Focal: Triaged Status in apport source package in Lunar: Invalid Status in gtk+3.0 source package in Lunar: Won't Fix Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 2049237] Re: libwacom-dev: Needs Depends: libevdev-dev
** Changed in: libwacom (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/2049237 Title: libwacom-dev: Needs Depends: libevdev-dev Status in libwacom package in Ubuntu: Fix Released Status in libwacom package in Debian: Fix Released Bug description: I'm filing this on the Ubuntu side to prevent migration out of proposed since the autopkgtest regression isn't being correctly detected. See LP: #2035101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/2049237/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
** Bug watch added: github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues #2 https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues/2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
I use a Lenovo Slim 7 Carbon with a ALC287 as well. We have an issue page open for this device/issue as well, and I think we nailed it down to the pin configurations. https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon- AMD/issues/2#issuecomment-1615152518 I welcome your thoughts on this. hdajackretask seems to be the software for this solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2051188] Re: Firefox 122 update breaks webextensions permission
Thank you for confirming, Paul. This happened because after the recent refresh of the native messaging patch shipped with the Firefox snap, it started using a newer 'GetManifest' DBus method from xdg-desktop-portal that hasn't yet been backported to the version of the portal available in Ubuntu 22.04. I sadly didn't catch this earlier because I did the development and testing work for this on Ubuntu 23.10 (which has an up-to-date portal package that does include the GetManifest method), and forgot to test it on Ubuntu 22.04. I'm working to fix this ASAP by removing the use of GetManifest in the patch for the time being, until we get a newer version of xdg-desktop- portal backported to Ubuntu 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2051188 Title: Firefox 122 update breaks webextensions permission Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: We build webextensions for Firefox. Since the latest update to Firefox 122, the native webextension bridge stopped working. ``` $ flatpak permission-show snap.firefox Table ObjectApp Permissions Data desktop-used-apps application/vnd.debian.binary-package snap.firefox gnome-software-local-file,1,3 0x00 webextensions net.downloadhelper.coapp snap.firefox yes 0x00 ``` This used to work and be enough, but not anymore. In the logs I see: ``` Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest” Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2051188/+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 2037604] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
Hello Lee, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2049895] Re: Distorted mouse pointer in the remote window
With non-factional scale like 100%/200% the issue is not reproducible. Also, rare after OS restart the pointer is correct, but then there is an another issue: pointer cannot "touch" the upper edge of the screen so the autohided top bar does never show up on the remote screen. -- 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/2049895 Title: Distorted mouse pointer in the remote window Status in mutter package in Ubuntu: New Bug description: Distorted mouse poitner in the remote window (see the photo attched) The bug is reproducable with Wayland only. Whith xorg all works fine on the same machine. I experience it more than a year. I'm using fraqtional scale 125%. $ gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer'] Video is AMD integrated Radeon 4750G. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 15:35:25 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-remote-desktop UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2049895/+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 2050884] Re: Ubuntu Metrics server is not accepting reports
ubuntu-report continues to try to send data Jan 25 11:18:27 corrado-n4-nn-0125 systemd[1165]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report. Jan 25 11:18:44 corrado-n4-nn-0125 systemd[1791]: Started ubuntu-report.path - Pending report trigger for Ubuntu Report. Jan 25 11:18:44 corrado-n4-nn-0125 systemd[1791]: Started ubuntu-report.service - Ubuntu report sends pending metrics data. Jan 25 11:18:54 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 30s" Jan 25 11:18:57 corrado-n4-nn-0125 systemd[1165]: Stopped ubuntu-report.path - Pending report trigger for Ubuntu Report. Jan 25 11:19:34 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 60s" Jan 25 11:20:44 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 120s" Jan 25 11:22:54 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 240s" Jan 25 11:27:04 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 480s" Jan 25 11:35:14 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 960s" Jan 25 11:51:25 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 1800s" Jan 25 12:21:35 corrado-n4-nn-0125 ubuntu-report[1812]: level=error msg="data were not delivered successfully to metrics server, retrying in 1800s" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: Triaged Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
Please amend the test case to test with both the GA and the (affected) 6.1 OEM kernels. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051188] Re: Firefox 122 update breaks webextensions permission
I meant 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2051188 Title: Firefox 122 update breaks webextensions permission Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: We build webextensions for Firefox. Since the latest update to Firefox 122, the native webextension bridge stopped working. ``` $ flatpak permission-show snap.firefox Table ObjectApp Permissions Data desktop-used-apps application/vnd.debian.binary-package snap.firefox gnome-software-local-file,1,3 0x00 webextensions net.downloadhelper.coapp snap.firefox yes 0x00 ``` This used to work and be enough, but not anymore. In the logs I see: ``` Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest” Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2051188/+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 2051188] Re: Firefox 122 update breaks webextensions permission
Amin, it's 22.05. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2051188 Title: Firefox 122 update breaks webextensions permission Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: We build webextensions for Firefox. Since the latest update to Firefox 122, the native webextension bridge stopped working. ``` $ flatpak permission-show snap.firefox Table ObjectApp Permissions Data desktop-used-apps application/vnd.debian.binary-package snap.firefox gnome-software-local-file,1,3 0x00 webextensions net.downloadhelper.coapp snap.firefox yes 0x00 ``` This used to work and be enough, but not anymore. In the logs I see: ``` Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest” Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2051188/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Status: Triaged => Fix Released ** Changed in: pango1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Invalid Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
So the script here fails to run snap info firefox It was pointed out it managed to upgrade the chromium snap before it, so not sure what's going on, this seems like a job for the snapd team to investigate. ** Package changed: ubuntu-release-upgrader (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+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 2045455] Re: add-apt-repository crashed with --- in _request()
Nevermind, a non-existent or private PPA has been tried to add and software-properties should properly surface the error to you. ** Changed in: software-properties (Ubuntu) Status: Incomplete => Triaged ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Also affects: software-properties (Ubuntu Noble) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2045455 Title: add-apt-repository crashed with --- in _request() Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Noble: Triaged Bug description: Error encountered during first boot after installing ubuntu-unity- desktop on Live Server 24.04 Daily Build. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.40 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 30 02:20:48 2023 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2023-11-30 (2 days ago) InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129) InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y'] PythonDetails: N/A SourcePackage: software-properties Title: add-apt-repository crashed with --- in _request() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
So, after some fairly exhausting debugging, I kind of gave up on that bug, but as a last ditch effort I tried a rebuild against the latest snapshot (even though the changelog didn't seem particularly relevant), nd... Now it builds. I'm so tired. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot Status in glibc package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: New Bug description: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
Tested on mantic install, and as Robie suggested, performed binary debdiff against old versions to ensure only change was the version number. Marking verification done. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21
Unsubscribing ubuntu sponsors as already subscribed to the merge -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: New Status in gettext package in Debian: New Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. Note: gettext 0.22.4 refactors Java support. This delta can be safely dropped after a new upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Daniel van Vugt (vanvugt) wrote 5 hours ago:#7 Are you using the Tiling Assistant extension? It's also been reported there: https://github.com/Leleat/Tiling-Assistant/issues/267 That's a good question. The windows definitely tile but I don't remember installing that particular extension. All I can see is: $ gnome-extensions list d...@rastersoft.com ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Follow up to #92 and #98. For reasons unrelated to this bug I upgraded my system to mantic and removed the workaround. It's been a week and so far I haven't hit this bug again. -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2051188] Re: Firefox 122 update breaks webextensions permission
** Package changed: ubuntu-release-upgrader (Ubuntu) => firefox (Ubuntu) ** Changed in: firefox (Ubuntu) Importance: Undecided => High ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Amin Bandali (bandali) ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1876447 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2051188 Title: Firefox 122 update breaks webextensions permission Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: We build webextensions for Firefox. Since the latest update to Firefox 122, the native webextension bridge stopped working. ``` $ flatpak permission-show snap.firefox Table ObjectApp Permissions Data desktop-used-apps application/vnd.debian.binary-package snap.firefox gnome-software-local-file,1,3 0x00 webextensions net.downloadhelper.coapp snap.firefox yes 0x00 ``` This used to work and be enough, but not anymore. In the logs I see: ``` Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest” Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2051188/+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 2051024] Re: mozillateam/ppa in Ubuntu 23.04 not working anymore
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2051024 Title: mozillateam/ppa in Ubuntu 23.04 not working anymore Status in firefox package in Ubuntu: Invalid Bug description: Until today I had firefox installed from mozillateam/ppa. Last update replaced this package by 1snap1-0ubuntu3 even though I have this ppa configured. I reproduced the issue as well via docker containers. The following happens after setting up the mozillateam/ppa repository and updating the apt sources. In ubuntu:23.04 I get the following: root@965db3f40120:/# apt policy firefox firefox: Installed: (none) Candidate: 1:1snap1-0ubuntu3 Version table: 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages While in ubuntu:23.10 (or ubuntu:22.04) I get the following: root@269f75d9fd26:/# apt policy firefox firefox: Installed: (none) Candidate: 1:1snap1-0ubuntu3 Version table: 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 122.0+build2-0ubuntu0.23.10.1~mt1 500 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu mantic/main amd64 Packages How can I make this package available again in ubuntu:23.04? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 17:56:49 2024 InstallationDate: Installed on 2023-01-17 (371 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SnapChanges: ID Status Spawn Ready Summary 59 Done2024-01-23T12:38:24Z 2024-01-23T12:39:34Z Remove "firefox" snap 60 Done2024-01-23T13:23:56Z 2024-01-23T13:24:05Z Install "firefox" snap SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-07-03 (204 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051024/+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 2051188] [NEW] Firefox 122 update breaks webextensions permission
You have been subscribed to a public bug: We build webextensions for Firefox. Since the latest update to Firefox 122, the native webextension bridge stopped working. ``` $ flatpak permission-show snap.firefox Table ObjectApp Permissions Data desktop-used-apps application/vnd.debian.binary-package snap.firefox gnome-software-local-file,1,3 0x00 webextensions net.downloadhelper.coapp snap.firefox yes 0x00 ``` This used to work and be enough, but not anymore. In the logs I see: ``` Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest” Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187 ``` ** Affects: firefox (Ubuntu) Importance: High Assignee: Amin Bandali (bandali) Status: Confirmed -- Firefox 122 update breaks webextensions permission https://bugs.launchpad.net/bugs/2051188 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- 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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
El problema persiste con: linux-image-6.5.0-14-generic y linux-image-6.5.0-15-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Changed in: gnome-shell-extension-tiling-assistant Status: Unknown => New -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2039868] Re: amdgpu reset during usage of firefox
no, -17 does
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2036333]
(In reply to jeff from comment #9) > (In reply to dabiswas112 from comment #6) > > Hi, I've fixed this on my copr at hazel-bunny/ports. I have also ported the > > signon-ui spec from webkit to webengine, because qt5-qtwebkit is a big > > security hole according to a GNOME guy. > > > > @rdieter could you check if the updates in > > https://github.com/hazel-bunny/rpm-packaging/tree/master/lib/signon are > > acceptable? > > Thoughts on becoming maintainer or co-maintainer of this package > @dabiswas112? Not opposed to it, but need time. This package needs changes for Qt6 and Plasma 6, where upstream KDE recommends using Nicolas Fella's fork. My package uses git master of the original repo and is currently broken on rawhide. Will look into the requirements for being a maintainer and negotiations with KDE SIG who currently maintain the stack to take over maintenance in the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/2036333 Title: signon-ui no longer works for Google authentication Status in kio-gdrive package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Status in signon-ui package in Fedora: Confirmed Bug description: The version of signon-ui from Launchpad no longer works for adding Google services in Kubuntu. The login hangs indefinitely after entering an email address. Apparently, a slightly newer version from its current home on git reportedly works, and is what others have been using: https://gitlab.com/accounts-sso/signon-ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 2049596] Re: Failed to send report information: data not delivered
*** This bug is a duplicate of bug 2050884 *** https://bugs.launchpad.net/bugs/2050884 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-report (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049596 Title: Failed to send report information: data not delivered Status in ubuntu-report package in Ubuntu: Confirmed Bug description: After install click to 'send info to canonical' 'help to improve Ubuntu' fails with msg: Failed to send report information... see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-report 1.7.2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:06:35 2024 InstallationDate: Installed on 2024-01-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-report UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Changed in: mutter Status: Unknown => New -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: Unknown Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Also affects: gnome-shell-extension-tiling-assistant via https://github.com/Leleat/Tiling-Assistant/issues/267 Importance: Unknown Status: Unknown -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Are you using the Tiling Assistant extension? It's also been reported there: https://github.com/Leleat/Tiling-Assistant/issues/267 ** Bug watch added: github.com/Leleat/Tiling-Assistant/issues #267 https://github.com/Leleat/Tiling-Assistant/issues/267 -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes to Login window when HDMI disconnected
Thanks. Since bug 1959507 already exists, we can ignore that here. Comments #3 and #4 however show a different crash: libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) so we will make this bug about that. It's also being tracked in: https://gitlab.gnome.org/GNOME/mutter/-/issues/2846 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2846 https://gitlab.gnome.org/GNOME/mutter/-/issues/2846 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2846 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Summary changed: - GNOME Wayland session crashes to Login window when HDMI disconnected + GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes to Login window when HDMI disconnected
I don't know if this is a duplicate so I am still posting the link: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051222 -- 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/2050865 Title: GNOME Wayland session crashes to Login window when HDMI disconnected Status in mutter package in Ubuntu: Incomplete Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes to Login window when HDMI disconnected
Taken after the crash ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+attachment/5742192/+files/prevjournal.txt -- 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/2050865 Title: GNOME Wayland session crashes to Login window when HDMI disconnected Status in mutter package in Ubuntu: Incomplete Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes to Login window when HDMI disconnected
Taken after the crash ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+attachment/5742191/+files/journal.txt -- 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/2050865 Title: GNOME Wayland session crashes to Login window when HDMI disconnected Status in mutter package in Ubuntu: Incomplete Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes to Login window when HDMI disconnected
The GNOME desktop actually crashes on reconnecting also. Here is my apport bug report: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051221 It also claimed that it was already reported previously: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507 -- 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/2050865 Title: GNOME Wayland session crashes to Login window when HDMI disconnected Status in mutter package in Ubuntu: Incomplete Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/+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
