[Desktop-packages] [Bug 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd
** Changed in: jackd2 (Ubuntu) Importance: Undecided => High ** Changed in: jackd2 (Ubuntu) Status: Confirmed => Triaged ** Changed in: jackd2 (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: Triaged Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not have this problem. jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1937072] Re: [Ice Lake] Incomplete screen redraws
It looks like this might be a Panel Self Refresh bug. PSR was disabled in Ubuntu 20.04 but seems to be enabled (sometimes) in newer Ubuntu releases. So please try disabling it by adding a kernel parameter: i915.enable_psr=0 ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] Re: [Ice Lake] Incomplete screen redraws
This post seems to confirm your model of laptop has issues with PSR on Linux: https://www.reddit.com/r/archlinux/comments/jzhwmv/graphical_glitches_on_arch_running_kde_520_on_new/ so the workaround should be: i915.enable_psr=0 But please confirm. ** Summary changed: - [Ice Lake] Incomplete screen redraws + [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Lenovo Yoga Slim 7 14IIL05] Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd
Reported upstream: https://github.com/jackaudio/jack2/issues/776 ** Bug watch added: github.com/jackaudio/jack2/issues #776 https://github.com/jackaudio/jack2/issues/776 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: Confirmed Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not have this problem. jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
The WWAN test is passed on Lenovo ThinkPad L460 https://certification.canonical.com/hardware/201601-20490/submission/223615/ https://certification.canonical.com/hardware/201601-20490/submission/223629/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2
[Desktop-packages] [Bug 1937127] Re: Gnome-shell animations smoother when external monitor is connected
Using 'Ubuntu on Xorg' instead of 'Ubuntu' also helps. Because the former having more layers and less internal blocking actually dabbles in triple buffering sometimes by accident. Although I'm not sure if that's the reason it's smoother or just Xorg adds extra GPU load. Since the default 'Ubuntu' session in 20.04 was Xorg and in 21.04 onward it is Wayland, that would explain a perceived performance drop that some users may notice. -- 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/1937127 Title: Gnome-shell animations smoother when external monitor is connected Status in gnome-shell package in Ubuntu: In Progress Bug description: When no external monitor is connected Gnome Shell activities animation is sluggish. Once an external monitor is connected the animation becomes noticeably smoother. It looks like the OS is not properly responding to the extra processing demands by raising the CPU/GPU performance, and having an external monitor connected somehow triggers a higher performance level. This is on a System76 Darter Pro machine with Intel® Core™ i7-8565U and Intel UHD 620 running Ubuntu 21.04 in Wayland session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-7620.21~1624379747~21.04~3abeff8~dev-generic 5.11.21 Uname: Linux 5.11.0-7620-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 12:51:55 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-14 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937127/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd
** Description changed: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. - This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this + This is specific to jackd2 1.9.19, jackd 1.9.17 does not have this problem. - jackd 1.9.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does + jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: Confirmed Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.9.19, jackd 1.9.17 does not have this problem. jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: jackd2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: Confirmed Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this problem. jackd 1.9.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1937325] Re: Jack clients have segmentation fault when trying to connect to jackd
** Description changed: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this problem. - jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.1.19 on 21.10 does + jackd 1.9.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: Confirmed Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this problem. jackd 1.9.19 on ubuntu 20.04 does work but jackd 1.9.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1937321] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1937321 Title: System freeze Status in Ubuntu: Incomplete Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+bug/1937321/+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 1937072] Re: Incomplete screen redraws
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Summary changed: - Incomplete screen redraws + [Ice Lake] Incomplete screen redraws -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: [Ice Lake] Incomplete screen redraws Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937127] Re: Gnome-shell animations smoother when external monitor is connected
The issue has always existed. But with such a sharp edge between smooth and stuttering any slightest change in the GUI can push it over the edge. Also a little annoyingly, as we optimize more code it can sometimes make the problem *worse* as the GPU becomes less loaded and less likely to up-clock to smoothness. Triple buffering is really the only solution that works with all drivers. Although sometimes you can tweak the graphics driver to change its clock scaling behaviour, I don't know if there's a more elegant workaround possible for Intel. -- 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/1937127 Title: Gnome-shell animations smoother when external monitor is connected Status in gnome-shell package in Ubuntu: In Progress Bug description: When no external monitor is connected Gnome Shell activities animation is sluggish. Once an external monitor is connected the animation becomes noticeably smoother. It looks like the OS is not properly responding to the extra processing demands by raising the CPU/GPU performance, and having an external monitor connected somehow triggers a higher performance level. This is on a System76 Darter Pro machine with Intel® Core™ i7-8565U and Intel UHD 620 running Ubuntu 21.04 in Wayland session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-7620.21~1624379747~21.04~3abeff8~dev-generic 5.11.21 Uname: Linux 5.11.0-7620-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 12:51:55 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-14 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937127/+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 1937325] [NEW] Jack clients have segmentation fault when trying to connect to jackd
Public bug reported: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this problem. jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.1.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1937325 Title: Jack clients have segmentation fault when trying to connect to jackd Status in jackd2 package in Ubuntu: New Bug description: Steps to show this bug. Start jackd either as jackd or jackdbus (with jack_control). run jack_lsp from the command line to show jackd's port. Jack_lsp will segfault. Other jack clients will have similar problems. This is specific to jackd2 1.1.19, jackd 1.1.17 does not have this problem. jackd 1.1.19 on ubuntu 20.04 does work but jackd 1.1.19 on 21.10 does not. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: jackd2 1.9.19~dfsg~ubuntu-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21 Uname: Linux 5.11.0-20-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jul 22 18:09:18 2021 InstallationDate: Installed on 2021-06-15 (37 days ago) InstallationMedia: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210613) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1937325/+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 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start
This bug was fixed in the package glib2.0 - 2.64.6-1~ubuntu20.04.4
---
glib2.0 (2.64.6-1~ubuntu20.04.4) focal; urgency=medium
* Initialise memory used for file builder buffers to zero, since memory
artifacts found themseleves into gschema.compiled files, leading to glib
being unable to parse the gschema.compiled files, causing gdm, gnome-shell
and various gnome applications to fail to
start. (LP: #1930359)
- d/p/gvdb-builder-Initialise-some-memory-to-zero-in-the-bloom-.patch
-- Matthew Ruffell Mon, 12 Jul 2021
15:56:16 +0100
** Changed in: glib2.0 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
Title:
glib2.0: Uninitialised memory is written to gschema.compiled, failure
to parse this file leads to gdm, gnome-shell failing to start
Status in GLib:
Unknown
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Focal:
Fix Released
Bug description:
[Impact]
A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
user with 300 VDIs running Focal, where GNOME applications would fail
to start, and if you reboot, gdm and gnome-shell both fail to start,
and you are left with a black screen and a blinking cursor.
After much investigation, mutter was not at fault. Instead, mutter-
common calls the libglib2.0-0 hook on upgrade:
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
...
This in turn calls glib-compile-schemas to recompile the gsettings
gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
result is a binary gschemas.compiled file, which is loaded by
libglib2.0 on every invocation of a GNOME application, or gdm or
gnome-shell to fetch application default settings.
Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
deterministic behaviour when calling glib-compile-schemas, causing
generated gschemas.compiled files to have differing contents on each
run:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 D0
3771 A4 DB
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 68
3771 A4 30
3772 55 56
The bytes on the left are from a corrupted gschemas.compiled provided
by an affected user. The changing bytes on the right are non-
deterministic.
I ran valgrind over glib-compile-schemas, and found that we are
writing to uninitialised memory.
https://paste.ubuntu.com/p/hvZccwdzxz/
What is happening is that a submodule of glib, gvdb, contains the
logic for serialising the gschema data structures, and when it
allocates a buffer to store the eventual gschemas.compiled file, it
does not initialise it.
When we populate the fields in the buffer, some bytes are never
overwritten, and these junk bytes find themselves written to
gschemas.compiled.
On boot, when gdm and gnome-shell attempt to parse and load this
corrupted gschemas.compiled file, it can't parse the junk bytes, and
raises and error, which propagates up to a breakpoint in glib logging,
but no debugger is present, so the kernel traps the breakpoint, and
terminates the library, and the calling application, e.g. gdm.
The result is that the user is left starting at a black screen with a
blinking pointer.
[Testcase]
On a Focal system, simply run valgrind over glib-compile-schemas:
# valgrind glib-compile-schemas /usr/share/glib-2.0/schemas
You will get output like this, with the warning "Syscall param
write(buf) points to uninitialised byte(s)":
https://paste.ubuntu.com/p/hvZccwdzxz/
If you happen to have a large amount of gschema overrides present on
your system, like my affected user does, you can save a copy of a
generated gschema.compiled to your home directory and bindiff it
against recompiles:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cp /usr/share/glib-2.0/schemas/gschema.compiled
/home/ubuntu/schemas/gschemas.compiled
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
If you install
[Desktop-packages] [Bug 1930359] Update Released
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
Title:
glib2.0: Uninitialised memory is written to gschema.compiled, failure
to parse this file leads to gdm, gnome-shell failing to start
Status in GLib:
Unknown
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Focal:
Fix Released
Bug description:
[Impact]
A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
user with 300 VDIs running Focal, where GNOME applications would fail
to start, and if you reboot, gdm and gnome-shell both fail to start,
and you are left with a black screen and a blinking cursor.
After much investigation, mutter was not at fault. Instead, mutter-
common calls the libglib2.0-0 hook on upgrade:
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
...
This in turn calls glib-compile-schemas to recompile the gsettings
gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
result is a binary gschemas.compiled file, which is loaded by
libglib2.0 on every invocation of a GNOME application, or gdm or
gnome-shell to fetch application default settings.
Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
deterministic behaviour when calling glib-compile-schemas, causing
generated gschemas.compiled files to have differing contents on each
run:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 D0
3771 A4 DB
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 68
3771 A4 30
3772 55 56
The bytes on the left are from a corrupted gschemas.compiled provided
by an affected user. The changing bytes on the right are non-
deterministic.
I ran valgrind over glib-compile-schemas, and found that we are
writing to uninitialised memory.
https://paste.ubuntu.com/p/hvZccwdzxz/
What is happening is that a submodule of glib, gvdb, contains the
logic for serialising the gschema data structures, and when it
allocates a buffer to store the eventual gschemas.compiled file, it
does not initialise it.
When we populate the fields in the buffer, some bytes are never
overwritten, and these junk bytes find themselves written to
gschemas.compiled.
On boot, when gdm and gnome-shell attempt to parse and load this
corrupted gschemas.compiled file, it can't parse the junk bytes, and
raises and error, which propagates up to a breakpoint in glib logging,
but no debugger is present, so the kernel traps the breakpoint, and
terminates the library, and the calling application, e.g. gdm.
The result is that the user is left starting at a black screen with a
blinking pointer.
[Testcase]
On a Focal system, simply run valgrind over glib-compile-schemas:
# valgrind glib-compile-schemas /usr/share/glib-2.0/schemas
You will get output like this, with the warning "Syscall param
write(buf) points to uninitialised byte(s)":
https://paste.ubuntu.com/p/hvZccwdzxz/
If you happen to have a large amount of gschema overrides present on
your system, like my affected user does, you can save a copy of a
generated gschema.compiled to your home directory and bindiff it
against recompiles:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cp /usr/share/glib-2.0/schemas/gschema.compiled
/home/ubuntu/schemas/gschemas.compiled
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
If you install the test package from the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test
When you run valgrind, it will report a clean run with no writing to
uninitialised
[Desktop-packages] [Bug 1934787] Re: Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main)
** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1934787 Title: Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main) Status in network-manager-openvpn package in Ubuntu: New Bug description: Please sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main) *NOTE: this release properly support tls-crypt-v2 certifcates, which current Ubuntu version fail to import!* Explanation of the Ubuntu delta and why it can be dropped: * Cherry-pick two upstream commits (that were released with 1.8.14) to fix connecting to some OpenVPN providers when using openvpn >= 2.5.0 (LP: #1922423) - debian/patches/upstream-56bb08f.patch - debian/patches/upstream-353a521.patch These changes are cherry picked from 1.8.14, so they are already included in Debian 1.8.14-1. Changelog entries since current impish version 1.8.12-2ubuntu1: network-manager-openvpn (1.8.14-1) experimental; urgency=medium * New upstream version 1.8.14 * Fix capitalization error in package description -- Michael Biebl Tue, 30 Mar 2021 15:13:23 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1934787/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
** No longer affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Focal) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Changed in: xorg-server (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Impish) Importance: Undecided => Medium ** Tags removed: 20.04 displaylink docking station ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Committed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared
** Changed in: wslu (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Impish) Importance: Undecided => Medium ** Tags added: unmetdeps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Status in wslu source package in Impish: Fix Released Bug description: [Impact] This bug will cause installation issues once LP #1911432 SRU Process complete. [Test Case] * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. [Regression Potential] The potential regressions would be a result of badly generated ~/.config/wslu/, or a badly merged package. [Original Bug Report] Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Tags removed: verification-needed -- 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/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which shows as graphical corruption on the desktop apps with certain hardware. The fix is to add a commit from upstream staging/21.0 -branch, which never got released as 21.0.4. [Test case] Install the update, use desktop apps, see that it works correctly now. [Where things could go wrong] The fix adds a single line for an earlier commit that was incomplete. In theory it might regress some other amd hw, but this is highly unlikely. -- Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1937321] [NEW] Xorg freeze
Public bug reported: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15-ef1xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2021 dmi.bios.release: 15.34 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8707 dmi.board.vendor: HP dmi.board.version: 37.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.19 dmi.modalias: dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-ef1xxx dmi.product.sku: 27A48UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 focal freeze 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/1937321 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: System freezes after I close the lid on the laptop and leave it closed overnight. It doesn't respond to any key presses or mouse clicks including Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the "suspend" screen showing but mostly it's just black. The Power settings -Dim screen when inactive = yes Blank screen = never Wifi and Bluetooth can be turned off to save power = yes Automatic suspend on battery power = yes Power button action = Power off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 22 17:34:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87cf] InstallationDate: Installed on 2021-06-30 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release
[Desktop-packages] [Bug 1914075] Re: subiquity 20.04.2 fails to install hwe kernel offline
** Changed in: ubuntu-meta (Ubuntu) Milestone: ubuntu-20.04.2 => ubuntu-20.04.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1914075 Title: subiquity 20.04.2 fails to install hwe kernel offline Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1914075/+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 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1937311] [NEW] copy-dir-locals-to-file-locals-prop-line command does nothing in LaTeX mode
Public bug reported: When in latex-mode with a latex source file in the buffer, running: M-x copy-dir-locals-to-file-locals-prop-line does nothing. It doesn't matter whether there is an existing line with -*- -*- or not. It's a bit annoying, because there are 4 latex engines to choose from in the configuration menu, and it would be convenient to be able to make emacs choose the correct engine for the file at hand (because different files work with different engines). Discovered on GNU Emacs 27.1 ** Affects: emacs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1937311 Title: copy-dir-locals-to-file-locals-prop-line command does nothing in LaTeX mode Status in emacs package in Ubuntu: New Bug description: When in latex-mode with a latex source file in the buffer, running: M-x copy-dir-locals-to-file-locals-prop-line does nothing. It doesn't matter whether there is an existing line with -*- -*- or not. It's a bit annoying, because there are 4 latex engines to choose from in the configuration menu, and it would be convenient to be able to make emacs choose the correct engine for the file at hand (because different files work with different engines). Discovered on GNU Emacs 27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1937311/+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 1926087] Re: LibreOffice LTS crashes after the extension re-launching
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1926087 Title: LibreOffice LTS crashes after the extension re-launching Status in libreoffice package in Ubuntu: New Bug description: Hi. I work on LibreOffice with Python extensions from https://extensions.libreoffice.org: * APSO (ver. 1.2.6) * MRI (ver. 1.3.4) APSO runs very well. But MRI not so. If launch MRI, close and launch it again LibreOffice 6.4 LTS crashes. See GDB log. Snap package LibreOffice 7.1 works well with MRI. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 18:42:26 2021 InstallationDate: Installed on 2020-06-03 (325 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1926087/+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 1936966] Re: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1936966 Title: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with Unity and MATE desktops 2. Add LO PPA, install full LO by sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update sudo apt-get install libreoffice 3a. Launch Libreoffice Impress, wait the Select a Template window to appear on task bar/window list 3b. Launch Libreoffice Writer, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3c. Launch Libreoffice Calc, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3d. Launch Libreoffice Draw, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list Expected results: * all Template windows use correct desktop/panel/window icons on task bar/window list Actual results: * all Template windows use wrong desktop/panel/window icons on task bar/window list Details: libreoffice1:7.1.4~rc2-0ubuntu0.18.04.1~lo1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1936966/+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 1935734] Re: nautilus can't open folder as root
same with nautilus 40.2 (imprish) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1935734 Title: nautilus can't open folder as root Status in nautilus package in Ubuntu: New Bug description: Latest daily of imprish Error message in terminal: (org.gnome.Nautilus:6242): GVFS-WARNING **: 09:06:02.331: The peer-to- peer connection failed: Verbindung ist gescheitert: Keine Berechtigung. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Window: GDBus.Error.org.freedesktop.PolicyKit1.Error.Failed:Unix process subject does not have uid set --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.window-state' b'initial-size' b'(1446, 704)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-07-09 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210709) Package: nautilus 1:3.38.2-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-11.11-generic 5.13.0 Tags: third-party-packages impish wayland-session Uname: Linux 5.13.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Even ubuntu 20.04 has the same issue. Audio device is shown as dummy device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1937127] Re: Gnome-shell animations smoother when external monitor is connected
That sounds like a heavy solution to lock the frequency at the max. How come this issue wasn't there in PopOS 20.04 (wayland session)? Was there a regression somewhere in the stack in 21.04, or is PopOS doing its own tuning? I haven't tried Ubuntu 20.04, nor PopOS 21.04, to know whether PopOS was doing something different, or just the older stack. -- 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/1937127 Title: Gnome-shell animations smoother when external monitor is connected Status in gnome-shell package in Ubuntu: In Progress Bug description: When no external monitor is connected Gnome Shell activities animation is sluggish. Once an external monitor is connected the animation becomes noticeably smoother. It looks like the OS is not properly responding to the extra processing demands by raising the CPU/GPU performance, and having an external monitor connected somehow triggers a higher performance level. This is on a System76 Darter Pro machine with Intel® Core™ i7-8565U and Intel UHD 620 running Ubuntu 21.04 in Wayland session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-7620.21~1624379747~21.04~3abeff8~dev-generic 5.11.21 Uname: Linux 5.11.0-7620-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 12:51:55 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-14 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937127/+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 1919255] Re: tracker-store crashed with signal 5
This week I moved the contents of my ~/Music directory to a different directory on a different physical drive mounted on /work, and I no longer get this behaviour. From that I surmise, perhaps incorrectly, that there was some situation in my music files (almost all FLAC, a few MP3s) that was causing this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1937072] Re: Incomplete screen redraws
List of things I have to Inform you what I have tested.I am Computer Science student but new to linux so I have tested many things. 1. I have used both x-org and nvidia GPU. After fresh installation and on reboot I got into many problem my touchpad and brightness controller were not working and screen glitch so i fixed my brightness and touchpad using ubuntu community posts. But glitch were all same I have tried many solution but not solved. so I posted ubuntu-bug. 2. I have changed setting from bios to disable NVIDIA but glitch problem not solved. And on using NVIDIA Driver there were not glitch performance were perfectly fine but on restart i got stucked on boot menu screen were blank so i ran into recovery and change my driver to x-org intel. 3. Before bug submission I have tested around 10 popular linux distro all were having same problem screen glitches. 4. only two distro have not occoured a display glitch problem one was ubuntu 20.04 LTS and ubuntu budgie 21.04 but that distro causes same touchpad and brightness controll problem that was so frustating. So I came to conclusion that my intel driver is buggy and on reboot my device alwaay fail to recognise touchpad and display driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1919255] Re: tracker-store crashed with signal 5
There is a fix in upstream (tracker 3.0.3) which might apply to this: https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/353 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1409536] Re: After testing settings cannot return to Mouse & Touchpad settings
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1409536 Title: After testing settings cannot return to Mouse & Touchpad settings Status in One Hundred Papercuts: Incomplete Status in unity-control-center package in Ubuntu: Incomplete Bug description: If I go into the "Mouse & Touchpad" section in "System Settings" and I click the button in the top-right hand corner called "Test Your Settings". Once I am in the "Test Your Settings" section I cannot return to the "Mouse & Touchpad" section by selecting it at the top- left hand corner next to the "System Settings" button, I can click it a hundred times but nothing happens. Instead I have to click the "System Settings" button and return to the main screen to go back into the "Mouse & Touchpad" section. And this is a small bug, but it is still rather annoying that I have to use min 2 clicks instead of 1, to return to the "Mouse & Touchpad" section. OS information: Description: Ubuntu 14.10 Release: 14.10 Package information: unity-control-center: Installed: 14.10.0+14.10.20140922-0ubuntu2 Candidate: 14.10.0+14.10.20140922-0ubuntu2 Version table: *** 14.10.0+14.10.20140922-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1409536/+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 1937247] [NEW] Difficulty closing the Dialog Preferences in Nautilus
Public bug reported: Dear maintainer, in Nautilus 40.2 the upper bar of the Preferences Dialog does not appear, so it is only possible to close the Preferences Dialog by pressing the ESC key on the keyboard. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1937247 Title: Difficulty closing the Dialog Preferences in Nautilus Status in nautilus package in Ubuntu: New Bug description: Dear maintainer, in Nautilus 40.2 the upper bar of the Preferences Dialog does not appear, so it is only possible to close the Preferences Dialog by pressing the ESC key on the keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1937247/+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 1633609] Re: spice-vdagentd does not work
** Changed in: spice-vdagent (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1633609 Title: spice-vdagentd does not work Status in spice-vdagent package in Ubuntu: Fix Released Bug description: After upgrade to Ubuntu 16.10, the Ubuntu system inside Quemu/KVM virtual machine stopped to resize screen whenever Spice client window size changes. I found out the following message in /var/log/spice-vdagent.log: spice-vdagentd: err: Error getting session for pid 3506: No such device or address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1633609/+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 1937245] [NEW] ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER`
Public bug reported: Firefox 90.0+build1-0ubuntu0.21.04.1 fails to load HTTPS URLs with the error: > Secure Connection Failed > > An error occurred during a connection to blog.fefe.de. The client has > encountered bad data from the server. > > Error code: SSL_ERROR_BAD_SERVER > > * The page you are trying to view cannot be shown because the authenticity > of the received data could not be verified. > * Please contact the website owners to inform them of this problem. Nothing related is logged in the terminal window, Firefox was started from. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1937245 Title: ppc64le: Fails to load HTTPS pages with `Error code: SSL_ERROR_BAD_SERVER` Status in firefox package in Ubuntu: New Bug description: Firefox 90.0+build1-0ubuntu0.21.04.1 fails to load HTTPS URLs with the error: > Secure Connection Failed > > An error occurred during a connection to blog.fefe.de. The client has encountered bad data from the server. > > Error code: SSL_ERROR_BAD_SERVER > > * The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. > * Please contact the website owners to inform them of this problem. Nothing related is logged in the terminal window, Firefox was started from. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937245/+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 1937072] Re: Incomplete screen redraws
Please try: * Installing the proprietary Nvidia driver via the 'Additional Drivers' app. The open source nouveau driver is frequently buggy so I would like to eliminate that from the equation ASAP. * Looking in your BIOS and see if you can disable the discrete Nvidia GPU temporarily. Does that fix it? ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
On 2021-07-22 08:45, Kai-Heng Feng wrote: > If we don't want the extra dependencies then we should include the > additional commits. Ouch! Ok.. > Do you want me to generate new debdiffs? Not necessary. We have repos at salsa.debian.org, and I just fixed the -ng package for hirsute and uploaded again. https://salsa.debian.org/gnome-team/shell-extensions/gnome-shell- extension-desktop-icons-ng/-/commit/5e109eb9 I chose to add the extra deps to match what we have in impish ATM. But what about gnome-shell-extension-desktop-icons? Do we have to change those as well? P.S. Good catch, Robie! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1937072] Re: Screen tearing and display glitches
Thanks. It looks like you've tried both Xorg and Wayland sessions. Are the bugs the same in both? ** Tags added: hybrid i915 nouveau ** Package changed: ubuntu => mutter (Ubuntu) ** Summary changed: - Screen tearing and display glitches + Incomplete screen redraws ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: licelake ** Tags removed: licelake ** Tags added: icelake -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937072 Title: Incomplete screen redraws Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937072/+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 1937072] [NEW] Screen tearing and display glitches
You have been subscribed to a public bug: In every 6/10 boot my ubuntu failed to start stuck on blank screen. Sometime touchpad stop working and unable to change my brightness after installation at first all feature are perfectly fine except screen glitch.Screen performance is laggy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 17:13:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug hirsute hybrid i915 nouveau ubuntu -- Screen tearing and display glitches https://bugs.launchpad.net/bugs/1937072 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter 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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
The workaround suggested in comment #9 is fine, however if you use fractional scaling under Wayland it makes the text in Thunderbird way too blurry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+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 1936643] Re: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview
The desktop icons will /animate/ whenever the desktop window is recreated. That's an older issue that was visible in 3.38 and separate to this bug. Although I guess many would see it as a nice feature. And sorry for the delay, I've been sick. -- 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/1936643 Title: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Status in mutter package in Ubuntu: In Progress Bug description: In Ubuntu 21.10 Impish Indri, I have done today's updates, including GNOME 40, and when I rebooted, I saw the desktop icons in the Activities overview that has the grey gears icon and the gibberish name. However, when I clicked on it, I'm taken to the desktop. When I open the Activities overview again, that "application" didn't show up. I suspect that this "application" came from a GNOME extension that handles desktop icons, called gnome-shell-extension-desktop-icons-ng. Because I thought that it loaded AFTER the Activities overview opened at log in. This repeats every time I reboot or just log off and log back in. Steps to reproduce: 1. Update the Impish system to the latest version 2. Reboot 3. Log in Expected results: The "application" that came from the desktop icon shell extension doesn't appear in the Activities overview Actual results: This "application" shows up in the overview with the grey gears icon and the gibberish name every time a user signs in to the new GNOME 40 desktop lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status If there is any more information needed, let me know. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:07:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1936643/+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 1936643] Re: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview
Well, this bug does not only happen in every startup or logout/login, but it seems that whenever you have an application open, focusing on its window, and you locked the system and logged in again, the desktop icons animate. However, when it zooms in, the application window loses focus. About the "vanilla" GNOME thing, there should be an option that controls how Ubuntu starts on log-in, whether or not to start to the Activities overview. Either way, this bug needs to be fixed sooner or later. -- 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/1936643 Title: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Status in mutter package in Ubuntu: In Progress Bug description: In Ubuntu 21.10 Impish Indri, I have done today's updates, including GNOME 40, and when I rebooted, I saw the desktop icons in the Activities overview that has the grey gears icon and the gibberish name. However, when I clicked on it, I'm taken to the desktop. When I open the Activities overview again, that "application" didn't show up. I suspect that this "application" came from a GNOME extension that handles desktop icons, called gnome-shell-extension-desktop-icons-ng. Because I thought that it loaded AFTER the Activities overview opened at log in. This repeats every time I reboot or just log off and log back in. Steps to reproduce: 1. Update the Impish system to the latest version 2. Reboot 3. Log in Expected results: The "application" that came from the desktop icon shell extension doesn't appear in the Activities overview Actual results: This "application" shows up in the overview with the grey gears icon and the gibberish name every time a user signs in to the new GNOME 40 desktop lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status If there is any more information needed, let me know. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:07:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1936643/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
If we don't want the extra dependencies then we should include the additional commits. Do you want me to generate new debdiffs? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1936303] Re: [SRU] Debounce multiple rfkill events
On hirsute, enable -proposed and upgrade G-S-D to 3.38.1-3ubuntu3.1.
Similar to Focal, observed two KEY_RKFILL in `libinput debug-events` on
a single airplane hotkey press, but the airplane mode can be toggled
on/off correctly.
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1936303
Title:
[SRU] Debounce multiple rfkill events
Status in OEM Priority Project:
New
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Focal:
Fix Committed
Status in gnome-settings-daemon source package in Hirsute:
Fix Committed
Status in gnome-settings-daemon source package in Impish:
Fix Released
Bug description:
[Impact]
Some laptops can generate multiple rfkill events from a single key press.
[Fix]
Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second
delay between each rfkill event").
The commit adds a delay between each rkfill events to only process the first
event and debounce the later ones.
[Test]
On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill
events on single key press. Airplane mode will be enabled and disabled in a
very short period, so the airplane mode cannot be turned off by the hotkey
anymore.
After applying the fix, pressing airplane mode hotkey can enable or
disable airplane mode correctly.
[Where problems could occur]
Since the delay is hardcoded as 1 second, the airplane mode cannot be
switched on/of in a very short time anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1937023] Re: Trash Bin "empty" indicator does not work consistently
** Attachment added: "Screencast from 21-07-2021 09:10:21.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+attachment/5512798/+files/Screencast%20from%2021-07-2021%2009%3A10%3A21.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1937023 Title: Trash Bin "empty" indicator does not work consistently Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: My OS is Ubuntu 20.04.2 LTS OS type is 64-bit When I want empty the trash bin: I right click on the TRASH icon and select "Empty the rubbish bin". A display comes up the says "Empty all items from the Rubbish Bin ?" and I select "Empty Rubbish Bin". The next display that SOMETIMES comes up for a moment confirms the process has been done. When this display shows then shortly after that the indicator on the icon show she Trash is empty. When the said display does not appear the "empty" indicator DOES NOT appear.I have not been able to that this behaviour is related to certain apps that are open when I empty the Trash bin. Whether the "empty" indicator works or not the trash is always emptied BUT you have to open the Trash to see that it has been emptied. I have made screen recordings showing what I have been experiencing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-06-27 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Tags: focal Uname: Linux 5.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+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 1937023] Re: Trash Bin "empty" indicator does not work consistently
** Attachment added: "Screencast from 20-07-2021 08:53:50.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+attachment/5512797/+files/Screencast%20from%2020-07-2021%2008%3A53%3A50.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1937023 Title: Trash Bin "empty" indicator does not work consistently Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: My OS is Ubuntu 20.04.2 LTS OS type is 64-bit When I want empty the trash bin: I right click on the TRASH icon and select "Empty the rubbish bin". A display comes up the says "Empty all items from the Rubbish Bin ?" and I select "Empty Rubbish Bin". The next display that SOMETIMES comes up for a moment confirms the process has been done. When this display shows then shortly after that the indicator on the icon show she Trash is empty. When the said display does not appear the "empty" indicator DOES NOT appear.I have not been able to that this behaviour is related to certain apps that are open when I empty the Trash bin. Whether the "empty" indicator works or not the trash is always emptied BUT you have to open the Trash to see that it has been emptied. I have made screen recordings showing what I have been experiencing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-06-27 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Tags: focal Uname: Linux 5.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+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 1937023] Re: Trash Bin "empty" indicator does not work consistently
** Attachment added: "Screencast from 21-07-2021 09:17:09.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+attachment/5512799/+files/Screencast%20from%2021-07-2021%2009%3A17%3A09.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1937023 Title: Trash Bin "empty" indicator does not work consistently Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: My OS is Ubuntu 20.04.2 LTS OS type is 64-bit When I want empty the trash bin: I right click on the TRASH icon and select "Empty the rubbish bin". A display comes up the says "Empty all items from the Rubbish Bin ?" and I select "Empty Rubbish Bin". The next display that SOMETIMES comes up for a moment confirms the process has been done. When this display shows then shortly after that the indicator on the icon show she Trash is empty. When the said display does not appear the "empty" indicator DOES NOT appear.I have not been able to that this behaviour is related to certain apps that are open when I empty the Trash bin. Whether the "empty" indicator works or not the trash is always emptied BUT you have to open the Trash to see that it has been emptied. I have made screen recordings showing what I have been experiencing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-06-27 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Tags: focal Uname: Linux 5.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1937023/+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 1908082] Re: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark
@Olivier Tilloy, ironically, I'm now seeing the same behavior in version 90. I don't remember if the performance behaved the same way in 89 or not, but maybe? At any rate, performance of Ubuntu's builds has vastly improved, even if it's still not quite on the same level as Chrome. I haven't re-tested non-Ubuntu Firefox yet either. Also, I'm on 20.04, which might be making a difference. -- 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/1908082 Title: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark Status in firefox package in Ubuntu: Incomplete Bug description: Steps to reproduce: I installed Firefox Flatpak (https://flathub.org/apps/details/org.mozilla.firefox) and Chrome. I executed closed all apps and processes and one by one I executed Speedometer test (https://browserbench.org/Speedometer2.0/) in each browser 3 times. I took the max score for reach browser out of the 3 executions of the test. Actual results: Results 100.3 - Firefox Flatpak 85.42 - FIrefox DEB (pre-installd from the store) 100.3 - Google Chrome The preinstalled DEB package Firefox was slower than both Firefox Flatpak and Chrome Expected results: I expected Firefox DEB and Firefox Flatpak to have the same results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908082/+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 1936303] Re: [SRU] Debounce multiple rfkill events
Enable -proposed and upgrade G-S-D to 3.36.1-0ubuntu1.1.
Use `sudo libinput debug-events` to monitor input events, press airplane
mode hotkey, observe there are two events.
The airplane mode can be toggled on/off despite there are two rfkill
events.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1936303
Title:
[SRU] Debounce multiple rfkill events
Status in OEM Priority Project:
New
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Focal:
Fix Committed
Status in gnome-settings-daemon source package in Hirsute:
Fix Committed
Status in gnome-settings-daemon source package in Impish:
Fix Released
Bug description:
[Impact]
Some laptops can generate multiple rfkill events from a single key press.
[Fix]
Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second
delay between each rfkill event").
The commit adds a delay between each rkfill events to only process the first
event and debounce the later ones.
[Test]
On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill
events on single key press. Airplane mode will be enabled and disabled in a
very short period, so the airplane mode cannot be turned off by the hotkey
anymore.
After applying the fix, pressing airplane mode hotkey can enable or
disable airplane mode correctly.
[Where problems could occur]
Since the delay is hardcoded as 1 second, the airplane mode cannot be
switched on/of in a very short time anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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
