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 260295 - When adding current day as an exception to a recurring event, evolution-alarm-notify crashes
When adding current day as an exception to a recurring event, evolution-alarm...
Status: RESOLVED DUPLICATE of bug 249624
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-06-16 16:50 UTC by rtsai
Modified: 2004-06-17 17:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description rtsai 2004-06-16 16:50:44 UTC 
Distribution: Debian testing/unstable
Package: Evolution
Priority: Normal
Version:  unspecified
Synopsis: When adding current day as an exception to a recurring event, evolution-alarm-notify crashes
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

See summary

Steps to reproduce the crash:
1. Create a recurring weekly event (starting some time in the past) with
an alarm
2. When "today" is one of those days, add "today" as an exception to the
recurrence (e.g., no meeting this week) 

Expected Results:

Application "evolution-alarm-notify" (process xxx) has crashed due to a
fatal error.

How often does this happen?

fairly frequently

Additional Information:

Debian evolution 1.4.6-2


Unknown reporter: rtsai@netapp.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-06-17 17:14:23 UTC 

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