On Sat, 29 Sep 2012, Jon Trulson wrote:

> On Sun, 30 Sep 2012, Marcin Cieslak wrote:
> 
> > On Sat, 29 Sep 2012, Jon Trulson wrote:
> > 
> > > On Sun, 30 Sep 2012, Marcin Cieslak wrote:
> > > 
> > > When I login, everything comes up, but a dialog appears saying that
> > > the session manager (I'm paraphrasing) could not be contacted.  It has
> > > an Ok buton, which if you hit, ends the session.  I'm guessing it has
> > > something to do with the fact that the 'hostname' does not match the
> > > dhcp IP and DNS reverse lookup on that IP.
> > 
> > Are you getting:
> > 
> >    TT_ERR_PROCID The process id passed is not valid.
> > 
> 
> No, I get "TT_ERR_INTERNAL (bug)".
> 
> strace shows that, for example dtwm does connect with ttsession.
> ttsession just returns the error code and dtwm complies.  Same with
> dtsession.
> 
> Well, dtsession just calls exit after reporting the same error
> (TT_ERR_INTERNAL).

Ok, I would check the following: 
- add the following to your $HOME/.dtprofile:

export dtstart_sessionlogfile="$HOME/.dt/session.log"
export dtstart_ttsession="$DT_BINPATH/ttsession -t"

then your $HOME/.dt/startlog will have a dump of the
ToolTalk transactions. 

Thinks to look for:

whether strings like:
                session:        01 2088 1342177279 1 1 169 127.0.0.1 4

make sense.

2088 <-- PID of the ttsession

1342177279 1 <-- this is RPC prognum/version number (allocated dynamically
                                   by ttsession via rpcbind
169 <- my userid

127.0.0.1 <- host where ttsession is running


If you get to some kind of terminal or just access
the X server from the outside ("DISPLAY=:0 xprop -root"
from console or something like that)

I would check if

xprop -root | grep TT_SESSION

looks the same; in my case:

TT_SESSION(STRING) = "01 2088 1342177279 1 1 169 127.0.0.1 4"

then I would check (no access to X server needed)
what "rpcinfo -p" says.

In my case I have only ttsession running and rpc.cmsd enabled 
in /etc/inetd.conf so I get:

    100068    2   udp  38596  cmsd
    100068    3   udp  38596  cmsd
    100068    4   udp  38596  cmsd
    100068    5   udp  38596  cmsd
1342177279    4   tcp  55555
1342177279    1   tcp  55555

1342177279 may of course be different.

Then I would see if ttsession really listens
on port 55555, nothing is blocking it etc.


//Marcin

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to