Re: [Evolution] Weird Calender Reminder Problem

[Pascal DeMilly <list evolution newgenesys com>]

Same here

On Fri, 2002-12-13 at 01:15, Thomas O'Dowd wrote:
> I have this problem now and again too. I'm one of those that presses
> snooze a lot and typically leave evolution open for long periods of time
> like 2 weeks or more. When I restart it sometimes after this, I get
> these old messages popping up. Very annoying, but I've not been able to
> spend time finding the pattern to repeat it to log a bug. I see you have
> the same problem.
>
> Tom.
>
> On Thu, 2002-12-12 at 21:23, Dave Barton wrote:
> > On Thu, 2002-12-12 at 22:15, Rodrigo Moya wrote:
> > > On Thu, 2002-12-12 at 04:05, Dave Barton wrote:
> > > > On Thu, 2002-12-12 at 12:38, Bob Haddleton wrote:
> > > > > On Wed, 2002-12-11 at 19:07, Dave Barton wrote:
> > > > > > Evolution 1.2 - SuSE 8.0 - KDE 3.0
> > > > > >
> > > > > > I have an ongoing problem with calendar reminders popping up at the
> > > > > > wrong time. Let's say I create an all-day appointment with a reminder to
> > > > > > be displayed a number of days before the start of appointment. The
> > > > > > reminder may or may not be displayed as required, but if it does appear
> > > > > > it will not show up until 11am and sometimes only if I switch to the
> > > > > > calendar or summary.
> > > > >
> > > > > I don't have any problem with the alarms firing reliably, but when I
> > > > > open and/or close the Calendar window, I usually get the last day's
> > > > > worth of already-fired alarm notifications repeated again.  It's pretty
> > > > > strange, and can be annoying when I had a lot of alarms in one day.
> > > > >
> > > > > I haven't had time to look into it much.
> > > >
> > > > Yes, I also get old alarms firing when I open and close the calendar. I
> > > > can live with that annoyance, if I can just get reliable alarms.
> > > this seems to be the alarm daemon not starting up on evolution startup,
> > > and starting instead when the calendar folders are opened. Could you
> > > check if that's the case? That is:
> > >
> > > $ killev
> > > $ evolution &
> > >
> > > wait some seconds
> > >
> > > $ ps ax | grep alarm
> > >
> > > the last command should show a evolution-alarm-notify process. If not,
> > > that's the problem.
> > >
> > > cheers
> >
> > OK I closed evolution then:
> >
> > dave master:~> killev
> > killing gnome-gtkhtml-editor-1.1
> > killing evolution-executive-summary
> > killing evolution-vcard-importer
> > killing evolution-calendar
> > killing evolution-ldif-importer
> > killing evolution-addressbook
> > killing evolution-elm-importer
> > killing evolution-netscape-importer
> > killing bonobo-moniker-xmldb
> > killing evolution-gnomecard-importer
> > killing wombat
> > killing evolution-mail
> > killing evolution-alarm-notify
> > killing evolution
> > killing evolution-calendar-importer
> > killing evolution-pine-importer
> > dave master:~> evolution &
> > [1] 1919
> >
> > Waited about 10 seconds, then:
> >
> > dave master:~> ps ax | grep alarm
> >  1405 ?        S      0:00 kalarmd -session 11c0a80001000103964334900000013960004
> >  1407 ?        S      0:00 kalarm -session 11c0a80001000103964334900000013960005
> >  1978 ?        S      0:00 evolution-alarm-notify 
> > --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory --oaf-ior-fd=17
> >  2007 pts/1    S      0:00 grep alarm
> > dave master:~>
> >
> > It seems that the alarm daemon is starting up with evolution.
> > Since very few others are having any problems with this, it seems as if
> > there is something wrong with my configuration, although I have
> > everything else in evolution set up and working the way I want it.
> >
> > What if I move /home/dave/evolution out of the way and restart evolution
> > then reconfigure my settings?
> >
> > Do you think this might resolve the problem, or is it more likely to be
> > something in evolution's global settings?
> >
> > What potential pitfalls should I be aware of if I need to restore my
> > evolution directory.
> >
> > I really like evolution and I am willing to do a bit of work to resolve
> > this issue.
> >
> > Thanks & Regards
> > Dave
-- 
Pascal DeMilly <list evolution newgenesys com>