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 253943 - Evolution-alarm-notify crashes when initially loggin in to gnome
Evolution-alarm-notify crashes when initially loggin in to gnome
Status: RESOLVED DUPLICATE of bug 241624
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-02-05 18:09 UTC by garth
Modified: 2004-02-06 18:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description garth 2004-02-05 18:09:10 UTC
Distribution: Unknown
Package: Evolution
Priority: Normal
Version: GNOME2.4.1 unspecified
Gnome-Distributor: FreeBSD GNOME Project
Synopsis: Evolution-alarm-notify crashes when initially loggin in to gnome
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

I am running Gnome2 on FreeBSD and I have Evolution as a saved window on
my desktop.  Whenever I log in, evolution-alarm-notify crashes and
displays the bug dialog.  The evolution mail program has no problem and
loads successfully.  Additionally, from a 'ps auwx | grep evolution' it
looks like evolution-alarm-notify is running (in addition to the crashed
process which is being held by this debug process)

Steps to reproduce the crash:
1. Start evolution in Gnome2
2. Log out of Gnome2 and check 'Save current setup' in the dialog box
3. Log into Gnome2

Expected Results:

Evolution should start without any problems

How often does this happen?

Every time.

Additional Information:


Unknown reporter: garth@zappos.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-02-06 18:50:42 UTC

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