[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
After upgrading to the last version of the packages: gnome-shell41.3-1ubuntu1 mutter-common 41.3-1ubuntu1 the issue is gone and I can see the option when right-clicking on a desktop launcher. ** Changed in: oem-priority Status: New => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: Invalid Status in gnome-shell package in Ubuntu: Invalid Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
Please try: * Updating the system (mutter and gnome-shell should be version 41 now). * Adding kernel parameter: nvidia-drm.modeset=1 * nvidia-495 instead of nvidia-470. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1877038]
https://github.com/mozilla/authenticator-rs/pull/157 is merged to https://github.com/mozilla/authenticator-rs/tree/ctap2-2021 branch now. I hope it can be included in Firefox Nightly test, I'm glad to test it! -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1877038]
I'd also love to see this get added — I'd love to use passwordless auth, but I'm not going to implement it if it's not supported by the main browser I use. Looks like https://github.com/mozilla/authenticator- rs/pull/157 just got approved a few days ago, so hopefully things are moving? Thanks for working on this! -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Attachment added: "lspci-k.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557896/+files/lspci-k.log -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Attachment added: "journalctl_lastboot.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959362/+attachment/5557897/+files/journalctl_lastboot.log -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1959363] [NEW] Update to libXfixes 6.x
Public bug reported: Update to libXfixes 6.x https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags It is a prerequisite to build mutter 42. ** Affects: libxfixes (Ubuntu) Importance: Undecided Status: New ** Tags: jammy needs-packaging ** Tags added: needs-packaging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfixes in Ubuntu. https://bugs.launchpad.net/bugs/1959363 Title: Update to libXfixes 6.x Status in libxfixes package in Ubuntu: New Bug description: Update to libXfixes 6.x https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags It is a prerequisite to build mutter 42. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1959363/+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 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Tags added: oem-priority -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+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 1959362] [NEW] "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
Public bug reported: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority third-party-packages -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 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-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28
[Desktop-packages] [Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
** Description changed: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . - The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass + The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] Some 4G/5G mobile networks(for ex., AT) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current network-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT SIM card in US 2. Enable 4G modem and connect to AT apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
Yes the kernel graphics driver provides the path to the monitor audio device so that might be it. Although history makes me suspect PulseAudio more. ** Tags added: amdgpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1959340] Re: frequent color snowing on screen after resuming from suspend
*** This bug is a duplicate of bug 1958591 *** https://bugs.launchpad.net/bugs/1958591 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 1958412, 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: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** This bug has been marked a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug is no longer a duplicate of bug 1958412 [amdgpu] Flickering/noise on screen started in kernel 5.13 ** This bug has been marked a duplicate of bug 1958591 [amdgpu] Random noise 'static' display after internal display turned off/on -- 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/1959340 Title: frequent color snowing on screen after resuming from suspend Status in linux-hwe-5.13 package in Ubuntu: New Bug description: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1959340/+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 1959340] Re: frequent color snowing on screen after resuming from suspend
** Package changed: ubuntu => xorg (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/1959340 Title: frequent color snowing on screen after resuming from suspend Status in xorg package in Ubuntu: New Bug description: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1959340/+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 1959340] [NEW] frequent color snowing on screen after resuming from suspend
You have been subscribed to a public bug: For the last 2 days my Thinkpad X13 laptop frequently opens with snowing pixels across the whole screen. The only way to stop it seems to be to hard-reset my laptop. $ uname -a Linux X13 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:56:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-09-23 (126 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20UF0014US ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=8e981ab2-e4f0-4607-b2c4-587a6db04c7d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.35 dmi.modalias: dmi:bvnLENOVO:bvrR1CET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- frequent color snowing on screen after resuming from suspend https://bugs.launchpad.net/bugs/1959340 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1953052] Re: In Jammy sound level reset after reboot
It's a bit weird, trying in a VM in a simple wmaker session, changing the level in pavucontrol and restarting the machine the sound is correctly restored on the same position after the restart so the systemd unit seems to be working as expected. Could someone having the issue change the level, restart, check that the level is indeed wrong and if it is get a log from the previous session with 'journalctl -b 1 > log' and add the log file to the report? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
[Desktop-packages] [Bug 1958094] Re: cups-filters should not recommend lynx since it's in universe
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1958094 ** Changed in: cups-filters (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1958094 Title: cups-filters should not recommend lynx since it's in universe Status in cups-filters package in Ubuntu: Fix Released Bug description: cups-filters 1.28.11-1 now recommends lynx for a braille convert to HTML feature. lynx is in universe and it's not allowed for packages in main to recommend packages in universe. Suggestions --- 1. We could just lower it to a Suggests since this might not be a feature we need to enable by default. (You can look at the file-roller for an example of how to tweak dependencies for Ubuntu but still keep the packaging in sync with Debian) 2. If it is acceptable to install w3m by default, maybe this feature could be updated to use w3m instead. This may be worth doing even if we lower the dependency to a Suggests. I suggest reaching out to the Debian Accessibility Team member Samuel Thibault since it looks like this is his code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1958094/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
Is there anything specific to the setup you are using? There is a report upstream about gateway issue with openssl3, https://github.com/FreeRDP/FreeRDP/issues/7449 I don't have a win8 to test but connecting to a standard win10 pro desktop works without issue using the current freerdp package (even before the recent patches) It might be worth reporting the issue on github directly, they probably would have a better understanding of the issue than we do here without an active maintainer for that stack in Ubuntu ** Changed in: freerdp2 (Ubuntu) Status: Incomplete => New ** Bug watch added: freerdp-issues #7449 https://github.com/FreeRDP/FreeRDP/issues/7449 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: New Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
I just tested it on a laptop with intel graphics, and sound and playback is perfectly normal on 60Hz when playing through the HDMI (playing on the television). Same cable, same television - only connected to my laptop instead. This makes me wonder whether this could be an issue in the kernel driver, amdgpu? Hardware: CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz GPU: Intel(R) HD Graphics 4400 (HSW GT2) OS: Ubuntu 21.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in pulseaudio package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1861250] Re: Apparmor error failed to start profiles
Looks like the profile for cups-browsed has a syntax error. (Did you change something in the profile, or is it the original profile as shipped in the package?) Also, AFAIK this profile is shipped with the cups package, therefore I'm adding that package. ** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: Confirmed Status in cups package in Ubuntu: New Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+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 1959015] Re: Switch to new HTTPS-capable domains for PPAs
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1959015 Title: Switch to new HTTPS-capable domains for PPAs Status in software-properties package in Ubuntu: New Status in software-properties source package in Jammy: New Bug description: As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04. The changes are: * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// works too, but we should prefer https://) * https://private-ppa.launchpad.net/ → https://private-ppa.launchpadcontent.net/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+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 problem is affecting my laptop. It gets to the point where the system starts thrashing so badly I care barely get to the console and log in to start killing processes. Ubuntu 20.04 gnome-shell 3.36.9-0ubuntu0.20.04.2 $ uname -a Linux cherna 5.4.0-96-generic #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Just now: $ pidstat -l -r|egrep 'UID|/usr/bin/gnome-shell' 10:34:32 AM UID PID minflt/s majflt/s VSZ RSS %MEM Command 10:34:32 AM 1000 3659 83.54 0.15 7330020 1768040 11.13 /usr/bin/gnome-shell It happens around once a week depending on my usage of the laptop which is my work laptop tat stays on almost all the time. I don't see a pattern to it yet. At least I can ALT-F2 & "r" to recover some RAM. If I notice the problem in time -- 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 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
the definition of the serie we want to use is a manual process, it has been updated now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: Triaged Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+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 1927100] Re: Slow file dialogs, open and save
I haven't seen the issue occur in an (idle) Ubuntu Mate VM after a week or so. To be fair, I can't reproduce it in a clean Mint VM either. There's a user in the Mint/Nemo issue tracker that was seeing the issue using Ubuntu+Cinnamon, but they've since upgraded to 21.10 (with newer gvfs) and are no longer affected. Not sure this will be verifiable without a user to test in their active/natural install--I can reproduce it readily on my workstation, but I'm really not sure which aspect of my setup/usage makes it occur. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Focal: Incomplete Bug description: [Description/Impact] glib GFileMonitors can cause deadlocks if not explicitly cancelled before unref-ing (as of Dec 2021; see https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ dialogs system-wide. The best userspace workaround is explicitly pkill-ing gvfsd-trash at a sometimes frequent interval. This issue was reported and fixed in gvfs issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340 merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 [Test Case] To my knowledge, there is not a 100% reproducer for gvfs from userspace as this is a probable lock-ordering issue in lower-level code. https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the underlying glib issue. User reports of gvfsd-trash manifesting this deadlock exist for Focal and Focal-based distributions, and it has been acknowledged and worked-around in gvfs. See: https://forums.linuxmint.com/viewtopic.php?f=47=328966 (Linux Mint forums) https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file manager) https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes diagnosis and stacktrace showing the gvfsd-trash thread) The code change patched-in here has propagated to various other projects. See: https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313 https://github.com/fwupd/fwupd/issues/2350 [Regression Potential] This patch explicitly cancels GFileMonitors before "unreferencing" them to workaround a known glib issue. Absent any currently-unknown issues with the GFileMonitor framework, code added by this patch should be entirely within valid usage of GFileMonitors, is already present in gvfs releases in wide distribution, and, at worst, should become superfluous if/when the underlying glib issue is fixed. In the event that gvfsd-trash had some (currently unknown) mismanagement of its file watchers, it's possible that attempting to cancel an invalid monitor might behave differently than unref-ing it (which was already happening), but, this scenario would likely be bad either way. [Original Description] On Ubuntu Mate 20.04. Sometime the Open and Save dialogs in GTK applications will over 20 seconds to display. I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which suggested this due to gvfsd-trash, and running `killall gvfsd-trash` which does temporary solve the problem. The issue is apparently fixed in gvfs 1.46.2 Please could 1.46.2 or the fix https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+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 1769496] Re: Onscreen keyboard bug - shift don't work
** Summary changed: - Onscreen keuboard bug - shift don't work + Onscreen keyboard bug - shift don't work ** Summary changed: - Onscreen keyboard bug - shift don't work + Onscreen keyboard bug - shift doesn't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1769496 Title: Onscreen keyboard bug - shift doesn't work Status in onboard package in Ubuntu: Confirmed Bug description: Onscreen keyboard bugs: 1. Uppercase don't work. 2. Special characters is changing to digits or another special characters, for example: "@" produce "2" "&" produce "7" "+" produce "=". It seems like shift don't work. I use polis language. In 17.04 version it works perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 6 20:28:36 2018 InstallationDate: Installed on 2017-12-02 (155 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1769496/+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 1769496] Re: Onscreen keuboard bug - shift don't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: onboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1769496 Title: Onscreen keyboard bug - shift doesn't work Status in onboard package in Ubuntu: Confirmed Bug description: Onscreen keyboard bugs: 1. Uppercase don't work. 2. Special characters is changing to digits or another special characters, for example: "@" produce "2" "&" produce "7" "+" produce "=". It seems like shift don't work. I use polis language. In 17.04 version it works perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 6 20:28:36 2018 InstallationDate: Installed on 2017-12-02 (155 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1769496/+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 1755983] Re: Onboard always produces lowercase letters regardless of shift
*** This bug is a duplicate of bug 1769496 *** https://bugs.launchpad.net/bugs/1769496 ** This bug has been marked a duplicate of bug 1769496 Onscreen keuboard bug - shift don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1755983 Title: Onboard always produces lowercase letters regardless of shift Status in onboard package in Ubuntu: New Bug description: Onboard 1.4.1-2ubuntu1 Running ubuntu 18.04 Bionic Beaver development branch Onboard always produces lowercase letters regardless of onboard shift button. Regardless of whether the letters are displayed as uppercase or lowercase on the onboard keyboard button faces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755983/+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 1951534] Re: Got /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.Layout
*** This bug is a duplicate of bug 1948723 ***
https://bugs.launchpad.net/bugs/1948723
** This bug has been marked a duplicate of bug 1948723
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1951534
Title:
Got /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
SyntaxWarning: 'str' object is not callable; perhaps you missed a
comma? raise Exceptions.LayoutFileError("Unrecognized modifier %s
in" \ during reinstallation
Status in onboard package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 22.04 LTS
2. Try to install or reinstall onboard with
sudo apt-get install --reinstall onboard
Expected results:
* onboard is reinstalled without errors or warnings
Actual results:
* onboard raises an exception during installation
Setting up onboard (1.4.1-5build4) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
Please fix this bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: onboard 1.4.1-5build4
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Nov 19 10:01:43 2021
InstallationDate: Installed on 2021-10-14 (35 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: onboard
UpgradeStatus: Upgraded to jammy on 2021-10-26 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1951534/+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 1948723] Re: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.LayoutFile
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: onboard (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1948723
Title:
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
SyntaxWarning: 'str' object is not callable; perhaps you missed a
comma? raise Exceptions.LayoutFileError("Unrecognized modifier %s
in" \
Status in Onboard:
New
Status in onboard package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. Install or reinstall Onboard with
sudo apt-get install --reinstall onboard onboard-common onboard-
data
Expected results:
* no warnings
Actual results:
* the following warning is shown -
```
$ sudo apt-get install --reinstall onboard onboard-common onboard-data
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
Need to get 5 217 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-common
all 1.4.1-5build4 [595 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard amd64
1.4.1-5build4 [380 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-data all
1.4.1-5build4 [4 242 kB]
Fetched 5 217 kB in 2s (2 938 kB/s)
(Reading database ... 243599 files and directories currently installed.)
Preparing to unpack .../onboard-common_1.4.1-5build4_all.deb ...
Unpacking onboard-common (1.4.1-5build4) over (1.4.1-5build4) ...
Preparing to unpack .../onboard_1.4.1-5build4_amd64.deb ...
Unpacking onboard (1.4.1-5build4) over (1.4.1-5build4) ...
Preparing to unpack .../onboard-data_1.4.1-5build4_all.deb ...
Unpacking onboard-data (1.4.1-5build4) over (1.4.1-5build4) ...
Setting up onboard-common (1.4.1-5build4) ...
Setting up onboard (1.4.1-5build4) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
Processing triggers for mailcap (3.70ubuntu1) ...
Processing triggers for bamfdaemon (0.5.5+21.10.20210710-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.26-1ubuntu2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu2) ...
Processing triggers for libglib2.0-0:amd64 (2.68.4-1ubuntu1) ...
Processing triggers for man-db (2.9.4-2build1) ...
Setting up onboard-data (1.4.1-5build4) ...
```
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: onboard 1.4.1-5build4
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Tue Oct 26 01:08:47 2021
InstallationDate: Installed on 2021-10-24 (1 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211024)
SourcePackage: onboard
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1948723/+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 1959223] [NEW] can't connect to XDMCP server with default settings, while Xephyr connects normally
Public bug reported: Steps to reproduce: 1. Configure XDMCP server by adding three lines [XDMCPServer] enabled=true port=177 into /etc/lightdm/lightdm.conf . Then reboot it. 2. On client (18.04 LTS or newer) install remmina-plugin-xdmcp package. 3. Open Remmina, click +, select XDMCP, provide IP address or hostname Expected results: * connection is successful Actual results: * connection failed, below is the terminal output $ remmina Load modules from /usr/lib/x86_64-linux-gnu/remmina/plugins Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. The glibsecret secret plugin has been initialized and it will be your default secret plugin StatusNotifier/Appindicator support: your desktop does support it and libappindicator is compiled in Remmina. Good. (org.remmina.Remmina:3492): Gtk-WARNING **: 18:00:24.372: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem text: def: (null) text: (null) def: (null) text: 2600 (Windows XP), 7601 (Windows Vista/7), 9600 (Windows 8 and newer) def: (null) text: (null) def: (null) (EE) Fatal server error: (EE) X11 error Error code: 8 Sequence number: 5 Major code: 1 Minor code: 0 Error value: 60825008 (EE) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: remmina-plugin-xdmcp 1.4.11+dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Jan 27 18:00:54 2022 InstallationDate: Installed on 2022-01-02 (25 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic focal hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1959223 Title: can't connect to XDMCP server with default settings, while Xephyr connects normally Status in remmina package in Ubuntu: New Bug description: Steps to reproduce: 1. Configure XDMCP server by adding three lines [XDMCPServer] enabled=true port=177 into /etc/lightdm/lightdm.conf . Then reboot it. 2. On client (18.04 LTS or newer) install remmina-plugin-xdmcp package. 3. Open Remmina, click +, select XDMCP, provide IP address or hostname Expected results: * connection is successful Actual results: * connection failed, below is the terminal output $ remmina Load modules from /usr/lib/x86_64-linux-gnu/remmina/plugins Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. The glibsecret secret plugin has been initialized and it will be your default secret plugin StatusNotifier/Appindicator support: your desktop does support it and libappindicator is compiled in Remmina. Good. (org.remmina.Remmina:3492): Gtk-WARNING **: 18:00:24.372: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem text: def: (null) text: (null) def: (null) text: 2600 (Windows XP), 7601 (Windows Vista/7), 9600 (Windows 8 and newer) def: (null) text: (null) def: (null) (EE) Fatal server error: (EE) X11 error Error code: 8 Sequence number: 5 Major code: 1 Minor code: 0 Error value: 60825008 (EE) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: remmina-plugin-xdmcp 1.4.11+dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Jan 27 18:00:54 2022 InstallationDate: Installed on 2022-01-02 (25 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1959223/+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 1952107] Re: Google Contacts API Deprecated
Same here. 3.36.5-0ubuntu2 in focal. "Connecting to address book failed: Unauthorized" ** Attachment added: "Screenshot from 2021-10-17 08-18-38.png" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1952107/+attachment/5557805/+files/Screenshot%20from%202021-10-17%2008-18-38.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1574354] Re: playing .mp4 in VLC freezes machine
Toimii nykyisin. Works now. Thanks. Juha to 27. tammik. 2022 klo 15.35 Timo Aaltonen (1574...@bugs.launchpad.net) kirjoitti: > vlc works just fine on several machines here, closing > > if you have further issues, open a new bug > > ** Changed in: mesa (Ubuntu) >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1574354 > > Title: > playing .mp4 in VLC freezes machine > > Status in mesa package in Ubuntu: > Invalid > > Bug description: > VLC was running fine on 15.10 but since upgrading, video files (e.g. > .mp4) play for a few minutes and then crash the whole machine (i.e. I > have to power off and on). Possibly linked is that audio (in web pages > or playing audio files thru Banshee) loops (stutters) for about a > second every few minutes (but doesn't crash the machine). > > vlc-nox: /usr/bin/vlc > > Description: Ubuntu 16.04 LTS > Release: 16.04 > > vlc: > Installed: 2.2.2-5 > Candidate: 2.2.2-5 > Version table: >*** 2.2.2-5 500 > 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: vlc 2.2.2-5 > ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 > Uname: Linux 4.4.0-21-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sun Apr 24 19:20:41 2016 > InstallationDate: Installed on 2014-02-17 (797 days ago) > InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 > (20131016.1) > ProcEnviron: >LANGUAGE=en_GB:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_GB.UTF-8 >SHELL=/bin/bash > SourcePackage: vlc > UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+subscriptions > > -- --J.K-- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Invalid Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1959179] Re: Video driver not working properly
Got it thanks a lot. On Thu, 27 Jan, 2022, 1:35 pm Daniel van Vugt, <1959...@bugs.launchpad.net> wrote: > Thanks for the bug report. > > There is no backlight control for desktops with external monitors. > Although in Xorg sessions you can use this to simulate it: > > xrandr --output NAME --brightness VALUE > > Also "the screen has pathches" sounds like bug 1867668. You need to > remove the old 'intel' driver and use the newer default 'modesetting' > driver instead. > > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) > > ** Changed in: xserver-xorg-video-intel (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1959179 > > Title: > Video driver not working properly > > Status in xserver-xorg-video-intel package in Ubuntu: > Invalid > > Bug description: > I cant change the brightness and after each start the screen has > pathches. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-27-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Jan 27 13:09:47 2022 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8694] > InstallationDate: Installed on 2022-01-18 (8 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 > (20210819) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 >Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M >|__ Port 3: Dev 2, If 0, Class=Human Interface Device, > Driver=usbhid, 1.5M >|__ Port 4: Dev 3, If 1, Class=Human Interface Device, > Driver=usbhid, 1.5M >|__ Port 4: Dev 3, If 0, Class=Human Interface Device, > Driver=usbhid, 1.5M > MachineType: ASUS System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic > root=UUID=1fb62a44-b30c-40e9-a7f2-507dd6b4d6f7 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/12/2021 > dmi.bios.release: 10.17 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1017 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME H510M-E > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH510M-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: ASUS > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.105-3~20.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1959179/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1959179 Title: Video driver not working properly Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: I cant change the brightness and after each start the screen has pathches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux
[Desktop-packages] [Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
looks like it's still unresolved upstream ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig Status in mesa package in Ubuntu: Confirmed Bug description: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+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 1574354] Re: playing .mp4 in VLC freezes machine
vlc works just fine on several machines here, closing if you have further issues, open a new bug ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Invalid Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1959206] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 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 #1946165, 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/1959206/+attachment/5557758/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557760/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557764/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557765/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557766/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557767/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1959206/+attachment/5557768/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1959206 Title: gjs-console assert failure: free(): invalid pointer Status in gjs package in Ubuntu: New Bug description: After disable show overview on startup dash to panel settings ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gjs 1.70.0-4 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AssertionMessage: free(): invalid pointer CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 14:51:04 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-01-27 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220127) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions Signal: 6 SourcePackage: gjs StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f46aaa3413d "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f46aaa31d86 "free(): invalid pointer") at malloc.c:5543 _int_free (av=, p=, have_lock=0) at malloc.c:4326 __GI___libc_free (mem=) at malloc.c:3278 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gjs-console assert failure: free(): invalid pointer 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/gjs/+bug/1959206/+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 1952107] Re: Google Contacts API Deprecated
The same here. Upgraded to 3.36.5-0ubuntu2 in focal. When starting Evolution I get "Connecting to address book failed: Unauthorized". Pressing button [Reconnect] clears the message but Address book is empty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 889889] Re: Use PNG or SVG instead of GIF
Marking the charset task as invalid - 4.0.0 does not appear to have any gif files. ** Changed in: chardet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/889889 Title: Use PNG or SVG instead of GIF Status in Adium Theme Ubuntu: Fix Released Status in OpenSSL: New Status in ace package in Ubuntu: New Status in app-install-data-ubuntu package in Ubuntu: Confirmed Status in blender package in Ubuntu: Fix Released Status in chardet package in Ubuntu: Invalid Status in cups package in Ubuntu: New Status in dvd+rw-tools package in Ubuntu: New Status in foo2zjs package in Ubuntu: New Status in libcgi-pm-perl package in Ubuntu: New Status in openssl package in Ubuntu: Won't Fix Status in python3.4 package in Ubuntu: Won't Fix Status in software-center package in Ubuntu: Invalid Bug description: Use modern file formats such as PNG or SVG instead of the legacy GIF file formats. $ find /usr -name "*.gif" To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/889889/+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 1959179] Re: Video driver not working properly
Thanks for the bug report. There is no backlight control for desktops with external monitors. Although in Xorg sessions you can use this to simulate it: xrandr --output NAME --brightness VALUE Also "the screen has pathches" sounds like bug 1867668. You need to remove the old 'intel' driver and use the newer default 'modesetting' driver instead. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid -- 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/1959179 Title: Video driver not working properly Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: I cant change the brightness and after each start the screen has pathches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 13:09:47 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2022-01-18 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=1fb62a44-b30c-40e9-a7f2-507dd6b4d6f7 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: PRIME H510M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH510M-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1959179/+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
