[Desktop-packages] [Bug 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
** Tags added: regression -- 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/1962699 Title: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.
It seems the performance issue in 22.04 only exists in 22.04 (bug 1962699) and not in earlier releases. That means we only need to backport https://github.com/micheleg/dash-to-dock/pull/1266 to fix this bug in 20.04. ** Tags added: rls-ff-incoming -- 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/1876641 Title: gnome-shell leaks hundreds of megabytes when the dock option 'show- trash' is enabled. Status in Dash to dock: Unknown Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Gnome shell is the single largest resident memory user on my system. It was hovering at ~700mb, then with a few minutes of use of the system (nothing in particular, mostly shell windows, one google-chrome window) - spiked to ~980mb or so, before retreating to 903m. Even with 16gb of ram, that's a huge chunk of the system. I've not been able to identify anything in particular that I'm doing that triggers the growth. In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1856838/comments/5, it was suggested to open a new bug, instead of adding to one of the several existing bugs for this. I'm happy to help try and debug this, but it's not clear where to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 17:32:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-18 (532 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876641/+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 1962699] Re: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
Fix proposed: https://github.com/micheleg/dash-to-dock/pull/1678 ** Summary changed: - gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled + [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled -- 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/1962699 Title: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
Umm yeah, glib doesn't do anything with it: case PROP_RATE_LIMIT: /* not supported by default */ break; -- 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/1962699 Title: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
It appears this line: this._monitor.set_rate_limit(UPDATE_TRASH_DELAY); which is only used in ubuntu-dock actually doesn't work. I still get signal floods of _onTrashChange(). -- 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/1962699 Title: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
Doesn't seem to be a problem in dashtodock, only ubuntu-dock. ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Invalid -- 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/1962699 Title: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] [NEW] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled
Public bug reported: gnome-shell memory usage spikes when deleting files in Nautilus if dash- to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: Invalid ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: amd64 apport-bug jammy performance third-party-packages -- 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/1962699 Title: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled. For example if I delete 1500 files in Nautilus then gnome-shell suddenly gets 15MB bigger. It does come back down within about 10 seconds, but still not ideal for performance. The same bug does not occur with upstream dash-to-dock so it looks like this has been fixed somewhere, but not yet in jammy. WORKAROUND: gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 2 14:06:54 2022 InstallationDate: Installed on 2021-11-05 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.
This sounds like the first fix for the issue which probably explains why it mostly went away in 20.10: https://github.com/micheleg/dash-to- dock/pull/1266/commits/a8c0e1ece7b69e893943ab44a561e8ab2979551f The fix is missing in 20.04 still. But performance of deleting files is still poor even in 22.04 so I'll see what I can do about that before suggesting backports. ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1265 https://github.com/micheleg/dash-to-dock/issues/1265 ** Also affects: ubuntu-dock via https://github.com/micheleg/dash-to-dock/issues/1265 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released ** Tags added: fixed-in-69 fixed-upstream ** Project changed: ubuntu-dock => dash-to-dock ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => High -- 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/1876641 Title: gnome-shell leaks hundreds of megabytes when the dock option 'show- trash' is enabled. Status in Dash to dock: Unknown Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Gnome shell is the single largest resident memory user on my system. It was hovering at ~700mb, then with a few minutes of use of the system (nothing in particular, mostly shell windows, one google-chrome window) - spiked to ~980mb or so, before retreating to 903m. Even with 16gb of ram, that's a huge chunk of the system. I've not been able to identify anything in particular that I'm doing that triggers the growth. In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1856838/comments/5, it was suggested to open a new bug, instead of adding to one of the several existing bugs for this. I'm happy to help try and debug this, but it's not clear where to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 17:32:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-18 (532 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876641/+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 1955058] Re: gnome-shell memory use climbs when dash-to-dock show-trash is enabled
** Summary changed: - gnome-shell memory use climbs to multiple GBs + gnome-shell memory use climbs when dash-to-dock show-trash is enabled ** This bug is no longer a duplicate of bug 1876641 gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled. -- 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/1955058 Title: gnome-shell memory use climbs when dash-to-dock show-trash is enabled Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Gnome Shell memory use grows over time Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs up again. Occasionally it goes so high on my 16 GB machine that it swaps and crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 16:53:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-03 (1565 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1955058/+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 1962565] Re: gnome-shell occupies a lot of RAM and blocks system when deleting files in Nautilus
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1265 https://github.com/micheleg/dash-to-dock/issues/1265 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1265 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-69 fixed-upstream ** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High -- 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/1962565 Title: gnome-shell occupies a lot of RAM and blocks system when deleting files in Nautilus Status in Dash to dock: Unknown Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: sometimes the system uses 11GB of 16GB ram for 10+ gnome-shell processes. It seemingly occurs as soon as deleting files via the file manager. It occurred for me when trying to delete 500 files with a total of 700mb but also when just deleting 200 files totaling around 75mb. A suggested solution to try gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false (bug 1876641, mentioned to me in bug 1962357) did not resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 1 10:52:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-02 (271 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1962565/+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 1962679] [NEW] take screenshot does not work
Public bug reported: playing an .avi video i select 'take screensot' and i have a small window with a message 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report'corrado@corrado-p5-jj-0203:~$ inxi -SGx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-18-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 41.3 Distro: Ubuntu 22.04 (Jammy Jellyfish) Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.2 direct render: Yes corrado@corrado-p5-jj-0203:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 41~alpha~20220222-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 06:26:15 2022 InstallationDate: Installed on 2022-02-08 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962679 Title: take screenshot does not work Status in totem package in Ubuntu: New Bug description: playing an .avi video i select 'take screensot' and i have a small window with a message 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report'corrado@corrado-p5-jj-0203:~$ inxi -SGx System: Host: corrado-p5-jj-0203 Kernel: 5.15.0-18-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 41.3 Distro: Ubuntu 22.04 (Jammy Jellyfish) Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.2 direct render: Yes corrado@corrado-p5-jj-0203:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 41~alpha~20220222-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 06:26:15 2022 InstallationDate: Installed on 2022-02-08 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1962679/+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 1955994] Re: LibreOffice Help
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1955994 Title: LibreOffice Help Status in libreoffice package in Ubuntu: Expired Bug description: Ubuntu 21.10 From Writer and Calc the Libreoffice Help is accessible only if the default browser is Google Chrome. If the default browser is Firefox, clicking on Libreoffice Help, the attached screen appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1955994/+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 1942307] Re: ubiquity uses performance mode for nvidia driver
Ok. So, we now have three bugs with identical descriptions - this one, bug #1942789, and bug #1946476. Either they're independent bugs, in which case they should have different test cases, or they're basically all the same bug, in which case we should pick one of the bugs and mark the others as duplicates. It *seems* like they're all fundamentally “We want to default to on- demand, and ensure that gives RTD3 on supported laptops”, so maybe that's *two* bugs and we drop the third? I don't really mind. Additionally, there are changes in the upload which do not appear to have any corresponding bugs. Namely: - Use bootvga detection when last_gfx_boot is not available. - Catch BrokenPipeError. If those are not part of the RTD3/ondemand fixes, they should have their own bugs so that we can test that they fix what they're expected to fix. If they *are* part of the ondemand fixes, that's fine, and someone should just document that. Sorry for the back and forth on this - to get this over the line, would you kindly give me a ping (RAOF on libera.chat in #ubuntu-devel or #ubuntu-release) when you've responded to this, and we'll see if we can get this all sorted out this week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+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 1935717] Re: Bug when right-clicking the trash icon on the taskbar
*** This bug is a duplicate of bug 1934185 *** https://bugs.launchpad.net/bugs/1934185 ** This bug is no longer a duplicate of bug 1936644 Right-clicking on the empty trash bin in the dock results in broken empty menu ** This bug has been marked a duplicate of bug 1934185 Ubuntu Dock popup menu in top left corner of the screen and won't go away -- 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/1935717 Title: Bug when right-clicking the trash icon on the taskbar Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When the trash can icon is right-clicked, a visual defect occurs in the upper left corner of the taskbar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1935717/+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 1902385] Re: At times I have an app. menu that opens and never closes
*** This bug is a duplicate of bug 1785527 *** https://bugs.launchpad.net/bugs/1785527 ** This bug has been marked a duplicate of bug 1785527 Menu associated with launcher tile right click does not disappear when it should. -- 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/1902385 Title: At times I have an app. menu that opens and never closes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: It has happened twice in the last little bit where I opened a menu on an icon in the dock and the menu remains opened "forever" (until next reboot). Opening other menus from other icons in the dock works as expected. In most cases, the menu that's stuck is "transparent" to clicks, that is, when I try to click a menu item, the thing behind the menu gets clicked. When I'm able to click on an item in the menu (it turns orange when I do that successfully) then the mouse pointer is stuck over that item and that's it... nothing happens. Using Cmd-Tab to switch between windows waken the mouse up so I could use it again. I tried to restart the GDM3, the dock & menu came back as it was before the restart. sudo systemctl restart display-manager I tried once to Log Out (instead of rebooting) and the graphical interface didn't come back. I tried to restart the GDM from another computer (remotely through SSH) and the screen flashed a bit but it went right back to the boot console. So in other words the Log Out failed. Probably waiting on something that has a deadlock? The only way I've found to fix the issue is to reboot the computer (which I do not like to do too much... plus it takes about 3 min. with my monster server). See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon- menu-gets-stuck-open-any-way-to-fix-that-without-having-to ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:09:43 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902385/+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 1936644] Re: Right-clicking on the empty trash bin in the dock results in broken empty menu
*** This bug is a duplicate of bug 1934185 *** https://bugs.launchpad.net/bugs/1934185 ** This bug has been marked a duplicate of bug 1934185 Ubuntu Dock popup menu in top left corner of the screen and won't go away -- 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/1936644 Title: Right-clicking on the empty trash bin in the dock results in broken empty menu Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: If the trash is empty (has no deleted files), the trash bin wasn't open at the time, and I right-clicked on it in the dock, it would result in the broken empty menu that appears in the top left corner. Moreover, it always appears on top of every window and the top bar, essentially blocking the Activities button and some parts of the application button that shows the menu for the app. Steps to reproduce: 1. Log in to GNOME 40 2. Right-click on the empty trash bin in the dock (not in Nautilus) Expected results: Nothing would appear. Actual results: The broken empty menu in the top left corner shows up lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:26:59 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 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-extension-ubuntu-dock/+bug/1936644/+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 1962513] Re: gnome-shell crashed with SIGSEGV in jammy live session (gnome-shell --sm-disable --mode=ubiquity)
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962513/+attachment/5564231/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Information type changed from Private to Public -- 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/1962513 Title: gnome-shell crashed with SIGSEGV in jammy live session (gnome-shell --sm-disable --mode=ubiquity) Status in gnome-shell package in Ubuntu: Confirmed Bug description: I was installing Jammy Jellyfish and an error popped up, It brought me to this so heres the info Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: Installed: 41.3-1ubuntu1 Candidate: 41.3-1ubuntu1 Version table: *** 41.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 16 18:10:33 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcEnviron: PATH=(custom, no user) LANG=C.UTF-8 XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SegvAnalysis: Segfault happened at: 0x7fe597633a6c:mov0x0(%rsi),%rax PC (0x7fe597633a6c) ok source "0x0(%rsi)" (0x14ac7110) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7fe597633a6c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffdb417b9d0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962513/+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 1962576] Re: Quirk with gnome context menu left over dock after program closed
*** This bug is a duplicate of bug 1934185 *** https://bugs.launchpad.net/bugs/1934185 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1934185, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** This bug has been marked a duplicate of bug 1934185 Ubuntu Dock popup menu in top left corner of the screen and won't go away -- 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/1962576 Title: Quirk with gnome context menu left over dock after program closed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I had thunderbird open with gnome dock saying it has two windows. I've realized then on the top left of my screen there is context menu of dock - where you can Quit/Open New Windows and some commands specific to program(thunderbird in my case). The menu is unclickable, over all other windows. So I've closed thunderbird, the process was indeed ended but the meanu still appears, with the thunderbird icon still active as having one more window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 13:46:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2489 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962576/+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 1962565] Re: gnome-shell occupies a lot of ram and blocks system
Thanks for the bug report. Yes this did sound a lot like bug 1876641 when you mentioned it yesterday and I even installed 20.04 and verified that "show-trash false" fixed it for me. I did however find that Ubuntu 22.04 has a lesser form of the issue where gnome-shell/ubuntu-dock will suddenly spike in memory usage by many megabytes when deleting files from Nautilus, and then mostly free the memory again 10 seconds later. I was planning on investigating that more. For the moment I will assume this issue is still just the ubuntu-dock extension. ** Tags added: gnome-shell-leak ** Summary changed: - gnome-shell occupies a lot of ram and blocks system + gnome-shell occupies a lot of RAM and blocks system when deleting files in Nautilus ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- 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/1962565 Title: gnome-shell occupies a lot of RAM and blocks system when deleting files in Nautilus Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: sometimes the system uses 11GB of 16GB ram for 10+ gnome-shell processes. It seemingly occurs as soon as deleting files via the file manager. It occurred for me when trying to delete 500 files with a total of 700mb but also when just deleting 200 files totaling around 75mb. A suggested solution to try gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false (bug 1876641, mentioned to me in bug 1962357) did not resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 1 10:52:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-02 (271 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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-extension-ubuntu-dock/+bug/1962565/+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 1962642] geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected
StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: New Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+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 1962642] Re: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: New Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Commit 83c6b2a was released already in gnome-shell 3.37.1 -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1961540] Re: tracker-miner-fs-3 massive CPU usage and system slowdown
** Changed in: ubuntu-power-consumption Status: New => Invalid -- 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/1961540 Title: tracker-miner-fs-3 massive CPU usage and system slowdown Status in Tracker: Unknown Status in The Ubuntu Power Consumption Project: Invalid Status in tracker-miners package in Ubuntu: Invalid Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center tracker-miner-fs: Installed: 3.1.3-1 Candidate: 3.1.3-1 Version table: *** 3.1.3-1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - Ubuntu indexes the files in the background at a very low priority. 4) What happened instead - Ubuntu grinds to a halt and the CPU usage is off the chart right after I boot up when search indexing is enabled. When checking the "System Monitor" it is always "tracker-miner-fs-3" consuming all of the resources. I have been having problems with tracker-miner since 20.04 LTS and so I upgraded to 21.10 and I'm still having problems with search indexing bringing my system to its knees and making Ubuntu clunky and unusable. I have attached a photo of my system specifications. -- My previous bug report for 20.04 is here: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920 I'm using the same system. -- The only fix I have found is to completely disable search indexing: Settings > Search > Turn Off Search Indexing. After doing this, my system is running perfectly again with low CPU usage! To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1961540/+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 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
** Summary changed:
- gnome-shell crashed with SIGSEGV in meta_context_terminate()
+ gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from
process_ice_messages()
--
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/1959937
Title:
gnome-shell crashed with SIGSEGV in
meta_context_terminate(context=0x0) from process_ice_messages()
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Confirmed
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
The error occurred when I ran apt update/upgrade in a terminal window
after logging in.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 3 09:03:52 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['gnome-initial-setup']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-02-03 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0
?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_context_terminate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1959937/+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 1958398] Re: seahorse does not show in HUD for "gpg"
Do you mean the desktop menu? IIRC, it matches entries based on their individual descriptions and names. You can edit the launcher by right-clicking on the entry. You can change it so that the 'Description' field includes the term 'GPG'. I did this and it worked for me on Linux Mint, but this is a Linux distro, so Your Mileage WILL Vary. Any luck yet?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1958398 Title: seahorse does not show in HUD for "gpg" Status in seahorse package in Ubuntu: New Bug description: Seahorse does not show as an option when typing "gpg" in HUD but it should. It is being offered as a choice when typing "password". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1958398/+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 1958398] Re: seahorse does not show in HUD for "gpg"
HUD?.. Heads-Up Display? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1958398 Title: seahorse does not show in HUD for "gpg" Status in seahorse package in Ubuntu: New Bug description: Seahorse does not show as an option when typing "gpg" in HUD but it should. It is being offered as a choice when typing "password". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1958398/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
I am still having the same issue, along with many others issues lol... I have stopped trying to find any useful answers, as most sources seem content with being in control, obfuscating, complaining about people's questions or just plain bullying. I actually saw this as advice in a 'support forum' (an oxymoron): User: "I can't get 'x' to work properly" 'Support' User: "You can uninstall it by typing " Is NOT a solution, no matter how dense you are. In the future, software will be developed when people feel like it. Bugs which plague modern systems will only be fixed if we act like sycophants, otherwise some of us will have the unique opportunity to discuss these various and endemic plague of software bugs which our grandchildren, no doubt, will also experience. Encryption software that doesn't encrypt; the poisonous sprawl of large- scale software projects managed by children and professional mini-nazis; file managers which can't mount drives; Error messages which never see the light of day, ever perpetuating everyone's desire to run a stable system; puerile arguments between projects, leaving the fallout for the end users to deal with; Non-existent documentation; When Developers basically say: "But I want it to work MY way, NOT the NORMAL, EXPECTED, AVERAGE way!"... Oh, this project has moved (Yet again... But we're leaving the old, inaccurate web site and forum up from 2011 to soil relevant search results"; Regularly requiring specific system/software information from end users posting reports, but offer said users NO framework for doing so... The list of mistakes and lapses of care goes on. Open source = Unfinished; buggy; elitist/out-of-touch/narcissistic developers. I mean, this stuff is written in people's 'free time'... What can we expect, really? A cohesive development and debugging roadmap? lol I haven't found anything useful on a support forum for years and have, sadly, grown accustomed to the modern Linux staples of the 'workaround' and the 'do without, then'. On one hand you have Microsoft advertising on your paid-for desktop, or you have a bunch of part-timers making out that they're the best thing since sliced bread... Humanity is embarrassing. And I will leave you all with this absolute gem from the MIT OS license... "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE." Basically: It's your own fault if you trust this software to do anything remotely useful. The author is not responsible for anything that goes wrong. This is one of the modern standards in production quality we have to look forward to. TL;DR: Don't expect all FOSS developers to even remotely consider the quality of their software or their support, these ad-hoc organisations have no charter and no legal responsibility to their end users. And, as always, don't use Linux if your income depends on a stable, available and working IT system - Most Linux distros are STILL 90% 'under construction'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Ok. So it seems that the bug *exists* in Focal, so now we just need to verify that the bug is *fixed* by the proposed package. @angie78 - as you seem to suffer from the bug, can you try to verify that the proposed packages (from https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comments/106 ) fix the bug? Once we've got verification that the bug is fixed, we can release the packages into -updates and everyone can benefit! Anyone else is also welcome to verify! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS
[Desktop-packages] [Bug 1962624] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 might affect bugs: 1955758 1962495 1962623 1962624 1962626 1962630 1962633 I will add this text to all open bugs. affected parts: tracker-miner-fs-3 totem gvfsd-mtp udisksd background information: - installed 18.04 lts - dist-upgraded to 20.04 lts - back up before sending hardware for repair, got replacement hardware (with default rubbish) - restore on replaced hardware with -- modified filesystem (btrfs, dont remember previously used fs) and -- full-disk encryption (multiple luks2 partitions instead of home-only) - noticed that integrating grub-2.06 correctly (building package etc) would be too much effort - downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04 - added grub-setup script to include cryptmount grub module etc. - got btrfs kernel warnings regularly - dist-upgraded to 22.04 lts (beta, late January) - still btrfs kernel warnings regularly [- many updates since, as to be expected.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1962624 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: automatically created data, did not look into it. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.chromium.rules Date: Thu Feb 24 23:58:25 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2018-12-10 (1177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MEDION DEFENDER P10 ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/mapper/newroot Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7febbba0db8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7febbba105d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7febbba46c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7febbba46c80 , p=0x5627404144c0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1962624/+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 1962638] [NEW] Ubuntu dock overlaps programs after resume from screen blank
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: Installed: 1.472 Candidate: 1.472 Version table: *** 1.472 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1962638 Title: Ubuntu dock overlaps programs after resume from screen blank Status in ubuntu-meta package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: Installed: 1.472 Candidate: 1.472 Version table: *** 1.472 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1962638/+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 1962638] Re: Ubuntu dock overlaps programs after resume from screen blank
** Attachment added: "Ubuntu dock overlapping a program after resume from screen blank" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1962638/+attachment/5564720/+files/Screenshot%20from%202022-03-02%2008-42-37.png ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: - Installed: 1.472 - Candidate: 1.472 - Version table: - *** 1.472 500 - 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.472 + Candidate: 1.472 + Version table: + *** 1.472 500 + 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages + 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program again rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. + - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1962638 Title: Ubuntu dock overlaps programs after resume from screen blank Status in ubuntu-meta package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: Installed: 1.472 Candidate: 1.472 Version table: *** 1.472 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1962638/+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 1793127]
Tested again on LibreOffice 7.3.0.3 on Windows 10. Now the formula line looks good but all LTR cells in the main view have font metrics mixed up, whether I'm currently typing them or not. For some reason, cells starting with a RTL character that Calc automatically aligns to the right behave as they should, although they're still not truly RTL, as the order of mixed LTR/RTL elements is wrong. See the attached screenshot. Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1793127 Title: [upstream] Font metrics mixed up for RTL insets in a LTR context in Calc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: In the attached screenshot, I’ve written an English sentence with an Arabic word in the middle on the first row of a Calc sheet. On the second row, I’ve written the same Arabic word (العربية) by itself. The second row looks as it should but on the first row, some of the characters overlap. The same problem occurs if I surround the isolated Arabic word with parentheses, in which case the cell is automatically aligned to the left. I’m using the default font settings, which in my environment are Liberation Sans for Latin text and DejaVu Sans for Arabic. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:32:13 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793127/+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 1793127]
Created attachment 178599 Screenshot on 7.3.0.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1793127 Title: [upstream] Font metrics mixed up for RTL insets in a LTR context in Calc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: In the attached screenshot, I’ve written an English sentence with an Arabic word in the middle on the first row of a Calc sheet. On the second row, I’ve written the same Arabic word (العربية) by itself. The second row looks as it should but on the first row, some of the characters overlap. The same problem occurs if I surround the isolated Arabic word with parentheses, in which case the cell is automatically aligned to the left. I’m using the default font settings, which in my environment are Liberation Sans for Latin text and DejaVu Sans for Arabic. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:32:13 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793127/+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 1962170] Re: DEP8 failure with samba 4.15.5
Hm no, if I apply this patch (or something like it) https://paste.ubuntu.com/p/vVTyzHMqvr/ the build succeeds. Wtf. -- 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/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: In Progress Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1962170] Re: DEP8 failure with samba 4.15.5
So fwiw the build failure on ppc64el is hanging on the the call to io.ReadAll(stderr) in SetupSmb (i.e. here: https://github.com/ubuntu/adsys/blob/v0.8/internal/testutils/samba.go#L38). No idea why, but my sense from poking around is that the test has already failed when the hang occurs so maybe it's some pipe buffer being full nonsense. -- 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/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: In Progress Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1962276] Re: Laptop monitor does not turn off/disconnect when the lid is closed
** Changed in: upower Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed Status in Upower: Fix Released Status in upower package in Ubuntu: Fix Released Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962276/+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 1962627] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
*** This bug is a duplicate of bug 1959937 *** https://bugs.launchpad.net/bugs/1959937 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1959937, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962627/+attachment/5564629/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564631/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564636/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564637/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564638/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564641/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962627/+attachment/5564642/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1959937 gnome-shell crashed with SIGSEGV in meta_context_terminate() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1962627 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() Status in gnome-shell package in Ubuntu: New Bug description: This problem (among others) occurred shortly after the system was updated and restarted. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 12:22:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-12-13 (78 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211212) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962627/+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 1962624] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1955758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962624/+attachment/5564585/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564588/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564599/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564601/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564602/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564603/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962624/+attachment/5564604/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1955758 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1962624 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: automatically created data, did not look into it. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.chromium.rules Date: Thu Feb 24 23:58:25 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2018-12-10 (1177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MEDION DEFENDER P10 ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/mapper/newroot Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7febbba0db8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7febbba105d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7febbba46c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7febbba46c80 , p=0x5627404144c0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1962624/+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
Re: [Desktop-packages] [Bug 1962043] Re: libwacom9 : depends on : libwacom-common
-- 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/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+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 1962347] Re: firefox-trunk crashed with SIGSEGV in wl_display_read_events()
Thanks for the report Anas. Can you consistently reproduce the crash? Is it also reproducible with a released version of firefox? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1962347 Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() Status in firefox package in Ubuntu: Incomplete Bug description: After Installing Nvidia 510.54, The system may have some problems in detection of GPUs properly. No VAAPI after Nvidia installation, even if i set nvidia-drm.modeset=1 in grub and doing update-grub. The system contains Intel Integrated GPU and nvidia MX250 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: firefox-trunk 99.0~a1~hg20220224r608565-0ubuntu0.22.04.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: glados 1693 F pipewire-media- glados10070 F pulseaudio /dev/snd/pcmC0D0p: glados10070 F...m pulseaudio /dev/snd/seq:glados 1692 F pipewire BuildID: 20220224090316 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 22:25:56 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:365 DefaultProfilePrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox-trunk/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox-trunk/firefox-trunk ForcedLayersAccel: False InstallationDate: Installed on 2022-02-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 ProcCmdline: /usr/lib/firefox-trunk/firefox-trunk Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:365 Profile0PrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=99.0a1/20220224090316 RunningIncompatibleAddons: False SegvAnalysis: Segfault happened at: 0x7f5b27582f48 : cmp 0x18(%rax),%r14d PC (0x7f5b27582f48) ok source "0x18(%rax)" (0x7f5b1da1ecf8) not located in a known VMA region (needed readable region)! destination "%r14d" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: firefox StacktraceTop: wl_display_read_events () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_dispatch_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_roundtrip_queue () from /lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/firefox-trunk/libxul.so ?? () from /usr/lib/firefox-trunk/libxul.so Title: firefox-trunk crashed with SIGSEGV in wl_display_read_events() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 09/03/2021 dmi.bios.release: 15.15 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.15:bd09/03/2021:br15.15:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:sku5SU52EA#BH4: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 5SU52EA#BH4 dmi.product.version:
[Desktop-packages] [Bug 1962609] [NEW] 1.20 version (jammy) makes pulseUI crash (core dump)
Public bug reported: Hi, just updated from 21.10 to 22.04 and noticed my pulseUI VPN client fails with a SIGSEGV. The core dump shows the following: (gdb) backtrace #0 0x0032 in () #1 0x7f7dd2b0c6c1 in () at /lib/x86_64-linux-gnu/libgstapp-1.0.so.0 #2 0x7f7dd13ee958 in _gst_debug_min () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #3 0x7f7d480d2c10 in () #4 0x7f7d38007f30 in () #5 0x7f7d480ce800 in () #6 0x0001 in () #7 0x7f7d480d2d38 in () #8 0x7f7dd141e292 in () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0 #9 0x7f7dd1330c7c in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #10 0x7f7dd13312fe in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #11 0x7f7dd13317b8 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #12 0x7f7dd1327660 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #13 0x7f7dd133488a in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #14 0x7f7d7b4add1c in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoreelements.so #15 0x7f7dd1359ea7 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #16 0x7f7dd2bcb5a4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f7dd2bc8941 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f7dd201eb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #19 0x7f7dd20b0b80 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 I found downgrading package libgstreamer-plugins-base1.0-0:amd64 to 1.18.5-1 (the version in 21.10) fixed the issue. I can provide the entire core dump file (~20Mb) if you need. best regards. ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962609 Title: 1.20 version (jammy) makes pulseUI crash (core dump) Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: Hi, just updated from 21.10 to 22.04 and noticed my pulseUI VPN client fails with a SIGSEGV. The core dump shows the following: (gdb) backtrace #0 0x0032 in () #1 0x7f7dd2b0c6c1 in () at /lib/x86_64-linux-gnu/libgstapp-1.0.so.0 #2 0x7f7dd13ee958 in _gst_debug_min () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #3 0x7f7d480d2c10 in () #4 0x7f7d38007f30 in () #5 0x7f7d480ce800 in () #6 0x0001 in () #7 0x7f7d480d2d38 in () #8 0x7f7dd141e292 in () at /lib/x86_64-linux-gnu/libgstbase-1.0.so.0 #9 0x7f7dd1330c7c in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #10 0x7f7dd13312fe in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #11 0x7f7dd13317b8 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #12 0x7f7dd1327660 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #13 0x7f7dd133488a in gst_pad_push_event () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #14 0x7f7d7b4add1c in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoreelements.so #15 0x7f7dd1359ea7 in () at /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #16 0x7f7dd2bcb5a4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f7dd2bc8941 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f7dd201eb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #19 0x7f7dd20b0b80 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 I found downgrading package libgstreamer-plugins-base1.0-0:amd64 to 1.18.5-1 (the version in 21.10) fixed the issue. I can provide the entire core dump file (~20Mb) if you need. best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1962609/+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 1961565] Re: Package in bionic installs unnecessary build artifacts
** Changed in: chromium-browser (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: chromium-browser (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1961565 Title: Package in bionic installs unnecessary build artifacts Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Bionic: Fix Committed Bug description: Not sure when this started happening, but today I noticed while testing chromium-browser 98.0.4758.102-0ubuntu0.18.04.1 that the chromium-browser binary package installs a lot of build artifacts that increase unnecessarily the size of the package. These artifacts include *.runtime_deps files, as well as binaries such as transport_security_state_generator or protozero_plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1961565/+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 1960947] Re: Graphical issues for GtKGL in software rendering
This bug was fixed in the package gtk+3.0 - 3.24.20-0ubuntu1.1 --- gtk+3.0 (3.24.20-0ubuntu1.1) focal; urgency=medium * debian/patches/git_rendering_issues.patch: - cherry pick an upstream fix for opengl display issues when using software rendering (lp: #1960947) * debian/patches/git_newglib_symbols.patch: - backport patch to fix the build with the current libglib version -- Sebastien Bacher Tue, 15 Feb 2022 18:50:52 +0100 ** Changed in: gtk+3.0 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1960947 Title: Graphical issues for GtKGL in software rendering Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Focal: Fix Released Bug description: * Issue GTK applications using GL graphic show corruption problems under software rendering * Test case 1. install gtk-3-examples 2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo 3. select the gl example, it should render without issues * Regression potentiel The change is in the GL backend so check for rendering issues in GTK softwares using GL, including flutter applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+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 1962593] Re: SMB Mount to backup directory prevents mounting parent directory
** Also affects: deja-dup Importance: Undecided Status: New ** Also affects: duplicity Importance: Undecided Status: New ** Description changed: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: - Storage location: Network Server - Network Location: smb://1.2.3.4/backup/UbuntuBackup - Folder: MyMachineBackup + Storage location: Network Server + Network Location: smb://1.2.3.4/backup/UbuntuBackup + Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - - At the bottom set "Connect to server" to: smb://1.2.3.4/backup + - At the bottom set "Connect to server" to: smb://1.2.3.4/backup - Result: + Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted - * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus - * Prevents all access to all parent folders of the backup folder + * Can happen at semi-random times if the backup is on a schedule + * This is especially a problem when backing up remotely over a VPN which can take a long time + * Prevents access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory - * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out - * This is especially a problem when backing up remotely over a VPN which can take a long time + * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus + * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out or the backup process exits Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: - XDG_RUNTIME_DIR= - SHELL=/bin/bash - PATH=(custom, user) - LANG=en_US.UTF-8 + XDG_RUNTIME_DIR= + SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1962593 Title: SMB Mount to backup directory prevents mounting parent directory Status in Déjà Dup: New Status in Duplicity: New Status in deja-dup package in Ubuntu: New Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * Can happen at semi-random times if the backup is on a schedule * This is especially a problem when backing up remotely over a VPN which can take a long time * Prevents access to all parent folders of the backup folder * Nautilus will
[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directory
Maybe not a "bug" per se, but definitely an unwanted side-effect of the network backup process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1962593 Title: SMB Mount to backup directory prevents mounting parent directory Status in deja-dup package in Ubuntu: New Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * Prevents all access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out * This is especially a problem when backing up remotely over a VPN which can take a long time Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1962593/+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 1962593] [NEW] SMB Mount to backup directory prevents mounting parent directory
Public bug reported: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * Prevents all access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out * This is especially a problem when backing up remotely over a VPN which can take a long time Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug backup focal network smb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1962593 Title: SMB Mount to backup directory prevents mounting parent directory Status in deja-dup package in Ubuntu: New Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * This causes a hanging problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * Prevents all access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out * This is especially a problem when backing up remotely over a VPN which can take a long time Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1962590] [NEW] Un-checking Make available to other users causes WiFi failure to connect
Public bug reported: If I un-check the "Make available to other users" box, as soon as the computer is rebooted it will not re-connect to that WiFi network again and acts as if it has never connected to the network. I have to click on the SSID name and set up a new connection (e.g. "SSIDname 1") to reconnect. If I again go into settings and un-check the box on the new connection, the issue repeats (and I end up with "SSIDname 2", etc.). Even if I go back and re-check the box and apply the settings, the system refuses to reconnect using that connection and I have to set up a new one. Any new connection works fine across reboots, etc. until the first reboot after I un-check the box and apply the settings. I only have one user on this system, currently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 10:17:15 2022 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-28 (489 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of affected settings screen" https://bugs.launchpad.net/bugs/1962590/+attachment/5564520/+files/Screenshot%20from%202022-03-01%2010-21-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1962590 Title: Un-checking Make available to other users causes WiFi failure to connect Status in gnome-control-center package in Ubuntu: New Bug description: If I un-check the "Make available to other users" box, as soon as the computer is rebooted it will not re-connect to that WiFi network again and acts as if it has never connected to the network. I have to click on the SSID name and set up a new connection (e.g. "SSIDname 1") to reconnect. If I again go into settings and un-check the box on the new connection, the issue repeats (and I end up with "SSIDname 2", etc.). Even if I go back and re-check the box and apply the settings, the system refuses to reconnect using that connection and I have to set up a new one. Any new connection works fine across reboots, etc. until the first reboot after I un-check the box and apply the settings. I only have one user on this system, currently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 10:17:15 2022 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-28 (489 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1962590/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Fixing the statement from the previous post, the feature had been not working and was fixed in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/83c6b2a So yes, it's a regression and we need to decide on the best way forward -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Was it a change on the packagekit side this cycle? The shell has been having the same behaviour of displaying the dialog if offline updates are enabled for a long time -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962566] Re: gnome-shell crash after resume from suspend in gdm/util.js:154
** Summary changed: - gnome-shell crash after resume from suspend in util.js:154 + gnome-shell crash after resume from suspend in gdm/util.js:154 -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+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 1962576] Re: Quirk with gnome context menu left over dock after program closed
The issue on the screen ** Attachment added: "Zrzut ekranu z 2022-03-01 13-52-51.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962576/+attachment/5564482/+files/Zrzut%20ekranu%20z%202022-03-01%2013-52-51.png -- 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/1962576 Title: Quirk with gnome context menu left over dock after program closed Status in gnome-shell package in Ubuntu: New Bug description: I had thunderbird open with gnome dock saying it has two windows. I've realized then on the top left of my screen there is context menu of dock - where you can Quit/Open New Windows and some commands specific to program(thunderbird in my case). The menu is unclickable, over all other windows. So I've closed thunderbird, the process was indeed ended but the meanu still appears, with the thunderbird icon still active as having one more window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 13:46:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2489 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962576/+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 1962576] [NEW] Quirk with gnome context menu left over dock after program closed
Public bug reported: I had thunderbird open with gnome dock saying it has two windows. I've realized then on the top left of my screen there is context menu of dock - where you can Quit/Open New Windows and some commands specific to program(thunderbird in my case). The menu is unclickable, over all other windows. So I've closed thunderbird, the process was indeed ended but the meanu still appears, with the thunderbird icon still active as having one more window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 13:46:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2489 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (8 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- 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/1962576 Title: Quirk with gnome context menu left over dock after program closed Status in gnome-shell package in Ubuntu: New Bug description: I had thunderbird open with gnome dock saying it has two windows. I've realized then on the top left of my screen there is context menu of dock - where you can Quit/Open New Windows and some commands specific to program(thunderbird in my case). The menu is unclickable, over all other windows. So I've closed thunderbird, the process was indeed ended but the meanu still appears, with the thunderbird icon still active as having one more window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 13:46:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2489 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962576/+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 1962510] Re: failing tests with new sssd, blocks python3-defaults
These tests are a firehose, but I think this is the only failure on armhf: "--- FAIL: TestInit/Configuration_changed (0.00s)" --- FAIL: TestInit (2.22s) --- PASS: TestInit/Error_on_config_flag_points_to_unexisting_path (0.00s) --- PASS: TestInit/Load_configuration,_no_file,_no_flag,_no_env (0.00s) --- PASS: TestInit/Empty_configuration_file_is_supported (0.02s) --- PASS: TestInit/Flag_is_supported (0.03s) --- PASS: TestInit/Error_on_invalid_configuration_file (0.00s) --- PASS: TestInit/Error_on_callback_returning_error_on_first_call (0.00s) --- PASS: TestInit/Load_configuration_with_file (0.00s) --- PASS: TestInit/No_config_flag_set_before_Init_is_call_is_ignored (0.00s) --- FAIL: TestInit/Configuration_changed (0.00s) --- PASS: TestInit/Error_on_no_verbose_flag_set_before_Init_is_call (0.00s) --- PASS: TestInit/Configuration_file_created_after_Init()_is_not_taken_into_account (2.00s) --- PASS: TestInit/Callback_in_error_on_refresh_only_prints_warning (0.00s) --- PASS: TestInit/Flag_has_precedence_over_env (0.03s) --- PASS: TestInit/Env_has_precedence_over_configuration (0.06s) --- PASS: TestInit/Configuration_flag_has_precedence_over_local_file (0.00s) --- PASS: TestInit/Configuration_flag,_not_in_config_dir (0.00s) --- PASS: TestInit/Environment_is_supported (0.00s) No idea what happened, there is no other clue whatsoever in the test output. -- 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/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Alas I've not been very thorough in recording which LibreOffice app I've opened in prior comments (it's usually one or two randomly I open), but I booted an QA-test install done earlier today on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) NOTE: Install was an "install using existing partition" type; ie. no format of partition; so additional packages installed (manually installed) get re-installed etc, and user configs or anything that existed in $HOME isn't touched. This install was a 21.04 system prior to it's EOL where it became a jammy install (I forget what it was pre-21.04, but parts of my $HOME will be many cycles ago). Either way - LibreOffice apps (math & draw I think I used) and LibreOffice - HELP - LibreOffice.Help did NOT show on error on either tried app; unlike the FRESH INSTALL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.
Actually bug 1955058 might have some other explanation. In my own testing I can now reproduce this bug on 20.04 but not 22.04. Although even 22.04 seems to spike 10MB+ temporarily and drops back down after a few seconds. -- 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/1876641 Title: gnome-shell leaks hundreds of megabytes when the dock option 'show- trash' is enabled. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Gnome shell is the single largest resident memory user on my system. It was hovering at ~700mb, then with a few minutes of use of the system (nothing in particular, mostly shell windows, one google-chrome window) - spiked to ~980mb or so, before retreating to 903m. Even with 16gb of ram, that's a huge chunk of the system. I've not been able to identify anything in particular that I'm doing that triggers the growth. In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1856838/comments/5, it was suggested to open a new bug, instead of adding to one of the several existing bugs for this. I'm happy to help try and debug this, but it's not clear where to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 17:32:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-18 (532 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876641/+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 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
** Description changed: + [ Description ] + + We should keep up with GStreamer's bugfix releases in the 1.16 series + that 20.04 shipped with. + + [ QA and testing ] + + Play a range of videos in Totem. Play a range of audio tracks in + Rhythmbox. Try to stream audio and/or video. Try to install a missing + codec. + + In all cases, make sure that everything which worked before still works. + + [ Regression potential ] + + If one of the fixes is bad then it might break video or audio playback, + or could crash any application that tries to use gstreamer. + + --- + + On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04 Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: New Status in gst-plugins-base1.0 source package in Focal: New Status in gst-plugins-good1.0 source package in Focal: New Status in gstreamer1.0 source package in Focal: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
** Also affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Fix Released ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04 Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 source package in Focal: New Status in gst-plugins-base1.0 source package in Focal: New Status in gst-plugins-good1.0 source package in Focal: New Status in gstreamer1.0 source package in Focal: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.16 series that 20.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+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 1962568] [NEW] [MIR] libadwaita-1
Public bug reported: [Availability] The package libadwaita-1 is already in Ubuntu universe. The package libadwaita-1 build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libadwaita-1 [Rationale] - The package libadwaita-1 is required in Ubuntu main because gnome-shell depends on it to be able to load extensions which use that library. - The package libadwaita-1 is required in Ubuntu main no later than March 28 which is beta freeze since it's going to block the new gnome-shell version to migrate out of proposed. [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu, it is rather new and has 1 low importance bug reported - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libadwaita-1 - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/587438856/buildlog_ubuntu-jammy-amd64.libadwaita-1_1.1~beta-1_BUILDING.txt.gz - The package runs an autopkgtest, and is currently passing on this list of architectures , https://autopkgtest.ubuntu.com/packages/liba/libadwaita-1 [Quality assurance - packaging] - debian/watch is present and works - This package has no important lintian warnings - Recent log from the debian service, https://lintian.debian.org/sources/libadwaita-1 - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to d/rules https://salsa.debian.org/gnome- team/libadwaita/-/blob/debian/master/debian/rules [UI standards] - Application is end-user facing, Translation is present, via standard gettext [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be Ubuntu Desktop - Team is already subscribed to the package - This does not use static builds - This does not use vendored code [Background information] The Package description explains the package well Upstream Name is libadwaita Link to upstream project https://gitlab.gnome.org/GNOME/libadwaita ** Affects: libadwaita-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/1962568 Title: [MIR] libadwaita-1 Status in libadwaita-1 package in Ubuntu: New Bug description: [Availability] The package libadwaita-1 is already in Ubuntu universe. The package libadwaita-1 build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libadwaita-1 [Rationale] - The package libadwaita-1 is required in Ubuntu main because gnome-shell depends on it to be able to load extensions which use that library. - The package libadwaita-1 is required in Ubuntu main no later than March 28 which is beta freeze since it's going to block the new gnome-shell version to migrate out of proposed. [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu, it is rather new and has 1 low importance bug reported - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libadwaita-1 - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log
[Desktop-packages] [Bug 1962566] Re: gnome-shell crash after resume from suspend in util.js:154
Bug 1960336 and bug 1960387 might be related -- 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/1962566 Title: gnome-shell crash after resume from suspend in util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+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 1962566] Re: gnome-shell crash after resume from suspend in util.js:154
** Package changed: fprintd (Ubuntu) => gnome-shell (Ubuntu) ** Project changed: fprintd => gnome-shell ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- 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/1962566 Title: gnome-shell crash after resume from suspend in util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu3.1~0.21.10.1 --- nvidia-settings (470.57.01-0ubuntu3.1~0.21.10.1) impish; urgency=medium [ Jeremy Szu ] * debian/patches/18_remove_power-saving_if_on-demand.patch, debian/patches/19_lp1957094-adjust-on-demand-mode-description.patch: - Disable the item of power saving mode if on-demand is supported (LP: #1957094). - Leave the item there because the user might issue 'prime-select intel' manually. Thus, leave it there could prevent selection confuse. - Explain the on-demand mode if driver < 450. -- Alberto Milone Tue, 18 Jan 2022 14:25:40 + -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.2.3 --- ubuntu-drivers-common (1:0.9.2.3) impish; urgency=medium * gpu-manager.c: - Fall back from on-demand to on if nvidia < 450 (LP: #1957094). -- Alberto Milone Tue, 18 Jan 2022 09:09:16 + ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: nvidia-settings (Ubuntu Impish) Status: Fix Committed => Fix Released -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1962542] Re: bose quietcomfort 35 unable to connect after suspend
OK the crash is a separate issue. This is https://github.com/bluez/bluez/issues/284 which is also fixed in BlueZ 5.64. ** Bug watch added: github.com/bluez/bluez/issues #284 https://github.com/bluez/bluez/issues/284 ** Bug watch added: github.com/bluez/bluez/issues #284 https://github.com/bluez/bluez/issues/284 ** Changed in: bluez Remote watch: github.com/bluez/bluez/issues #272 => github.com/bluez/bluez/issues #284 ** Changed in: bluez (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** No longer affects: linux (Ubuntu) ** No longer affects: linux-firmware (Ubuntu) ** Tags added: fixed-in-5.64 fixed-upstream -- 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/1962542 Title: bose quietcomfort 35 unable to connect after suspend Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Committed Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device
[Desktop-packages] [Bug 1962563] Re: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_messa
I'll leave this open until we have >=5.64 released and are sure the same crash isn't happening. ** Also affects: bluez via https://github.com/bluez/bluez/issues/272 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1962563 Title: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_message_iter_append_basic() Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.63-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66 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/bluez/+bug/1962563/+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 1962565] Re: gnome-shell occupies a lot of ram and blocks system
attached you can find a screenshot of htop after deleting multiple files. The ram usage does not seem to be dependent of the files deleted (no apparent difference between deleting 200 files totaling 75mb and 500 files totaling 700mb) In this instance there were almost 40 processes of the gnome-shell running "alt+f2" "r" cleared the used ram but did not reduce the number of gnome-shell processes. ** Attachment added: "Screenshot from 2022-03-01 10-54-41.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962565/+attachment/5564430/+files/Screenshot%20from%202022-03-01%2010-54-41.jpg -- 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/1962565 Title: gnome-shell occupies a lot of ram and blocks system Status in gnome-shell package in Ubuntu: New Bug description: sometimes the system uses 11GB of 16GB ram for 10+ gnome-shell processes. It seemingly occurs as soon as deleting files via the file manager. It occurred for me when trying to delete 500 files with a total of 700mb but also when just deleting 200 files totaling around 75mb. A suggested solution to try gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false (bug 1876641, mentioned to me in bug 1962357) did not resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 1 10:52:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-02 (271 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/1962565/+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 1962565] [NEW] gnome-shell occupies a lot of ram and blocks system
Public bug reported: sometimes the system uses 11GB of 16GB ram for 10+ gnome-shell processes. It seemingly occurs as soon as deleting files via the file manager. It occurred for me when trying to delete 500 files with a total of 700mb but also when just deleting 200 files totaling around 75mb. A suggested solution to try gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false (bug 1876641, mentioned to me in bug 1962357) did not resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 1 10:52:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-02 (271 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- 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/1962565 Title: gnome-shell occupies a lot of ram and blocks system Status in gnome-shell package in Ubuntu: New Bug description: sometimes the system uses 11GB of 16GB ram for 10+ gnome-shell processes. It seemingly occurs as soon as deleting files via the file manager. It occurred for me when trying to delete 500 files with a total of 700mb but also when just deleting 200 files totaling around 75mb. A suggested solution to try gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false (bug 1876641, mentioned to me in bug 1962357) did not resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Mar 1 10:52:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-02 (271 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/1962565/+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 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Actually it sounds like https://github.com/bluez/bluez/issues/272 but yours isn't crashing(?) There's mention of QC35 in https://github.com/bluez/bluez/issues/220 too, and that it works after downgrading to BlueZ 5.61. Both seem to be fixed in upstream master (which will be BlueZ 5.64). ** Changed in: bluez (Ubuntu) Status: Invalid => New ** Bug watch added: github.com/bluez/bluez/issues #272 https://github.com/bluez/bluez/issues/272 ** Bug watch added: github.com/bluez/bluez/issues #220 https://github.com/bluez/bluez/issues/220 ** Also affects: bluez via https://github.com/bluez/bluez/issues/272 Importance: Unknown Status: Unknown -- 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/1962542 Title: bose quietcomfort 35 unable to connect after suspend Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09
[Desktop-packages] [Bug 1962563] [NEW] bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_mes
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.63-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: impish jammy -- 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/1962563 Title: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_message_iter_append_basic() Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.63-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66 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/bluez/+bug/1962563/+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 1901446] Re: Add gir1.2-tepl-5 package depedency
** Changed in: gedit (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1901446 Title: Add gir1.2-tepl-5 package depedency Status in gedit package in Ubuntu: Invalid Status in gedit package in Debian: Fix Released Bug description: (This is most likely a bug/request for Debian, but since I use Ubuntu I thought I would report it here first.) gedit in groovy depends on libtepl-5-0. It would be great if the package also depended on gir1.2-tepl-5 so that gedit plugins written in Python can call functions from tepl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1901446/+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 1962542] Re: bose quietcomfort 35 unable to connect after suspend
^^^ That's missing two of your radio devices (the Intel Wifi and Bluetooth), if you compare to comment #17. So it looks like the kernel devices have vanished after resuming from suspend the first time. ** Changed in: bluez (Ubuntu) Status: New => Invalid ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1962542 Title: bose quietcomfort 35 unable to connect after suspend Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
[Desktop-packages] [Bug 1962556] [NEW] [FFe] WSL systemd experimental support
Public bug reported: WSL on Ubuntu 22.04 has a strecth goal to ship systemd experimental support. This relies on 3 changes: - a script started up on WSL VM boot, which is shipped as part of this package to start systemd in its own namespace. - a change in the ubuntu Windows launcher executable, which is then looking for the boot= parameter in wsl.conf and if systemd experimental support is enabled, starts any new commands into that systemd namespace - an option in our OOBE installer, under advanced menu, disabled by default, to change the boot= parameter in wsl.conf. The feature will be labeled as experimental. So, this experimental support won’t be enabled by default and paved the way to have a discussion with Microsoft for potential limitations and how we can get this to a wider audience in the long term. This feature is long-awaited for WSL users. ** Affects: wsl-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wsl-setup in Ubuntu. https://bugs.launchpad.net/bugs/1962556 Title: [FFe] WSL systemd experimental support Status in wsl-setup package in Ubuntu: New Bug description: WSL on Ubuntu 22.04 has a strecth goal to ship systemd experimental support. This relies on 3 changes: - a script started up on WSL VM boot, which is shipped as part of this package to start systemd in its own namespace. - a change in the ubuntu Windows launcher executable, which is then looking for the boot= parameter in wsl.conf and if systemd experimental support is enabled, starts any new commands into that systemd namespace - an option in our OOBE installer, under advanced menu, disabled by default, to change the boot= parameter in wsl.conf. The feature will be labeled as experimental. So, this experimental support won’t be enabled by default and paved the way to have a discussion with Microsoft for potential limitations and how we can get this to a wider audience in the long term. This feature is long-awaited for WSL users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/1962556/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Though on the other hand I don't really want flavours to do offline upgrades, but I don't think we have a clear-cut policy on that. Either way, removing the feature inside PackageKit might break some flavours, so seeing as we are past feature freeze, fixing that in the frontend would be less invasive. ** Also affects: packagekit (Ubuntu) Importance: Undecided Status: New -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962510] Re: failing tests with new sssd, blocks python3-defaults
why removing the package rather than just hinting the test results? -- 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/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1962510] Re: failing tests with new sssd, blocks python3-defaults
why removing the package rather than just hinting the test results? -- 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/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
This is *not* a packagekit issue. There are flavours upgrading using packagekit, not everyone uses update-manager. It's either gnome-shell or gnome-session or something that should not be reacting to this. ** Package changed: packagekit (Ubuntu) => gnome-shell (Ubuntu) -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Fresh install of Lubuntu jammy on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) Post install and using the fresh lubuntu system, opening LibreOffice - HELP - Libreoffice.Help gets `firefox` opened & FILE NOT FOUND - file://tmp/lu23267w8nw8.tmp/NewHelp1.htmp ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists
You have been subscribed to a public bug: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug impish rls-jj-incoming third-party-packages wayland-session -- Ubuntu reboots instead of powering off if a software updates exists https://bugs.launchpad.net/bugs/1962346 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1962542] Re: bose quietcomfort 35 unable to connect after suspend
Also does the 'rfkill' command show any difference in the radio status after resume? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1962542 Title: bose quietcomfort 35 unable to connect after suspend Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device
[Desktop-packages] [Bug 1962542] [NEW] bose quietcomfort 35 unable to connect after suspend
Public bug reported: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:10 fenrir acpid[1503]: input device has been disconnected, fd 19 And then the headset will not connect until the next boot. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1962542 Title: bose quietcomfort 35 unable to connect after suspend Status in bluez package in Ubuntu: New Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii
[Desktop-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
the issue there is that packagekit is proposing offline updates which it shouldn't do on Ubuntu ** Package changed: gnome-shell (Ubuntu) => packagekit (Ubuntu) ** Changed in: packagekit (Ubuntu) Importance: Low => High ** Tags added: rls-jj-incoming -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1962346/+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
