[Desktop-packages] [Bug 2022885] Re: ubuntu-dock unresponsive
Ubuntu dock is unresponsive also when all active apps are minimized. So I minimize an app and then i'm unable to unminimize it clicking on the icon in the dock. -- 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/2022885 Title: ubuntu-dock unresponsive Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2022885/+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 2022889] [NEW] [SRU] libreoffice 7.5.4 for lunar
Public bug reported: [Impact] * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release * Version 7.5.3 is currently released in lunar. For a list of fixed bugs compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14936260/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [riscv64] not available * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.a ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Lunar) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: New ** Also affects: libreoffice (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu Lunar) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Lunar) Importance: Undecided => High -- 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/2022889 Title: [SRU] libreoffice 7.5.4 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: New Bug description: [Impact] * LibreOffice 7.5.4 is in its forth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.4_release * Version 7.5.3 is currently released in lunar. For a list of fixed bugs compared to 7.5.3 see the list of bugs fixed in the release candidates of 7.5.4 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1460/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net
[Desktop-packages] [Bug 2022885] Re: ubuntu-dock unresponsive
attaching journal ** Attachment added: "jo.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2022885/+attachment/5677820/+files/jo.txt -- 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/2022885 Title: ubuntu-dock unresponsive Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2022885/+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 2022885] [NEW] ubuntu-dock unresponsive
Public bug reported: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2022885 Title: ubuntu-dock unresponsive Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2022885/+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 2022883] Re: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/2022883 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Do any of the following bugs describe the bug you're trying to report? #299774 package tex-common 1.11 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Invalid (14 comments) last updated 2017-08-06 view this bug #349469 debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Open (159 comments) last updated 2021-06-13 view this bug #312740 package texlive-base 2007.dfsg.1-2 failed to install/upgrade: exit status 1 - fmtutil-sys failed Open (5 comments) last updated 2014-07-15 view this bug #473444 package tex-common 1.20 failed to install/upgrade: Invalid (3 comments) last updated 2016-09-07 view this bug #228334 package texlive-base 2007-13 failed to install/upgrade: updmap-sys failed Open (8 comments) last updated 2010-11-01 view this bug #554956 package tex-common 2.06 failed to upgrade : The map file `classicovn.map' has not been found at all Fix Released (10 comments) last updated 2011-01-11 view this bug #570046 package texlive-base 2009-7 failed to install/upgrade: Open (8 comments) last updated 2012-09-11 view this bug #581145 tex-common 2.06 doesn't install without texlive-base Fix Released (11 comments) last updated 2012-01-04 view this bug #653411 package tex-common 2.08 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Confirmed (3 comments) last updated 2017-06-26 view this bug #710933 package tex-common 2.06 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Confirmed (3 comments) last updated 2012-05-30 view this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-212.223-generic 4.15.18 Uname: Linux 4.15.0-212-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 Date: Thu Jun 1 07:51:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-10-22 (2051 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.12ubuntu0.2 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2022883/+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 2022883] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: Do any of the following bugs describe the bug you're trying to report? #299774 package tex-common 1.11 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Invalid (14 comments) last updated 2017-08-06 view this bug #349469 debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Open (159 comments) last updated 2021-06-13 view this bug #312740 package texlive-base 2007.dfsg.1-2 failed to install/upgrade: exit status 1 - fmtutil-sys failed Open (5 comments) last updated 2014-07-15 view this bug #473444 package tex-common 1.20 failed to install/upgrade: Invalid (3 comments) last updated 2016-09-07 view this bug #228334 package texlive-base 2007-13 failed to install/upgrade: updmap-sys failed Open (8 comments) last updated 2010-11-01 view this bug #554956 package tex-common 2.06 failed to upgrade : The map file `classicovn.map' has not been found at all Fix Released (10 comments) last updated 2011-01-11 view this bug #570046 package texlive-base 2009-7 failed to install/upgrade: Open (8 comments) last updated 2012-09-11 view this bug #581145 tex-common 2.06 doesn't install without texlive-base Fix Released (11 comments) last updated 2012-01-04 view this bug #653411 package tex-common 2.08 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Confirmed (3 comments) last updated 2017-06-26 view this bug #710933 package tex-common 2.06 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Confirmed (3 comments) last updated 2012-05-30 view this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-212.223-generic 4.15.18 Uname: Linux 4.15.0-212-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.29 Architecture: amd64 Date: Thu Jun 1 07:51:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-10-22 (2051 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.12ubuntu0.2 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/2022883 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Do any of the following bugs describe the bug you're trying to report? #299774 package tex-common 1.11 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Invalid (14 comments) last updated 2017-08-06 view this bug #349469 debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Open (159 comments) last updated 2021-06-13 view this bug #312740 package texlive-base 2007.dfsg.1-2 failed to install/upgrade: exit status 1 - fmtutil-sys failed Open (5 comments) last updated 2014-07-15 view this bug #473444 package tex-common 1.20 failed to install/upgrade: Invalid (3 comments) last updated 2016-09-07 view this bug #228334 package texlive-base 2007-13 failed to install/upgrade: updmap-sys failed Open (8 comments) last updated 2010-11-01 view this bug #554956 package tex-common 2.06 failed to upgrade : The map file `classicovn.map' has not been found at all Fix Released (10 comments) last updated 2011-01-11 view this bug #570046 package texlive-base 2009-7 failed to install/upgrade: Open (8 comments) last updated 2012-09-11 view this bug #581145 tex-common 2.06 doesn't install without texlive-base Fix Released (11 comments) last updated 2012-01-04 view this bug #653411 package tex-common 2.08 failed to install/upgrade: subprocess
[Desktop-packages] [Bug 2022882] [NEW] Lunar - gnome-shell crashes
Public bug reported: Since updating from Kinetic to Lunar my gnome-shell regularly crashes. It happens out of nothing, sorry I cannot give any hint on how to reproduce it :( This is happening ~ 3 to 5 times a day. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:04:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (139 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-10 (25 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar 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/2022882 Title: Lunar - gnome-shell crashes Status in gnome-shell package in Ubuntu: New Bug description: Since updating from Kinetic to Lunar my gnome-shell regularly crashes. It happens out of nothing, sorry I cannot give any hint on how to reproduce it :( This is happening ~ 3 to 5 times a day. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:04:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (139 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-10 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022882/+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 2022881] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022881 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASU
[Desktop-packages] [Bug 2022880] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2022880 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in alsa-driver package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: surfer12877 F wireplumber /dev/snd/controlC1: surfer12877 F wireplumber /dev/snd/controlC0: surfer12877 F wireplumber /dev/snd/seq:surfer12875 F pipewire CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:47:29 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402XV.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402XV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.39 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402XV.301:bd03/23/2023:br5.29:efr0.39:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402XV_GA402XV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402XV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: "ROG Zephyrus G14" dmi.product.name: ROG Zephyrus G14 GA402XV_GA402XV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022880/+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 2022879] [NEW] No sound from Woofer speaker of Asus Zephyrus G14 2023
Public bug reported: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2022879 Title: No sound from Woofer speaker of Asus Zephyrus G14 2023 Status in pipewire package in Ubuntu: New Bug description: On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter speaker. The woofer speaker does not produce any sound at all on either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations 1) ┌─[surfer@M5-RGV]-[~] └──╼ $lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ) 2) ┌─[surfer@M5-RGV]-[~] └──╼ $apt-cache policy pipewire pipewire: Installed: 0.3.65-3 Candidate: 0.3.65-3 Version table: *** 0.3.65-3 500 500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) The Woofer/rear speaker should produce sound 4) Sound only comes from the pair of tweeter speaker ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire 0.3.65-3 Uname: Linux 6.3.5-060305-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jun 5 12:33:02 2023 InstallationDate: Installed on 2023-05-31 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2022879/+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 2018504] Re: cups-browsed is using an excessive amount of CPU
This bug was fixed in the package cups-browsed - 2.0~rc1-0ubuntu2 --- cups-browsed (2.0~rc1-0ubuntu2) mantic; urgency=medium * Fixed handling of failures when creating local print queues. On a failure a global variable was set by the queue creation function running as background thread, to stop the loop for updating the local queues, but the variable was never reset, making no local queue updates done any more for the rest of the life of the daemon, making the daemon falling into a busy loop. Completely done away with the variable. It is actually not needed (LP: #2018504). -- Till Kamppeter Sun, 4 Jun 2023 18:50:57 +0200 ** Changed in: cups-browsed (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU Status in cups-browsed package in Ubuntu: Fix Released Status in cups-browsed source package in Lunar: In Progress Bug description: [ Impact ] One observes that a certain time after booting cups-browsed suddenly starts to occupy a certain percentage or all of one CPU core. This slows down other processes on the system, consumes battery power, causes noise of the CPU fan. It does not require to have any local printers set up on ones machine, but there must be printers available in the local network. A typical trigger for this bug is a sudden disappearing of a printer in the network, for example if a laptop shares a printer and it gets suspended by closing the lid. This way the shared printer most probably disappears without the laptop's Avahi sending out some "disappered" notification. cups-browsed does not recover from the failure, once failed it consumes CPU and stops working, until being restarted, for most with the next boot. The problem got introduced on the transition from cups-browsed 1.x to 2.x (in Ubuntu 23.04). cups-browsed got a multi-threading feature added to be able to create more local queues at a time, especially when there are many printers available in the network.. The bug is in the error handling: If cups-browsed fails to access a remote printer in a sub-thread, it sets a flag to inform the main thread, to stop an update loop. The main thread misses to reset the flag once it has stopped the loop and so any further update loop during the rest of the life of cups-browsed gets stopped immediately, no printers updated at all, and as because of the updates not performed, updates are still needed and so the loop called again immediately, ending up in an infinite busy loop. And these access errors happen especially if a remote printer goes away without any DNS-SD/Avahi notification about it disappearing. So not only CPU load is caused but cups-browsed ceases completely to work. [ Test Plan ] This bug is not easy to reproduce, but at least for everyone who reported it here it occurs again and again. So everyone already suffering it is asked to test the proposed SRU package. To try to reproduce it one ideally takes 2 computers, one running Ubuntu 23.04 with the affected cups-browsed (the client) and one running any Linux and sharing printers by means of CUPS queues, Printer Applications, or the ippeveprinter utility (the server). Some ways to try to trigger the failure on the client: - Suspend the server, either by closing its laptpp lid or by selecting the "Suspend" function in its desktop's menus. - On the server start a Printer Application or ippeveprinter manually (this way no systemd watch dog applies to it). Then hard-kill its process with "kill -9 ...". - If the server is connected to the local network only by wired Ethernet, unplug its Ethernet cable. - If the server is connected to the local network only by Wi-Fi, switch it into flight mode. All these methods should make (a) shared printer(s) on the server go away without getting it properly de-registered from Avahi on the server, and so no notification being broadcasted into the local network. So the client's cups-browsed would not remove the corresponding local print queue and keep maintaining it, sooner or later failing to access the printer and then getting stuck as described above. Anyone who is suffering this bug could also simply install the proposed package and observe and when the CPU load by cups-browsed does not appear again after some days consider the fix as verified. [ Where problems could occur ] The fix does nothing more than removing the mentioned flag, and instead mark the remote printer as disappeared. This way the update loop is not stopped but finishes normally, which is no problem as the remote printers are independent, there is no reason to skip updating printers because one
[Desktop-packages] [Bug 2022864] [NEW] Xorg freeze
Public bug reported: Frequent lockups, not sure if it's related to NVIDIA or not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 12:29:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo RocketLake-S GT1 [UHD Graphics 750] [17aa:32dd] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db] InstallationDate: Installed on 2023-06-01 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 30EF004VUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro nomodeset text SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: M3JKT3AA dmi.board.name: 32DD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305435660291 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrM3JKT3AA:bd03/16/2023:br1.58:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny: dmi.product.family: ThinkStation P350 Tiny dmi.product.name: 30EF004VUS dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny dmi.product.version: ThinkStation P350 Tiny dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze lunar ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2022864 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Frequent lockups, not sure if it's related to NVIDIA or not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64
[Desktop-packages] [Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
** Also affects: cups-browsed (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups-browsed (Ubuntu Lunar) Status: New => In Progress ** Changed in: cups-browsed (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU Status in cups-browsed package in Ubuntu: In Progress Status in cups-browsed source package in Lunar: In Progress Bug description: [ Impact ] One observes that a certain time after booting cups-browsed suddenly starts to occupy a certain percentage or all of one CPU core. This slows down other processes on the system, consumes battery power, causes noise of the CPU fan. It does not require to have any local printers set up on ones machine, but there must be printers available in the local network. A typical trigger for this bug is a sudden disappearing of a printer in the network, for example if a laptop shares a printer and it gets suspended by closing the lid. This way the shared printer most probably disappears without the laptop's Avahi sending out some "disappered" notification. cups-browsed does not recover from the failure, once failed it consumes CPU and stops working, until being restarted, for most with the next boot. The problem got introduced on the transition from cups-browsed 1.x to 2.x (in Ubuntu 23.04). cups-browsed got a multi-threading feature added to be able to create more local queues at a time, especially when there are many printers available in the network.. The bug is in the error handling: If cups-browsed fails to access a remote printer in a sub-thread, it sets a flag to inform the main thread, to stop an update loop. The main thread misses to reset the flag once it has stopped the loop and so any further update loop during the rest of the life of cups-browsed gets stopped immediately, no printers updated at all, and as because of the updates not performed, updates are still needed and so the loop called again immediately, ending up in an infinite busy loop. And these access errors happen especially if a remote printer goes away without any DNS-SD/Avahi notification about it disappearing. So not only CPU load is caused but cups-browsed ceases completely to work. [ Test Plan ] This bug is not easy to reproduce, but at least for everyone who reported it here it occurs again and again. So everyone already suffering it is asked to test the proposed SRU package. To try to reproduce it one ideally takes 2 computers, one running Ubuntu 23.04 with the affected cups-browsed (the client) and one running any Linux and sharing printers by means of CUPS queues, Printer Applications, or the ippeveprinter utility (the server). Some ways to try to trigger the failure on the client: - Suspend the server, either by closing its laptpp lid or by selecting the "Suspend" function in its desktop's menus. - On the server start a Printer Application or ippeveprinter manually (this way no systemd watch dog applies to it). Then hard-kill its process with "kill -9 ...". - If the server is connected to the local network only by wired Ethernet, unplug its Ethernet cable. - If the server is connected to the local network only by Wi-Fi, switch it into flight mode. All these methods should make (a) shared printer(s) on the server go away without getting it properly de-registered from Avahi on the server, and so no notification being broadcasted into the local network. So the client's cups-browsed would not remove the corresponding local print queue and keep maintaining it, sooner or later failing to access the printer and then getting stuck as described above. Anyone who is suffering this bug could also simply install the proposed package and observe and when the CPU load by cups-browsed does not appear again after some days consider the fix as verified. [ Where problems could occur ] The fix does nothing more than removing the mentioned flag, and instead mark the remote printer as disappeared. This way the update loop is not stopped but finishes normally, which is no problem as the remote printers are independent, there is no reason to skip updating printers because one printer failed. After the update loop having completed, in the next update loop the local queue for the faulty printer gets removed, as it is marked as disappeared. If cups-browsed gets notified about a disappeared printer by Avahi, it also marks it as disappeared so that the queue gets removed in the next update loop. So now we do the same with faulty printers, which simply do not answer to an IPP request. As the regular procedure when a remote printer gets shut down works correctly we
[Desktop-packages] [Bug 2022858] [NEW] gnome-shell-extension-desktop-icons-ng unresponsive
Public bug reported: after closing firefox gnome-shell-extension-desktop-icons-ng becomes unresponsive click on any icon in the dock has no effect. Alt+f2 allows commands, also click on icon in desktop works. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 17:50:24 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2022858 Title: gnome-shell-extension-desktop-icons-ng unresponsive Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: after closing firefox gnome-shell-extension-desktop-icons-ng becomes unresponsive click on any icon in the dock has no effect. Alt+f2 allows commands, also click on icon in desktop works. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-desktop-icons-ng 46+really47.0.2-3 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 17:50:24 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-desktop-icons-ng 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-desktop-icons-ng/+bug/2022858/+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 2020806] Re: Move to trash: file icon moved, not removed
Also, when moving multiple files to a different folder, some icons are moved but some stay behind in the source folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2020806 Title: Move to trash: file icon moved, not removed Status in nautilus package in Ubuntu: Confirmed Bug description: Click on file icon on nautilus window, select 'move to trash' the file is moved to trash but the icon does not disappear, but is just moved in the window. see attached screencast. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 25 19:16:31 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(861, 761)' InstallationDate: Installed on 2023-05-21 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020806/+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 2022851] [NEW] Inappropriate files display
Public bug reported: When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2022851 Title: Inappropriate files display Status in nautilus package in Ubuntu: New Bug description: When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022851/+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 2022849] [NEW] Nautilus UI glitch during file operation
Public bug reported: ~$ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 ~$ apt-cache policy nautilus nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://in.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status Package Details: nautilus/lunar,now 1:44.0-1ubuntu2 amd64 During any file/folder GUI (copy/move/paste/create/delete) operations, the active items overrides the previous item, (observed in both Grid and list views) Steps to reproduce: 1. Open any directory with lots of files and folders. 2. Perform a delete operation. The file gets deleted but its icon overrides on other files, creating some confusion Only after performing reload the file goes away, ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: lunar nautilus ** Attachment added: "uiglitch.mp4" https://bugs.launchpad.net/bugs/2022849/+attachment/5677688/+files/uiglitch.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2022849 Title: Nautilus UI glitch during file operation Status in nautilus package in Ubuntu: New Bug description: ~$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 ~$ apt-cache policy nautilus nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://in.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status Package Details: nautilus/lunar,now 1:44.0-1ubuntu2 amd64 During any file/folder GUI (copy/move/paste/create/delete) operations, the active items overrides the previous item, (observed in both Grid and list views) Steps to reproduce: 1. Open any directory with lots of files and folders. 2. Perform a delete operation. The file gets deleted but its icon overrides on other files, creating some confusion Only after performing reload the file goes away, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022849/+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 2020225] Re: Update mutter to 44.1
Confirmed that after install of libmutter-12-0 v44.1-0ubuntu1 from lunar-proposed on ubuntu budgie no additional regressions were noted. Tested standard stuff like window switching/max/min, tiling etc. Independently team member Jacob has also confirmed that the same version does not additionally impacted his setup Note - I tried to reproduce the artefact issue Andreas noted above with google chrome on ubuntu budgie + this new version but was unable to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+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
