Desktop crash on Linux: Notifications "Open Settings" tries to spawn gnome-control-center (ENOENT)

[yart]

Hi team,

I found another Desktop issue on Linux.

In Settings → App → Notifications, clicking Open Settings crashes Goose Desktop and shows this error:

spawn gnome-control-center ENOENT

From the UI, Goose says that notifications are managed by the OS, so the button appears to be intended to open the system notification settings. However, on my setup it seems to assume a GNOME environment and tries to launch gnome-control-center directly.

That does not work on my system and causes Goose Desktop to fail instead of handling the situation gracefully.

Expected behavior

• Goose Desktop should not crash when clicking Open Settings.
• On non-GNOME Linux desktops, it should either:
  • use a desktop-appropriate settings integration,
  • use xdg/portal-based behavior if available,
  • or show a non-fatal message that system notification settings cannot be opened automatically.

Actual behavior

• Clicking Open Settings leads to an error screen.
• The error shown is:

spawn gnome-control-center ENOENT

Environment

• OS: Arch Linux
• Session: Wayland / Hyprland
• Goose Desktop version: 1.29.0

Thanks.

[mvanhorn]

Submitted a fix in #8304 - uses execFileSync('which', [cmd]) to check binary availability before spawning, instead of relying on try/catch around spawn().