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 261101 - evolution-alarm-notify crashes on startup (segmentation fault)
evolution-alarm-notify crashes on startup (segmentation fault)
Status: RESOLVED DUPLICATE of bug 249624
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-07-02 17:43 UTC by Adam Ambrose
Modified: 2004-07-02 19:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Adam Ambrose 2004-07-02 17:43:30 UTC
Package: Evolution
Priority: Normal
Version: 1.4.6
Synopsis: evolution-alarm-notify crashes on startup (segmentation fault)
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
I get a error dialog when first starting evolution for the day, saying
that evolution-alarm-notify has crashed with a segmentation fault. 
Evolution continues to load without any problems.

I have received alarm messages successfully in the past.  I may have
upgraded evolution since the alarm was first created, but I am not
sure.

Steps to reproduce the problem:
1. Set an alarm for a few minutes in the future
2. Shut down evolution & machine
3. Wait for alarm time to pass
4. Startup machine, login, start evolution.

Actual Results:
Get Error dialog described above.

Expected Results:
Get alarm notification dialog.

How often does this happen?
Recently, it has been occurring every time I start evolution when I
first start the computer.  If I exit evolution & then start it again
right away, I do not get the error.

Additional Information:




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-02 19:25:28 UTC

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