Screenshosts of the notification you're talking about would be nice. At the moment I can only guess what you're seeing. Next would be to file this bug against seahorse (and not notify-osd), because it is not within notify-osd's scope to control what gets send to it. Some advice for enhancing seahorse: 1.) Properly query the notification-daemon's capabilities (e.g. support for actions). We collected that information on this page https://wiki.ubuntu.com/NotificationDevelopmentGuidelines. Upstream notify-osd also comes with C-, Python- and C#-examples which can be easily adapted in applications (notify-osd/examples/*.[c|py|cs]). 2.) If notify-osd is found (or another notification-daemon not supporting the optional actions-capability) use proper dialogs, if user-interaction is needed and do not rely on notifications for this. notify-osd's rendered notifications are "click-through" and do not allow user-interaction by design. Guidelines for applications adapting to this we provide here https://wiki.ubuntu.com/NotificationDesignGuidelines.
-- notifikation with seahorse https://bugs.launchpad.net/bugs/375370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
