From kde-core-devel  Wed Dec 17 21:57:22 2008
From: Albert Astals Cid <aacid () kde ! org>
Date: Wed, 17 Dec 2008 21:57:22 +0000
To: kde-core-devel
Subject: Re: Can't use --nofork for KUniqueApplications from another kde
Message-Id: <200812172257.22773.aacid () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=122955108016929

A Dimecres 17 Desembre 2008, Hamish Rodda va escriure:
> Hi,
>
> I'm trying to implement the "run in external terminal" feature for
> kdevelop, basically the aim is to be able to launch a new konsole with the
> user's program running inside it.
>
> However, I want to run konsole with --nofork, so that kdevelop remains
> associated with the konsole, can track the life of the running program, and
> can kill it if desired.
>
> It works fine without passing --nofork to konsole, and works if there's no
> other konsole process running, but if there's another konsole running, it
> fails with the message "KUniqueApplication: Can't setup D-Bus service.
> Probably already running."
>
> My guess is this is because kdevelop's dbus connection is being used to try
> to register org.kde.konsole, but konsole itself has already registered it.
>
> Is there any way to get around this?

Not sure if that means much, but i can launch two "konsole --nofork" from a 
shell. If i can do that why kdevelop can't?

Albert

>
> Cheers,
> Hamish.