[kde-solaris] Fatal communication error with a client

[Stefan Teleman]

Hi. :-)

I have uploaded a patch to for this bug (kdearts-patch01). It only 
contains /opt/kde-3.1.4/bin/artsd, with the correct permissions (for 
now, until i find the real cause for this problem, and the real fix) 
-- the binary itself is identical.

I have also added an explanation for this patch in the installation 
instructions.

The patch is in KDE-3.1.4

--Stefan

-----

On Thursday 29 January 2004 08:13, André Schneider wrote:
> Hi Stefan,
>
> Thank you - it works now. After first log out a reboot
> was necessary. Now the startup logfile doesn't contain
> any error messages.
>
> I guess the twice login is needed after each reboot - so
> fixing this bug would be helpful for the future.
>
> /André
>
> Stefan Teleman wrote:
> > Hi.
> >
> > Please check the following:
> >
> > if /opt/kde-3.1.4/bin/artsd is instaled setuid root, change the
> > permissions to non-setuid root (0755).
> >
> > Log out, then log back into KDE. Chances are you will get an
> > error message from artsd, something to the effect of "assertion
> > failed, moduleName != "" -- click OK, and just ignore it.
> >
> > Log out of KDE.
> >
> > Log back into KDE. You should not be seeing any error messages
> > now, neither the "Fatal communication with a client" from DCOP in
> > /tmp/${USER}-startkde, nor the "assertion failed" one. artsd
> > should start fine, and you should hear the KDE startup chimes.
> >
> > This is a problem when artsd is installed setuid root. I'm trying
> > to figure out what causes it.
> >
> > Let me know!
>
> ___________________________________________________
> This message is from the kde-solaris mailing list.
> Account management: 
> https://mail.kde.org/mailman/listinfo/kde-solaris. Archives:
> http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman at nyc.rr.com                          -Monty Python