[Desktop-packages] [Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()
I'm not sure if there's a better place to report this, but the lunar- proposed mutter related packages seem to be stable here and I can't reproduce the DnD crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012100 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb I have this error when I'm connecting to nym-connect (nymtech.net) ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 17 18:10:09 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()
I see gnome-shell and mutter 44.1 packages in lunar-proposed. Is it a good idea to give them a try? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012100 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb I have this error when I'm connecting to nym-connect (nymtech.net) ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 17 18:10:09 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] Re: gnome-shell segfault when dragging a link from firefox
This appears to be the same as #2012100. meta_wayland_compositor_get_context (compositor=0x0) at ../src/wayland/meta-wayland.c:863 display_from_offer (offer=0x55e903542650) at ../src/wayland/meta-wayland-data-offer.c:45 data_offer_receive (client=, resource=, mime_type=0x55e903b084dc "text/uri-list", fd=105) at ../src/wayland/meta-wayland-data-offer.c:97 ffi_call_unix64 () at ../src/x86/unix64.S:104 ffi_call_int (cif=cif@entry=0x7ffca9966770, fn=, rvalue=, avalue=, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673 Is it a good idea to try the fix from gnome-shell/lunar-proposed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2020904/+attachment/5675901/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020904/+attachment/5675899/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2020904/+attachment/5675898/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2020904/+attachment/5675900/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] Re: gnome-shell segfault when dragging a link from firefox
apport information ** Tags added: apport-collected ** Description changed: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2019-06-18 (1438 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gnome-shell 44.0-2ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, user) + SHELL=/bin/bash + TERM=tmux-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2020904/+attachment/5675897/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 44.0-2ubuntu3 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020904] [NEW] gnome-shell segfault when dragging a link from firefox
Public bug reported: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020904 Title: gnome-shell segfault when dragging a link from firefox Status in gnome-shell package in Ubuntu: New Bug description: This has happened to me twice in the last 24h. I was dragging a link from firefox to another application. The crash occurs before I release the mouse button to drop the link in the second application. In both cases the drag was across two displays. The first time, the intended target was wezterm (deb). The second time, the intended target was chromium (snap). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:57:45 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1438 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
** Tags removed: kinetic ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011483] [NEW] notification popup stuck
Public bug reported: A notification popup from solaar (Mouse battery low/Wireless mouse is low on power) is orphaned on my screen after I removed the notification from the notification/calendar dropdown. Clicking on the notification itself, or on the x button generates messages like this: JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 18:09:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1364 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-direct PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (134 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2011483 Title: notification popup stuck Status in gnome-shell package in Ubuntu: New Bug description: A notification popup from solaar (Mouse battery low/Wireless mouse is low on power) is orphaned on my screen after I removed the notification from the notification/calendar dropdown. Clicking on the notification itself, or on the x button generates messages like this: JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 JS ERROR: TypeError: this.notification is null vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:796:9 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 18:09:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1364 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-direct PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
The issue eventually occurred with the bleeding edge mesa, but it took a week. I've since reverted to the kinetic mesa and tried mainline 5.18 and 5.17 kernels, but the issue continues to appear with those kernels. For now I'm just running the jammy kernel, since that seems to work without static. I still sometimes see one screen freeze up entirely. Playing a video seems to fix that pretty reliably. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
A couple more data points. I installed and booted a 5.19.17 mainline kernel (from the ubuntu mainline kernel archive) and the static started immediately. I booted the 5.15.0-52-generic kernel left over from ubuntu 20.04 and haven't had any problems with static or full screen video after 30 minutes. This seems to point toward a kernel/driver issue rather than gnome- shell. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
Upon returning from an appointment the flickering has returned. The fractional scaling setting must have been a coincidence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
I'm still seeing issues with full screen video in firefox. Perhaps it’s a separate issue, but the static looks similar in its blockiness. ** Attachment added: "trim.B65976FD-B044-4CA2-B25F-2C8720927D82.MOV" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+attachment/5628526/+files/trim.B65976FD-B044-4CA2-B25F-2C8720927D82.MOV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] Re: [amdgpu] intermittent green static
Static is confined to specific windows or surfaces, disappears behind other windows. Static seems to have stopped completely when fractional scaling is turned off. ** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995320] [NEW] intermittent green static
Public bug reported: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: intermittent green static Status in gnome-shell package in Ubuntu: New Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This might be addressed in 22.10, by this MR in the gnome-shell package. Resolve "calendar: Correct handling of recurring events" https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2328 I haven't upgraded, so I can't confirm at this time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in evolution-data-server: New Status in evolution-data-server package in Ubuntu: Confirmed Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This continues to be an issue in 22.04. ** Tags removed: impish ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in evolution-data-server: New Status in evolution-data-server package in Ubuntu: Confirmed Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows
https://bugzilla.mozilla.org/show_bug.cgi?id=1756170 ** Bug watch added: Mozilla Bugzilla #1756170 https://bugzilla.mozilla.org/show_bug.cgi?id=1756170 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1957944 Title: CSD do not distinguish focused and unfocused FF windows Status in firefox package in Ubuntu: Incomplete Bug description: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 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:365 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (941 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=96.0/20220106144528 (In use) Profile0 (Default) - LastVersion=96.0/20220106144528 (In use) Profile2 - LastVersion=71.0/20191205203726 (Out of date) RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957944] Re: CSD do not distinguish focused and unfocused FF windows
At the moment it's "Yaru-dark / Yaru" and the issue remains. I was using a third party theme when I first encountered this. I switched back to Yaru before filing this bug, but about:support was still showing the third party theme. After resetting the theme it's showing "Yaru-dark / Yaru". I did some more testing with a separate login I use for steam and a new FF profile. It seems to only happen when a a FF colorways theme is used. If the default theme is used I am able to see a difference in the titlebar shade (it's too subtle IMO, but I can see it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1957944 Title: CSD do not distinguish focused and unfocused FF windows Status in firefox package in Ubuntu: Incomplete Bug description: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 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:365 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (941 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=96.0/20220106144528 (In use) Profile0 (Default) - LastVersion=96.0/20220106144528 (In use) Profile2 - LastVersion=71.0/20191205203726 (Out of date) RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1957944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957944] [NEW] CSD do not distinguish focused and unfocused FF windows
Public bug reported: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 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:365 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (941 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=96.0/20220106144528 (In use) Profile0 (Default) - LastVersion=96.0/20220106144528 (In use) Profile2 - LastVersion=71.0/20191205203726 (Out of date) RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "ff-csd-focus-bug.png" https://bugs.launchpad.net/bugs/1957944/+attachment/5554362/+files/ff-csd-focus-bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1957944 Title: CSD do not distinguish focused and unfocused FF windows Status in firefox package in Ubuntu: New Bug description: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales:
[Desktop-packages] [Bug 1952468] [NEW] gnome-settings-daemon resetting time zone after network-manager sets it
Public bug reported: I am currently traveling and have observed the time zone being set correctly when I connect to a network and then reset to my home time zone a short while later. Automatic Time Zone is enabled in settings. Logs indicate the reset is coming from /usr/libexec/gsd-datetime. I guess it's not informed of the configuration coming from network- manager? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-settings-daemon 40.0.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 10:35:29 2021 InstallationDate: Installed on 2019-03-17 (984 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to impish on 2021-10-17 (39 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1952468 Title: gnome-settings-daemon resetting time zone after network-manager sets it Status in gnome-settings-daemon package in Ubuntu: New Bug description: I am currently traveling and have observed the time zone being set correctly when I connect to a network and then reset to my home time zone a short while later. Automatic Time Zone is enabled in settings. Logs indicate the reset is coming from /usr/libexec/gsd-datetime. I guess it's not informed of the configuration coming from network- manager? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-settings-daemon 40.0.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 10:35:29 2021 InstallationDate: Installed on 2019-03-17 (984 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to impish on 2021-10-17 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1952468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This issue in evolution-data-server seems to describe the problem. https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276 ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #276 https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in gnome-shell package in Ubuntu: New Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This is still happening after upgrading to 21.10. The calendar reminder I saw today and last night was canceled several weeks ago. When I looked in the topbar calendar dropdown, the event did not appear there. It's unclear to me if this is a gnome-shell issue or a gnome-calendar issue or maybe something like evolution-data-server? ** Tags removed: hirsute ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in gnome-shell package in Ubuntu: New Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time
This is still happening in 21.04, most recently with a repeating calendar event instance that was canceled over a week ago. The desktop has been rebooted in the interim. ** Tags added: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in gnome-shell package in Ubuntu: New Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923893] [NEW] After rescheduling an event, calendar alerts appear for the old time
Public bug reported: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1923893 Title: After rescheduling an event, calendar alerts appear for the old time Status in gnome-shell package in Ubuntu: New Bug description: I use google calendar. Events are created and updated via the browser. The calendar feed is configured through settings/online accounts. I can see upcoming events in the calendar drop down. The calendar and desktop are configured for the same timezone, and alerts normally appear simultaneously on my phone and desktop. I know sometimes stale calendar entries can be a factor, but I don't *think* that's an issue at this time (the change was made almost 24 hours ago, I don't see the API limit errors I used to see in logs). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 15:02:11 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (666 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-49-generic linux-base RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897754] Re: flameshot: The icon does not appear in the GNOME bar
I've also had this problem with the flameshot icon disappearing after upgrading to 20.04. Reverting to gnome-shell-extension-appindicator 33-1 has fixed it for now, but having broken dependencies isn't good (even if things seem to be working). Comments on https://github.com/flameshot-org/flameshot/issues/1206 also suggest this problem doesn't occur with the flameshot snap. Testing the deb package specifically may be a good idea. ** Bug watch added: github.com/flameshot-org/flameshot/issues #1206 https://github.com/flameshot-org/flameshot/issues/1206 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: flameshot: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://github.com/flameshot-org/flameshot/issues/1009 --- When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
I am running the 5.4.0-32-generic kernel from focal-proposed, and rtkit- daemon seems to be working normally now. : kai@dipper kai; uname -r 5.4.0-32-generic : kai@dipper kai; journalctl -b0 -u rtkit-daemon -- Logs begin at Fri 2020-01-03 16:35:36 EST, end at Tue 2020-05-19 11:02:23 EDT. -- May 19 10:59:19 dipper systemd[1]: Starting RealtimeKit Scheduling Policy Service... May 19 10:59:19 dipper systemd[1]: Started RealtimeKit Scheduling Policy Service. May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully called chroot. May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully dropped privileges. May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully limited resources. May 19 10:59:19 dipper rtkit-daemon[2535]: Running. May 19 10:59:19 dipper rtkit-daemon[2535]: Canary thread running. May 19 10:59:19 dipper rtkit-daemon[2535]: Watchdog thread running. May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2444 of process 2444 owned by '123' high priority at nice level -11. May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes of 1 users. May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 1 threads of 1 processes of 1 users. May 19 10:59:19 dipper rtkit-daemon[2535]: Successfully made thread 2682 of process 2444 owned by '123' RT at priority 5. May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes of 1 users. May 19 10:59:19 dipper rtkit-daemon[2535]: Supervising 2 threads of 1 processes of 1 users. ⋮ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-kvm source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-riscv source package in Focal: Fix Committed Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled. It was only disabled for the lowlatency kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the cause of this: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=9b039fc517876d312e7fa0955571101a299c91f5 Some discussion of this WRT lowlatency kernel is here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
The full log is the best I can offer unless I figure out how to reproduce this (it hasn't even re-occurred randomly). If you skip the first 50 lines and ignore the libinput errors, it's entirely errors produced during or immediately after a freeze. gnome-shell-extension-prefs shows the following enabled: - Desktop Icons - Ubuntu AppIndicators - Ubuntu Dock I don't know how to reproduce this problem, so I can't meaningfully test disabling the Ubuntu AppIndicators extension. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367364/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
>From top, just now (gnome-shell has not been freezing during this session): PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3885 kai 20 0 8342772 602120 331580 R 12.9 1.8 101:26.43 gnome-shell When I enter and leave the activities screen, CPU time spikes to about 30%. At idle it runs between 3% and 13%. Cumulative CPU time is over 8-10h. I don't have any record of the resource usage when it was freezing, but I will try to grab that if it happens again. This probably wasn't a low memory situation as the machine had just booted and I had wasn't able to run anything more than a terminal before I gave up and rebooted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
In logs I have going back 6 months the errors "Attempting to run a JS callback during garbage collection." and "The offending callback was ..." only appear on one other date. There is a similar message "Attempting to call back into JSAPI during the sweeping phase of GC." that appears more frequently. I think it will be hard to get good timing data when the console is freezing and unresponsive and I'm not sure when the issue might re- occur. I'm attaching the log from this session, as well as the log from my current session for comparison. ** Attachment added: "GnomeShellFreezeLog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367200/+files/GnomeShellFreezeLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
** Attachment added: "GnomeShellNormalLog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367201/+files/GnomeShellNormalLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876946] [NEW] gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
Public bug reported: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: New Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
At this point it's just these log messages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Incomplete Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
In a virtual machine I can reproduce this by installing pulseaudio and docker.io. I'm attaching a Vagrantfile that reproduces the issue for me. :; vagrant up :; vagrant ssh -t -- journalctl -u rtkit-daemon ** Attachment added: "vagrantfile to reproduce issue" https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5364696/+files/Vagrantfile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Incomplete Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875665] [NEW] rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Public bug reported: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) ** Affects: rtkit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: New Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out
I'm unable to resubmit the retraced crash report using the linked instructions. A message in the journal says "Crash already reported." I can try submitting a new report if the problem reoccurs. Below is the content of StacktraceSource. I'm attaching the more detailed ThreadStacktrace. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Error: raise.c was not found in source tree] #1 0x5573ecb6a52a in dump_gjs_stack_on_signal_handler () #2 #3 0x in ?? () #4 0x7f073d599a37 in meta_selection_source_wayland_deactivated (source=0x5573fc425b50) at ../src/wayland/meta-selection-source-wayland.c:121 [Error: meta-selection-source-wayland.c was not found in source tree] #5 0x7f073e191936 in _g_closure_invoke_va () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1 #6 0x7f073e1ae36c in g_signal_emit_valist () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1 #7 0x7f073e1aefa9 in g_signal_emit_by_name () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1 #8 0x7f073d55fd99 in meta_selection_set_owner (selection=0x5573edfeb8c0, selection_type=META_SELECTION_DND, owner=0x5573f439a290) at ../src/core/meta-selection.c:100 [Error: meta-selection.c was not found in source tree] #9 0x7f073d586437 in source_new_cb (object=, res=, user_data=user_data@entry=0x5573fdafb8a0) at ../src/x11/meta-x11-selection.c:257 [Error: meta-x11-selection.c was not found in source tree] #10 0x7f073e28c029 in g_task_return_now (task=0x7f072c003a50) at ../../../gio/gtask.c:1212 [Error: gtask.c was not found in source tree] #11 0x7f073e28cbfd in g_task_return (task=0x7f072c003a50, type=) at ../../../gio/gtask.c:1281 [Error: gtask.c was not found in source tree] #12 0x7f073d5819b2 in read_mimetypes_cb (stream=, res=, task=task@entry=0x7f072c003a50) at ../src/x11/meta-selection-source-x11.c:199 [Error: meta-selection-source-x11.c was not found in source tree] #13 0x7f073e28c029 in g_task_return_now (task=0x5573efdee8e0) at ../../../gio/gtask.c:1212 [Error: gtask.c was not found in source tree] #14 0x7f073e28cbfd in g_task_return (task=0x5573efdee8e0, type=) at ../../../gio/gtask.c:1281 [Error: gtask.c was not found in source tree] #15 0x7f073e256826 in read_bytes_callback (stream=0x5573f3cb0380, result=0x5573fdae4e40, user_data=0x5573efdee8e0) at ../../../gio/ginputstream.c:874 [Error: ginputstream.c was not found in source tree] #16 0x7f073e257d2b in async_ready_callback_wrapper (source_object=0x5573f3cb0380, res=0x5573fdae4e40, user_data=0x5573efdee8e0) at ../../../gio/ginputstream.c:532 [Error: ginputstream.c was not found in source tree] #17 0x7f073e28c029 in g_task_return_now (task=0x5573fdae4e40) at ../../../gio/gtask.c:1212 [Error: gtask.c was not found in source tree] #18 0x7f073e28c06d in complete_in_idle_cb (task=0x5573fdae4e40) at ../../../gio/gtask.c:1226 [Error: gtask.c was not found in source tree] #19 0x7f073e0a671e in g_main_context_dispatch () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1 #20 0x7f073e0a6ad0 in g_main_context_iterate.isra () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1 #21 0x7f073e0a6dc3 in g_main_loop_run () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1 #22 0x7f073d55c280 in meta_run () at ../src/core/main.c:676 #23 0x5573ecb69d85 in main () ** Attachment added: "ThreadStacktrace" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+attachment/5309904/+files/ThreadStacktrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855198 Title: Gnome shell crash, maybe related to wireless mouse battery running out Status in gnome-shell package in Ubuntu: Invalid Bug description: This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously. There is a crash report, with the following oops id: https://errors.ubuntu.com/oops/8ad61c2c-16e5-11ea-b0eb-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 17:44:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Desktop-packages] [Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out
Adding StacktraceSource as an attachment since it got folded in my previous comment. ** Attachment added: "StacktraceSource" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+attachment/5309905/+files/StacktraceSource -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855198 Title: Gnome shell crash, maybe related to wireless mouse battery running out Status in gnome-shell package in Ubuntu: Invalid Bug description: This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously. There is a crash report, with the following oops id: https://errors.ubuntu.com/oops/8ad61c2c-16e5-11ea-b0eb-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 17:44:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855198] Re: Gnome shell crash, maybe related to wireless mouse battery running out
Sorry, I'm not very familiar with apport or what the ubuntu error collection system does with crash files. I've been able to get an actual stack trace using apport-retrace here. Is that useful if I resubmit with that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855198 Title: Gnome shell crash, maybe related to wireless mouse battery running out Status in gnome-shell package in Ubuntu: Invalid Bug description: This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously. There is a crash report, with the following oops id: https://errors.ubuntu.com/oops/8ad61c2c-16e5-11ea-b0eb-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 17:44:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855198] [NEW] Gnome shell crash, maybe related to wireless mouse battery running out
Public bug reported: This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously. There is a crash report, with the following oops id: 8ad61c2c-16e5-11ea-b0eb-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 17:44:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1855198 Title: Gnome shell crash, maybe related to wireless mouse battery running out Status in gnome-shell package in Ubuntu: New Bug description: This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously. There is a crash report, with the following oops id: 8ad61c2c-16e5-11ea-b0eb-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 4 17:44:39 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851564] [NEW] Daily Limit Exceeded messages for google calendars
Public bug reported: This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have logs going back to mid august. The message is repeated for each calendar at various times. Nov 06 13:49:13 dipper gnome-calendar[8681]: source_credentials_required_cb: Failed to authenticate 'Kai Groner': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:07:56 2019 InstallationDate: Installed on 2019-06-18 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1851564 Title: Daily Limit Exceeded messages for google calendars Status in gnome-calendar package in Ubuntu: New Bug description: This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have logs going back to mid august. The message is repeated for each calendar at various times. Nov 06 13:49:13 dipper gnome-calendar[8681]: source_credentials_required_cb: Failed to authenticate 'Kai Groner': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:07:56 2019 InstallationDate: Installed on 2019-06-18 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1851564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850173] Re: HDMI output selected when it isn't plugged in
** Description changed: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have - to repeat this after suspend/resume. + to repeat this sometimes. I'm not sure what the pattern is. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=tmux-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850173 Title: HDMI output selected when it isn't plugged in Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this sometimes. I'm not sure what the pattern is. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850173] [NEW] HDMI output selected when it isn't plugged in
Public bug reported: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this after suspend/resume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1850173 Title: HDMI output selected when it isn't plugged in Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this after suspend/resume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849415] [NEW] Magnifier stuck on wayland
Public bug reported: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849415 Title: Magnifier stuck on wayland Status in gnome-shell package in Ubuntu: New Bug description: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
I am experiencing this after upgrading to 19.10 and enabling fractional scaling on wayland. The extra cursor appears at 125%/150% scaling and disappears at 100% scaling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
