cocoaforge

Whoohaaaa! Finally it works! :D After talking to our systems admin again, we found out that when he sais "all the standard system fonts are installed" that does not include the non-latin fonts (like LiHei, AquaKana, HiraKakuPro...)! So guess what happened after I manually re-installed them...

Thanx for the links... I followed the advice to check fonts for duplicates and other conflicts. I did find some, so it was a good idea. Unfortunately, it did not affect the initial Adium problem... :( It will still crash, even if I have only the basic (non-deactivatable) system fonts running. Althou...

Hmm. Are there any fonts you have added since getting the system? Could you move the non-standard fonts out and then put them back one by one and see at what point Adium starts/stops causing you described problems. It may be a corrupt font file? Yeah, since this is my computer at work (graphics pro...

[...] 507 com.apple.CoreText 0x9023b1bc TGlyphEncoder::AppendUnmappedCharRun(TRun&, CFRange, TGlyphList<TAATDeletedGlyphIndex>&, TFontCascade const&) + 476 508 com.apple.CoreText 0x9023af3c TGlyphEncoder::RunUnicodeEncoder(CTRun*, CFRange, TGlyphList<TAATDeletedGlyphIndex>&, TFontCas...

You're getting the font stuff in the crash logs? Jap, there's also font stuff in the crash log... Here we go: -- Date/Time: 2007-02-06 13:40:36.007 +0100 OS Version: 10.4.8 (Build 8L127) Report Version: 4 Command: Adium Path: /Applications/Adium_1.app/Contents/MacOS/Adium Parent: WindowServer [2017...

Mac: Dual 2 GHz PowerPC G5, OS X 10.4.8, latest updates Language: German Add. Programs: None! (nothing I know of, that is) Other account: Same problem! Disk utility: No changes whatsoever! I'm pretty sure, this is not what you wanted to hear, but... ;) Being a little more patient I found out, that i...

That didn't do the trick, I'm afraid...

Even after erasing all the program files and preferences (as mentioned somewhere in this forum/thread), rebooting (just for good measure), and completely re-installing the program from the scratch, nothing changed!

I have exactly the same problem.
Took me some time to find an older issue to reinstall, but now I'm running on version 0.89...
So please don't forget to drop a note here, once you've found a suitable solution to the problem...