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 267838 - evolution-alarm-notify has quit unexpectedly
evolution-alarm-notify has quit unexpectedly
Status: RESOLVED DUPLICATE of bug 249624
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-10-08 14:19 UTC by tlabach
Modified: 2004-10-11 19:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tlabach 2004-10-08 14:19:55 UTC
Distribution:                         Solaris 9 4/03 s9s_u3wos_08 SPARC
Package: Evolution
Priority: Normal
Version: GNOME2.6.2 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: evolution-alarm-notify has quit unexpectedly
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
Description:
Description of Problem:

An error popup appears announcing that "evolution-alarm-notify has quit
unexpectedly".

Steps to reproduce the problem:
1. set up calendar appointments with reminders.
2. After one or two reminders are displayed, the problem occurs.
3. 

Actual Results:

After one or two reminders, the calendar will not display reminders

Expected Results:

The calendar will display all requested reminders.

How often does this happen?

Shortly after every fresh startup of evolution.

Additional Information:

blastwave evolution 1.4.6 package for Solaris 9.


Unknown reporter: tlabach@uwaterloo.ca, 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-10-11 19:50:39 UTC
What Evolution version is this?
Comment 2 Gerardo Marin 2004-10-11 19:55:31 UTC
Sorry, overlooked last line.


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