trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-users] Kmail in TrinityDE 3.5.12, restoring from KDE 3.5.10

From: Greg Madden <gomadtroll@...>
Date: Sun, 23 Sep 2012 19:30:06 -0800

On Sunday 23 September 2012 3:24:38 pm Slávek Banko wrote:
> On Monday 24 of September 2012 01:03:29 Lisi Reisz wrote:
> > 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:~$

Looks like you logged in as root, su to lisi. user lisi will not be able to 
connect to X server. not sure if that is the only issue. 

When I want to let a user, other than the one that is logged in, I use xhost to 
grqant access to the X server.

'xhost +local:<user>'

hopefully on topic. 


> > --------------------------------------------------
> >
> > 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.
>
> Lisi,
>
> in the configuration files from KDE 3.5.10 may be used .kde/share
> and /usr/share. It is necessary to change these settings to .trinity/share
> and /opt/trinity/share.
>
> Note: The identities for KMail are in
> .trinity/share/config/emailidentities.
>
> Slávek


-- 
Peace,

Greg