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 261135 - "evolution-alarm-notify exited unexpectedly" on startup
"evolution-alarm-notify exited unexpectedly" on startup
Status: RESOLVED DUPLICATE of bug 249624
Product: evolution
Classification: Applications
Component: general
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-07-03 21:51 UTC by Jack Woychowski
Modified: 2004-07-05 19:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jack Woychowski 2004-07-03 21:51:33 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.6. 1.4.6
Gnome-Distributor: Red Hat, Inc
Synopsis: "evolution-alarm-notify exited unexpectedly" on startup
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 1.4.6
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:

On every startup, I get a popup saying evolution-alarm-notify has exited
unexpectedly.
The program will continue after acknowledging the error, though
functionality is limited
(obviously no alarms) and sometimes strange behaviour occurs such as
inability to contact
calendar server, missing appointments or inability to add appointments.

Steps to reproduce the crash:
1. Just start up product
2. 
3. 

Expected Results:


How often does this happen?
Occurs on every startup; began happening after an update to 1.4.6 via
rc.

Additional Information:

Occurred on both Fedora Core 1 and now on Fedora Core 2.


Unknown reporter: wojo@wojones.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2004-07-05 19:37:37 UTC

*** This bug has been marked as a duplicate of 249624 ***