[Bug 2063336] Re: All Chromium based applications fail to render on Wayland
Daniel, yes it's indeed an NVIDIA GPU as the primary one (both primary and secondary are NVIDIA, an RTX A6000 and a RTX3090). The issue shows up for both the Chromium snap and any other Chromium based app I could find. I did have some Wayland & NVIDIA issues (glitchy rendering after typing on the keyboard) also on Mantic and before on this same system, but this symptom is a lot more extreme now on Noble. Another observation as I messed around with reproducing this: I can see that on Noble hotplugging the display on Wayland doesn't really work (between these same NVIDIA GPUs), whereas on Mantic I didn't have the same problem. ** Description changed: - I am noticing two - - - Most of the time (3/4 desktop sessions attempted) all Chromium based + Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, - and when screenshotted, showing supposedly showing transparent pixels. + and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063336] [NEW] All Chromium based applications fail to render (dual NVIDIA GPU system)
Public bug reported: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble snap wayland-session ** Attachment added: "Screenshot showing the blank window that is supposed to be Chromium" https://bugs.launchpad.net/bugs/2063336/+attachment/5770045/+files/Screenshot%20from%202024-04-24%2016-21-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render (dual NVIDIA GPU system) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971130] Re: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
I left a terminal session tailing `/var/log/syslog` to track what's happening at the time when the notification shows up, and indeed managed to observe it happen again, with a fragment of system logs found below. Looks like NetworkManager fires off a `CONNECTED_SITE` state change, and the location is updated -> notification fires, even if timezone has not changed. I think the condition that triggers the unnecessary notification is the _location_ changing even if the timezone has not changed, and for whatever reason the location keeps flickering between either Denmark or Germany (both in CET). Here goes the log example: ``` May 2 15:19:41 iris NetworkManager[4609]: [1651493981.4907] manager: NetworkManager state is now CONNECTED_SITE May 2 15:19:41 iris dbus-daemon[4607]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=4609 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") May 2 15:19:41 iris systemd[1]: Starting Network Manager Script Dispatcher Service... May 2 15:19:41 iris dbus-daemon[4607]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' May 2 15:19:41 iris systemd[1]: Started Network Manager Script Dispatcher Service. May 2 15:19:41 iris NetworkManager[4609]: [1651493981.7719] manager: NetworkManager state is now CONNECTED_GLOBAL May 2 15:19:46 iris wpa_supplicant[4694]: TDLS: Invalid frame - payloadtype=1 category=240 action=26 May 2 15:19:51 iris systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. May 2 15:19:52 iris gsd-datetime[7371]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed May 2 15:19:52 iris gsd-datetime[7371]: message repeated 71 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_has_coords: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_city_name: assertion 'loc != NULL' failed May 2 15:19:52 iris gsd-datetime[7371]: gweather_location_get_country: assertion 'loc != NULL' failed May 2 15:19:52 ir
[Bug 1971130] Re: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
** Description changed: I am seeing repeated "time zone updated" notifications when "Automatic Time Zone" is enabled in Settings > Date & Time in gnome-control-center - on 22.04, whilst my gnome session continues to be active. The timezone - itself continues to be correct (and unchanged). + on 22.04, whilst my gnome session continues to be active (without me + taking any time related actions). The timezone itself continues to be + correct (and unchanged). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 10:26:46 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-26 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971130 Title: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971130] [NEW] Repeated "time zone updated" notifications when "Automatic Time Zone" enabled
Public bug reported: I am seeing repeated "time zone updated" notifications when "Automatic Time Zone" is enabled in Settings > Date & Time in gnome-control-center on 22.04, whilst my gnome session continues to be active. The timezone itself continues to be correct (and unchanged). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 2 10:26:46 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-26 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971130 Title: Repeated "time zone updated" notifications when "Automatic Time Zone" enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970389] [NEW] [nvidia] Janky text entry in some applications in a GNOME / Wayland session
Public bug reported: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) ** Affects: xorg-server Importance: Unknown Status: Unknown ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy nvidia nvidia-wayland wayland wayland-session ** Attachment added: "A video showing the janky text entry" https://bugs.launchpad.net/bugs/1970389/+attachment/5583887/+files/IMG_8615.MOV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry in some applications in a GNOME / Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
I can confirm that with the proposed update on a previously impacted system (where Wayland was not available as an option) with an NVIDIA only GPU (RTX3090), "Test Case 1" behaves after the proposed update as expected: the Wayland option is made available, but default is "Ubuntu" (not "Ubuntu on Wayland"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Tags added: cbox-51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] [NEW] 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
Public bug reported: After installing the proposed snapd update 2.54.2+21.10, I see the following when launching a new fish shell session on 21.10: ``` /usr/share/fish/vendor_conf.d/snapd.fish (line 3): fish_add_path -aP $snap_bin_path ^ from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish called on line 294 of file /usr/share/fish/config.fish from sourcing file /usr/share/fish/config.fish called during startup ``` Said line of `/usr/share/fish/vendor_conf.d/snapd.fish` references the fish function `fish_add_path` which seems (*) to have only been made available in fish 3.2 (Ubuntu 21.10 packages 3.1.2 of fish presently). Upgrading fish by installing 3.2 or later via https://launchpad.net/~fish-shell/+archive/ubuntu/release-3 indeed works around (or modifying above script to `set -gx $PATH ...` (I guess this comes with the downside of duplicate entries that `fish_add_path` removes?) (*) PR adding `fish_add_path`: https://github.com/fish-shell/fish-shell/pull/7028 was part of the 3.2 milestone ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
