Can't use --nofork for KUniqueApplications from another kde process

[Robert Knight]

> 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?

Konsole checks whether it was started from a new terminal and if so, passes
the KUniqueApplication::NotUniqueInstance argument to
KUniqueApplication::start() to make
the application use a new process instead of an existing one.  You
could make Konsole do this
if --nofork is passed as well - although that would make the behavior
different from other single-instance
KDE processes, which don't permit multiple --nofork instances.

Regards,
Robert.

2008/12/17 Albert Astals Cid <aacid at kde.org>:
> 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.
>
>
>