** Changed in: evolution
Status: New => Fix Released
** Changed in: evolution
Importance: Unknown => Medium
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
** Branch linked: lp:ubuntu/evolution
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.
** Changed in: evolution
Status: Unknown => New
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-b
** Also affects: evolution via
http://bugzilla.gnome.org/show_bug.cgi?id=573919
Importance: Unknown
Status: Unknown
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Deskt
Reported in upstream bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=573919
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
This bug was fixed in the package evolution - 2.25.92-0ubuntu1
---
evolution (2.25.92-0ubuntu1) jaunty; urgency=low
* New upstream version:
Bug Fixes:
- #238346 : Set timezones from component to the calendar first, then add
events
- #333716 : Do not store incomplete or
> - would it be possible to have a libnotify call to query capabilities rather
> than having to implement those
> can_support_actions() in each softwares?
Well, that'd require changing libnotify, which we currently don't do.
timeout shouldn't be affected, since it just uses DEFAULT anyway.
> -
thank you for your work there, some comments though:
- would it be possible to have a libnotify call to query capabilities rather
than having to implement those can_support_actions() in each softwares?
- are urgency and timeout equivalent to actions in regard of the spec? ie you
check for action
This proposed patch will check if actions are supported, and only
display the action if it is.
** Attachment added: "328596.patch"
http://launchpadlibrarian.net/23300219/328596.patch
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this
** Tags added: jaunty-uif
--
evolution shouldn't use notifications with actions
https://bugs.launchpad.net/bugs/328596
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://
https://wiki.ubuntu.com/NotifyOSD is available now and has details
** Changed in: evolution (Ubuntu)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Incomplete => Confirmed
** Tags added: notifications
--
evolution shouldn't
Hi,
"This should be replaced by the message status menu."
It's a bit difficult to know what to do here without a specification for
this.
Is there something we can do with evolution in Jaunty in the meantime? Is this
something which
will land for jaunty? Is there something we can do that will wo
12 matches
Mail list logo
