AppImageLauncher desktop ID does not match notification desktop-entry, so GNOME notification settings do not suppress notifications

[pettijohn]

Steps to reproduce

1. Install the OpenCloud Desktop AppImage using AppImageLauncher, following the official Linux installation documentation.

2. Open Settings → Notifications in GNOME.

3. Disable notifications for the entry shown as:

   OpenCloud Desktop desktop sync client (3.0.3.2073)
   

4. Trigger a sync activity notification by modifying a synchronized file.

5. Observe that the notification is still shown.

6. Inspect the notification with:

   dbus-monitor --session \
     "interface='org.freedesktop.Notifications',member='Notify'"

7. Observe that OpenCloud sends:

   desktop-entry = opencloud
   

   while AppImageLauncher installed the desktop entry as:

   appimagekit_d93ff9afb874b7190678e9b246ec8f6f-OpenCloud_Desktop_desktop_sync_client.desktop
   

Expected behavior

• Disabling OpenCloud notifications in GNOME Settings should suppress all subsequent OpenCloud notification banners.
• The desktop entry shown in GNOME Settings should match the desktop-entry identifier used by OpenCloud notifications.

Actual behavior

• GNOME Settings disables notifications for the AppImageLauncher-generated desktop ID, but OpenCloud sends notifications with desktop-entry=opencloud.
• Because these identifiers do not match, GNOME applies the notification settings to the wrong application entry and notifications continue to appear.
• Manually creating an opencloud.desktop entry and disabling /org/gnome/desktop/notifications/application/opencloud/ successfully suppresses the notifications.

Setup

• Operating system: Ubuntu 26.04, GNOME, Wayland

• Client version: OpenCloud Desktop 3.0.3.2073

• Installation method: AppImage installed and integrated using AppImageLauncher

• GNOME notification settings created for the AppImageLauncher entry:

  [appimagekit-d93ff9afb874b7190678e9b246ec8f6f-opencloud-desktop-desktop-sync-client]
  application-id='appimagekit_d93ff9afb874b7190678e9b246ec8f6f-OpenCloud_Desktop_desktop_sync_client.desktop'
  enable=false
  enable-sound-alerts=false
  show-banners=false

• Notification emitted by OpenCloud:

  method call sender=:1.95 -> destination=org.freedesktop.Notifications
  interface=org.freedesktop.Notifications
  member=Notify
  
     string "OpenCloud Desktop"
     uint32 0
     string "file:///tmp/OpenCloud-ILLXuc/4294967296.png"
     string "Sync Activity"
     string "»Photostream/GPX/20260720.gpx« has been updated."
     array [
     ]
     array [
        dict entry(
           string "desktop-entry"
           variant string "opencloud"
        )
        dict entry(
           string "image-path"
           variant string "file:///tmp/OpenCloud-ILLXuc/317827579904.png"
        )
     ]
     int32 -1
  

• Working manual configuration:

  [opencloud]
  application-id='opencloud.desktop'
  enable=false
  enable-sound-alerts=false
  show-banners=false

• Suspected cause: the notification desktop-entry value, opencloud, does not match the AppImageLauncher-generated desktop-file ID.

[TheOneRing]

That's probably caused by:

desktop/src/gui/main.cpp

Lines 413 to 422 in 0e2884a

	#ifdef Q_OS_LINUX
	// HACK:
	// With X11 arg0.name is used to map WM_CLASS to the desktop file.
	// With Wayland it uses app.desktopFileName() or app.organizationDomain()
	// As we preferably use AppImages the real deskop file name is unknown, we just ensure it mathces the StartupWMClass entry in our desktop file
	if (qgetenv("XDG_SESSION_TYPE") == "wayland") {
	// https://bugreports.qt.io/browse/QTBUG-77182 Qt 6.9 brings setAppId() but its private api
	app.setDesktopFileName(QFileInfo(app.applicationFilePath()).baseName());
	}
	#endif

🙈