[Kbabel] DCOP Communication Error

[Marco Wegner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 25 November 2002 16:31, Stanislav Visnovsky wrote:
> Hi!
>
> The best way to produce backtrace is to start KBabel by hand with the
> --nofork option (in fact, this is available in all KUniqueApplication(s)).

Next time...

> The DCOP error message only informs you that the application didn't start
> correctly.
>
> Unfortunately, you don't have your config files anymore, so no reproducing
> of the problem :-((

Yes, sorry about this, but I rather think it was some problem with the 
database instead. I had other problems with it, too. Like not stopping an 
automatic search but instead displaying all the found entries again and 
again...

Marco

- -- 
Marco Wegner <mail@marcowegner.de>, <dubbleu@web.de>
Contributing to KBabel http://i18n.kde.org/tools/kbabel 
   and kde-i18n-de http://i18n.kde.org/teams/de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE94oeNX3rotM03gSgRAhRnAKDkG2AYCrk8MfQ+hAPa1OxGPzWonQCgtP99
QySPDFFBopmrjJcxLYiPlB4=
=NYfo
-----END PGP SIGNATURE-----