OK, now mono is gone. Thanks for that suggestion. Also we are no longer endlessly looking for pidgin and beagle bits. Restarted, and those particular errors seem to have gone, but are now succeeded by the following...!
I googled them, and some of them seem to be associated with kmail. Then I have some nphelix errors, that is another thing that you have to go to endless lengths to kill but it won't stay dead.
Is it normal to have xsession errors? Or if your system is set up right, should there basically be none?
Peter
** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) Removing DOMNodeRemoved listener ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) kbuildsycoca running... Launched ok, pid = 3954 ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave QLayout::addChildLayout: layout already has a parent WeaverThreadLogger: thread (ID: 1) suspended.