Does not display alarms until I start evolution
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | evolution-data-server |
Fix Released
|
Medium
|
||
| | evolution (Ubuntu) |
High
|
Martin Pitt | ||
| | Dapper |
Undecided
|
Unassigned | ||
Bug Description
For some weeks now I do not get appointment notifications (alarms) any more until I start evolution once (after closing it alarm notifications continue to work fine).
Reproduce:
* Start evolution, add an event in 10 minutes, add an alarm for '5 minutes before the event'
* Log out (check on VT that all your processes have terminated, kill -15 -1)
* Log back in and wait some minutes until the alarm time has passed (no notification here)
* open evolution and instantly see the late alarm, together with a blinking clock/exclamation mark in the panel
* after closing evo, further notifications work fine.
This worked well in earlier edgy and the stable releases before.
| Martin Pitt (pitti) wrote : | #1 |
Evolution alarm notify should really start on log-in. The gnome panel clock/calendar shows these events, for them not to actually trigger an alarm just because you haven't opened the app that edits them seems pretty poor, surely this is one of the major arguments for e-d-s?
This behaviour is also broken for me on Dapper.
I've filed a related bug about this, and there's one on Gnome's bugzilla too:
https:/
Related Gnome bug:
| Sebastien Bacher (seb128) wrote : | #4 |
Upstream bug about that: http://
| Changed in evolution-data-server: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → High |
| status: | Unconfirmed → Confirmed |
| Changed in evolution-data-server: | |
| status: | Unknown → Unconfirmed |
| Matt Zimmerman (mdz) wrote : | #5 |
Upstream says that either evolution-
| towsonu2003 (towsonu2003) wrote : | #6 |
having the same problem. not using evolution for much (except alarms), I almost missed the due dates to order books for the class I'll be teaching. ouch
| towsonu2003 (towsonu2003) wrote : | #7 |
any workarounds? like a program I can add to gnome session? thanks
| Martin Pitt (pitti) wrote : | #8 |
I'll take it for now, will look into it.
| Changed in evolution-data-server: | |
| assignee: | desktop-bugs → pitti |
| Changed in evolution-data-server: | |
| status: | Confirmed → In Progress |
| Martin Pitt (pitti) wrote : | #9 |
I see two possibilities here:
(1) spawn e-a-n from e-d-s
(2) add an /etc/xdg/autostart .desktop file for e-a-n to evolution
I'd prefer (2), it is the cleaner solution and also the one suggested by upstream in the upstream bug. (1) would have a better semantics, though (only started when necessary, can be --force-shutdown'ed if wanted, etc.). But having it always running should DTRT given that we don't want to miss meeting notifications :)
| Martin Pitt (pitti) wrote : | #10 |
If I put the attached .desktop file into /etc/xdg/autostart, it works. The only thing I'm concerned about: previously the process looked like this:
/usr/
(as started by evolution). Now the process has no command line arguments. Seb, does that hurt?
| Martin Pitt (pitti) wrote : | #11 |
evolution (2.8.1-0ubuntu3) edgy; urgency=low
.
* Add debian/
evolution-
because no notification went off! Closes: LP#62593
* debian/
| Changed in evolution-data-server: | |
| status: | In Progress → Fix Released |
| towsonu2003 (towsonu2003) wrote : | #12 |
can you comment on how to fix this one on dapper? thanks :)
| Martin Pitt (pitti) wrote : | #13 |
Sure, just stick the attached desktop file into /etc/xdg/autostart
| towsonu2003 (towsonu2003) wrote : | #14 |
just fixed references to evolution 2.8 (dapper has 2.6).
> just stick the attached desktop file into /etc/xdg/autostart
thanks a lot :) I'll report back if it causes any problems.
| towsonu2003 (towsonu2003) wrote : | #15 |
works nicely with dapper :) hopefully you can backport this fix to dapper.
| Changed in evolution: | |
| status: | Unconfirmed → Confirmed |
| Changed in evolution-data-server: | |
| importance: | Unknown → Medium |
| Changed in evolution (Ubuntu Dapper): | |
| status: | Confirmed → Invalid |
| Changed in evolution-data-server: | |
| status: | New → Fix Released |
I suspect the reason is that evolution-