After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 352429 - evolution-alarm-notify is not started upon log-in
evolution-alarm-notify is not started upon log-in
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.8.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-08-22 17:58 UTC by Tolan Blundell
Modified: 2012-10-10 02:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Tolan Blundell 2006-08-22 17:58:01 UTC 
Please describe the problem:
When logging into Gnome e-a-n should be started by default (perhaps only if there are items with alarms in the future). Currently it only starts when the Evolution application is started. This leads to missed alarms.

It is reasonable for an end user to expect alarm notification without starting Evolution as the Gnome clock/calendar applet shows these events, thus they are not necessarily tied specifically to Evolution in the user's mind.

Steps to reproduce:
1. Log in to Gnome
2. Check the process list to see if evolution-alarm-notify is running

This has been tested on Ubuntu 6.06. I filed a bug with them and it was rejected as an upstream issue.


Actual results:
e-a-n is not running.

Expected results:
e-a-n should be running if there are alarm events.

Does this happen every time?
To my knowledge

Other information:
Comment 1 André Klapper 2006-08-28 13:24:31 UTC 
e-a-n will be *triggered* by evolution-data-server if there is an alarm t display the alarm. e-a-n does not manage alarms.
in my humble opinion, ubuntu should fix this by starting e-d-s by default.
seb?
Comment 2 Sebastien Bacher 2006-09-27 10:27:42 UTC 
How is evolution-data-server supposed to be started? Shouldn't it be autospawned since the gnome-panel calendar uses it?

Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/evolution-data-server/+bug/62593
Comment 3 Karsten Bräckelmann 2006-09-27 10:48:47 UTC 
Comment 1 is wrong. Sorry, Andre. ;)

The issue is, that e-a-n needs to be added to the session, AFAIK. Also, I'm pretty sure this is filed somewhere already...
Comment 4 Martin Pitt 2006-09-27 14:06:47 UTC 
For the record, e-d-s is started automatically. e-a-n is not. I do not know whether it was started with the session or triggered by e-d-s in earlier releases.
Comment 5 Martin Pitt 2006-10-13 13:06:39 UTC 
For Ubuntu 6.10 we will install /etc/xdg/autostart/evolution-alarm-notify.desktop:

---- 8< -----
[Desktop Entry]
Encoding=UTF-8
Name=Evolution Alarm Notifier
Comment=Evolution Alarm Notifier
Icon=stock_alarm
Exec=/usr/lib/evolution/2.8/evolution-alarm-notify
Terminal=false
Type=Application
Categories=
---- 8< ----

Not sure whether this is the cleanest solution, but it works fine.
Comment 6 Matthew Barnes 2012-10-10 02:55:10 UTC 
evolution-alarm-notify has an autostart .desktop file now.

Closing this as FIXED.