JuK - reason for starting as a background process?

[Georg Grabler]

Hi guys,

Is there any reason why JuK is started in the "background" (sorry, don't
know the correct wording here, simply that you keep control of your shell)?
I havn't seen any other KDE application doing so, and I'm currently having
problems tracking the most nasty bug in JuK I currently experience (crashing
with dbus sometimes for some reason I don't know), because gdb always thinks
the application quit. Probably because I'm lazy using qtcreator (until
kdevelop fits my needs again at least), because I can't really control gdb
in shell - always needed a tool for it ;-).

Do we actually need launching juk in background?

Kind regards,
Georg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-multimedia/attachments/20090511/22d0d576/attachment.htm>
-------------- next part --------------
_______________________________________________
kde-multimedia mailing list
kde-multimedia at kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia