Re: [Evolution-hackers] [RFC] Make e-{addressbook, calendar}-factory automatically quit when superseded
- From: Matthew Barnes <mbarnes redhat com>
- To: David Woodhouse <dwmw2 infradead org>
- Cc: evolution-hackers gnome org
- Subject: Re: [Evolution-hackers] [RFC] Make e-{addressbook, calendar}-factory automatically quit when superseded
- Date: Fri, 20 May 2011 12:34:22 -0400
On Fri, 2011-05-20 at 16:13 +0100, David Woodhouse wrote:
> I have lost count of the number of times I've been trying to debug
> something in e-calendar-factory, but the factory I'm running in gdb is
> *not* the one that's actually being used.
>
> Sometimes I forget to kill the old factory. Sometimes I *do* kill it,
> but Evolution, *while* complaining that calendars will never work again,
> automatically starts a replacement (that it will never use).
>
> This patch should allow replacement simply by running a new factory
> process. This will upset Evolution, because its existing factory will go
> away. But users should never be doing that anyway; this is only for
> debugging. And it should make debugging a *lot* easier.
>
> Comments?
Looks reasonable to me. No reason for the backend process to continue
running if it loses its bus name.
Haven't encountered that myself -- I'm still on Fedora 14 with E-D-S
2.32, so I always run the 3.0 or 3.1 backend processes manually. But I
can see how that would be confusing when debugging the same version as
the system package.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]