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 273130 - evolution-alarm-notify has quit unexpectedly
evolution-alarm-notify has quit unexpectedly
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-02-28 23:02 UTC by steven.unger
Modified: 2005-06-16 18:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description steven.unger 2005-02-28 23:02:37 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution-alarm-notify has quit unexpectedly
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
evolution calendar notification shows first alarm display, then abends

Steps to reproduce the crash:
1. launch Evolution 1.4.6 w/connector	
2. past alarm notification displays
3. 

Expected Results:
Error message: Application "evolution-alarm-notify" has quit
unexpectedly.

How often does this happen?
Consistently

Additional Information:
Fedora Core 2; kernel 2.6.9-1.6_FC2; Connector 1.4.7.2-0.fdr.1.2


Unknown reporter: steven.unger@cingular.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 C Shilpa 2005-04-07 12:57:42 UTC

*** This bug has been marked as a duplicate of 271693 ***
Comment 2 C Shilpa 2005-05-17 05:33:24 UTC
sorry, wrong duplicate.
Comment 3 Peter Robinson 2005-06-09 15:08:25 UTC
When ever I login I get evolution-alarm-notify crashing. When I run it from the
command line I get the following errors and then a dialog to say that the
application crashed and asking if I wanted to inform developers (which it won't
allow me to submit due it it not recognising its part of evolution.

I'm running 2.2.2 with exchange connector.

[peterr@localhost ~]$ /usr/libexec/evolution/2.2/evolution-alarm-notify
evolution-alarm-notify-Message: Setting timeout for 29219 1118358000 1118328781
evolution-alarm-notify-Message:  Fri Jun 10 00:00:00 2005

evolution-alarm-notify-Message:  Thu Jun  9 15:53:01 2005

evolution-alarm-notify-Message: Loading
file:///home/peterr/.evolution/calendar/local/system
evolution-alarm-notify-Message: Loading contacts:///
evolution-alarm-notify-Message: Loading
exchange://peterr@mail.foo.com/personal/Calendar
evolution-alarm-notify-Message: Loading
file:///home/peterr/.evolution/tasks/local/system
evolution-alarm-notify-Message: Loading
exchange://peterr@mail.foo.com/personal/Tasks
evolution-alarm-notify-Message: alarm-notify.c:176: Could not get the list of
sources to load
evolution-alarm-notify-Message: Loading alarms for today
Comment 4 Poornima 2005-06-16 18:26:36 UTC
Stevan: There are lots of alarm notify crash bugs already raised. So the bug 
raised seems to be related to one of the existing. The bug details are 
incomplete for a crash bug without stack traces. So please reopen this bug if 
the stack traces observed in your system are different then existing alarm 
notify crash bugs.