[GTX 1070] Visual artifacts (white cursor blocks) and broken tray surfaces after NVIDIA 580.126.18 update

[reaonzaver-tech]

Describe the bug

After the latest update (2026-04-25) to NVIDIA driver 580.126.18 and cosmic-comp, I am experiencing two main issues on my GTX 1070:

1. Cursor Artifacts: Random white rectangular fields appear around the mouse cursor and disappear shortly after.
2. System Tray / App Indicators: Applications (like Heroic Games Manager) are visible in the tray, but clicking them does not open the window ("surface missing" errors in logs).

Steps to reproduce

• Boot into COSMIC session with NVIDIA 580.126.18.
• Move the cursor across the desktop (artifacts appear).
• Try to open a minimized app from the system tray (fails to render).

System Info (from bug_report_data.txt)

[HIER DEN INHALT DER DATEI bug_report_data.txt EINFÜGEN]

Additional Context

The issues started immediately after the update of cosmic-comp and the NVIDIA driver. Performance in heavy 3D applications (Cyberpunk 2077) seems relatively stable, but the desktop compositor stability is compromised.

System Logs & Info

Click to expand logs

[### System Information
Kernel: 6.18.7-76061807-generic
GPU: NVIDIA GeForce GTX 1070
Driver Version: NVRM version: NVIDIA UNIX x86_64 Kernel Module  580.126.18  Wed Feb 11 18:49:55 UTC 2026

### Graphics Stack
ii  cosmic-comp                                    0.1~1776708607~24.04~21679f2                                    amd64        Wayland compositor of pop-os cosmic shell
ii  libnvidia-egl-wayland1:amd64                   1:1.1.20-1pop1~1759419563~24.04~6d277c8                         amd64        Wayland EGL External Platform library -- shared library
ii  libnvidia-egl-wayland1:i386                    1:1.1.20-1pop1~1759419563~24.04~6d277c8                         i386         Wayland EGL External Platform library -- shared library
ii  nvidia-driver-550                              580.126.18-1pop1~1774967562~24.04~fce3b46                       amd64        Transitional package for nvidia-driver-580
ii  nvidia-driver-580                              580.126.18-1pop1~1774967562~24.04~fce3b46                       amd64        NVIDIA driver metapackage

### Desktop Session
Session Type: wayland

### Recent Compositor / Graphics Errors
Apr 26 12:58:09 pop-os wireplumber[2737]: wp-proc-utils: failed to get cgroup for PID 708: Datei »/proc/708/status« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:09 pop-os wireplumber[2737]: wp-proc-utils: failed to get cmdline for PID 708: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:23 pop-os wireplumber[2737]: wp-proc-utils: failed to get status for PID 708: Datei »/proc/708/status« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:23 pop-os wireplumber[2737]: GLib: GError set over the top of a previous GError or uninitialized memory.
                                        This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
                                        The overwriting error message was: Datei »/proc/708/cgroup« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:23 pop-os wireplumber[2737]: wp-proc-utils: failed to get cgroup for PID 708: Datei »/proc/708/status« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:23 pop-os wireplumber[2737]: wp-proc-utils: failed to get cmdline for PID 708: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:52 pop-os wireplumber[2737]: wp-proc-utils: failed to get status for PID 708: Datei »/proc/708/status« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:52 pop-os wireplumber[2737]: GLib: GError set over the top of a previous GError or uninitialized memory.
                                        This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
                                        The overwriting error message was: Datei »/proc/708/cgroup« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:52 pop-os wireplumber[2737]: wp-proc-utils: failed to get cgroup for PID 708: Datei »/proc/708/status« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Apr 26 12:58:52 pop-os wireplumber[2737]: wp-proc-utils: failed to get cmdline for PID 708: Datei oder Verzeichnis nicht gefunden
Apr 26 12:59:00 pop-os cosmic-comp[2834]: surface missing from known popups
Apr 26 13:00:26 pop-os tracker-miner-fs-3[9416]: (tracker-extract-3:9416): GLib-GIO-WARNING **: 13:00:26.956: Error creating IO channel for /proc/self/mountinfo: Das Argument ist ungültig (g-io-error-quark, 13)
Apr 26 13:43:06 pop-os tracker-miner-fs-3[11994]: (tracker-extract-3:11994): GLib-GIO-WARNING **: 13:43:06.908: Error creating IO channel for /proc/self/mountinfo: Das Argument ist ungültig (g-io-error-quark, 13)
Apr 26 13:47:28 pop-os cosmic-comp[2834]: surface missing from known popups
Apr 26 13:48:47 pop-os cosmic-comp[2834]: Failed to force redraw for corner radius change.
Apr 26 13:48:48 pop-os xdg-desktop-por[3181]: Backend call failed: Remote peer disconnected
Apr 26 13:48:48 pop-os systemd[2716]: dbus-:1.1-org.freedesktop.impl.portal.desktop.cosmic@0.service: Failed with result 'core-dump'.
Apr 26 13:48:53 pop-os cosmic-comp[2834]: Failed to force redraw for corner radius change.
Apr 26 13:49:19 pop-os xdg-desktop-portal-cosmic[12554]: [2026-04-26T11:49:19Z WARN  cosmic_files::tab] failed to read metadata for entry at /home/zoanever/.steampath: No such file or directory (os error 2)
Apr 26 13:50:12 pop-os xdg-desktop-portal-cosmic[12554]: [2026-04-26T11:50:12Z WARN  cosmic_files::tab] failed to read metadata for entry at /home/zoanever/.steampath: No such file or directory (os error 2)
Apr 26 13:50:22 pop-os cosmic-comp[2834]: surface missing from known popups
]

[reaonzaver-tech]

Update 2026-04-26 – Accidental workaround discovered

After the compositor became completely unusable (Wayland session crashing immediately back to the login screen), the artifacts and all related issues (broken tray surfaces, unresponsive browser uploads, unclickable tray icons) disappeared on the next successful login.

My interpretation: The hard crash of cosmic-comp — unlike a clean logout — forced a full reinitialization of the NVIDIA driver's GPU buffer state. A normal session shutdown appears to preserve corrupted Explicit Sync state, whereas the crash discards it entirely. This suggests the root cause is persistent corrupted state in the 580.126.18 driver's Explicit Sync path rather than a one-time initialization failure.

The system is currently stable. I have pinned the driver at 580.126.18 to prevent further updates until this is resolved upstream:

sudo apt-mark hold nvidia-driver-580 nvidia-dkms-580 nvidia-firmware-580-580.126.18

The bug is reproducible in the sense that the corrupted state accumulates over a session — a hard crash resets it, a clean logout does not. Happy to run further diagnostics if useful.

[aomukai]

Confirmed on RTX 3060 / Pop!_OS 24.04 (noble)

Same issues after the 2026-04-25 update to NVIDIA 580.126.18 + cosmic-comp 1.0.2~1776374845~24.04~1d0e662:

• Clicking the App List applet steals keyboard focus and causes the compositor to lose popup surfaces (surface missing from known popups spam in logs)
• Shutdown/session dialogs appear and immediately vanish
• GL errors in cosmic-comp: GL_INVALID_VALUE: Size and/or offset out of range

The corrupted state accumulates over the session. The TTY kill workaround from the OP works (kill -9 $(pgrep cosmic-comp) from TTY2), confirming this is the same Explicit Sync state corruption — not hardware-specific to GTX 1070.

Rollback to 570 is not viable on Pop!_OS — nvidia-driver-570 is aliased to the 580 package in the Pop repo.