El ds 13 de 11 de 2010 a les 09:23 +0000, en/na Karl Lattimer va
escriure:
> @Victor after speaking with tedg in august he had assured me that it was
> in libindicator but didn't give me a bug number :/ I am certain however
> that the bug can't be in gsd because I tried nuking the error in a
> variety of ways which all led to either the error going in the opposite
> direction off by one or not changing at all. I'll discuss this bug with
> tedg again on monday and see if we can figure it out.
>
Karl,
Have you had the chance to talk to Ted about this and add a task with
the libindicator bug?
If not, do you think we could at least reopen the bug against g-s-d or
open a new task agains libindicator in the meantime ? It has been
confirmed already, and right now it remaining as Invalid does not make
it easier to track.
El ds 13 de 11 de 2010 a les 09:23 +0000, en/na Karl Lattimer va
escriure:
> @Victor after speaking with tedg in august he had assured me that it was
> in libindicator but didn't give me a bug number :/ I am certain however
> that the bug can't be in gsd because I tried nuking the error in a
> variety of ways which all led to either the error going in the opposite
> direction off by one or not changing at all. I'll discuss this bug with
> tedg again on monday and see if we can figure it out.
>
Karl,
Have you had the chance to talk to Ted about this and add a task with
the libindicator bug?
If not, do you think we could at least reopen the bug against g-s-d or
open a new task agains libindicator in the meantime ? It has been
confirmed already, and right now it remaining as Invalid does not make
it easier to track.
Thanks!
Regards,
David.