Sorry for the noise, I solved the problem 30 seconds after sending this mail.
Actually, the problem does not occur if I install the program on run it. The
problem only occurs if I try with the executable from source directory
(a shell script that starts .libs/lt-<progname>).

Michael.

> > I have a small utility which actually only shows a dialog. So the main
> > program calls "KDialog::exec()", but "KApplication::exec()" is not called.
> > Note that the KApplication object is created with the standard way (with
> > KCmdLineArgs, ...). The program runs well until I try to call
> > "KFileDialog::getExistingDirectory", then I get
> >
> > QToolBar::QToolBar main window cannot be 0.
> > Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
> >
> > And my application freezes.
> > What can be the cause ?
>
> The DCOP protocol of the early 2.2-series was incompatible with the one in
> 2.1. This has been fixed over the weekend but it means that recent 2.2 is
> incompatible with early 2.2 (but compatible again with 2.1)
>
> Solution: compile & install a fresh version from CVS and restart your desktop.
>
> Cheers,
> Waldo
> --
> bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
>
> >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--
------------------------------------------------------------------
Michael Goffioul                IMEC-DESICS-MIRA
e-mail: goffioul@imec.be        (Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510          Kapeldreef, 75
Fax:    +32/16/28-1515          3001 HEVERLEE, BELGIUM
------------------------------------------------------------------



 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<