[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: hrmpf! essential libs/apps screwed
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-03-16 0:18:24
[Download RAW message or body]

On Wed, Mar 15, 2000 at 11:39:23AM +0100, Lars Knoll wrote:
> Let me add another rant ;-)
> 
> Has someone tried starting a kde app _without_ running the full KDE
> desktop? I tried with konqueror and got the following results:
> 
> First try: konqueror starts up, but complains about missing mimetypes, and
> does basically nothing.
> 
> Then I ran kbuildsycoca by hand, to get around the missing
> mimetypes. Which user would guess about this command???
>
> Next try starting konqueror again: konqueror crashes with the following
> error:
> DCOPClient: got a DCOPReplyFailed opcode.
> konqueror: Can't launch kioslave: 'KLauncher could not be reached via
> DCOP.
> '
> konqueror: couldn't create slave 353 <null>
> Aborted

It has been said more than once that kdeinit should be launched automatically
if it's not running when we need it - much like kioslave used to be
run automatically. I think Waldo will do that as part of his plans
for kdeinit ?

> Not very user friendly. After running kdeinit (who would guess the missing
> KLauncher is kdeinit?), I was finally able to run konqueror.

Yes. The ONE command that people need to run before the first KDE-2 app
is simply : kdeinit +kded

> Ok, so I browsed a bit using konqueror, and then at some point quit the
> app, and guess what's left over (quoting the relevant part from ps):
> 
> 19511  p7 S    0:00 kdeinit: klauncher
> 19512  p7 S    0:00 kdeinit: Running...
> 19515  p7 S    0:00 kdeinit: kcookiejar
> 19517  p7 S    0:00 kioslave
> 19518  p7 S    0:00 kioslave 
>
> So konqueror started these 5 processes, and didn't clean them up after
> him, when I exited it. Ok, it couldn't possibly clean up kdeinit, but the
> kioslaves and the cookiejar should get cleaned up automatically.

This is old - kioslave doesn't exist anymore.
And the new slaves time-out and exit after a while...

kcookiejar has to be left running, in case any other instance of konqueror
needs it (at the same time or later on) - or do we want to make it
exit if no konqy needs it, i.e. implement a reference counter on it ?
I'm no cookie expert... (need Waldo again)

The current sequence would be:
kdeinit +kded
konqueror
killall kdeinit

which makes sense.
OTOH, if konqueror autostarts kdeinit, no way it should close it automatically
(what if other apps are running). Oh, unless we put a ref count in kdeinit
too (using DCOPServer's app registration mechanism...).
Some apps that don't register to dcop, but those can't use kdeinit (klauncher)
anyway...

To be rediscussed with Waldo IMHO.

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]