[Bug 2065295] [NEW] spicy-client-gtk has no desktop file so GNOME won't remember 'allow inhibiting shortcuts' selection
Public bug reported: Whenever I use spicy-client-gtk (which is launched from a command-line script) I get a pop up asking me to "Allow inhibiting shortcuts". This popup appears every single time. I would like it not to. I am told GNOME is designed for this option selection to be remembered, if there is a desktop file. spice-client-gtk does not appear to ship one (at least in the package I have on 24.04). Could a .desktop file please be added? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: spice-client-gtk 0.42-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 9 13:31:56 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 (643 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: spice-gtk UpgradeStatus: Upgraded to noble on 2024-04-23 (16 days ago) ** Affects: spice-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session ** Attachment added: "Screenshot from 2024-05-09 12-56-26.png" https://bugs.launchpad.net/bugs/2065295/+attachment/5776638/+files/Screenshot%20from%202024-05-09%2012-56-26.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065295 Title: spicy-client-gtk has no desktop file so GNOME won't remember 'allow inhibiting shortcuts' selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-gtk/+bug/2065295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065101] [NEW] theme_kwargs in terminal after upgrading to 24.04
Public bug reported: I had powerline installed prior to 24.04. After upgrading to 24.04, powerline stopped working. My terminal now outputs two lines: 'theme_kwargs' 'theme_kwargs' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: powerline 2.8.3-5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 7 21:29: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 (641 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: powerline UpgradeStatus: Upgraded to noble on 2024-04-23 (14 days ago) ** Affects: powerline (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065101 Title: theme_kwargs in terminal after upgrading to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerline/+bug/2065101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063219] Re: mantic to noble upgrade failed
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 I managed to sudo dpkg -i ./libglib2.0-0t64_2.80.0-6ubuntu1_amd64.deb As per suggestion from Juliank. Sadly it's all still a bit of a mess.. alan@ziggy:~/2063219$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... failed. The following packages have unmet dependencies. at-spi2-core : Depends: libatspi2.0-0t64 (>= 2.9.90) but it is not installed gir1.2-atspi-2.0 : Depends: libatspi2.0-0t64 (>= 2.52.0-1build1) but it is not installed gobject-introspection : Depends: libglib2.0-dev (>= 2.80.0) but 2.78.0-2 is installed gobject-introspection-bin : Depends: python3 (>= 3.12~) but 3.11.4-5 is installed Depends: libelf1t64 (>= 0.144) but it is not installed libatspi2.0-dev : Depends: libatspi2.0-0t64 (= 2.52.0-1build1) but it is not installed libegl-mesa0 : Depends: libglapi-mesa (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libegl-mesa0:i386 : Depends: libglapi-mesa:i386 (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libglib2.0-bin : Depends: libglib2.0-0 (= 2.78.0-2) libglib2.0-dev : Depends: libglib2.0-0 (= 2.78.0-2) libglib2.0-dev-bin : Depends: python3-distutils but it is not installable Depends: libglib2.0-0 (= 2.78.0-2) libglx-mesa0 : Depends: libglapi-mesa (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libglx-mesa0:i386 : Depends: libglapi-mesa:i386 (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libice-dev : Depends: libice6 (= 2:1.0.10-1build3) but 2:1.0.10-1build2 is installed libmutter-13-0 : Depends: mutter-common-bin (= 45.0-3ubuntu3) but 46.0-1ubuntu9 is installed libosmesa6 : Depends: libglapi-mesa (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libosmesa6:i386 : Depends: libglapi-mesa:i386 (= 24.0.5-1ubuntu1) but 23.2.1-1ubuntu3 is installed libpng-dev : Depends: libpng16-16t64 (= 1.6.43-5build1) but it is not installed libpython3-stdlib : Depends: libpython3.12-stdlib (>= 3.12.3-0~) but it is not installed libpython3.12-dev : Depends: libpython3.12-stdlib (= 3.12.3-1) but it is not installed Depends: libpython3.12t64 (= 3.12.3-1) but it is not installed libreoffice-common : Depends: libreoffice-uiconfig-common (= 4:7.6.4-0ubuntu0.23.10.1) but 4:24.2.2-0ubuntu1 is installed libssl-dev : Depends: libssl3 (= 3.0.10-1ubuntu2.3) libvlc5 : Depends: libvlccore9 (>= 3.0.20) but 3.0.18-4 is installed libxt-dev : Depends: libxt6t64 (= 1:1.2.1-1.2build1) but it is not installed libyelp0 : Depends: libgtk-3-0t64 (>= 3.13.3) but it is not installed mesa-va-drivers : Depends: libelf1t64 (>= 0.142) but it is not installed mesa-va-drivers:i386 : Depends: libelf1t64:i386 (>= 0.142) but it is not installed mesa-vdpau-drivers : Depends: libelf1t64 (>= 0.142) but it is not installed mesa-vdpau-drivers:i386 : Depends: libelf1t64:i386 (>= 0.142) but it is not installed mesa-vulkan-drivers : Depends: libelf1t64 (>= 0.142) but it is not installed mesa-vulkan-drivers:i386 : Depends: libelf1t64:i386 (>= 0.142) but it is not installed python3 : PreDepends: python3-minimal (= 3.11.4-5) but 3.12.3-0ubuntu1 is installed Depends: libpython3-stdlib (= 3.11.4-5) but 3.12.3-0ubuntu1 is installed python3-all : Depends: python3 (= 3.12.3-0ubuntu1) but 3.11.4-5 is installed python3-all-dev : Depends: python3 (= 3.12.3-0ubuntu1) but 3.11.4-5 is installed python3-dev : Depends: python3 (= 3.12.3-0ubuntu1) but 3.11.4-5 is installed python3-talloc : Depends: python3 (>= 3.12~) but 3.11.4-5 is installed Depends: libpython3.12t64 (>= 3.12.1) but it is not installed python3.12 : Depends: libpython3.12-stdlib (= 3.12.3-1) but it is not installed python3.12-dev : Depends: libpython3.12t64 (= 3.12.3-1) but it is not installed rlwrap : Depends: libreadline8t64 (>= 6.3) but it is not installed squid : Depends: libgnutls30t64 (>= 3.8.1) but it is not installed Depends: libnettle8t64 but it is not installed texlive-binaries : Depends: libpng16-16t64 (>= 1.6.2) but it is not installed Depends: libxt6t64 but it is not installed thunderbird-locale-en : Depends: thunderbird (>= 2:1snap1-0ubuntu3) but 1:115.9.0+build1-0ubuntu0.23.10.1 is installed vim : Depends: vim-runtime (= 2:9.0.1672-1ubuntu2.3) but 2:9.1.0016-1ubuntu7 is installed vim-gtk3 : Depends: vim-runtime (= 2:9.0.1672-1ubuntu2.3) but 2:9.1.0016-1ubuntu7 is installed vim-tiny : Depends: vim-common (= 2:9.1.0016-1ubuntu7) but 2:9.0.1672-1ubuntu2.3 is installed vlc : Depends: vlc-bin (= 3.0.18-4) but 3.0.20-3build6 is installed Recommends: vlc-plugin-access-extra (= 3.0.18-4) but 3.0.20-3build6 is installed Recommends: vlc-plugin-video-splitter (= 3.0.18-4) but 3.0.20-3build6 is installed Recommends: vlc-plugin-visualization (= 3.0.18-4) but
[Bug 2063219] [NEW] mantic to noble upgrade failed
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 Public bug reported: Sorry I don't have much data, as my system is hosed, can't run ubuntu- bug or apt. I have a Lenovo ThinkPad Z13 which shipped with 20.04 and has been upgraded through 23.10. I tried a do-release-upgrade but that failed part way through. I'll attach what I can. Some snippets: I think this was the start of the badness: dpkg: libssl3:i386: dependency problems, but removing anyway as you requested: libssh-4:i386 depends on libssl3 (>= 3.0.0). libshout3:i386 depends on libssl3 (>= 3.0.0~~alpha1). libsasl2-modules:i386 depends on libssl3 (>= 3.0.0). libsasl2-2:i386 depends on libssl3 (>= 3.0.0). libkrb5-3:i386 depends on libssl3 (>= 3.0.0). libcurl4:i386 depends on libssl3 (>= 3.0.0). gstreamer1.0-plugins-good:i386 depends on libssl3 (>= 3.0.0). ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic-to-noble-upgrade-fail.log.txt" https://bugs.launchpad.net/bugs/2063219/+attachment/5769721/+files/mantic-to-noble-upgrade-fail.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063219 Title: mantic to noble upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060122 Title: minimise animations fly everywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2060122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058761 Title: FileNotFoundError: [Errno 2] No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/switcheroo-control/+bug/2058761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037076 Title: System Details incorrectly shows multiple GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938195 Title: Configuration for eGPU removed on update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881701] Re: NVIDIA cards should have set AllowExternalGpus in /usr/share/X11/xorg.conf.d/10-nvidia.conf
Confirmed I had to jump through these hoops on a ThinkPad X1 Carbon 9th Generation, with a Razer Core attached. Using 21.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881701 Title: NVIDIA cards should have set AllowExternalGpus in /usr/share/X11/xorg.conf.d/10-nvidia.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1881701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922781] Re: Does not appear to work in Hirsuit Hippo
** Changed in: barrier (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922781 Title: Does not appear to work in Hirsuit Hippo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/barrier/+bug/1922781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922735] Re: Incorrect grub menu appears in live session
Lubuntu from Hisute daily image today. ** Attachment added: "Screenshot_20210406_150717.png" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1922735/+attachment/5484741/+files/Screenshot_20210406_150717.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922735 Title: Incorrect grub menu appears in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/1922735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921139 Title: [UIFe] Hippo wallpapers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1921139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: windows maximise underneath dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: windows maximise underneath dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915579] Re: lvm2 version 2.03.11-2ubuntu1 breaks initramfs
The steps in comment #7 worked for me. Thanks @toabctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915579 Title: lvm2 version 2.03.11-2ubuntu1 breaks initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915579] Re: lvm2 version 2.03.11-2ubuntu1 breaks initramfs
I've tried the steps in comment 2, but I'm still left at (initramfs) after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915579 Title: lvm2 version 2.03.11-2ubuntu1 breaks initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917676] Re: dropped into initramfs after update on March 1
Screenshot is from my system. It's my secondary system, so I can keep it to debug. But I don't know what to do to get past this initramfs prompt. I'm stuck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917676 Title: dropped into initramfs after update on March 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
I've tried doing various IO intensive things to trigger it but no luck yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
I can try, but I can't trigger it to happen. Given I had 60 days uptime on my system before it happened last time, and 12 days the time before that. That gives you some idea of the interval between it happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] Re: nvme drive fails after some time
It's the TOSHIBA-RD400 on /home for me that's failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910866] [NEW] nvme drive fails after some time
Public bug reported: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-09-20 (110 days ago) dmi.bios.date: 12/17/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0053.2018.1217.1739 dmi.board.name: NUC8i7HVB dmi.board.vendor: Intel Corporation dmi.board.version: J68196-502 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias:
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907239 Title: Oh no! Something has gone wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900984 Title: Multi-monitor window-snapping snaps to wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900984 Title: Multi-monitor window-snapping snaps to wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888380 Title: Give better experience of migration of deb to snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1888380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887795 Title: snap "chromium" has bad plugs or slots: system-packages-doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5370279/+files/journal ** Bug watch added: Red Hat Bugzilla #1506339 https://bugzilla.redhat.com/show_bug.cgi?id=1506339 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
Possibly related: https://bugzilla.redhat.com/show_bug.cgi?id=1506339 Also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662 which suggests 5.4.0-rc7-drm-tip-git-g3ff71899c56c works for them -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
I've had this twice today. Lost data as a result of walking away for a cup of tea. Came back to a locked up desktop May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected 3724b6ad, found 3f64da57) May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) May 12 11:18:04 mcp kernel: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) May 12 11:18:04 mcp kernel: [ cut here ] May 12 11:18:04 mcp kernel: pipe state doesn't match! May 12 11:18:04 mcp kernel: WARNING: CPU: 0 PID: 8183 at drivers/gpu/drm/i915/display/intel_display.c:13158 verify_crtc_state+0x2ad/0x300 [i915] May 12 11:18:04 mcp kernel: Modules linked in: hidp rfcomm xt_comment dummy ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 intel_rapl_msr mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul ghash_clmulni_intel snd_usb_audio snd_usbmidi_lib gspca_vc032x gspca_main uvcvideo videobuf2_vmalloc snd_hda_codec_realtek usblp snd_hda_codec_generic videobuf2_memops videobuf2_v4l2 snd_hda_codec_hdmi videobuf2_common videodev snd_hda_intel snd_intel_dspcfg mc snd_hda_codec btusb snd_hda_core btrtl aesni_intel btbcm snd_hwdep crypto_simd btintel cryptd bluetooth glue_helper intel_cstate thinkpad_acpi intel_rapl_perf nvram ledtrig_audio ecdh_generic ecc snd_pcm snd_seq_midi May 12 11:18:04 mcp kernel: snd_seq_midi_event iwlmvm snd_rawmidi mac80211 libarc4 iwlwifi snd_seq wmi_bmof input_leds joydev snd_seq_device snd_timer serio_raw cfg80211 intel_pch_thermal rtsx_pci_ms memstick mei_me snd mei soundcore mac_hid sch_fq_codel kvm_intel kvm parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) hid_generic usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit crc32_pclmul drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse i2c_i801 ahci libahci e1000e drm rtsx_pci lpc_ich wmi video May 12 11:18:04 mcp kernel: CPU: 0 PID: 8183 Comm: Xorg Tainted: P O 5.4.0-30-generic #34-Ubuntu May 12 11:18:04 mcp kernel: Hardware name: LENOVO 20BV001BUK/20BV001BUK, BIOS JBET73WW (1.37 ) 08/14/2019 May 12 11:18:04 mcp kernel: RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] May 12 11:18:04 mcp kernel: Code: b6 45 bf e9 8d fe ff ff 80 3d 85 76 10 00 00 0f b6 f0 48 c7 c7 40 aa 52 c0 75 32 e8 5d e7 de ff e9 1e fe ff ff e8 ae 9d 24 e5 <0f> 0b e9 1b ff ff ff e8 a2 9d 24 e5 0f 0b e9 85 fe ff ff e8 96 9d May 12 11:18:04 mcp kernel: RSP: 0018:b1e543f67a80 EFLAGS: 00010282 May 12 11:18:04 mcp kernel: RAX: RBX: 8db0a7d202b0 RCX: 0006 May 12 11:18:04 mcp kernel: RDX: 0007 RSI: 0092 RDI: 8db0bda178c0 May 12 11:18:04 mcp kernel: RBP: b1e543f67ac8 R08: 0530 R09: 0004 May 12 11:18:04 mcp kernel: R10: R11: 0001 R12: 8db0b98f3800 May 12 11:18:04 mcp kernel: R13: 8db0a7d202b8 R14: 8db0a7d2 R15: 8dad521aa000 May 12 11:18:04 mcp kernel: FS: 7f98402dda80() GS:8db0bda0() knlGS: May 12 11:18:04 mcp kernel: CS: 0010 DS: ES: CR0: 80050033 May 12 11:18:04 mcp kernel: CR2: 7f33c8ee0024 CR3: 00075ffda006 CR4: 003606f0 May 12 11:18:04 mcp kernel: DR0: DR1: DR2: May 12 11:18:04 mcp kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 12 11:18:04 mcp kernel: Call Trace: May 12 11:18:04 mcp kernel: intel_atomic_commit_tail+0xa43/0x12e0 [i915] May 12 11:18:04 mcp kernel: ? flush_workqueue_prep_pwqs+0x12e/0x140 May 12 11:18:04 mcp kernel: ? flush_workqueue+0x193/0x420 May 12 11:18:04 mcp kernel: ? intel_atomic_commit_ready+0x4d/0x54 [i915] May 12 11:18:04 mcp kernel: intel_atomic_commit+0x284/0x2b0 [i915] May 12 11:18:04 mcp kernel: drm_atomic_commit+0x4a/0x50 [drm] May 12 11:18:04 mcp kernel: drm_atomic_connector_commit_dpms+0xdf/0x100 [drm] May 12 11:18:04 mcp kernel: drm_mode_obj_set_property_ioctl+0x156/0x2a0 [drm] May 12 11:18:04 mcp kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm] May 12 11:18:04 mcp kernel: drm_connector_property_set_ioctl+0x3b/0x60 [drm] May 12 11:18:04 mcp kernel: drm_ioctl_kernel+0xae/0xf0 [drm] May 12 11:18:04 mcp kernel: drm_ioctl+0x234/0x3d0 [drm] May 12 11:18:04 mcp
[Bug 1668495] Re: Unable to render Roboto font needed for Guitarix UI
Tried Guitarix on 20.04 and it looks like this is no longer an issue. If you're still seeing the problem on a supported version of Ubuntu, do re- open this bug and we can investigate further. ** Changed in: guitarix (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668495 Title: Unable to render Roboto font needed for Guitarix UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guitarix/+bug/1668495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744899] Re: package linux-headers-4.4.0-109 (not installed) failed to install/upgrade: unable to create `/usr/src/linux-headers-4.4.0-109/include/uapi/linux/pr.h.dpkg-new' (while processing `./u
For anyone else stumbling upon this bug with a similar error message, it's possible you're out of inodes. https://askubuntu.com/questions/485743/no-space-left-on-device-when- installing-packages-yet-i-have-space-left ** Changed in: linux-lts-xenial (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744899 Title: package linux-headers-4.4.0-109 (not installed) failed to install/upgrade: unable to create `/usr/src/linux- headers-4.4.0-109/include/uapi/linux/pr.h.dpkg-new' (while processing `./usr/src/linux-headers-4.4.0-109/include/uapi/linux/pr.h'): No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1744899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696594 Title: gnome-font-viewer crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1696594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
I'm running linux-image-5.4.0-30-generic and it happened again last night. I come back to the machine and see corruption on both external panels, while internal panel is off. So it does indeed feel like i915 related. Would be happy to try and get more debug info, but it's hard given the machine completely locks up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876440] Re: Kernel no longer getting updated
It was indeed installed on 1st March. alan@mcp:~$ cat /var/log/installer/media-info Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) There is even video evidence of me nuking it on that day :D https://www.youtube.com/watch?v=YOUwdhNbHtk I assume I can't do the moving files around from /boot to bpool/BOOT/ubuntu_.. from the running environment? I need to use a live USB? I'm gonna need a pointer to some more detailed docs on how to do the mounting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Kernel no longer getting updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876440] Re: Kernel no longer getting updated
** Attachment added: "journal_bug_1876440_cleaned.txt" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+attachment/5366054/+files/journal_bug_1876440_cleaned.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Kernel no longer getting updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876440] Re: Kernel no longer getting updated
** Summary changed: - Wrong kernel is booted + Kernel no longer getting updated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Kernel no longer getting updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876440] Re: Wrong kernel is booted
Looks like update-grub is failing... alan@mother:~$ ssh 192.168.1.94 alan@192.168.1.94's password: Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * Ubuntu 20.04 LTS is out, raising the bar on performance, security, and optimisation for Intel, AMD, Nvidia, ARM64 and Z15 as well as AWS, Azure and Google Cloud. https://ubuntu.com/blog/ubuntu-20-04-lts-arrives 0 updates can be installed immediately. 0 of these updates are security updates. Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings Last login: Sat May 2 14:59:14 2020 from 192.168.1.50 alan@mcp:~$ sudo update-grub [sudo] password for alan: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... grub-probe: error: unknown filesystem. Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-18-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-18-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-20-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-20-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-21-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-21-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg Found linux image: vmlinuz-5.4.0-18-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg Found initrd image: initrd.img-5.4.0-18-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_591yqg cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_awswj7': dataset does not exist Found linux image: vmlinuz-5.4.0-22-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 Found initrd image: initrd.img-5.4.0-22-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 Found linux image: vmlinuz-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 Found initrd image: initrd.img-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 Found linux image: vmlinuz-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 Found initrd image: initrd.img-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_awswj7 cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_u6xmer': dataset does not exist Found linux image: vmlinuz-5.4.0-22-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer Found initrd image: initrd.img-5.4.0-22-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer Found linux image: vmlinuz-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer Found initrd image: initrd.img-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer Found linux image: vmlinuz-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer Found initrd image: initrd.img-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_u6xmer cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_4s8kzl': dataset does not exist Found linux image: vmlinuz-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_4s8kzl Found initrd image: initrd.img-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_4s8kzl Found linux image: vmlinuz-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_4s8kzl Found initrd image: initrd.img-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_4s8kzl cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_5ea1rw': dataset does not exist Found linux image: vmlinuz-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ea1rw Found initrd image: initrd.img-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ea1rw Found linux image: vmlinuz-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ea1rw Found initrd image: initrd.img-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ea1rw cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_v2qbhr': dataset does not exist Found linux image: vmlinuz-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr Found initrd image: initrd.img-5.4.0-24-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr Found linux image: vmlinuz-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr Found initrd image: initrd.img-5.4.0-25-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr Found linux image: vmlinuz-5.4.0-26-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr Found initrd image: initrd.img-5.4.0-26-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_v2qbhr cannot open 'bpool/BOOT/ubuntu_pyyy5h@autozsys_qmtqqf': dataset does not exist Found
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876440 Title: Wrong kernel is booted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1876440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
Adding your PPA and getting linux-image-5.4.0-29-generic. Will reboot and try this over the weekend. I never know how to trigger this, so no idea if it actually will or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
Had this a few more times. Took some time to rummage in the journal and found this just before it happened. May 01 10:00:54 mcp kernel: [ cut here ] May 01 10:00:54 mcp kernel: pipe state doesn't match! May 01 10:00:54 mcp kernel: WARNING: CPU: 1 PID: 13809 at drivers/gpu/drm/i915/display/intel_display.c:13148 verify_crtc_state+0x2ad/0x300 [i915] May 01 10:00:54 mcp kernel: Modules linked in: scsi_transport_iscsi sctp hidp nls_iso8859_1 exfat(C) mmc_block nls_utf8 isofs uas usb_storage ebtable_filter ebtables unix_diag btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid rfcomm dummy veth xt_comment xt_CHECKSUM xt_MA> May 01 10:00:54 mcp kernel: snd_seq_midi input_leds snd_seq_midi_event iwlmvm joydev serio_raw snd_hda_codec_realtek mac80211 snd_hda_codec_generic snd_hda_codec_hdmi libarc4 snd_hda_intel snd_rawmidi wmi_bmof snd_intel_nhlt snd_hda_codec snd_hda_core iwlwifi snd_hwdep snd_pcm snd_seq cfg80211 thinkpad_ac> May 01 10:00:54 mcp kernel: CPU: 1 PID: 13809 Comm: Xorg Tainted: P C O 5.4.0-21-generic #25-Ubuntu May 01 10:00:54 mcp kernel: Hardware name: LENOVO 20BV001BUK/20BV001BUK, BIOS JBET73WW (1.37 ) 08/14/2019 May 01 10:00:54 mcp kernel: RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] May 01 10:00:54 mcp kernel: Code: b6 45 bf e9 8d fe ff ff 80 3d 15 79 10 00 00 0f b6 f0 48 c7 c7 78 b7 3c c0 75 32 e8 7d 2a e0 ff e9 1e fe ff ff e8 be 8f 7a d0 <0f> 0b e9 1b ff ff ff e8 b2 8f 7a d0 0f 0b e9 85 fe ff ff e8 a6 8f May 01 10:00:54 mcp kernel: RSP: 0018:a72a8dbdba80 EFLAGS: 00010282 May 01 10:00:54 mcp kernel: RAX: RBX: 8b4d66ee02b0 RCX: 0006 May 01 10:00:54 mcp kernel: RDX: 0007 RSI: 0092 RDI: 8b4d9dc578c0 May 01 10:00:54 mcp kernel: RBP: a72a8dbdbac8 R08: 0002ce27 R09: 0004 May 01 10:00:54 mcp kernel: R10: R11: 0001 R12: 8b4d66d56800 May 01 10:00:54 mcp kernel: R13: 8b4d66ee02b8 R14: 8b4d66ee R15: 8b4927284000 May 01 10:00:54 mcp kernel: FS: 7f48d9e10a80() GS:8b4d9dc4() knlGS: May 01 10:00:54 mcp kernel: CS: 0010 DS: ES: CR0: 80050033 May 01 10:00:54 mcp kernel: CR2: 7f6cbbbc6421 CR3: 0006c6c06002 CR4: 003606e0 May 01 10:00:54 mcp kernel: DR0: DR1: DR2: May 01 10:00:54 mcp kernel: DR3: DR6: fffe0ff0 DR7: 0400 May 01 10:00:54 mcp kernel: Call Trace: May 01 10:00:54 mcp kernel: intel_atomic_commit_tail+0xa4b/0x12f0 [i915] May 01 10:00:54 mcp kernel: ? flush_workqueue_prep_pwqs+0x12e/0x140 May 01 10:00:54 mcp kernel: ? flush_workqueue+0x193/0x420 May 01 10:00:54 mcp kernel: ? intel_atomic_commit_ready+0x4d/0x54 [i915] May 01 10:00:54 mcp kernel: intel_atomic_commit+0x284/0x2b0 [i915] May 01 10:00:54 mcp kernel: drm_atomic_commit+0x4a/0x50 [drm] May 01 10:00:54 mcp kernel: drm_atomic_connector_commit_dpms+0xdf/0x100 [drm] May 01 10:00:54 mcp kernel: drm_mode_obj_set_property_ioctl+0x156/0x2a0 [drm] May 01 10:00:54 mcp kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm] May 01 10:00:54 mcp kernel: drm_connector_property_set_ioctl+0x3b/0x60 [drm] May 01 10:00:54 mcp kernel: drm_ioctl_kernel+0xae/0xf0 [drm] May 01 10:00:54 mcp kernel: drm_ioctl+0x234/0x3d0 [drm] May 01 10:00:54 mcp kernel: ? drm_connector_set_obj_prop+0x90/0x90 [drm] May 01 10:00:54 mcp kernel: ? __switch_to_asm+0x34/0x70 May 01 10:00:54 mcp kernel: ? __switch_to_asm+0x40/0x70 May 01 10:00:54 mcp kernel: ? __switch_to+0x110/0x470 May 01 10:00:54 mcp kernel: do_vfs_ioctl+0x407/0x670 May 01 10:00:54 mcp kernel: ? __schedule+0x2eb/0x740 May 01 10:00:54 mcp kernel: ksys_ioctl+0x67/0x90 May 01 10:00:54 mcp kernel: __x64_sys_ioctl+0x1a/0x20 May 01 10:00:54 mcp kernel: do_syscall_64+0x57/0x190 May 01 10:00:54 mcp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 May 01 10:00:54 mcp kernel: RIP: 0033:0x7f48da16e37b May 01 10:00:54 mcp kernel: Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 May 01 10:00:54 mcp kernel: RSP: 002b:7fff40926ee8 EFLAGS: 0246 ORIG_RAX: 0010 May 01 10:00:54 mcp kernel: RAX: ffda RBX: 7fff40926f20 RCX: 7f48da16e37b May 01 10:00:54 mcp kernel: RDX: 7fff40926f20 RSI: c01064ab RDI: 000c May 01 10:00:54 mcp kernel: RBP: c01064ab R08: 555e05f12800 R09: May 01 10:00:54 mcp kernel: R10: 555e05f12800 R11: 0246 R12: 555e060e0ea0 May 01 10:00:54 mcp kernel: R13: 000c R14: R15: 555e04edf980 May 01 10:00:54 mcp kernel: ---[ end trace adc6362abe5c8cae ]--- -- You received this bug notification because you are a member of Ubuntu
[Bug 1871687] Re: System hard locks up intermittently
This feels very multi-monitor centric. I have had it numerous times overnight. I have 2 external displays permanently attached, so 3 displays active in total, at most times. This is sometimes triggered overnight, probably when a notification comes in and triggers the displays to wake up. This morning I noticed one display was off, like it was receiving no signal. But it is there in gnome display settings. So I try and turn it off and on again in there. But that causes the display corruption to appear, and it locked up. I had to hard reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869737 Title: App icons shrink or disappear after closing an app folder To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1869571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873804] [NEW] Website in debian packaging no longer valid, directing to dodgy site
Public bug reported: Reported via ubuntu discourse at https://discourse.ubuntu.com/t /hijacked-website-of-the-app-wallch-in-ubuntu-software/15402 The debian packaging contains a url which seems to have been lost by the original author of the software. It should be removed, or replaced with a different url for the upstream author. The domain is melloristudio dot com. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wallch 4.0-0ubuntu6 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: Mon Apr 20 13:51:04 2020 InstallationDate: Installed on 2020-03-01 (49 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: wallch UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wallch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873804 Title: Website in debian packaging no longer valid, directing to dodgy site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1873804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873332] Re: Triangle arrow next to "Copying files" is mis-aligned
** Attachment added: "Screenshot from 2020-04-16 20-01-02.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1873332/+attachment/5355713/+files/Screenshot%20from%202020-04-16%2020-01-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873332 Title: Triangle arrow next to "Copying files" is mis-aligned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1873332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873332] [NEW] Triangle arrow next to "Copying files" is mis-aligned
Public bug reported: Steps to reproduce. Install Ubuntu 20.04 (or indeed pretty much any previous release) Follow all prompts up until the installation begins. During the slideshow, observe an "> Copying files" at the bottom of the window. Actual outcome The > arrow is slightly vertically mis-aligned. Expected outcome It perfectly aligns vertically with the text it accompanies. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.11 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:01:33 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.11 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873332 Title: Triangle arrow next to "Copying files" is mis-aligned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1873332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872276 Title: Gnome shell huge app's icon size in the app folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872276 Title: Gnome shell huge app's icon size in the app folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872269 Title: Gnome Shell App Launch Grid random vertical navigation Buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
** Attachment added: "bootlog3.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349866/+files/bootlog3.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
** Attachment added: "bootlog2.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349865/+files/bootlog2.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
** Attachment added: "bootlog1.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349864/+files/bootlog1.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] Re: System hard locks up intermittently
** Attachment added: "bootlog0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+attachment/5349863/+files/bootlog0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871687] [NEW] System hard locks up intermittently
Public bug reported: My T450 main laptop is generally left on all day and night. I sometimes suspend it when moving around the house, but it's often left on all the time. Sometimes when I go to start work in the morning there's some corruption on screen and the laptop won't respond. I can't REISUB or ssh in. This has happened a few times since clean installing 20.04. Previously I was on an upgraded-to-20.04 install and don't recall it happening there. The other obvious difference is I'm now running ZFS which I wasn't before. :S ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 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-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: alan 8365 F pulseaudio /dev/snd/controlC2: alan 8365 F pulseaudio /dev/snd/controlC1: alan 8365 F pulseaudio /dev/snd/controlC0: alan 8365 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 19:30:46 2020 InstallationDate: Installed on 2020-03-01 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) MachineType: LENOVO 20BV001BUK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux StagingDrivers: exfat 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: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871687 Title: System hard locks up intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868083 Title: gnome-shell process "estabilished" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867598 Title: Inconsistency in naming of "Permissions & Access" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1867598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867065] Re: Installer hangs at boot on machine
Confirmed on hardware (X220 / i7 / 16GB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867065 Title: Installer hangs at boot on machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1867065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867067] Re: ERROR context deadline exceeded
I guess you want me to time doing a stand-alone grub-update? alan@mcp:~$ time sudo update-grub [sudo] password for alan: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ak6ru Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_5ak6ru Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_e5n5dg Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_e5n5dg Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_vszmvi Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_vszmvi Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_vszmvi Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_vszmvi Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_quko78 Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_quko78 Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_quko78 Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_quko78 Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_yy211i Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_yy211i Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_yy211i Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_yy211i Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_mvo757 Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_mvo757 Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_mvo757 Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_mvo757 Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_031jjy Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_031jjy Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_031jjy Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_031jjy Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_8sjc7w Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_8sjc7w Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_8sjc7w Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_8sjc7w Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_7ovtu5 Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_7ovtu5 Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_7ovtu5 Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_7ovtu5 Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_nw2agd Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_nw2agd Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_nw2agd Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_nw2agd Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_h9bny3 Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_h9bny3 Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_h9bny3 Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_h9bny3 Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_aojpvx Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_aojpvx Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_aojpvx Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_aojpvx Found linux image: vmlinuz-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_jywwy8 Found initrd image: initrd.img-5.4.0-14-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_jywwy8 Found linux image: vmlinuz-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_jywwy8 Found initrd image: initrd.img-5.4.0-17-generic in rpool/ROOT/ubuntu_pyyy5h@autozsys_jywwy8 Found linux image: vmlinuz-5.4.0-14-generic in
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867067 Title: ERROR context deadline exceeded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1867067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858456] Re: ThinkPad T450 stutters without intel_idle.max_cstate=2
I have upgraded to focal, am now running 5.4.0-9-generic and no longer see the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858456 Title: ThinkPad T450 stutters without intel_idle.max_cstate=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Nope. Stock kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859970 Title: orange tint in screenshots when running wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1859970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859320 Title: Multiple sign-in options in menu of Ubuntu Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859320 Title: Multiple sign-in options in menu of Ubuntu Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859319 Title: widget factory slighty too wide for common 1366x768 display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859319] Re: widget factory slighty too wide for common 1366x768 display
** Attachment added: "Screenshot from 2020-01-12 10-20-54.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+attachment/5319370/+files/Screenshot%20from%202020-01-12%2010-20-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859319 Title: widget factory slighty too wide for common 1366x768 display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858456] [NEW] ThinkPad T450 stutters without intel_idle.max_cstate=2
Public bug reported: I noticed my 19.10 laptop was stuttering - YouTube videos freezing. Did further investigations and the entire desktop freezes, not just the video rendering. https://www.youtube.com/watch?v=869e9YwW0vw Some investigation led me to https://bugzilla.kernel.org/show_bug.cgi?id=109051 and https://askubuntu.com/questions/803640/system-freezes-completely-with- intel-bay-trail I set intel_idle.max_cstate=2 in my grub config and now the issue never happens, but I have (anecdotally) seen worse battery life as a result. Can this be fixed in such a way that I don't have to suffer poor battery performance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 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: Mon Jan 6 16:26:20 2020 HibernationDevice: RESUME=UUID=60f73ebd-ac30-42de-968a-76a4f3332440 InstallationDate: Installed on 2018-02-04 (700 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 MachineType: LENOVO 20BV001BUK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=36ab10c5-4404-47e2-89ec-6639af6cc629 ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-19 (109 days ago) 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: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858456 Title: ThinkPad T450 stutters without intel_idle.max_cstate=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856838 Title: gnome-shell using a lot of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848053] Re: (or swipe finger) text is barely readble on login screen
I am not a designer, but it looks fine to me. I believe it should be the same weight as the password prompt. Which it looks like to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848053 Title: (or swipe finger) text is barely readble on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1848053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848053] Re: (or swipe finger) text is barely readble on login screen
That fixed it, thanks! ** Attachment added: "IMG_20191128_110356.jpg" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1848053/+attachment/5308447/+files/IMG_20191128_110356.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848053 Title: (or swipe finger) text is barely readble on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1848053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848053] Re: (or swipe finger) text is barely readble on login screen
Happy to test any fixes. Just let me know what I need to do. I have multiple machines which have finger print readers, so happy to dedicate one to testing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848053 Title: (or swipe finger) text is barely readble on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1848053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852905] Re: nvidia-drivers-435 won't load on GeForce GTX 980M
I manually tried going back to nvidia-drivers-430 which didn't work either. The module wasn't built by nvidia-dkms-430. Further investigation revealed the kernel headers were missing. I would have expected them to be pulled in, but ok. I moved forward to 435 again, ensuring nvidia-dkms-435 was installed, and this time installed the kernel headers, and this triggered nvidia-dkms-435. So it looks like the nvidia-drivers-435 didn't pull in the headers - which must have previously been there, because I've been using the nvidia drivers on this machine for a week or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852905 Title: nvidia-drivers-435 won't load on GeForce GTX 980M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852905] [NEW] nvidia-drivers-435 won't load on GeForce GTX 980M
Public bug reported: Preamble I have an Entroware Athena with GeForce GTX 980M GPU. It was running 18.04, and then upgraded to 19.10 where it was running fine. I was on GNOME but due to another unrelated bug I switched to MATE. While away, I think some packages updated on it and when I tried using the machine it was slow, feeling like I was using a VESA driver (very slow framerate on the desktop). I thought it needed an nvidia driver update and reboot, however, I couldn't install the latest nvidia driver. It got into a situation where nvidia-drivers-435 wouldn't install because xserver-xorg-video-nvidia-435 and libnvidia-cfg1-435 were being held back. So I did: sudo apt install nvidia-driver-435 xserver-xorg-video-nvidia-435 libnvidia-cfg1-435 When I rebooted, it's still not using the nvidia binary driver. I also noted it doesn't seem to trigger dkms at all. Surely it needs to? (base) alan@mother:~$ sudo apt install nvidia-driver-435 xserver-xorg-video-nvidia-435 libnvidia-cfg1-435 --reinstall Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: augeas-lenses chromium-codecs-ffmpeg-extra g++-7 gcc-8-base:i386 guile-2.0-libs libarmadillo8 libaugeas0 libavcodec-extra57 libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55 libboost-program-options1.65.1 libcharls1 libcrystalhd3 libcue1 libdouble-conversion1 libenca0 libgeos-3.6.2 libgfortran4 libglew2.0 libgovirt-common libgovirt2 libiptcdata0 liblivemedia62 libllvm7 libllvm8 libllvm8:i386 liblvm2app2.2 liblvm2cmd2.02 libmysqlclient20 libnetcf1 libnfs11 libnvidia-common-390 libnvidia-common-430 libostree-1-1 libplacebo4 libpostproc54 libproj12 libprotobuf-lite10 libpython3.6-dev libstdc++-7-dev libswresample2 libswscale4 libtagc0 libtinfo5:i386 libupnp6 libwayland-client0:i386 libwayland-server0:i386 libwxgtk3.0-0v5 libx264-152 libx265-146 libzip4 net-tools python-idna python-oauth python-zope.interface python3.6-dev schroot-common xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-input-wacom-hwe-18.04 xserver-xorg-legacy-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Use 'sudo apt autoremove' to remove them. 0 to upgrade, 0 to newly install, 3 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,986 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 libnvidia-cfg1-435 amd64 435.21-0ubuntu2 [69.2 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 nvidia-driver-435 amd64 435.21-0ubuntu2 [413 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 xserver-xorg-video-nvidia-435 amd64 435.21-0ubuntu2 [1,504 kB] Fetched 1,986 kB in 0s (85.7 MB/s) (Reading database ... 306958 files and directories currently installed.) Preparing to unpack .../libnvidia-cfg1-435_435.21-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-435:amd64 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Preparing to unpack .../nvidia-driver-435_435.21-0ubuntu2_amd64.deb ... Unpacking nvidia-driver-435 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Preparing to unpack .../xserver-xorg-video-nvidia-435_435.21-0ubuntu2_amd64.deb ... Unpacking xserver-xorg-video-nvidia-435 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Setting up libnvidia-cfg1-435:amd64 (435.21-0ubuntu2) ... Setting up xserver-xorg-video-nvidia-435 (435.21-0ubuntu2) ... Setting up nvidia-driver-435 (435.21-0ubuntu2) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... (base) alan@mother:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 17 12:00:29 2019 InstallationDate: Installed on 2019-06-19 (150 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852905 Title: nvidia-drivers-435 won't load on GeForce GTX 980M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847597 Title: gnome-control-center cannot access google account To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847597 Title: gnome-control-center cannot access google account To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1847597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850052] Re: installing zsys breaks desktop login
Thanks everyone for the prompt fix! Love you all. <3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850052 Title: installing zsys breaks desktop login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1850052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850174 Title: This is not a bug, please ignore - just testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850052] Re: installing zsys breaks desktop login
Tested zsys from the ubuntu-desktop ppa on a clean system which has not had zsys installed. I am able to login and see my files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850052 Title: installing zsys breaks desktop login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1850052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs