> OK, I'm on the rebuild and I do have the _complete_ 3.5.12
> profile :)

Okay. I expect to be close to my computer this evening.

The basic test method we want to use each time we try anything:

* Ensure your original 3.5.12 profile is always safe or restorable from backups. :-)
* Restore/copy the 3.5.12 profile as $HOME/.trinity.
* Start Trinity.
* See what breaks: one thing at a time.

I see a potential snag. Your 3.5.12 profile directory is named $HOME/.kdemod3. I believe Arch had started KDE3 mod before Trinity started. The migratekde3 script does not look for that specific name because I never knew about that name, but I'll update the script. I think a 3.5.12 profile is essentially a KDE3 profile. If true then I'll do some testing here copying a $HOME/.kde3 profile to $HOME/.trinity and see what breaks.

I always ran the migratekde3 script and you probably never have. I'm wondering what happens when you run the migratekde3 script against your 3.5.12 profile. Perhaps that fixes a lot, some of which the r14-xdg-update script does not touch. If you want to test the migratekde3 script you can temporarily edit the script to look for $HOME/.kdemod3 rather than $HOME/.kde3.

Darrell