Ubuntu
notify-osd package

  1. Bug #1107919
  2. Comment #2

Comment 2 for bug 1107919

Revision history for this message
Bastien Nocera (hadess-deactivatedaccount) wrote :

You don't want to implement this for all apps, fine by me. But let me put this another way:
- gnome-settings-daemon and vino are GNOME components, and they're made to work with gnome-shell
- gnome-shell supports actions
- so there's no need to implement a fallback in those core GNOME components

So you could use that same proposal I made in comment 0, and only apply it to known core components by checking their well-known D-Bus names, eg. if the client is "org.gnome.SettingsDaemon", implement actions internally.

That would save you from patching gnome-settings-daemon, vino and other core GNOME components you're re-using, with minimal work in notify-osd.

I'm not going to bring this up on the fd.o lists, as this is an Ubuntu/notify-osd specific problem, or on the Unity list, as I have no vested interest in making Unity better. I'm speaking as the downstream maintainer for a project you reuse. If you're not willing to implement this, you're merely deflecting the work from you to the gnome-settings-daemon Ubuntu maintainers.