OpenSUSE Freeze Fix

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Disabling desktop system notifications on Linux (KDE Plasma: remove/disable the Notifications system-tray plasmoid) causes Cursor chat to freeze for ~60 seconds when an agent turn finishes.

Root cause on the Cursor side: the Electron main process calls libnotify synchronously. When org.freedesktop.Notifications is unowned, D-Bus activation blocks inside StartServiceByName until timeout. Chat/UI is stuck for that whole wait. Journal shows:

notify_notification_show: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached

This is not a model/chat-storage bug. KWallet and Secret Service stayed fast. Re-enabling the Notifications plasmoid in the system tray made plasmashell own the bus name again; notify returned in ~10 ms and Cursor stopped freezing. Cursor should treat desktop notifications as best-effort and never block the main process / chat when the OS notification service is missing or disabled.

Steps to Reproduce

  1. On KDE Plasma 6 (Linux), open Configure System Tray → Entries and disable/remove Notifications so the Notifications plasmoid is not loaded.

  2. Confirm the session bus name is unowned (optional; listing only — do not call methods on it while broken):

    busctl --user list | grep org.freedesktop.Notifications

    Expect (activatable) with no plasmashell owner.

  3. In Cursor IDE, run a chat agent turn that would normally fire a completion notification.

  4. When the turn finishes, Cursor chat/UI freezes for roughly 60 seconds.

  5. Check the user journal for Cursor notify_notification_show / StartServiceByName timeout errors and plasma_waitforname: WaitForName: Service was not registered within timeout.

  6. Re-enable Notifications in the system tray (Shown/Auto).

  7. Confirm org.freedesktop.Notifications is owned by plasmashell and the next agent completion no longer freezes.

Expected Behavior

If desktop notifications are disabled or unavailable, Cursor should skip or fail the notification without blocking chat. The IDE must stay responsive when the OS notification service is missing.

Operating System

Linux

Version Information

IDE:

Version: 3.29.15
VSCode Version: 1.128.0
Commit: 86776fcb52ca505783155631089b65d646f9b030
Date: 2026-11-08T21:35:59.668Z
Electron: (bundled with Cursor Linux x64 stable)
OS: Linux x64 (openSUSE Tumbleweed, KDE Plasma 6 Wayland)

For AI issues: which model did you use?

Not model-specific. Observed across agent chat turns; freeze is on the desktop notification path after the turn completes.

For AI issues: add Request ID with privacy disabled

Request ID correlated with a freeze-side-effect slow span (~136s ComposerBlobStore.getBlob.slow while main process was blocked on notify):

32e3a4b6-604e-4695-b695-6741db9687bd

Additional Information

Please read this first: disabling system notifications (Plasma Notifications tray entry) leaves org.freedesktop.Notifications unowned. Cursor still tries to notify via libnotify on the Electron main thread, so chat freezes for the full D-Bus activation timeout (~60s). That is the bug.

Workaround that restored normal speed: manually re-enable the Notifications plasmoid in the system tray. After fix:

  • org.freedesktop.Notifications owned by plasmashell
  • notify-send ~10 ms
  • Cursor agent-finish freezes gone

Evidence while broken:

  • busctl: org.freedesktop.Notifications = (activatable) / unowned

  • Journal (examples from 2026-11-11):

    cursor: notify_notification_show: ... StartServiceByName for org.freedesktop.Notifications: Timeout was reached
    plasma_waitforname: WaitForName: Service was not registered within timeout
    
  • Same hang also hit WhatsApp / notify-send / kded6 on this host; Cursor is uniquely painful because chat completion triggers notify on the main process.

  • Plasma activator file only waits; it does not start a daemon:

    /usr/share/dbus-1/services/org.kde.plasma.Notifications.service → Exec=/usr/bin/plasma_waitforname org.freedesktop.Notifications

Requested fix: make Linux desktop notifications non-blocking (async / worker / fail-fast). If the Notifications name is missing or only activatable, skip further notify attempts for the session after the first failure instead of blocking chat for ~60s.

Full local investigation report available if useful (mechanism, layout config, before/after timings).

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @David_Gayman, you can avoid this from Cursor’s side too, without re-enabling the Plasma applet: turn off Cursor Settings > General > Notifications > System Notifications. With that off, Cursor stops sending a desktop notification when an agent finishes or needs approval, so there’s nothing left to wait on.

Your read of the cause matches what we see: that notification is sent from the main process, and with nothing owning org.freedesktop.Notifications the whole window waits on it. A missing notification service shouldn’t be able to hold up the UI (this is something we already fixed for Grok Bot), so I’ve passed this to the team.