Wednesday, 21 March 2007

ldap in mozilla and IPv6

The bug has existed for so long:
ipv6 enabled on winxp
thunderbird, mozilla etc address book hangs because the ldap connection tries to create IPv6 socket to IPv4 address.

So easy to fix, why hasn't it happened?
I'd fix it for them, but haven't followed it through.
I note some statements about IPv6 support in latest mozilla stuff, but so far no fix.

The ldap directory service attempts to
connect to the ipv6 socket ::ffff:xx.xx.xx.xx instead of the ipv4 socket
xx.xx.xx.xx

This is consistent with the last few years and on the thunderbird 3.0a1 that I
just downloaded/installed it still fails in the same way on a dual hosted ipv4
ipv6 machine.
Logging ldap:5 only produces the following:
0[274310]: nsLDAPOperation::SimpleBind(): called; bindName = '';
2348[278d2d0]: nsLDAPConnection::Run() entered

channel deepening port phillip bay victoria

The newspaper reports today that the SEES will give the go ahead for channel deepening and dredging in port phillip bay, victoria.

As the SDFV secretary, I expected to see some prior notice - but we haven't received any thing through official channels.

What's the dredging going to mean for me?
Well it may interfere with some winter diving.
It's unlikely to interfere with summer diving (beach tourism too big for them to interfere with).
Long term should make no difference and if their predictions of fewer larger ships coming in are correct that means less ships to dodge while drift diving.

Alternatively it may absolutely ruin the ecology of port phillip bay - but the EES , SEES and monitoring process is meant to prevent that.
What's it going to cost POMC if they do stuff the bay? Is there an eco-bond?

Have to wait for the report I guess.

OSX 10.4.9 upgrade loginwindow crash

Mac OSX 10.4.9 upgrade led to loginwindow crash.
Repeatedly put you back at login window after you type your password in.
Safe boot made no difference.
This is a new intel powerbook pro model - from about jan07.

crashreporter showed loginwindow crashing.

Solution: Remove users keychain file!!!!!
Tried all the other things first though - you know: remove user preferences, delete user Caches
delete System/Caches and System/Library/Caches

This seems to have been a problem that nobody else has identified - may be unique to this box.
Was set up by using the import/migration from a powerpc based unit during system set up.


Perhaps this should go on macfixit or macintouch or apple proper.