Re: [Evolution] calender reminders

[Peter Robinson <pbrobinson gmail com>]

> > > > > > That's fine in theory, but my calender often "forgets" to remind me ;-)
> > > > > >
> > > > > > That is, I set an alarm and then no reminder pops up at the set time.
> > > > > > Specifically, it seems that unless I visit my calender I get no reminders,
> > > > > > then when I open calender view the "forgotten" reminders pop up.  Since I
> > > > > > stay in mail view 99.995 of the time this next to useless.  Shouldn't the
> > > > > > reminders pop up over my mail view as well?
> > >
> > > Yes, they should. And I can confirm they do. :)
> > >
> > >
> > > > I have the same problem. I find that if evolution-alarm-notify isn't
> > > > running I don't get them. The problem is that for me at least is that
> > > > e-a-n crashes just about every time I run evo. You could try running
> > > > it manually and see if that works, it does sometimes (not regularly
> > > > though) for me.
> > > >
> > > > It looks like this problem is bugzilla and I added some details to it
> > > > but couldn't work out how to add the current version to the bug to try
> > > > and get it added to the bug day last friday.
> > > > http://bugzilla.gnome.org/show_bug.cgi?id=273130
> > >
> > > Well, yes -- if e-a-n isn't running, you won't get those reminders.
> > >
> > > Maybe this is the reason for anyone contributing to this thread so far?
> > > (Sorry, already deleted most of this thread.)
> > >
> > > Can you please check this? Is e-a-n running at all? Check with the
> > > command below, multiple times, including times when (test) alarms are
> > > due.
> > >
> > > $ ps axw | grep evolution-alarm-notify
> >
> > The problem I seem to have with e-a-n is that just about every time I
> > start evolution it crashes for some unknown reason. If I start it
> > manually it sometimes work and sometimes crashes.
>
> Can you try to gather some more information and maybe reproduce this
> crash? When starting e-a-n manually, can you use gdb? If it crashes, get
> a backtrace. [1]
>
> Then file a bug report in bugzilla.gnome.org and attach that backtrace
> to the bug.

Will do my best.