[NTLUG:Discuss] DCOP server & KDE 3.

[MadHat]

On Fri, 2002-11-08 at 17:09, Steve Baker wrote:
> MadHat wrote:
> 
> (Hey - I didn't say it was *good* advice - just what I'd found from researching
> the problem :-).
> 

understood. 

> >>  13) Make sure your search path includes /opt/kde3/bin and /usr/X11R6/bin
> >>      and EXCLUDES /opt/kde2/bin
> > 
> > Does suse use /opt?
> 
> Not usually - but for KDE3 it evidently does.
> 

sad.

> >>...actually, what worked for me was changing my '/etc/passwd' so that my
> >>user account starts up in bash instead of tcsh (which is my preference),
> >>and then nuking a *bunch* of files in my home directory and in /tmp.
> >>
> >>Using tcsh is the one thing I'd changed from the default installation...but
> >>I still don't see how it was the source of the problem.
> >>
> >>Nobody mentioned that *ANYWHERE*.  I eventually realised when I found I
> >>could start KDE as root - AND using my son's user account (both of which
> >>are started into bash instead of tcsh.
> >>
> > 
> > well.... how are you starting X?
> 
> Originally, from the KDE login manager thingy - which SuSE handily
> configured to run on startup.   When I started getting these DCOP
> problems (sometime after I changed my login shell evidently), I tried
> everything I could think of - ended up doing a ctrl-alt-F1 to get a
> console and then killing off X so I could restart it with 'startx'.
> 
> When I did that as my normal user account, I just got DCOP errors - but
> I could still start as root and (as I belatedly discovered) and other user
> with /bin/bash as their login shell in /etc/passwd.
> 
> Unfortunately, I really hate working in bash - I've been using csh/tcsh
> ever since the late 1970's and I'm too old to adapt!

understood.  I started with tcsh, but got tired of installing it on
every box I wanted to work on, so I settled with what ever is there. 
jack of all trades and all.

> 
> > Maybe it has someting to do with an
> > ENV that is or is not getting set because the script are designed for
> > bash and you know that export does not work in tcsh...  just an idea.
> 
> Right - but 'setenv' does the same thing as 'export' and I'm pretty sure
> I have everything set up the same.

same thing yes, same syntax no.  That is what I meant.  Maybe some
script is expecting bash and running an 'export KEY=var' and you needed
'setenv KEY var'.  So it wouldn't catch everything it needed properly.  
maybe look at the startkde script?  Don't know just thinking outloud.

it shouldn't matter what you are running, because each script should
point at the proper interpretor.

> 
> If only one of these stupid programs would leave a detailed log file - or
> have a 'verbose' option - or just a more explicit error message.
> 

now you are just dreaming...  next thing is you might want decent
logging

Speaking of which, have you looked in .xsession-errors in your home
dir?.

-- 
MadHat at Unspecific.com
"Anyone who understands Linux/Unix, really understands the universe.
 Anyone who understands Windows, really understands Windows."
          - Richard Thieme, DefCon 10, 2002