[Desktop-packages] [Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
I managed to unbreak my system (in case anyone stumbles here looking for help) after reporting bug 2063219 Julian suggested installing libglib2.0-0t64_2.80.0-6ubuntu1_amd64.deb manually downloaded from the archive with dpkg, which I did. Then checked the debs in /var/cache/apt/archives/*.deb were only from the release upgrade (not from previous updates) by correlating with my /var/log/dpkg.log package update timings. sudo dpkg --install /var/cache/apt/archives/*.deb. # ran this twice sudo apt --fix-broken install. # this now runs successfully sudo apt update sudo apt dist-upgrade # to continue the broken mantic to noble upgrade liblxc-common 1:5.0.1-0ubuntu7 and liblxc1 1:5.0.1-0ubuntu7 have a colliding /usr/lib/x86_64-linux-gnu/lxc/rootfs/README sudo apt --fix-broken install. # resolved above by removing liblxc1 sudo apt dist-upgrade sudo apt install ubuntu-desktop^ sudo apt dist-upgrade After all that, it's "fixed". Thanks Julian <3 -- 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/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: Confirmed Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+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 2060122] [NEW] minimise animations fly everywhere
Public bug reported: Problem: When maximising/minimising/restoring a window by clicking on the item in the launcher, sometimes (often) the animation - which makes the window shrink and 'fly' to or from the dock, will fly in the wrong direction. Steps to reproduce: * Have multiple monitors (I think, I don't recall seeing this in a single monitor usage) * Launch a number of applications * Click icons in the dock to trigger animation as applications grow and shrink from the launcher up to the workspace. What should happen: * Window appears near the dock, and grows to the final location on screen and * Window shrinks back down to the dock What happens: * Sometimes windows fly up to the top left of the display, *and* to the dock at the bottom. Animation frames flicker all over the place, but mostly both towards the top left and towards the bottom. It *looks* like alternate frames of animation are flying up and down. Here is a video of it happening. https://www.youtube.com/watch?v=b2vgEurkHk8 I am currently running Ubuntu 23.10, but I am sure I have seen this on multiple releases. I am using multiple displays. Arranged like this: ( 1 )( 2 ) ( 3 ) 1 - external display 2 - external display 3 - Laptop (primary) The launcher is on the bottom of the primary monitor. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 3 13:31:22 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (607 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to mantic on 2023-10-15 (171 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2060122 Title: minimise animations fly everywhere Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Problem: When maximising/minimising/restoring a window by clicking on the item in the launcher, sometimes (often) the animation - which makes the window shrink and 'fly' to or from the dock, will fly in the wrong direction. Steps to reproduce: * Have multiple monitors (I think, I don't recall seeing this in a single monitor usage) * Launch a number of applications * Click icons in the dock to trigger animation as applications grow and shrink from the launcher up to the workspace. What should happen: * Window appears near the dock, and grows to the final location on screen and * Window shrinks back down to the dock What happens: * Sometimes windows fly up to the top left of the display, *and* to the dock at the bottom. Animation frames flicker all over the place, but mostly both towards the top left and towards the bottom. It *looks* like alternate frames of animation are flying up and down. Here is a video of it happening. https://www.youtube.com/watch?v=b2vgEurkHk8 I am currently running Ubuntu 23.10, but I am sure I have seen this on multiple releases. I am using multiple displays. Arranged like this: ( 1 )( 2 ) ( 3 ) 1 - external display 2 - external display 3 - Laptop (primary) The launcher is on the bottom of the primary monitor. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 3 13:31:22 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (607 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to mantic on 2023-10-15 (171 days ago) To manage notifications about this
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Why do we have to file a new bug for this. The task for mantic says it's fix released, but it clearly isn't. alan@ziggy:~$ grep -r Meta.Rectangle /usr/share/gnome-shell/extensions/ /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js: const rect = new Meta.Rectangle(); alan@ziggy:~$ dpkg -S /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js gnome-shell-extension-ubuntu-dock: /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js alan@ziggy:~$ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 87ubuntu1 Candidate: 87ubuntu1 Version table: *** 87ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status This is fixed in noble, but not mantic. I see no SRU pending: https://ubuntu-archive-team.ubuntu.com/pending-sru This bug was filed against mantic, it's a mantic bug. So the status of 'fixed released' is clearly just incorrect, surely? -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
alan@ziggy:~$ sudo journalctl -b0 | grep Meta.Rectangle | wc -l 1836 -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2058761] [NEW] FileNotFoundError: [Errno 2] No such file or directory
Public bug reported: Crashes on my ThinkPad Z13 running up-to-date Ubuntu 23.10. $ sudo switcherooctl --list Traceback (most recent call last): File "/usr/bin/switcherooctl", line 187, in launch(args, gpu) File "/usr/bin/switcherooctl", line 66, in launch os.execvp(args[0], args) File "", line 574, in execvp File "", line 616, in _execvpe File "", line 607, in _execvpe FileNotFoundError: [Errno 2] No such file or directory ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: switcheroo-control 2.6-1 Uname: Linux 6.7.9-060709-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 16:28:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (595 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: switcheroo-control UpgradeStatus: Upgraded to mantic on 2023-10-15 (159 days ago) ** Affects: switcheroo-control (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to switcheroo-control in Ubuntu. https://bugs.launchpad.net/bugs/2058761 Title: FileNotFoundError: [Errno 2] No such file or directory Status in switcheroo-control package in Ubuntu: New Bug description: Crashes on my ThinkPad Z13 running up-to-date Ubuntu 23.10. $ sudo switcherooctl --list Traceback (most recent call last): File "/usr/bin/switcherooctl", line 187, in launch(args, gpu) File "/usr/bin/switcherooctl", line 66, in launch os.execvp(args[0], args) File "", line 574, in execvp File "", line 616, in _execvpe File "", line 607, in _execvpe FileNotFoundError: [Errno 2] No such file or directory ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: switcheroo-control 2.6-1 Uname: Linux 6.7.9-060709-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 16:28:23 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (595 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: switcheroo-control UpgradeStatus: Upgraded to mantic on 2023-10-15 (159 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/switcheroo-control/+bug/2058761/+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 2037076] Re: System Details incorrectly shows multiple GPUs
alan@nuc:~$ switcherooctl list Device: 0 Name:Advanced Micro Devices, Inc. [AMD®/ATI] Polaris 22 XT [Radeon RX Vega M GH] Default: yes Environment: DRI_PRIME=pci-_01_00_0 Device: 1 Name:NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+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 2037076] Re: System Details incorrectly shows multiple GPUs
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2662 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+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 2037076] [NEW] System Details incorrectly shows multiple GPUs
Public bug reported: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "Screenshot from 2023-09-22 11-39-20.png" https://bugs.launchpad.net/bugs/2037076/+attachment/5703519/+files/Screenshot%20from%202023-09-22%2011-39-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center package in Ubuntu: New Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037076/+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 2019886] Re: Printer ink levels are incorrect
** Attachment added: "Screenshot from 2023-05-16 17-26-13.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019886/+attachment/5673370/+files/Screenshot%20from%202023-05-16%2017-26-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019886 Title: Printer ink levels are incorrect Status in gnome-control-center package in Ubuntu: New Bug description: I would like to see the printer ink levels of my printer. If I visit the gnome settings printer panel, I see lots of cyan, and a small amount of magenta, and a small amount of yellow. An unknown about of black is shown, perhaps in between magenta and yellow, or perhaps the bar after the yellow. I don't know. What's more concerning is the bars don't even line up with what the printer thinks the fill level is. Attached two screenshots. One of gnome settings, and one of the web UI for the printer. The ink levels don't correlate at all. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:31:08 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019886/+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 2019886] [NEW] Printer ink levels are incorrect
Public bug reported: I would like to see the printer ink levels of my printer. If I visit the gnome settings printer panel, I see lots of cyan, and a small amount of magenta, and a small amount of yellow. An unknown about of black is shown, perhaps in between magenta and yellow, or perhaps the bar after the yellow. I don't know. What's more concerning is the bars don't even line up with what the printer thinks the fill level is. Attached two screenshots. One of gnome settings, and one of the web UI for the printer. The ink levels don't correlate at all. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:31:08 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot from 2023-05-16 17-26-57.png" https://bugs.launchpad.net/bugs/2019886/+attachment/5673366/+files/Screenshot%20from%202023-05-16%2017-26-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019886 Title: Printer ink levels are incorrect Status in gnome-control-center package in Ubuntu: New Bug description: I would like to see the printer ink levels of my printer. If I visit the gnome settings printer panel, I see lots of cyan, and a small amount of magenta, and a small amount of yellow. An unknown about of black is shown, perhaps in between magenta and yellow, or perhaps the bar after the yellow. I don't know. What's more concerning is the bars don't even line up with what the printer thinks the fill level is. Attached two screenshots. One of gnome settings, and one of the web UI for the printer. The ink levels don't correlate at all. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:31:08 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019886/+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 2019885] Re: Printer ink level bars don't line up
Sorry, attached wrong screenshot! ** Attachment added: "Screenshot from 2023-05-16 17-26-13.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019885/+attachment/5673365/+files/Screenshot%20from%202023-05-16%2017-26-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019885 Title: Printer ink level bars don't line up Status in gnome-control-center package in Ubuntu: New Bug description: See screenshot. I'd like to know the ink level in my laser printer. I can see the ink level in the gnome control center. However the colours look like they're not centred vertically. The ink levels are inside a losenge but don't fit perfectly vertically. There's a gap below the coloured bar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:28:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019885/+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 2019885] [NEW] Printer ink level bars don't line up
Public bug reported: See screenshot. I'd like to know the ink level in my laser printer. I can see the ink level in the gnome control center. However the colours look like they're not centred vertically. The ink levels are inside a losenge but don't fit perfectly vertically. There's a gap below the coloured bar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:28:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot from 2023-05-16 17-26-57.png" https://bugs.launchpad.net/bugs/2019885/+attachment/5673361/+files/Screenshot%20from%202023-05-16%2017-26-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019885 Title: Printer ink level bars don't line up Status in gnome-control-center package in Ubuntu: New Bug description: See screenshot. I'd like to know the ink level in my laser printer. I can see the ink level in the gnome control center. However the colours look like they're not centred vertically. The ink levels are inside a losenge but don't fit perfectly vertically. There's a gap below the coloured bar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 Uname: Linux 6.3.1-060301-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 16 17:28:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (284 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-01-02 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019885/+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 2018978] [NEW] "Failed to scan" unable to connect to scanner - HP m175nw
Public bug reported: This scanner has previously worked on other computers running Ubuntu. However, it doesn't work on 23.04. The scanner is on, and shows up in the front screen in simple-scan When I press the scan button a dialog appears titled "Failed to scan" "Unable to connect to scanner". ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: simple-scan 44.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 9 09:42:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (276 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21D2CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=96c77f27-d90f-4d14-a5d5-59ac57b3f6dc ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to lunar on 2023-01-02 (126 days ago) dmi.bios.date: 12/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.54 dmi.modalias: dmi:bvnLENOVO:bvrN3GET47W(1.27):bd12/08/2022:br1.27:efr1.54:svnLENOVO:pn21D2CTO1WW:pvrThinkPadZ13Gen1:rvnLENOVO:rn21D2CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D2_BU_Think_FM_ThinkPadZ13Gen1: dmi.product.family: ThinkPad Z13 Gen 1 dmi.product.name: 21D2CTO1WW dmi.product.sku: LENOVO_MT_21D2_BU_Think_FM_ThinkPad Z13 Gen 1 dmi.product.version: ThinkPad Z13 Gen 1 dmi.sys.vendor: LENOVO ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2018978 Title: "Failed to scan" unable to connect to scanner - HP m175nw Status in simple-scan package in Ubuntu: New Bug description: This scanner has previously worked on other computers running Ubuntu. However, it doesn't work on 23.04. The scanner is on, and shows up in the front screen in simple-scan When I press the scan button a dialog appears titled "Failed to scan" "Unable to connect to scanner". ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: simple-scan 44.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 9 09:42:36 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (276 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 MachineType: LENOVO 21D2CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=96c77f27-d90f-4d14-a5d5-59ac57b3f6dc ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to lunar on 2023-01-02 (126 days ago) dmi.bios.date: 12/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.54 dmi.modalias: dmi:bvnLENOVO:bvrN3GET47W(1.27):bd12/08/2022:br1.27:efr1.54:svnLENOVO:pn21D2CTO1WW:pvrThinkPadZ13Gen1:rvnLENOVO:rn21D2CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D2_BU_Think_FM_ThinkPadZ13Gen1: dmi.product.family: ThinkPad Z13 Gen 1 dmi.product.name: 21D2CTO1WW dmi.product.sku: LENOVO_MT_21D2_BU_Think_FM_ThinkPad Z13 Gen 1 dmi.product.version: ThinkPad Z13 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2018978/+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 2017756] [NEW] Pipewire-pulse consuming huge amounts of memory
Public bug reported: I noticed my RAM usage was high. pipewire-pulse is the highest user of RAM on my system. The system has been up for four days. I have used all manner of audio applications in that time, including Slack huddle, Zoom, mpv, VLC and Microsoft Edge (YouTube, Netflix) and Kdenlive. alan@ziggy:~$ pactl stat Currently in use: 7865827 blocks containing 2.1 GiB bytes total. Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total. Sample cache size: 275.2 KiB alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail 207.7 MiB + 419.6 MiB = 627.2 MiB gnome-shell 227.3 MiB + 455.3 MiB = 682.7 MiB syncthing (2) 385.4 MiB + 855.8 MiB = 1.2 GiB slack (8) 409.5 MiB + 928.5 MiB = 1.3 GiB Discord (8) 4.2 GiB + 8.9 GiB = 13.1 GiB msedge [updated] (45) 14.1 GiB + 28.2 GiB = 42.3 GiB pipewire-pulse - 62.7 GiB = ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-pulse 0.3.65-3 Uname: Linux 6.2.2-060202-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 10:24:47 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (263 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2023-01-02 (113 days ago) ** Affects: pipewire Importance: Unknown Status: Unknown ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot from 2023-04-26 10-32-36.png" https://bugs.launchpad.net/bugs/2017756/+attachment/5668843/+files/Screenshot%20from%202023-04-26%2010-32-36.png ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1840 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017756 Title: Pipewire-pulse consuming huge amounts of memory Status in PipeWire: Unknown Status in pipewire package in Ubuntu: New Bug description: I noticed my RAM usage was high. pipewire-pulse is the highest user of RAM on my system. The system has been up for four days. I have used all manner of audio applications in that time, including Slack huddle, Zoom, mpv, VLC and Microsoft Edge (YouTube, Netflix) and Kdenlive. alan@ziggy:~$ pactl stat Currently in use: 7865827 blocks containing 2.1 GiB bytes total. Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total. Sample cache size: 275.2 KiB alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail 207.7 MiB + 419.6 MiB = 627.2 MiB gnome-shell 227.3 MiB + 455.3 MiB = 682.7 MiB syncthing (2) 385.4 MiB + 855.8 MiB = 1.2 GiB slack (8) 409.5 MiB + 928.5 MiB = 1.3 GiB Discord (8) 4.2 GiB + 8.9 GiB = 13.1 GiB msedge [updated] (45) 14.1 GiB + 28.2 GiB = 42.3 GiB pipewire-pulse - 62.7 GiB = ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-pulse 0.3.65-3 Uname: Linux 6.2.2-060202-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 10:24:47 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (263 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2023-01-02 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2017756/+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 1988484] [NEW] Holding down volume keys sometimes crashes xorg
Public bug reported: Running KDE 5.24.4 on Ubuntu Jammy. On a few occasions, I've been able to trigger a complete desktop crash by pressing and holding the volume keys on my laptop. Steps to reproduce: 1) Have something play audio - typically youtube in a browser 2) Hold down Fn+F3 or Fn+F2 to increase/decrease volume. Crash. More information: You may find more detail in crashes from this machine at https://errors.ubuntu.com/user/39741994cfebc02a360b6373cda1e148b8bca640b31a1aec7727d4862d5bbdf25251b0221ae0686ac25e1f415fd9a5a73a8a95d904dac3ba9a31985bb2ec824d The last time this happened was a week or so back - here's the crash report https://errors.ubuntu.com/oops/8bd96e8c-2540-11ed-97b9-fa163e993415 Todays crash hasn't finished being processed yet so I can't link to it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 23:16:03 2022 DistUpgraded: 2022-03-29 22:59:20,069 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: akvcam/1.2.2, 5.13.0-30-generic, x86_64: installed akvcam/1.2.2, 5.13.0-37-generic, x86_64: installed akvcam/1.2.2, 5.15.0-43-generic, x86_64: installed akvcam/1.2.2, 5.15.0-46-generic, x86_64: installed akvcam/1.2.2, 5.15.0-47-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5034] InstallationDate: Installed on 2020-06-11 (812 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20BV001BUK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-03-29 (156 days ago) dmi.bios.date: 08/14/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BV_BU_Think_FM_ThinkPadT450: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg-server Importance: Unknown Status: Unknown ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu ** Bug watch added: KDE Bug Tracking System #454683 https://bugs.kde.org/show_bug.cgi?id=454683 ** Also affects: xorg-server via https://bugs.kde.org/show_bug.cgi?id=454683 Importance: Unknown Status: Unknown -- 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/1988484 Title: Holding down volume keys sometimes crashes xorg Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: Running KDE 5.24.4 on Ubuntu Jammy. On a few occasions, I've been able to trigger a complete desktop crash by pressing and holding the volume keys on my laptop. Steps to reproduce: 1) Have something play audio - typically youtube in a browser 2) Hold down Fn+F3 or Fn+F2 to increase/decrease volume. Crash. More information: You may find more detail in crashes from this machine at https://errors.ubuntu.com/user/39741994cfebc02a360b6373cda1e148b8bca640b31a1aec7727d4862d5bbdf25251b0221ae0686ac25e1f415fd9a5a73a8a95d904dac3ba9a31985bb2ec824d The last time this happened was a week or so back - here's the crash report
[Desktop-packages] [Bug 1938195] [NEW] Configuration for eGPU removed on update
Public bug reported: ThinkPad X1C9 running Kubuntu. I'm using an external nVidia GPU in an enclosure, attached via thunderbolt. I have applied updates over the last few weeks, and rebooted today. Got a black screen. Turns out an update back in mid June (22nd) removed the Option "AllowExternalGpus" "true" from my xorg.conf. Why is an update removing a vital configuration option enabling me to display my login screen? I had to re-edit the xorg.conf like an cave man from 20 years ago. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Tue Jul 27 16:42:11 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tp_smapi, 0.43, 5.11.0-22-generic, x86_64: installed tp_smapi, 0.43, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2021-05-14 (73 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f73d534c-9211-43d9-a8d5-fe9b6bb3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2021 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET47W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN32ET47W(1.23):bd03/26/2021:br1.23:efr1.22:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1938195 Title: Configuration for eGPU removed on update Status in xorg package in Ubuntu: New Bug description: ThinkPad X1C9 running Kubuntu. I'm using an external nVidia GPU in an enclosure, attached via thunderbolt. I have applied updates over the last few weeks, and rebooted today. Got a black screen. Turns out an update back in mid June (22nd) removed the Option "AllowExternalGpus" "true" from my xorg.conf. Why is an update removing a vital configuration option enabling me to display my login screen? I had to re-edit the xorg.conf like an cave man from 20 years ago. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
[Desktop-packages] [Bug 1921139] Re: [UIFe] Hippo wallpapers
Here's a tarball of the wallpapers and the mascot in SVG format: https://people.canonical.com/~alan/Hirsute_Hippo_Wallpapers.zip https://people.canonical.com/~alan/Hirsute_Hippo_Mascot.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1921139 Title: [UIFe] Hippo wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Committed Bug description: Here we go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1921139/+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 1917939] Re: windows maximise underneath dock
** Attachment added: "Screenshot from 2021-03-05 19-24-08.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+attachment/5473781/+files/Screenshot%20from%202021-03-05%2019-24-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: windows maximise underneath dock Status in gnome-shell package in Ubuntu: New Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+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 1917939] [NEW] windows maximise underneath dock
Public bug reported: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re-maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: windows maximise underneath dock Status in gnome-shell package in Ubuntu: New Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+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 1907239] [NEW] Oh no! Something has gone wrong
Public bug reported: I got the "Oh no!" screen. The likely trigger was when I was playing a game and took a screenshot - where the environment is likely hard to reproduce because the game I'm playing that triggered the scenario isn't out yet. It can be built tho. 1) git clone https://github.com/mcphail/boa 2) git checkout core18 3) snapcraft --use-lxd (wait a while, it's a monster snap) 4) snap install boa*.snap --dangerous 5) snap run boa (wait for game to load to title screen) 6) press ALT+PrintScreen to get a screenshot GNOME crashed at this point, giving me the "Oh no!" screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 8 10:54:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-15 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-20 (78 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1907239/+attachment/5441954/+files/journal.txt -- 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/1907239 Title: Oh no! Something has gone wrong Status in gnome-shell package in Ubuntu: New Bug description: I got the "Oh no!" screen. The likely trigger was when I was playing a game and took a screenshot - where the environment is likely hard to reproduce because the game I'm playing that triggered the scenario isn't out yet. It can be built tho. 1) git clone https://github.com/mcphail/boa 2) git checkout core18 3) snapcraft --use-lxd (wait a while, it's a monster snap) 4) snap install boa*.snap --dangerous 5) snap run boa (wait for game to load to title screen) 6) press ALT+PrintScreen to get a screenshot GNOME crashed at this point, giving me the "Oh no!" screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 8 10:54:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-15 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-20 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907239/+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 1900984] Re: Multi-monitor window-snapping snaps to wrong display
*** This bug is a duplicate of bug 199 *** https://bugs.launchpad.net/bugs/199 It does indeed! Thanks. Looks like upstream marked the linked bug from there as a dupe of https://gitlab.gnome.org/GNOME/mutter/-/issues/1389 which is the 'real' bug marked as fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1493 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1389 https://gitlab.gnome.org/GNOME/mutter/-/issues/1389 -- 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/1900984 Title: Multi-monitor window-snapping snaps to wrong display Status in gnome-shell package in Ubuntu: New Bug description: Summary: Snapping a window to one side of the screen will often snap to the side of the wrong monitor. Steps to reproduce: 1. Have two monitors arranged side by side 2. Open a new application window such as nautilus or a terminal 3a. Grab the right half of the title bar of the window and drag it to the left side of the right monitor. Don't let go or 3b. Grab the left half of the title bar of the window and drag it to the right side of the left monitor. Don't let go - The orange window snapping guide will appear in the correct place 4. Let go of the mouse - The window will snap to the wrong monitor It appears due to the amount of the window hanging over the separation gap between the displays, it will favour snapping to the wrong monitor. Here's a video showing it: https://www.youtube.com/watch?v=bdJ6x9nnvOQ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 09:40:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-15 (67 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-20 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900984/+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 1900984] [NEW] Multi-monitor window-snapping snaps to wrong display
Public bug reported: Summary: Snapping a window to one side of the screen will often snap to the side of the wrong monitor. Steps to reproduce: 1. Have two monitors arranged side by side 2. Open a new application window such as nautilus or a terminal 3a. Grab the right half of the title bar of the window and drag it to the left side of the right monitor. Don't let go or 3b. Grab the left half of the title bar of the window and drag it to the right side of the left monitor. Don't let go - The orange window snapping guide will appear in the correct place 4. Let go of the mouse - The window will snap to the wrong monitor It appears due to the amount of the window hanging over the separation gap between the displays, it will favour snapping to the wrong monitor. Here's a video showing it: https://www.youtube.com/watch?v=bdJ6x9nnvOQ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 09:40:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-15 (67 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-20 (31 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1900984 Title: Multi-monitor window-snapping snaps to wrong display Status in gnome-shell package in Ubuntu: New Bug description: Summary: Snapping a window to one side of the screen will often snap to the side of the wrong monitor. Steps to reproduce: 1. Have two monitors arranged side by side 2. Open a new application window such as nautilus or a terminal 3a. Grab the right half of the title bar of the window and drag it to the left side of the right monitor. Don't let go or 3b. Grab the left half of the title bar of the window and drag it to the right side of the left monitor. Don't let go - The orange window snapping guide will appear in the correct place 4. Let go of the mouse - The window will snap to the wrong monitor It appears due to the amount of the window hanging over the separation gap between the displays, it will favour snapping to the wrong monitor. Here's a video showing it: https://www.youtube.com/watch?v=bdJ6x9nnvOQ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 09:40:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-15 (67 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-20 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900984/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
I added a workaround to the askubuntu post. https://askubuntu.com/a/1266706/612 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Triaged Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+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 1888380] [NEW] Give better experience of migration of deb to snap
Public bug reported: Summary of current state: Back in 19.10 we migrated the deb of chromium to a snap. Users who installed the deb, got snapd and the snap of chromium. Users who already had the deb of chromium, and upgraded, got snapd and the snap. The goal of making the snap was (largely) to reduce the workload on the desktop team in packaging chromium, and to enable the desktop team to publish updates to users very quickly across all supported releases. For users, the goal is to have an up to date chromium browser. For people upgrading, the migration goal was to ensure they kept the browser they'd installed (chromium has never been a default on Ubuntu, but has been on at least one flavour). Feedback from the field: * Some have complained that the Chromium snap has bugs which didn't manifest in the deb (see this very bug tracker) * Some complained that there was no indication that they'd have a deb replaced by a snap (hard to know how many users actually care about this) * Derivative distributions have complained that snapd is being installed "under the covers" or "via the backdoor" (or other pejorative statements) Suggestion for improvement: I believe a fair amount of critique comes from the ignorance of why chromium was migrated to a snap, as most users don't read our blog posts, news articles or release notes. In addition, there's not a tremendous number of user-facing packages which have gone through the deb-to-snap migration, so not a lot of prior art in the field. So it's my believe we should document this better, inform the users better. * At the point of installation of the deb, make it clear that snapd will be installed, followed by the chromium snap (and whatever other content and base snaps are required). * During an upgrade from the deb to the snap, make it clear the deb is being replaced, with similar information to when the snap is installed. * Link to documentation / blog / specific release notes in visible places which makes it clear why this is happening. I'll refrain from suggesting technical solutions because I think we need to discuss the options. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1888380 Title: Give better experience of migration of deb to snap Status in chromium-browser package in Ubuntu: New Bug description: Summary of current state: Back in 19.10 we migrated the deb of chromium to a snap. Users who installed the deb, got snapd and the snap of chromium. Users who already had the deb of chromium, and upgraded, got snapd and the snap. The goal of making the snap was (largely) to reduce the workload on the desktop team in packaging chromium, and to enable the desktop team to publish updates to users very quickly across all supported releases. For users, the goal is to have an up to date chromium browser. For people upgrading, the migration goal was to ensure they kept the browser they'd installed (chromium has never been a default on Ubuntu, but has been on at least one flavour). Feedback from the field: * Some have complained that the Chromium snap has bugs which didn't manifest in the deb (see this very bug tracker) * Some complained that there was no indication that they'd have a deb replaced by a snap (hard to know how many users actually care about this) * Derivative distributions have complained that snapd is being installed "under the covers" or "via the backdoor" (or other pejorative statements) Suggestion for improvement: I believe a fair amount of critique comes from the ignorance of why chromium was migrated to a snap, as most users don't read our blog posts, news articles or release notes. In addition, there's not a tremendous number of user-facing packages which have gone through the deb-to-snap migration, so not a lot of prior art in the field. So it's my believe we should document this better, inform the users better. * At the point of installation of the deb, make it clear that snapd will be installed, followed by the chromium snap (and whatever other content and base snaps are required). * During an upgrade from the deb to the snap, make it clear the deb is being replaced, with similar information to when the snap is installed. * Link to documentation / blog / specific release notes in visible places which makes it clear why this is happening. I'll refrain from suggesting technical solutions because I think we need to discuss the options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1887795] [NEW] snap "chromium" has bad plugs or slots: system-packages-doc
Public bug reported: I just installed chromium on my 20.04 machine. I've not used chromium on this system before. It installed but I get this warning: snap "chromium" has bad plugs or slots: system-packages-doc $ snap install chromium 2020-07-16T11:52:42+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") 2020-07-16T11:52:45+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") chromium 84.0.4147.89 from Canonical✓ installed WARNING: There is 1 new warning. See 'snap warnings'. $ snap version snap2.45.1+20.04.2 snapd 2.45.1+20.04.2 series 16 ubuntu 20.04 kernel 5.4.0-40-generic According to the documentation for system-packages-doc, this isn't available until snapd 2.46+, which isn't available in any channel. https://snapcraft.io/docs/the-system-package-doc-interface channels: latest/stable:2.45.2 2020-07-15 (8542) 31MB - latest/candidate: 2.45.2 2020-07-15 (8542) 31MB - latest/beta: 2.45.1 2020-06-05 (8140) 31MB - latest/edge: 2.45.2+git2005.gfdaa74a 2020-07-16 (8596) 31MB - installed: 2.45.1 (8140) 31MB snapd Perhaps we shouldn't use interfaces which aren't available yet? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: I just installed chromium on my 20.04 machine. I've not used chromium on this system before. It installed but I get this warning: snap "chromium" has bad plugs or slots: system-packages-doc $ snap install chromium 2020-07-16T11:52:42+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") 2020-07-16T11:52:45+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") chromium 84.0.4147.89 from Canonical✓ installed WARNING: There is 1 new warning. See 'snap warnings'. $ snap version snap2.45.1+20.04.2 snapd 2.45.1+20.04.2 series 16 ubuntu 20.04 kernel 5.4.0-40-generic + + According to the documentation for system-packages-doc, this isn't + available until snapd 2.46+, which isn't available in any channel. + https://snapcraft.io/docs/the-system-package-doc-interface + + channels: + latest/stable:2.45.2 2020-07-15 (8542) 31MB - + latest/candidate: 2.45.2 2020-07-15 (8542) 31MB - + latest/beta: 2.45.1 2020-06-05 (8140) 31MB - + latest/edge: 2.45.2+git2005.gfdaa74a 2020-07-16 (8596) 31MB - + installed: 2.45.1 (8140) 31MB snapd + + Perhaps we shouldn't use interfaces which aren't available yet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1887795 Title: snap "chromium" has bad plugs or slots: system-packages-doc Status in chromium-browser package in Ubuntu: New Bug description: I just installed chromium on my 20.04 machine. I've not used chromium on this system before. It installed but I get this warning: snap "chromium" has bad plugs or slots: system-packages-doc $ snap install chromium 2020-07-16T11:52:42+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") 2020-07-16T11:52:45+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") chromium 84.0.4147.89 from Canonical✓ installed WARNING: There is 1 new warning. See 'snap warnings'. $ snap version snap2.45.1+20.04.2 snapd 2.45.1+20.04.2 series 16 ubuntu 20.04 kernel 5.4.0-40-generic According to the documentation for system-packages-doc, this isn't available until snapd 2.46+, which isn't available in any channel. https://snapcraft.io/docs/the-system-package-doc-interface channels: latest/stable:2.45.2 2020-07-15 (8542) 31MB - latest/candidate: 2.45.2 2020-07-15 (8542) 31MB - latest/beta: 2.45.1 2020-06-05 (8140) 31MB - latest/edge: 2.45.2+git2005.gfdaa74a 2020-07-16 (8596) 31MB - installed: 2.45.1 (8140) 31MB snapd Perhaps we shouldn't use interfaces which aren't available yet? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887795/+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 1696594] Re: gnome-font-viewer crashed with SIGSEGV
I appreciate some considerable time has passed since this bug was reported. Does it still occur with newer versions of the font viewer? Was there (if you recall) a particular font file which triggered this? ** Changed in: gnome-font-viewer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1696594 Title: gnome-font-viewer crashed with SIGSEGV Status in gnome-font-viewer package in Ubuntu: Incomplete Bug description: The viewer crashes immediately after trying to open a font file from the file manager. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-font-viewer 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Jun 7 17:29:50 2017 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2017-01-29 (129 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170118) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc08bd7f6ea:mov0x50(%r12),%rdi PC (0x7fc08bd7f6ea) ok source "0x50(%r12)" (0x00f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-font-viewer StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-font-viewer crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-06-04 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1696594/+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 1876440] [NEW] Wrong kernel is booted
Public bug reported: As part of debugging bug #1871687 I was asked to add a ppa and install a new kernel. My system booted not into that kernel, but the older original one shipping in Ubuntu. Steps to reproduce On a zfs/zsys enabled 20.04 system, add ppa:canonical-kernel-team/proposed and update/upgrade. As of today you'll get linux-image-5.4.0-29-generic Reboot Expected outcome Boot to newer linux-image-5.4.0-29-generic kernel Actual outcome Booted to older stock kernel - 5.4.0-21-generic Data: alan@mcp:~$ uname -a Linux mcp 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alan@mcp:~$ dpkg -l linux-image* | grep ^ii ii linux-image-5.4.0-14-generic 5.4.0-14.17 amd64Signed kernel image generic ii linux-image-5.4.0-21-generic 5.4.0-21.25 amd64Signed kernel image generic ii linux-image-5.4.0-28-generic 5.4.0-28.32 amd64Signed kernel image generic ii linux-image-5.4.0-29-generic 5.4.0-29.33 amd64Signed kernel image generic ii linux-image-generic 5.4.0.29.34 amd64Generic Linux kernel image alan@mcp:~$ ls -l /boot total 192029 -rw-r--r-- 1 root root 237718 Apr 22 15:08 config-5.4.0-28-generic -rw-r--r-- 1 root root 237718 Apr 29 14:34 config-5.4.0-29-generic drwxr-xr-x 2 root root5 May 2 06:17 grub lrwxrwxrwx 1 root root 27 May 1 10:36 initrd.img -> initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 86232405 Apr 29 10:09 initrd.img-5.4.0-28-generic -rw-r--r-- 1 root root 86232164 May 1 10:37 initrd.img-5.4.0-29-generic lrwxrwxrwx 1 root root 27 May 1 10:36 initrd.img.old -> initrd.img-5.4.0-28-generic -rw--- 1 root root 4736015 Apr 22 15:08 System.map-5.4.0-28-generic -rw--- 1 root root 4736015 Apr 29 14:34 System.map-5.4.0-29-generic lrwxrwxrwx 1 root root 24 May 1 10:36 vmlinuz -> vmlinuz-5.4.0-29-generic -rw--- 1 root root 11657976 Apr 22 15:43 vmlinuz-5.4.0-28-generic -rw--- 1 root root 11657976 Apr 29 14:54 vmlinuz-5.4.0-29-generic lrwxrwxrwx 1 root root 24 May 1 10:36 vmlinuz.old -> vmlinuz-5.4.0-28-generic alan@mcp:~$ cat /proc/cmdline BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zsys 0.4.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:35:41 2020 InstallationDate: Installed on 2020-03-01 (61 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash RelatedPackageVersions: zfs-initramfs 0.8.3-1ubuntu12 zfsutils-linux 0.8.3-1ubuntu12 SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT rpool 920G 656G 264G- -32%71% 1.00xONLINE - ZFSListcache-bpool: bpool /boot off on on off on off on off bpool/BOOT noneoff on on off on off on off bpool/BOOT/ubuntu_pyyy5h /boot on on on off on off on off ZSYSJournal: -- Logs begin at Mon 2020-04-13 16:16:40 BST, end at Sat 2020-05-02 11:35:46 BST. -- [ 102.002626] mcp zsysd[12235]: alan ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Wrong kernel is booted Status in zsys package in Ubuntu: New Bug description: As part of debugging bug #1871687 I was asked to add a ppa and install a new kernel. My system booted not into that kernel, but the older original one shipping in Ubuntu. Steps to reproduce On a zfs/zsys enabled 20.04 system, add ppa:canonical-kernel-team/proposed and update/upgrade. As of today you'll get linux-image-5.4.0-29-generic Reboot Expected outcome Boot to newer linux-image-5.4.0-29-generic kernel Actual outcome Booted to older stock kernel - 5.4.0-21-generic Data: alan@mcp:~$ uname -a Linux mcp 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alan@mcp:~$ dpkg -l linux-image* | grep ^ii ii linux-image-5.4.0-14-generic 5.4.0-14.17 amd64Signed kernel image generic ii linux-image-5.4.0-21-generic 5.4.0-21.25 amd64Signed kernel image generic ii
[Desktop-packages] [Bug 1869737] Re: App icons shrink or disappear after closing an app folder
Confirmed I'm no longer seeing the tiny-icons thing, but still seeing the pager issue, fully up to date. -- 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/1869737 Title: App icons shrink or disappear after closing an app folder Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: When using a smaller screen resolution like 1366x768, opening and closing a folder inside the applications menu breaks the scaling of the icons. Icons either become very small or disappear. The bug did not occur when using a 1920x1080 display. I've also recorded a little video: https://youtu.be/v98TfvBaxqk ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 11:22:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-28 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869737/+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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
I just ninja'ed the docking.js file as per the change in comment #23 and that fixes both the issue in this bug, and the issue where the icons are all small (as shown here https://www.youtube.com/watch?v=2mZZtClVOSg) Screenshots attached. ** Attachment added: "Screenshot from 2020-04-20 15-21-15.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5357145/+files/Screenshot%20from%202020-04-20%2015-21-15.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in Dash to dock: New Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Attachment added: "Screenshot from 2020-04-20 15-21-23.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5357146/+files/Screenshot%20from%202020-04-20%2015-21-23.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in Dash to dock: New Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+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 1872276] Re: Gnome shell huge app's icon size in the app folder
This seems somewhat dependent on the screen resolution. At 1920x1080 (the most popular screen resolution) our default web browser is "Firefox Web br..." At 1366x768 (the next most popular screen resolution) it's "Firefox W..." It looks like the GNOME stock application names have been optimised for this behaviour, being called short names like "Calendar", "Calculator", "Terminal", "Settings", "Fonts" which fit beneath their icons. Perhaps our stock .desktop files should be examined, and developers encouraged to use shorter names. In 2020, does anyone on Linux really not know that Firefox is a Web browser for example? ** Attachment added: "1366x768.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5352415/+files/1366x768.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872276 Title: Gnome shell huge app's icon size in the app folder Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app folder created in app launcher, the resulting dialog holding apps of app folder are having icon size larger than the other apps shown in the app launcher. How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Drag app icon to create apps folder. 3- As the app folder gets created, click to open it and observe the size of app icons shown by the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:48:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872276/+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 1872276] Re: Gnome shell huge app's icon size in the app folder
** Attachment added: "1920x1080.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5352416/+files/1920x1080.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872276 Title: Gnome shell huge app's icon size in the app folder Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app folder created in app launcher, the resulting dialog holding apps of app folder are having icon size larger than the other apps shown in the app launcher. How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Drag app icon to create apps folder. 3- As the app folder gets created, click to open it and observe the size of app icons shown by the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:48:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872276/+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 1872269] Re: Gnome Shell App Launch Grid random vertical navigation Buttons
Confirmed here on up to date 20.04 1) Click app launcher 2) Click a group 3) Click the page icon on the right 4) Click outside the group Expected behaviour: Group closes Actual behaviour: Additional pages are created, app grid zooms out weirdly. Video showing it: https://www.youtube.com/watch?v=tCnTXBzhU9s -- 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/1872269 Title: Gnome Shell App Launch Grid random vertical navigation Buttons Status in gnome-shell package in Ubuntu: Confirmed Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, shows random number of grid page navigation button on right side. How to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Drag app icon to create apps folder. 3- As the app folder gets created check the number of vertical navigation buttons on the right side, few of them are not clickable. And this wont get fix until you will restart the shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:09:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872269/+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 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04
Reproduced this on up to date 20.04 1. Drag two icons into a group 2. Click group 3. Click group title 4. Click outside group title Shell locks up Video showing it: https://www.youtube.com/watch?v=7nqyHx0WMPY -- 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/1872268 Title: Gnome Shell completely freezes Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872268/+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 1869981] Re: Printer notification every day at midnight
I am getting it on 3 machines. One is a clean install of 20.04 from the media dated 20200301. Another is an upgrade done some weeks back which was previously 18.04 installed from media dated 20190210. I can't tell you when I started getting it, but it's been a while. The clean install has been getting it and I just thought it was because I was getting software updates that restarted cups or something. Then I noticed a couple of days ago it happens to all the machines at midnight. Then I waited a couple of days before reporting the bug, to confirm that's the case. The screenshot is a collection of 3 notifications over 3 nights. I don't recall seeing it on older releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight Status in cups package in Ubuntu: Incomplete Bug description: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+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 1869981] [NEW] Printer notification every day at midnight
Public bug reported: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-04-01 00-01-14.png" https://bugs.launchpad.net/bugs/1869981/+attachment/5343944/+files/Screenshot%20from%202020-04-01%2000-01-14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight Status in cups package in Ubuntu: New Bug description: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Tested with the latest packages in proposed and it's fixed, I can now install and play Minecraft. Thank you! <3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
I have proposed enabled. $ apt-cache policy libpango-1.0-0 libpango-1.0-0: Installed: 1.44.7-2ubuntu1 Candidate: 1.44.7-2ubuntu1 Version table: *** 1.44.7-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.44.7-2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
This doesn't seem properly fixed... dpkg: dependency problems prevent configuration of minecraft-launcher: minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however: Package libpango1.0-0 is not installed. Version of libpango1.0-0 on system, provided by libpango-1.0-0:amd64, is . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] [NEW] Removing libpango1.0-0 broke Minecraft Launcher
Public bug reported: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Confirmed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1868083] Re: gnome-shell process "estabilished"
Looks like gnome-shell is checking for updates to extensions on startup. https://gitlab.gnome.org/GNOME/gnome- shell/commit/db9ef11f2893eae0905b091be361ff5417156beb?merge_request_iid=945 There is an upstream PR to add an option to turn this behavior off. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1099 -- 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/1868083 Title: gnome-shell process "estabilished" Status in gnome-shell package in Ubuntu: New Bug description: I opened a discussion on the Ubuntu forum (https://discourse.ubuntu.com/t/gnome-shell-process/14870), not knowing if it was a bug or if expected, but as recommended I'm reporting the bug here. "Hello I don’t know if it’s a bug, or if it’s the right place to discuss this, in case you let me know and move on. Recently a user reported this problem to me, at the first installation of Ubuntu 20.04 by giving the command “ss -stp” the system is found (checked also me and I also find it that way) that constantly communicates in" estabilished “with” 8.43.85.13:https users: ((“gnome-shell”, pid = 3800, fd = 34)) ". It has no active data diagnostics. If the process ends, obviously the desktop ends. Do you by any chance know why gnome-shell activates this process on the system?" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:27:02 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+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 1867598] [NEW] Inconsistency in naming of "Permissions & Access"
Public bug reported: Steps to reproduce * Install a snap (such as sosumi) * Open gnome-control-center * In Applications section, search for the snap Outcome * Note the permissions are listed, some with descriptive text, and some with technical names Expected outcome * All permissions should have human-readable text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 09:23:44 2020 InstallationDate: Installed on 2020-03-12 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-03-16 09-26-51.png" https://bugs.launchpad.net/bugs/1867598/+attachment/5337499/+files/Screenshot%20from%202020-03-16%2009-26-51.png ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1867598 Title: Inconsistency in naming of "Permissions & Access" Status in gnome-control-center package in Ubuntu: New Bug description: Steps to reproduce * Install a snap (such as sosumi) * Open gnome-control-center * In Applications section, search for the snap Outcome * Note the permissions are listed, some with descriptive text, and some with technical names Expected outcome * All permissions should have human-readable text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 09:23:44 2020 InstallationDate: Installed on 2020-03-12 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867598/+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 1867067] [NEW] ERROR context deadline exceeded
Public bug reported: ( Oddly, "ubuntu-bug zsys" didn't work, I clicked send and nothing happened ) When I install new packages, or do significant updates on my laptop, I often see the following error. ERROR context deadline exceeded This usually happens after "Saving system state" then a pause of some seconds. This feels like a bad thing? ** Affects: zsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1867067 Title: ERROR context deadline exceeded Status in zsys package in Ubuntu: New Bug description: ( Oddly, "ubuntu-bug zsys" didn't work, I clicked send and nothing happened ) When I install new packages, or do significant updates on my laptop, I often see the following error. ERROR context deadline exceeded This usually happens after "Saving system state" then a pause of some seconds. This feels like a bad thing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1867067/+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 1859955] Re: Long delays and repeated flashing when docking laptop with multiple monitors
I'm happy for this to be a low priority / wishlist bug. Ultimately it works, it's just a pretty ugly / nasty experience for the user. -- 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/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859955] Re: Long delays and repeated flashing when docking laptop with multiple monitors
Would it help for me to bring the docking station to Frankfurt in March? We could get a couple of displays and do some debugging? -- 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/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859955] Re: Long delays and repeated flashing when docking laptop with multiple monitors
Apologies for the noise of filing the same thing twice. I'm old. Here's the requested logs. ** Attachment added: "bug1859955.tgz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+attachment/5321050/+files/bug1859955.tgz -- 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/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859970] [NEW] orange tint in screenshots when running wayland
Public bug reported: All my screenshots taken on 20.04 with wayland have an orange tint to them. This appears to be the overlay which you get when selecting an area. Full screen screenshots and window screenshots are unaffected, only area screenshots appear to have the problem. Steps to reproduce Login to a wayland session Hold down Shift and Press PrintScreen Select an area to screenshot Navigate to ~/Pictures Open the picture you just took Expected outcome Screenshot of area taken as it would have been on screen Actual outcome Screenshot is taken, but has an orange border and overlay. (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:50:50 2020 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "Screenshot from 2020-01-16 11-49-52.png" https://bugs.launchpad.net/bugs/1859970/+attachment/5320829/+files/Screenshot%20from%202020-01-16%2011-49-52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1859970 Title: orange tint in screenshots when running wayland Status in gnome-screenshot package in Ubuntu: New Bug description: All my screenshots taken on 20.04 with wayland have an orange tint to them. This appears to be the overlay which you get when selecting an area. Full screen screenshots and window screenshots are unaffected, only area screenshots appear to have the problem. Steps to reproduce Login to a wayland session Hold down Shift and Press PrintScreen Select an area to screenshot Navigate to ~/Pictures Open the picture you just took Expected outcome Screenshot of area taken as it would have been on screen Actual outcome Screenshot is taken, but has an orange border and overlay. (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:50:50 2020 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1859970/+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 1859955] Re: Display freaks out when external monitors are attached
Comparison: Ubuntu on Wayland on same hardware: https://www.youtube.com/watch?v=rw0cq5FwpHU Less flicker than Ubuntu, and faster it seems. Around 13 seconds. -- 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/1859955 Title: Display freaks out when external monitors are attached Status in gnome-shell package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859955] Re: Display freaks out when external monitors are attached
Comparison: Windows 10 on the same hardware: https://www.youtube.com/watch?v=VEvidzgedGk Process takes 5 seconds, no flicker. -- 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/1859955 Title: Display freaks out when external monitors are attached Status in gnome-shell package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859955] [NEW] Display freaks out when external monitors are attached
Public bug reported: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1859955 Title: Display freaks out when external monitors are attached Status in gnome-shell package in Ubuntu: New Bug description: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+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 1859320] Re: Multiple sign-in options in menu of Ubuntu Software
They appear to both have been removed. Does this impact my ability to see my own private or unlisted snaps? I may want to publish a snap, make it private or unlisted but still be able to review what it looks like in the store. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1859320 Title: Multiple sign-in options in menu of Ubuntu Software Status in gnome-software package in Ubuntu: New Bug description: Why does Ubuntu Software have (effectively) two sign in / sign out options for the same thing? Steps to reproduce * Install 20.04 (or indeed 19.10, not tested on previous releases) * Launch Ubuntu Software Expected behaviour * Option to sign in to Snap Store should exist * Option to sign in to Ubuntu One should not exist Actual behaviour * Options for signing into Ubuntu One and Snap Store are present ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:29:11 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu11 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859320/+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 1859320] [NEW] Multiple sign-in options in menu of Ubuntu Software
Public bug reported: Why does Ubuntu Software have (effectively) two sign in / sign out options for the same thing? Steps to reproduce * Install 20.04 (or indeed 19.10, not tested on previous releases) * Launch Ubuntu Software Expected behaviour * Option to sign in to Snap Store should exist * Option to sign in to Ubuntu One should not exist Actual behaviour * Options for signing into Ubuntu One and Snap Store are present ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:29:11 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu11 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-01-12 10-28-59.png" https://bugs.launchpad.net/bugs/1859320/+attachment/5319371/+files/Screenshot%20from%202020-01-12%2010-28-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1859320 Title: Multiple sign-in options in menu of Ubuntu Software Status in gnome-software package in Ubuntu: New Bug description: Why does Ubuntu Software have (effectively) two sign in / sign out options for the same thing? Steps to reproduce * Install 20.04 (or indeed 19.10, not tested on previous releases) * Launch Ubuntu Software Expected behaviour * Option to sign in to Snap Store should exist * Option to sign in to Ubuntu One should not exist Actual behaviour * Options for signing into Ubuntu One and Snap Store are present ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:29:11 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu11 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859320/+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 1859319] [NEW] widget factory slighty too wide for common 1366x768 display
Public bug reported: I'm using a ThinkPad X220 to test the Ubuntu default theme. It has a wildly common 1366x768 display panel. At the time of writing, around 25% of installs have such a resolution - https://ubuntu.com/desktop/statistics The default non-hiding 48px launcher, and width of the widget factory, means that it's impossible to get the entire application on screen at once. There appears to be some space which could be saved by shrinking horizontally a couple of components on each page. Steps to reproduce * Install Ubuntu 20.04. * Set system resolution to 1366x768 * Install gtk3-examples * Alt-f2, gtk3-widget-factory Expected outcome * Entire widget factory should fit on the screen Actual outcome * The widget factory window is off the right hand side of the screen Workaround Set the launcher to auto hide, to make room. I don't consider this suitable, because part of the point of gtk widget factory is to test the theme, the experience, the out of the box install. Being unable to actually get the window on the screen seems a flawed set of tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-3-examples 3.24.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:13:41 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-01-12 10-20-48.png" https://bugs.launchpad.net/bugs/1859319/+attachment/5319366/+files/Screenshot%20from%202020-01-12%2010-20-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1859319 Title: widget factory slighty too wide for common 1366x768 display Status in gtk+3.0 package in Ubuntu: New Bug description: I'm using a ThinkPad X220 to test the Ubuntu default theme. It has a wildly common 1366x768 display panel. At the time of writing, around 25% of installs have such a resolution - https://ubuntu.com/desktop/statistics The default non-hiding 48px launcher, and width of the widget factory, means that it's impossible to get the entire application on screen at once. There appears to be some space which could be saved by shrinking horizontally a couple of components on each page. Steps to reproduce * Install Ubuntu 20.04. * Set system resolution to 1366x768 * Install gtk3-examples * Alt-f2, gtk3-widget-factory Expected outcome * Entire widget factory should fit on the screen Actual outcome * The widget factory window is off the right hand side of the screen Workaround Set the launcher to auto hide, to make room. I don't consider this suitable, because part of the point of gtk widget factory is to test the theme, the experience, the out of the box install. Being unable to actually get the window on the screen seems a flawed set of tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-3-examples 3.24.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:13:41 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+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 1856838] [NEW] gnome-shell using a lot of RAM
Public bug reported: Just noticed my laptop was using 3G RAM. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856838 Title: gnome-shell using a lot of RAM Status in gnome-shell package in Ubuntu: New Bug description: Just noticed my laptop was using 3G RAM. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856838/+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 1847597] Re: gnome-control-center cannot access google account
I have tested with a second google account (my canonical one, as opposed to my personal one) and get the exact same error. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42 https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42 ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1847597 Title: gnome-control-center cannot access google account Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+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 1847597] Re: gnome-control-center cannot access google account
I'm seeing the same error. Steps to reproduce: Open System Settings Go to Online Accounts Add a google account Enter username / password I then get the same dialog as the reporter of this bug. I'm on Ubuntu 19.10. This smacks of our online accounts api key being revoked / rate-limited or otherwise restricted by Google. ** Attachment added: "Screenshot from 2019-11-07 20-13-19.png" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1847597/+attachment/5303569/+files/Screenshot%20from%202019-11-07%2020-13-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1847597 Title: gnome-control-center cannot access google account Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+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 1851127] Re: app page shows no install progress
The output of journalctl -b 0. Having difficulty reproducing the issue now :( ** Attachment added: "foo.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+attachment/5303028/+files/foo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress Status in gnome-software package in Ubuntu: Incomplete Bug description: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+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 1851127] Re: app page shows no install progress
** Attachment added: "Screenshot from 2019-11-03 11-42-19.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+attachment/5302434/+files/Screenshot%20from%202019-11-03%2011-42-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress Status in gnome-software package in Ubuntu: New Bug description: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+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 1851127] [NEW] app page shows no install progress
Public bug reported: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot from 2019-11-03 11-42-13.png" https://bugs.launchpad.net/bugs/1851127/+attachment/5302430/+files/Screenshot%20from%202019-11-03%2011-42-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress Status in gnome-software package in Ubuntu: New Bug description: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+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 1850174] [NEW] This is not a bug, please ignore - just testing
Public bug reported: Impact. Impact of the bug. Steps to reproduce 1.. this 2. that 3. also this Expected outcome Page loads What actually happened Page didn't load ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0+build2-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BuildID: 20191021062727 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 15:43:22 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-10-27 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20191021062727 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- 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/1850174 Title: This is not a bug, please ignore - just testing Status in firefox package in Ubuntu: Confirmed Bug description: Impact. Impact of the bug. Steps to reproduce 1.. this 2. that 3. also this Expected outcome Page loads What actually happened Page didn't load ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0+build2-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BuildID: 20191021062727 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 15:43:22 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:930 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-10-27 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20191021062727 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850174/+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 1850052] [NEW] installing zsys breaks desktop login
Public bug reported: I installed zsys on an up to date 19.10 system and can now no longer login. Removing zsys from a tty does not solve the problem. The home partition is no longer available - I have "lost" all my files, which were there before I installed zsys and rebooted Steps to reproduce. 1. Install 19.10 using experimental ZFS disk partitioning. 2. Complete the first run wizard 3. Install all updates 4. sudo apt install zsys 5. reboot 6. Attempt to login to the desktop Actual outcome * GDM accepts user/password, clears screen, looks like desktop is about to start, then I get dropped back to GDM Expected outcome * Login successful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys 0.2.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 14:50:10 2019 InstallationDate: Installed on 2019-10-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - I installed zsys on an up to date 19.10 system and can now no longer - login. + I installed zsys on an up to date 19.10 system and can now no longer login. Removing zsys from a tty does not solve the problem. + The home partition is no longer available - I have "lost" all my files, which were there before I installed zsys and rebooted Steps to reproduce. - 1. Install 19.10 + 1. Install 19.10 using experimental ZFS disk partitioning. 2. Complete the first run wizard 3. Install all updates 4. sudo apt install zsys 5. reboot 6. Attempt to login to the desktop Actual outcome * GDM accepts user/password, clears screen, looks like desktop is about to start, then I get dropped back to GDM Expected outcome * Login successful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys 0.2.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 14:50:10 2019 InstallationDate: Installed on 2019-10-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zsys 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 zsys in Ubuntu. https://bugs.launchpad.net/bugs/1850052 Title: installing zsys breaks desktop login Status in zsys package in Ubuntu: New Bug description: I installed zsys on an up to date 19.10 system and can now no longer login. Removing zsys from a tty does not solve the problem. The home partition is no longer available - I have "lost" all my files, which were there before I installed zsys and rebooted Steps to reproduce. 1. Install 19.10 using experimental ZFS disk partitioning. 2. Complete the first run wizard 3. Install all updates 4. sudo apt install zsys 5. reboot 6. Attempt to login to the desktop Actual outcome * GDM accepts user/password, clears screen, looks like desktop is about to start, then I get dropped back to GDM Expected outcome * Login successful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zsys 0.2.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 14:50:10 2019 InstallationDate: Installed on 2019-10-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1850052/+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 1849955] [NEW] Display jumps on dock/undock and on volume/brightness overlay
Public bug reported: I often dock/undock my laptop, introducing two additional displays. Every time I dock/undock (and when using the volume/brightness controls after undocking) the display jumps about. Here's a video showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8 Steps to reproduce. * Plug laptop into a docking station (possibly just attach an external display) * Configure the desktop running spanning all displays * Remove the external display / undock * Observe the laptop desktop jump around * Use the brightness or volume adjust keys * Observe the laptop desktop jump around Expected behaviour * The desktop should not jump around ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 14:15:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (628 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1849955 Title: Display jumps on dock/undock and on volume/brightness overlay Status in gnome-shell package in Ubuntu: New Bug description: I often dock/undock my laptop, introducing two additional displays. Every time I dock/undock (and when using the volume/brightness controls after undocking) the display jumps about. Here's a video showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8 Steps to reproduce. * Plug laptop into a docking station (possibly just attach an external display) * Configure the desktop running spanning all displays * Remove the external display / undock * Observe the laptop desktop jump around * Use the brightness or volume adjust keys * Observe the laptop desktop jump around Expected behaviour * The desktop should not jump around ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 14:15:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (628 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849955/+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 1848053] [NEW] (or swipe finger) text is barely readble on login screen
Public bug reported: With fingerprint login enabled per user, the sub-prompt on the login screen to enter password "(or swipe finger)" is really hard to read on the purple background. Steps to reproduce On a finger-print-reader equipped device Go to Settings -> Details -> Users -> Click the button next to "Fingerprint login" Enrol a finger Lock the screen Actual behaviour "(or swipe finger)" text beneath password prompt is dark and hard to read Expected behaviour "(or swipe finger)" text should be clear and readable ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yaru-theme-gnome-shell 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 16:38:06 2019 Dependencies: InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1848053 Title: (or swipe finger) text is barely readble on login screen Status in yaru-theme package in Ubuntu: New Bug description: With fingerprint login enabled per user, the sub-prompt on the login screen to enter password "(or swipe finger)" is really hard to read on the purple background. Steps to reproduce On a finger-print-reader equipped device Go to Settings -> Details -> Users -> Click the button next to "Fingerprint login" Enrol a finger Lock the screen Actual behaviour "(or swipe finger)" text beneath password prompt is dark and hard to read Expected behaviour "(or swipe finger)" text should be clear and readable ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yaru-theme-gnome-shell 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 16:38:06 2019 Dependencies: InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1848053/+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 1848009] Re: Delay launching application launcher gets longer the more apps are open
Yes, confirmed the Activites view is slow to load also. -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open Status in gnome-shell package in Ubuntu: Confirmed Bug description: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+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 1848009] [NEW] Delay launching application launcher gets longer the more apps are open
Public bug reported: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. + On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. + + Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848009 Title: Delay launching application launcher gets longer the more apps are open Status in gnome-shell package in Ubuntu: New Bug description: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present
[Desktop-packages] [Bug 1847740] [NEW] Auto-hide dock causes clock/notification to move
Public bug reported:
When disabling / enabling hiding of the dock - or indeed changing the
width of the dock - in system settings - the clock / notification area
moves. These feels wrong. The clock is not related to the dock size, and
should not move with it. The clock should be in the centre of the
display, not the centre of the usable area of the desktop I believe.
Steps to reproduce
Open system settings
Select dock
change the toggle to auto-hide the dock
Observe the clock move with the toggle
Expected behaviour
Clock/notification are is locked to the middle of the screen.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 11:11:44 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry',
'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['org-gnome-screenshot', 'update-manager']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-10-11 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
** Attachment added: "Screenshot from 2019-10-11 11-11-16.png"
https://bugs.launchpad.net/bugs/1847740/+attachment/5296549/+files/Screenshot%20from%202019-10-11%2011-11-16.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1847740
Title:
Auto-hide dock causes clock/notification to move
Status in gnome-shell package in Ubuntu:
New
Bug description:
When disabling / enabling hiding of the dock - or indeed changing the
width of the dock - in system settings - the clock / notification area
moves. These feels wrong. The clock is not related to the dock size,
and should not move with it. The clock should be in the centre of the
display, not the centre of the usable area of the desktop I believe.
Steps to reproduce
Open system settings
Select dock
change the toggle to auto-hide the dock
Observe the clock move with the toggle
Expected behaviour
Clock/notification are is locked to the middle of the screen.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 11:11:44 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['org-gnome-screenshot', 'update-manager']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-10-11 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847740/+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 1847740] Re: Auto-hide dock causes clock/notification to move
** Attachment added: "Screenshot from 2019-10-11 11-11-14.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847740/+attachment/5296554/+files/Screenshot%20from%202019-10-11%2011-11-14.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1847740
Title:
Auto-hide dock causes clock/notification to move
Status in gnome-shell package in Ubuntu:
New
Bug description:
When disabling / enabling hiding of the dock - or indeed changing the
width of the dock - in system settings - the clock / notification area
moves. These feels wrong. The clock is not related to the dock size,
and should not move with it. The clock should be in the centre of the
display, not the centre of the usable area of the desktop I believe.
Steps to reproduce
Open system settings
Select dock
change the toggle to auto-hide the dock
Observe the clock move with the toggle
Expected behaviour
Clock/notification are is locked to the middle of the screen.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 11 11:11:44 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children'
b"['org-gnome-screenshot', 'update-manager']"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2019-10-11 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847740/+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 1847738] [NEW] Empty item in folder context menu
Public bug reported: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot from 2019-10-11 11-01-55.png" https://bugs.launchpad.net/bugs/1847738/+attachment/5296545/+files/Screenshot%20from%202019-10-11%2011-01-55.png -- 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/1847738 Title: Empty item in folder context menu Status in nautilus package in Ubuntu: New Bug description: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1847738/+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 1845017] Re: Desktop hard lockup in 19.10
Having tremendous difficulty triggering a crash now :( -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1846477] Re: Dragging icons in launcher is slow until shell restarted
As a separate test I have reproduced this on my X220 which has now got an uptime of 3 days with zero applications running besides gnome terminal. When originally booted it was fast as expected. But now, after a number of lock/unlock cycles and 3 days uptime, it's slow to move icons around the launcher. -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+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 1846477] Re: Dragging icons in launcher is slow until shell restarted
I don't know if it's related, but I frequently add and remove external displays. Maybe a couple of times a day. I plug it into the docking station when I work. When I do, the shell freaks out a bit and then settles down. I wonder if the dock is not handling the rapid change in screen resolution well? -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+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 1846477] Re: Dragging icons in launcher is slow until shell restarted
Seems to happen after a couple of days uptime of the shell. I am also seeing the little triangle pointer lingering both on the indicator area, but not seen it that I recall on the dock. I have a bunch of things favourited apps (see screenshot) but nothing out of the ordinary - as in not a ton of things. Is there some way I can get debug logs or traces from the extension? ** Attachment added: "Screenshot from 2019-10-05 10-49-15.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+attachment/5294499/+files/Screenshot%20from%202019-10-05%2010-49-15.png -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+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 1846477] Re: Dragging icons in launcher is slow until shell restarted
First gif was with 3 screens attached (internal panel and two 1080p screens). This gif is with the laptop screen only enabled (laptop removed from dock) ** Attachment added: "Peek 2019-10-03 12-17.gif" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+attachment/5293972/+files/Peek%202019-10-03%2012-17.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+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 1846477] Re: Dragging icons in launcher is slow until shell restarted
Finally this gif is after alt-f2, r. ** Attachment added: "Peek 2019-10-03 12-22.gif" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+attachment/5293973/+files/Peek%202019-10-03%2012-22.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+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 1846477] [NEW] Dragging icons in launcher is slow until shell restarted
Public bug reported: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Peek 2019-10-03 12-14.gif" https://bugs.launchpad.net/bugs/1846477/+attachment/5293965/+files/Peek%202019-10-03%2012-14.gif -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell package in Ubuntu: New Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846477/+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 1845017] Re: Desktop hard lockup in 19.10
Had another lockup, it seemed to lock up the gpu, so when trying to reboot via ssh it was hanging. ** Attachment added: "pb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+attachment/5290940/+files/pb.txt -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1845017] Re: Desktop hard lockup in 19.10
It's hard to reproduce. I've had it twice today though. Once when I was doing a "snap refresh" and one when using lxd. -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1845017] [NEW] Desktop hard lockup in 19.10
Public bug reported: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1831903] [NEW] Microphone audio pitch changes sometimes
Public bug reported: For a little while now on my KDE Neon (based on Ubuntu 18.04) system, while I'm talking to someone my voice will suddenly drop in pitch. People have likened it to "Barry White" mode because my voice sounds like his. This can happen in Mumble, on a hangout, using riot or pretty much any audio recording app. Killing pulseaudio to restart it, works around the issue. However it sometimes comes back minutes later. It's quite common having this - but I use my microphone more than most users as I record podcasts, do live YouTube videos and have constant audio/video meetings with people. I have only seen this happen on 18.04 based systems, both this KDE Neon and my main Ubuntu 18.04 rig. Since updating that rig to 19.10 I've not seen the issue. So I suspect it's something strange in pulseaudio in 18.04 ProblemType: Bug DistroRelease: KDE neon Plasma LTS 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 21396 F pulseaudio /dev/snd/controlC0: alan 21396 F pulseaudio CurrentDesktop: KDE Date: Thu Jun 6 14:43:48 2019 InstallationDate: Installed on 2018-02-04 (486 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-10-05 (243 days ago) dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-02-27T21:50:13.756477 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1831903 Title: Microphone audio pitch changes sometimes Status in pulseaudio package in Ubuntu: New Bug description: For a little while now on my KDE Neon (based on Ubuntu 18.04) system, while I'm talking to someone my voice will suddenly drop in pitch. People have likened it to "Barry White" mode because my voice sounds like his. This can happen in Mumble, on a hangout, using riot or pretty much any audio recording app. Killing pulseaudio to restart it, works around the issue. However it sometimes comes back minutes later. It's quite common having this - but I use my microphone more than most users as I record podcasts, do live YouTube videos and have constant audio/video meetings with people. I have only seen this happen on 18.04 based systems, both this KDE Neon and my main Ubuntu 18.04 rig. Since updating that rig to 19.10 I've not seen the issue. So I suspect it's something strange in pulseaudio in 18.04 ProblemType: Bug DistroRelease: KDE neon Plasma LTS 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 21396 F pulseaudio /dev/snd/controlC0: alan 21396 F pulseaudio CurrentDesktop: KDE Date: Thu Jun 6 14:43:48 2019 InstallationDate: Installed on 2018-02-04 (486 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-10-05 (243 days ago) dmi.bios.date: 12/14/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET67WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET67WW(1.31):bd12/14/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450
[Desktop-packages] [Bug 1824188] [NEW] Software tab is empty on clean 19.04 install
Public bug reported: Did a clean install of Ubuntu 19.04. Rebooted into the new installation. Started using it, and after a short while the gnome initial setup appeared. I went through each step, but the final one "You're ready to go!" should have some software listed from the snap store, but doesn't. I have a working internet connection (I'm filing list bug from it) See screenshot ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-initial-setup 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 17:13:41 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410) SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Screenshot from 2019-04-10 17-10-14.png" https://bugs.launchpad.net/bugs/1824188/+attachment/5254734/+files/Screenshot%20from%202019-04-10%2017-10-14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824188 Title: Software tab is empty on clean 19.04 install Status in gnome-initial-setup package in Ubuntu: New Bug description: Did a clean install of Ubuntu 19.04. Rebooted into the new installation. Started using it, and after a short while the gnome initial setup appeared. I went through each step, but the final one "You're ready to go!" should have some software listed from the snap store, but doesn't. I have a working internet connection (I'm filing list bug from it) See screenshot ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-initial-setup 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 17:13:41 2019 InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410) SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1824188/+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 1821349] [NEW] package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I was upgrading a machine from 18.10 to 19.04 with "do-release-upgrade -d". This system was updated from 14.04 to 16.04 to 18.04 to 18.10, and today from 18.10 to 19.04. Looks like this crashed towards the end of the upgrade. After reporting this bug it proceeded to dpkg --configure -a, and once the upgrade finished, I did an apt-get update and apt-get dist-upgrade. Seems okay. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Fri Mar 22 13:03:18 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-12-23 (1184 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.5ubuntu1 apt 1.8.0 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1821349 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: I was upgrading a machine from 18.10 to 19.04 with "do-release-upgrade -d". This system was updated from 14.04 to 16.04 to 18.04 to 18.10, and today from 18.10 to 19.04. Looks like this crashed towards the end of the upgrade. After reporting this bug it proceeded to dpkg --configure -a, and once the upgrade finished, I did an apt-get update and apt-get dist-upgrade. Seems okay. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Fri Mar 22 13:03:18 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-12-23 (1184 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.5ubuntu1 apt 1.8.0 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1821349/+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 1812841] Re: Installing / Removal behaves differently depending on how GNOME Software is launched
I have since rebooted, and now I can't reproduce this anymore :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1812841 Title: Installing / Removal behaves differently depending on how GNOME Software is launched Status in gnome-software package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Invalid Bug description: Summary. Launching GS manually from the launcher, and navigating to an app and clicking install works fine. Launching GS via clicking a link in the snapcraft webstore causes GS to require a snap login. Scenario. Trying to install software using the green "Install" button via the snapcraft web store. Steps to reproduce 1) Open Firefox on Ubuntu 18.04 2) Visit https://snapcraft.io/wps-office-all-lang-no-internet 3) Click the green "Install" button 4) Click "View in Desktop Store" 5) Click "Software" in the popup box to launch GNOME Software Observe an error in GS "Unable to install 'WPS Office - All langiages - No internet': authentication was required 6) Click "Install" in GNOME Software Observe an "Authenticate" dialog appears. Expected behaviour. At step 5 no error should occur. At step 6 no popup should appear, app should install. Further. 7) Do not login, close GNOME Software 8) Open GNOME Software from the launcher 9) Search for WPS, click it in the results 10) Click "Install" Observe that the software installs fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 10:52:35 2019 InstallationDate: Installed on 2018-10-07 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1812841/+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 1812841] [NEW] Installing / Removal behaves differently depending on how GNOME Software is launched
Public bug reported: Summary. Launching GS manually from the launcher, and navigating to an app and clicking install works fine. Launching GS via clicking a link in the snapcraft webstore causes GS to require a snap login. Scenario. Trying to install software using the green "Install" button via the snapcraft web store. Steps to reproduce 1) Open Firefox on Ubuntu 18.04 2) Visit https://snapcraft.io/wps-office-all-lang-no-internet 3) Click the green "Install" button 4) Click "View in Desktop Store" 5) Click "Software" in the popup box to launch GNOME Software Observe an error in GS "Unable to install 'WPS Office - All langiages - No internet': authentication was required 6) Click "Install" in GNOME Software Observe an "Authenticate" dialog appears. Expected behaviour. At step 5 no error should occur. At step 6 no popup should appear, app should install. Further. 7) Do not login, close GNOME Software 8) Open GNOME Software from the launcher 9) Search for WPS, click it in the results 10) Click "Install" Observe that the software installs fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 10:52:35 2019 InstallationDate: Installed on 2018-10-07 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2019-01-22 10-52-01.png" https://bugs.launchpad.net/bugs/1812841/+attachment/5231421/+files/Screenshot%20from%202019-01-22%2010-52-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1812841 Title: Installing / Removal behaves differently depending on how GNOME Software is launched Status in gnome-software package in Ubuntu: New Bug description: Summary. Launching GS manually from the launcher, and navigating to an app and clicking install works fine. Launching GS via clicking a link in the snapcraft webstore causes GS to require a snap login. Scenario. Trying to install software using the green "Install" button via the snapcraft web store. Steps to reproduce 1) Open Firefox on Ubuntu 18.04 2) Visit https://snapcraft.io/wps-office-all-lang-no-internet 3) Click the green "Install" button 4) Click "View in Desktop Store" 5) Click "Software" in the popup box to launch GNOME Software Observe an error in GS "Unable to install 'WPS Office - All langiages - No internet': authentication was required 6) Click "Install" in GNOME Software Observe an "Authenticate" dialog appears. Expected behaviour. At step 5 no error should occur. At step 6 no popup should appear, app should install. Further. 7) Do not login, close GNOME Software 8) Open GNOME Software from the launcher 9) Search for WPS, click it in the results 10) Click "Install" Observe that the software installs fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 10:52:35 2019 InstallationDate: Installed on 2018-10-07 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1812841/+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 1795702] [NEW] snap-store reports incorrect OS to odrs
Public bug reported: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_20181002_173237.png" https://bugs.launchpad.net/bugs/1795702/+attachment/5196001/+files/Screenshot_20181002_173237.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1795702 Title: snap-store reports incorrect OS to odrs Status in gnome-software package in Ubuntu: New Bug description: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+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 1774395] [NEW] ubuntu-report doesn't capture GPU on virtualbox
Public bug reported:
I have an 18.04 Ubuntu MATE system which is running in VirtualBox
5.2.10. If I run ubuntu-report, I see no listing of GPU. I certainly do
have a GPU, because I'm typing this bug report in a browser window in
the VM :)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox
Graphics Adapter (prog-if 00 [VGA controller])
Flags: fast devsel, IRQ 18
Memory at e000 (32-bit, prefetchable) [size=16M]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Kernel driver in use: vboxvideo
Kernel modules: vboxvideo
{
"Version": "18.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"CPU": [
{
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "94",
"Stepping": "3"
}
],
"Arch": "amd64",
"RAM": 4,
"Partitions": [
41
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "MATE",
"Name": "mate",
"Type": "x11"
},
"Timezone": "Europe/London",
"Install": {
"Media": "Ubuntu-MATE 18.04 LTS \"Bionic Beaver\" - Release amd64
(20180426)",
"Type": "GTK",
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"1": "language",
"14": "console_setup",
"18": "console_setup",
"21": "prepare",
"30": "partman",
"43": "start_install",
"47": "timezone",
"50": "usersetup",
"86": "user_done",
"420": "done"
}
}
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-report 1.0.11
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Thu May 31 12:04:10 2018
Dependencies:
gcc-8-base 8-20180414-1ubuntu2
libc6 2.27-3ubuntu1
libgcc1 1:8-20180414-1ubuntu2
InstallationDate: Installed on 2018-05-11 (19 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
SourcePackage: ubuntu-report
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-report (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1774395
Title:
ubuntu-report doesn't capture GPU on virtualbox
Status in ubuntu-report package in Ubuntu:
Confirmed
Bug description:
I have an 18.04 Ubuntu MATE system which is running in VirtualBox
5.2.10. If I run ubuntu-report, I see no listing of GPU. I certainly
do have a GPU, because I'm typing this bug report in a browser window
in the VM :)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox
Graphics Adapter (prog-if 00 [VGA controller])
Flags: fast devsel, IRQ 18
Memory at e000 (32-bit, prefetchable) [size=16M]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Kernel driver in use: vboxvideo
Kernel modules: vboxvideo
{
"Version": "18.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"CPU": [
{
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "94",
"Stepping": "3"
}
],
"Arch": "amd64",
"RAM": 4,
"Partitions": [
41
],
"Autologin": false,
"LivePatch": false,
"Session": {
"DE": "MATE",
"Name": "mate",
"Type": "x11"
},
"Timezone": "Europe/London",
"Install": {
"Media": "Ubuntu-MATE 18.04 LTS \"Bionic Beaver\" - Release amd64
(20180426)",
"Type": "GTK",
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": true,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"1": "language",
"14": "console_setup",
"18": "console_setup",
"21": "prepare",
"30": "partman",
"43": "start_install",
"47": "timezone",
"50": "usersetup",
"86": "user_done",
"420": "done"
}
}
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-report 1.0.11
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Thu May 31 12:04:10 2018
Dependencies:
gcc-8-base 8-20180414-1ubuntu2
libc6 2.27-3ubuntu1
libgcc1 1:8-20180414-1ubuntu2
InstallationDate: Installed on 2018-05-11 (19 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" -
[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV
Just had this again. https://errors.ubuntu.com/oops/0c692c82-643d-11e8-b7b3-fa163e8d4bab Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' Is the error I see in the xorg crash reports. I -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1760104 Title: Xorg crashed with SIGSEGV Status in snapd: New Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Installed a snap, immediately after I installed it, the machine froze and then x crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 30 14:15:35 2018 Disassembly: => 0x7f6b0008: Cannot access memory at address 0x7f6b0008 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541] InstallationDate: Installed on 2018-02-13 (44 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Notebook P65_P67RGRERA ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f6b0008:Cannot access memory at address 0x7f6b0008 PC (0x7f6b0008) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: () () () () start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463 Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Mar 29 14:49:09 2018 xserver.configfile: default xserver.errors: client bug: Invalid path /dev/input/event7 systemd-logind: failed to take device /dev/input/event19: No such device client bug: Invalid path
[Desktop-packages] [Bug 1773369] [NEW] Editors pics are random
Public bug reported: In GNOME Software the editors picks are showing 10 of however many are tagged in the store as 'featured'. However the list is randomized. I believe we agreed not to randomize this list, but keep the list the same so we can effectively measure the benefit of being in slot 1 vs slot 10 (for example). Indeed in bug 1705953 and bug 1705953 we make reference to debian/patches/0048-Don-t-randomize-editors-picks.patch which suggests we should indeed not randomize the editors picks, but this doesn't appear to be working. Attached is a screenshot showing the current selection. However the list is as follows:- zenkit notepadqq vscode gravit-designer eclipse sublime-text noson hugo signal-desktop audovia corsixth zulip cloudtag discrographer htop ao codenamelt bitwarden mosquitto wekan nextcloud docker canonical-livepatch hiri ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "Screenshot from 2018-05-25 14-21-20.png" https://bugs.launchpad.net/bugs/1773369/+attachment/5144256/+files/Screenshot%20from%202018-05-25%2014-21-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1773369 Title: Editors pics are random Status in gnome-software package in Ubuntu: Confirmed Bug description: In GNOME Software the editors picks are showing 10 of however many are tagged in the store as 'featured'. However the list is randomized. I believe we agreed not to randomize this list, but keep the list the same so we can effectively measure the benefit of being in slot 1 vs slot 10 (for example). Indeed in bug 1705953 and bug 1705953 we make reference to debian/patches/0048-Don-t-randomize-editors-picks.patch which suggests we should indeed not randomize the editors picks, but this doesn't appear to be working. Attached is a screenshot showing the current selection. However the list is as follows:- zenkit notepadqq vscode gravit-designer eclipse sublime-text noson hugo signal-desktop audovia corsixth zulip cloudtag discrographer htop ao codenamelt bitwarden mosquitto wekan nextcloud docker canonical-livepatch hiri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1773369/+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 1760104] Re: Xorg crashed with SIGSEGV
I've had this again. Here's the crash report links. May 23rd: https://errors.ubuntu.com/oops/18a718fc-5e7e-11e8-a6ec-fa163ed44aae May 10th: https://errors.ubuntu.com/oops/274be904-57ae-11e8-9ec0-fa163ef911dc Feb 27th: https://errors.ubuntu.com/oops/1ce27eb4-1ba0-11e8-a91a-fa163e8d4bab Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' ^ is the first line of the crash report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1760104 Title: Xorg crashed with SIGSEGV Status in snapd: New Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Installed a snap, immediately after I installed it, the machine froze and then x crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 30 14:15:35 2018 Disassembly: => 0x7f6b0008: Cannot access memory at address 0x7f6b0008 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541] InstallationDate: Installed on 2018-02-13 (44 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Notebook P65_P67RGRERA ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f6b0008:Cannot access memory at address 0x7f6b0008 PC (0x7f6b0008) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: () () () () start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463 Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Mar 29 14:49:09 2018
[Desktop-packages] [Bug 1760104] Re: Xorg crashed with SIGSEGV
I've added a task for snapd, because this only happens when I'm doing "snap install" something. Usually at the point when it connects the opengl interface. ** Information type changed from Private to Public ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1760104 Title: Xorg crashed with SIGSEGV Status in snapd: New Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Installed a snap, immediately after I installed it, the machine froze and then x crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-12ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 30 14:15:35 2018 Disassembly: => 0x7f6b0008: Cannot access memory at address 0x7f6b0008 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6541] InstallationDate: Installed on 2018-02-13 (44 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Notebook P65_P67RGRERA ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=d6c2bf6a-9191-40b5-b3f5-ce493dcdec01 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f6b0008:Cannot access memory at address 0x7f6b0008 PC (0x7f6b0008) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing unknown VMA Signal: 11 SourcePackage: nvidia-graphics-drivers StacktraceTop: () () () () start_thread (arg=0x7f6b3c98b700) at pthread_create.c:463 Title: Xorg crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_P67RGRERA dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_P67RGRERA dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Mar 29 14:49:09 2018 xserver.configfile: default xserver.errors: client bug: Invalid path /dev/input/event7 systemd-logind: failed to take device
[Desktop-packages] [Bug 1752359] [NEW] GNOME Software 'snap install' inconsistent state
Public bug reported: GNOME Software thinks I have a snap installed which I just removed. Killing and restarting GNOME Software rectified this. I shouldn't have to kill GNOME Software background process for it to be in sync. Steps to reproduce snap install peek snap install gnome-3-26-1604 snap connect peek:gnome-3-26-1604 gnome-3-26-1604 snap run peek Peek runs. snap remove peek snap remove gnome-3-26-1604 Open GNOME Software Search for Peek (to test re-installing it via G-S) Expected behaviour - Get an [Install] button Actual behaviour - Get a [Launch] button Workaround killall gnome-software gnome-software ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Summary changed: - GNOME Software snap install inconsistent state + GNOME Software 'snap install' inconsistent state -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1752359 Title: GNOME Software 'snap install' inconsistent state Status in gnome-software package in Ubuntu: New Bug description: GNOME Software thinks I have a snap installed which I just removed. Killing and restarting GNOME Software rectified this. I shouldn't have to kill GNOME Software background process for it to be in sync. Steps to reproduce snap install peek snap install gnome-3-26-1604 snap connect peek:gnome-3-26-1604 gnome-3-26-1604 snap run peek Peek runs. snap remove peek snap remove gnome-3-26-1604 Open GNOME Software Search for Peek (to test re-installing it via G-S) Expected behaviour - Get an [Install] button Actual behaviour - Get a [Launch] button Workaround killall gnome-software gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1752359/+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 1751888] [NEW] G-S Says I have an update and I don't
Public bug reported: Running 18.04. I have an update button for Skype in GNOME Software. I am running the latest version though. It seems a bit confused. $ snap version snap2.31.1+18.04 snapd 2.31.1+18.04 series 16 ubuntu 18.04 kernel 4.15.0-10-generic $ snap info skype name: skype summary: One Skype for all your devices. New features. New look. All Skype. publisher: skype contact: https://www.skype.com/ license: unknown description: | (...) snap-id: QRDEfjn4WJYnm0FzDKwqqRZZI77awQEV commands: - skype tracking:edge installed: 8.16.0.4 (16) 109MB classic refreshed: 2018-02-21 07:15:21 + UTC channels: stable:8.16.0.4 (16) 109MB classic candidate: ↑ beta: ↑ edge: ↑ insider/stable:8.17.76.1 (17) 109MB classic insider/candidate: ↑ insider/beta: ↑ insider/edge: ↑ ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1751888 Title: G-S Says I have an update and I don't Status in gnome-software package in Ubuntu: New Bug description: Running 18.04. I have an update button for Skype in GNOME Software. I am running the latest version though. It seems a bit confused. $ snap version snap2.31.1+18.04 snapd 2.31.1+18.04 series 16 ubuntu 18.04 kernel 4.15.0-10-generic $ snap info skype name: skype summary: One Skype for all your devices. New features. New look. All Skype. publisher: skype contact: https://www.skype.com/ license: unknown description: | (...) snap-id: QRDEfjn4WJYnm0FzDKwqqRZZI77awQEV commands: - skype tracking:edge installed: 8.16.0.4 (16) 109MB classic refreshed: 2018-02-21 07:15:21 + UTC channels: stable:8.16.0.4 (16) 109MB classic candidate: ↑ beta: ↑ edge: ↑ insider/stable:8.17.76.1 (17) 109MB classic insider/candidate: ↑ insider/beta: ↑ insider/edge: ↑ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1751888/+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 1751750] Re: Can't zoom in on screenshots
https://gitlab.gnome.org/GNOME/gnome-software/issues/313 - filed upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1751750 Title: Can't zoom in on screenshots Status in gnome-software package in Ubuntu: Triaged Bug description: I can't read the contents of screenshots in GNOME Software. I would like to click on the screenshot to make it larger. Unfortunately clicking a screenshot in GNOME Software does nothing. I'd expect it to 'zoom' in, maybe making the screenshot full screen with left/right arrows to flip between screenshots, and an X to close it and return to the application view. Steps to reproduce Open GNOME Software Click on any application which has screenshots Click on screenshot Expected outcome Screenshot gets bigger Actual outcome Nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1751750/+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 1751750] [NEW] Can't zoom in on screenshots
Public bug reported: I can't read the contents of screenshots in GNOME Software. I would like to click on the screenshot to make it larger. Unfortunately clicking a screenshot in GNOME Software does nothing. I'd expect it to 'zoom' in, maybe making the screenshot full screen with left/right arrows to flip between screenshots, and an X to close it and return to the application view. Steps to reproduce Open GNOME Software Click on any application which has screenshots Click on screenshot Expected outcome Screenshot gets bigger Actual outcome Nothing ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1751750 Title: Can't zoom in on screenshots Status in gnome-software package in Ubuntu: New Bug description: I can't read the contents of screenshots in GNOME Software. I would like to click on the screenshot to make it larger. Unfortunately clicking a screenshot in GNOME Software does nothing. I'd expect it to 'zoom' in, maybe making the screenshot full screen with left/right arrows to flip between screenshots, and an X to close it and return to the application view. Steps to reproduce Open GNOME Software Click on any application which has screenshots Click on screenshot Expected outcome Screenshot gets bigger Actual outcome Nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1751750/+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 1750548] [NEW] Need some way to show multiple banners
Public bug reported: While GNOME Software allows one banner to be shown, it would be great to have multiple banners in rotation. Having multiple banners would enable us to rotate around a bunch of promoted applications rather than have one application stuck there for a while. A discussion was had on the forum. https://forum.snapcraft.io/t /supporting-multiple-featured-snaps-in-gnome-software/3124/7 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750548 Title: Need some way to show multiple banners Status in gnome-software package in Ubuntu: New Bug description: While GNOME Software allows one banner to be shown, it would be great to have multiple banners in rotation. Having multiple banners would enable us to rotate around a bunch of promoted applications rather than have one application stuck there for a while. A discussion was had on the forum. https://forum.snapcraft.io/t /supporting-multiple-featured-snaps-in-gnome-software/3124/7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750548/+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 1750533] [NEW] Proprietary software is labelled red
Public bug reported: Proprietary software delivered as snaps in GNOME Software is highlighted red in the software details. While it's great that we show the license for software, it's not ideal that the implication of the colours is that free=good, proprietary=bad. We should provide software and enable users to make an informed choice what they install, but not make the implication that it's a bad choice. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750533 Title: Proprietary software is labelled red Status in gnome-software package in Ubuntu: New Bug description: Proprietary software delivered as snaps in GNOME Software is highlighted red in the software details. While it's great that we show the license for software, it's not ideal that the implication of the colours is that free=good, proprietary=bad. We should provide software and enable users to make an informed choice what they install, but not make the implication that it's a bad choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750533/+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 1750534] [NEW] Channel selector doesn't look like a button
Public bug reported: In GNOME Software the channel selection item is a green label, but doesn't look like a click-able button. It should be more obviously clickable, so that users understand how to switch channel. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750534 Title: Channel selector doesn't look like a button Status in gnome-software package in Ubuntu: New Bug description: In GNOME Software the channel selection item is a green label, but doesn't look like a click-able button. It should be more obviously clickable, so that users understand how to switch channel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750534/+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 1690280] Re: Classic confined snaps don't install
I have also tested with 3.20.5-0ubuntu0.16.04.8 on 16.04 and this issue is fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install Status in GNOME Software: Confirmed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Apps that use classic confinement show up in search results but don't install. [Test Case] 1. Open GNOME Software 2. Search for a classic snap, e.g. "atom" 3. Install snap Expected result: Either: a) Snap is installed b) Snap is not installed and error given c) Snap is installed but user needs to provide some sort of confirmation since it is not confined. Observed result: Snap is not installed, no error given. [Regression Potential] Patch changes the code path used to request installation of all snap packages. Ensure that strict confined snaps continue to be installed with correct confinement. For example, try installing "ohmygiraffe" via gnome-software, then run "snap info ohmygiraffe" from a terminal. The "installed:" line should not include the word "classic". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+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 1743429] Re: GNOME Software doesn't support animated Gifs for screenshots
** Bug watch added: GNOME Bug Tracker #792602 https://bugzilla.gnome.org/show_bug.cgi?id=792602 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=792602 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1743429 Title: GNOME Software doesn't support animated Gifs for screenshots Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: New Bug description: I am running GNOME Software on Ubuntu 16.04. If I look for Tizonia, it shows the app description and a static screenshot. The media uploaded to the store is actually a gif, but GNOME Software doesn't seem to support it. Steps to reproduce * Open GNOME Software * Search for tizonia * Wait for screenshot to load Expected behaviour * Animated gif plays in the page for the application Actual behaviour * Only the first frame of the animated gif is displayed. See screenshot attached. This is the media as it has been uploaded to the store:- https://dashboard.snapcraft.io/site_media/appmedia/2017/12/tizonia- usage-screencast.gif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 15 17:15:51 2018 InstallationDate: Installed on 2017-07-03 (196 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1743429/+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 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_in
Looking through the individual crashers that happened today, there's something common in the 50 or so I clicked through. They're *all* running kernel 4.4 or below (one person was on 3.13). Nobody seems to be on the HWE kernels. So perhaps there's something which mitigates this issue in HWE kernels. If Robert was debugging and trying to reproduce locally, perhaps he's on a HWE kernel which might be why he can't reproduce? https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 - scroll down and (if you have access) click through each crash instance in turn. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1648534 Title: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_connection_call_sync Status in gnome-software package in Ubuntu: Confirmed Status in gnome-software source package in Xenial: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+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
