Re: Gnome logout script
- From: Rodrigo Moya <rodrigo gnome-db org>
- To: Sean Atkinson <sean netproject com>
- Cc: Mariano Suarez-Alvarez <msuarezalvarez arnet com ar>, GNOME Desktop List <desktop-devel-list gnome org>
- Subject: Re: Gnome logout script
- Date: Mon, 20 Oct 2003 13:16:34 +0200
On Mon, 2003-10-20 at 09:28, Sean Atkinson wrote:
> > > Sure, unless there's some reason I don't understand that some of its
> > > processes choose to hang around. However that's a bigger problem for
> > > the longer term. Also there are other reasons to want logout scripts
> > > and tidy up the user's environment, so I think it's worth looking into.
> > >
> > evolution-alarm-notify has to be kept around, for calendar alarms, and
> > since it uses the wombat for the calendar, it also keeps
> > evolution-wombat around. So, those 2 processes are saved in the session,
> > which is what they are supposed to do.
> >
> > There is a bug in Ximian's bugzilla about making it exit if there are no
> > alarms. But if so, we need a way to restart the alarm daemon at some
> > interval in the future to check for new alarms.
>
> Looking into the processes left after a clean logout, I find
> evolution-wombat remains without any alarm (I didn't set any).
>
the alarm daemon doesn't check if you dont have. It just runs making
sure you dont miss any alarm. If you dont have alarms, it just keeps
there running and listening for changes in the calendars.
> Presumably as a result of this bonobo-activation-server and gconfd-2
> also remain. Previously I remember seeing oafd too.
>
hmm, that's weird. If wombat was running and the alarm daemon wasnt.
What version of evolution are you running? Could you apply the attached
patch to the evolution 1.4 branch and see if it still happens?
> The file locks left by gconfd-2 are probably the biggest problem since
> they prevent login from another machine sharing the same /home, but I'm
> looking into that separately.
>
right, if some of those processes are running, gconfd-2 will be also
running, which as you say is a problem. I guess the problem is caused by
the alarm daemon not shutting down correctly its bonobo objects, which
is what my patch fixes. So, please, have a try if possible at it.
The patch is for calendar/gui/alarm-notify/notify-main.c
cheers
Index: notify-main.c
===================================================================
RCS file: /cvs/gnome/evolution/calendar/gui/alarm-notify/notify-main.c,v
retrieving revision 1.25.4.2
diff -u -p -r1.25.4.2 notify-main.c
--- notify-main.c 22 Aug 2003 15:23:35 -0000 1.25.4.2
+++ notify-main.c 20 Oct 2003 11:14:25 -0000
@@ -193,10 +193,11 @@ main (int argc, char **argv)
bonobo_object_unref (BONOBO_OBJECT (factory));
factory = NULL;
- /* FIXME: free the alarm_notify_service */
-
alarm_queue_done ();
alarm_done ();
+
+ if (alarm_notify_service)
+ bonobo_object_unref (BONOBO_OBJECT (alarm_notify_service));
gnome_sound_shutdown ();
gnome_vfs_shutdown ();
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]