hello folks!
> snip
> after playing around a bit, i've found out that the permissions of
> the kde-dirs in /tmp aren't set correctly:
>
> drw---2 gurkegurke4096 Apr 25 13:28 kde-gurke
> drw---2 gurkegurke4096 Apr 26 00:09 ksocket-gurke
>
> re
hello again!
concerning the kded-problem:
> > > so - no problem at all if kded runs. my question now is:
> > > why doesn't it get started automatically?
> >
> > That's what has to be found out. ;-)
>
> hopefully :-)
kded now again starts automatically - i suppose one of the recent
update
hi Adeodato
> > so - no problem at all if kded runs. my question now is:
> > why doesn't it get started automatically?
> That's what has to be found out. ;-)
hopefully :-)
> > or is it a problem of my setup?
> I'd say so. Can you create a new user account and see if it happens
> to
* Pascal Mainini [Wed, 28 Apr 2004 01:06:22 +0200]:
> problem 2:
> =
> so - no problem at all if kded runs. my question now is:
> why doesn't it get started automatically?
That's what has to be found out. ;-)
> is kded a new daemon introduced with kde3.2?
Nope.
> or is it a pro
hi folks!
i've got two independent problems with kde-installations on different
boxes here.
problem 1:
=
one the first box, running testing, i've got a strange error-message
upon starting konqueror:
"There was an error setting up inter-process communications for KDE.
The message returned
5 matches
Mail list logo
