Re: [Tracker] [PATCH] fixing a _bad_ bug in tracker-handler.py



Hi Mikkel,

On 8/2/07, Mikkel Kamstrup Erlandsen <mikkel kamstrup gmail com> wrote:
2007/8/2, Marcus Fritzsch <fritschy googlemail com>:

Hey there...

There was a pretty bad bug in tracker-handler.py which only pops up if
one has so strange usage patterns as I do ;). A related problem was
reported[1].

If traker is running in a different session tracker-handler.py will be
happy with its requirements but will actually fail to connect to
tracker. The problem is solved by adding one more check to the
requirements.

The downside of this is, that tracker will be started, even if the
tracker-handler will not be used.

Cheers, Marcus

[1] http://bugzilla.gnome.org/show_bug.cgi?id=403752

PS: I am looking for 'how' to put apps into the handler, but haven't
found it yet.

Where can I review this fix?

The problem is my above refernced strange usage patterns. I am KDE
user and to look inside deskbar I started another session running
gnome. This session had no knowledge of the other tracker session, but
tracker would nonetheless know that an instance is running.

I am very skeptic about the idea that trackerd will be started even if the
handler is deactivated. It will be almost impossible for users to tracker
down why Tracker always starts up during the session initialization.

Yep, I know of this.

Cheers,
Mikkel


PS: I wrote the current code to check the availability of tracker, and I
think that it should fix the bug you refer to - I might be mistaken though,
I received only little feedback from testers (positive though). I think your
issue is another bug..?

Well, the bug is fixed. The reference was just so to mention that it
is a similar but rare problem. After all, I don't know much users
having two desktop session simultaneously open on one machine (as the
same user) ;).



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]