KUniqueApplication problem in KMail.

[Waldo Bastian]

On Saturday 09 March 2002 04:44 pm, Waldo Bastian wrote:
> On Saturday 09 March 2002 04:27 pm, Marc Mutz wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi!
> >
> > For me, it suffices to
> >   mv ~/Mail{,.save}
> >   mv ~/.kde/share/config/kmailrc{,.save}
> >   kmail --nofork
> > to get a reproducable crash. BT attached.
> > As far as I can tell, some QTimer fires while the messagebox stays on
> > screen that informs the user that ~/Mail is being created. That timer
> > (probably the one that's responsible for the timeout on the search for
> > another KMail instance) activates a new instantation of a
> > KMailApplication, which tries to bulid (among other things) a
> > KMFolderTree. The latter, in turn, wants to connect to the folderMgr(),
> > which is still waiting for the user to ack the informative messge. Thus
> > an assert( kernel->folderMgr() ) that I added to KMFolderTree's ctor is
> > triggered.
> >
> > What makes me think that this is an KUniqueApplication issue is that
> > leaving out the --nofork in the command sequence above (ie. just saying
> > "kmail") doesn't lead to a crash.
>
> Yes,  KMail uses kapp->dcopClient()->suspend(); to delay handling of the
> newInstance() call. However, with --nofork that doesn't work because that
> doesn't use dcop to call newInstance().
>
> I'll see if I can fix it but I don't consider it a showstopper since I
> doubt many people will use --nofork other than for debuging.

Ok, please update kdelibs/dcop and kdelibs/kdecore, things should work with 
--nofork now too.

Cheers,
Waldo
-- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com