Making applications exit if they can't connect to the session bus

[Thiago Macieira]

Stephan Kulow wrote:
>So this exit 125 made testing KDE4 applications from a KDE3 _much_
> harder and appeared heavily unnecessary - especially creating a core
> file(!) on missing session bus appeared me a bit _too_ dbus centric.

If we don't make KApplication exit, then we should protect every and all 
accesses to D-Bus with a check if the application is connected. This 
means that KToolInvocation::klauncher() can now return null, which means 
all uses of it must also be protected. And so forth.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080308/0f4860b9/attachment.sig>