I am restoring my KMail details from Lenny with KDE 3.5.10 to Squeeze
with TDE 3.5.13, patched with Slávek's patches.

I have copied .kde/share/apps/kmail from my backup to
.trinity/share/apps/kmail.  It wasn't a success.

The klauncher didn't do anything.  (At least, it probably did, but I
have no way of knowing what!!)

I then launched it by various methods, which are self explanatory.
Finally, I launched it from the menu, and got the backtrace (or lack
of it) below.

It's pretty obvious that I have copied something across during the
restauration that has gummed up the works.  But how do I find out
what?  Or should I simply delete all the files that are there and
start again, but if so, how?

I gummed up kdm-trinity as well, but have managed to sort that out via
Google.  This one I am failing with.

Once I get this installation going I'll try to be trouble-free, or at
least quiet, for some time! :-(


root@Tux-II:/home/lisi# kmail
Session management error: Authentication Rejected, reason : None of
the authentication protocols specified are supported and host-based
authentication failed
WeaverThreadLogger: thread (ID: 3) suspended.
WeaverThreadLogger: thread (ID: 2) suspended.
WeaverThreadLogger: thread (ID: 1) suspended.
WeaverThreadLogger: thread (ID: 4) suspended.
root@Tux-II:/home/lisi# Weaver dtor: destroying inventory.
WeaverThreadLogger: thread (ID: 1) destroyed.
WeaverThreadLogger: thread (ID: 2) destroyed.
WeaverThreadLogger: thread (ID: 3) destroyed.
WeaverThreadLogger: thread (ID: 4) destroyed.
Weaver dtor: done
^C
root@Tux-II:/home/lisi# su lisi
lisi@Tux-II:~$ kmail
bash: kmail: command not found
lisi@Tux-II:~$ whereis kmail
kmail: /opt/trinity/bin/kmail
lisi@Tux-II:~$ /opt/trinity/bin/kmail
No protocol specified
kmail: cannot connect to X server :0
lisi@Tux-II:~$
--------------------------------------------------

root@Tux-II:/home/lisi# kmail
bash: kmail: command not found
root@Tux-II:/home/lisi# /opt/trinity/bin/kmail
Session management error: Authentication Rejected, reason : None of
the authentication protocols specified are supported and host-based
authentication failed
WeaverThreadLogger: thread (ID: 1) suspended.
WeaverThreadLogger: thread (ID: 3) suspended.
WeaverThreadLogger: thread (ID: 2) suspended.
WeaverThreadLogger: thread (ID: 4) suspended.
root@Tux-II:/home/lisi# QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged(
KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part *
)
Weaver dtor: destroying inventory.
WeaverThreadLogger: thread (ID: 1) destroyed.
WeaverThreadLogger: thread (ID: 2) destroyed.
WeaverThreadLogger: thread (ID: 3) destroyed.
WeaverThreadLogger: thread (ID: 4) destroyed.
Weaver dtor: done

----------------------------------------


This backtrace appears to be of no use.
This is probably because your packages are built in a way which
prevents creation of proper backtraces, or the stack frame was
seriously corrupted in the crash.