Brian J. Murrell wrote:
> On Thu, 2009-10-01 at 16:42 +0000, Zachery Bir wrote:
>> Hi, Brian.
>
> Hi,
>
>> Thanks for reporting this. Can you do two things to help me diagnose
>> this?
>
> Before I do this, I should mention, that I appear to be afflicted by bug
> 435943. Is that as likely a cause of this problem as I think it is?
Interesting. However, if Bindwood can't get hold of the desktop couch
information, it *should* be quietly not doing anything. Aha! The error
you were receiving was due to the bookmark modification event handlers,
not the main bulk of Bindwood's operations. Those aren't (currently)
excepted from acting when DC can't be found.
Thanks! I'll make sure that when DC can't be found, we also unsubscribe
Bindwood from those event notifications.
Brian J. Murrell wrote:
> On Thu, 2009-10-01 at 16:42 +0000, Zachery Bir wrote:
>> Hi, Brian.
>
> Hi,
>
>> Thanks for reporting this. Can you do two things to help me diagnose
>> this?
>
> Before I do this, I should mention, that I appear to be afflicted by bug
> 435943. Is that as likely a cause of this problem as I think it is?
Interesting. However, if Bindwood can't get hold of the desktop couch
information, it *should* be quietly not doing anything. Aha! The error
you were receiving was due to the bookmark modification event handlers,
not the main bulk of Bindwood's operations. Those aren't (currently)
excepted from acting when DC can't be found.
Thanks! I'll make sure that when DC can't be found, we also unsubscribe
Bindwood from those event notifications.
Zac