[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#231392: konqueror: Can't talk to klauncher



Peter Nuttall writes:

> On Monday 09 February 2004 12:46, Helge Kreutzmann wrote:
>> Hello Peter,
>>
>> On Fri, Feb 06, 2004 at 04:25:10PM +0000, Peter Nuttall wrote:
>> > Thanks for reporting the bug. can you tell be if the same problem
>> > happens within kde itself?
>>
>> Mmh, that'll be difficult. Since it only happens sometimes, this
>> would mean I would have to use KDE for a longer time which I really
>> would like to avoid[1]. If you have anything which requires testing
>> once, I could install KDE, try it out, and remove it again.
>>
> <sinp>

> The reason I asked was becuase kde has this thing called DCOP which
> lets kde programs talk to each other (like IPC in a tty). I was
> thinking that it wasn't running in wmaker. (klauncher is part of
> this). You could check if it is running with the kdcop program, if
> you have konqi installed, then it should already be there. The
> problems you are descibing sound like a problem with the dcop system
> to me.

The dcopserver is supposed to be started by kde apps if it is not
already running.  

The klauncher warning is probably unrelated to the bug, as it is
issued by kded when it can't run the cache update program with
klauncher.  After this warning, it falls back to the system call for
starting the program, and this is probably not a problem.

cheers
domi



Reply to: