[KDE/Mac] making applications "launch in the foreground"

Ian Wadham iandw.au at gmail.com
Tue Jul 8 03:32:48 UTC 2014

Hi René,

On 04/07/2014, at 5:31 PM, René J.V. Bertin wrote:
> On Friday July 04 2014 07:15:35 Marko Käning wrote:
> >  KCrash (in kdelibs) tries to start DrK as a stand-alone process using kdeinit as an intermediary, but
> > that always fails in my test setup.
> Any idea why? And how would kdeinit launch the process - I'm guessing using fork+exec, meaning that way too the application would launch somewhere behind?

The immediate cause is a failed socket connection:
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = palapeli path = /kdedev/kde4.13/kdesrc/build/kde/kdegames/palapeli/src/palapeli.app/Contents/MacOS pid = 328
KCrash: Arguments: /kdedev/kde4.13/kdesrc/build/kde/kdegames/palapeli/src/palapeli.app/Contents/MacOS/palapeli --nocrashhandler 
KCrash: Attempting to start /kdedev/kde4.13/kde4/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from kdeinit
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /kdedev/kde4.13/kde4/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
… it now uses fork() …

Anyone know anything about sockets and how they are
programmed?  I never used them back in the day: always
preferred popen() (open a pipe).

Also I remember Brandon Allbery saying something about
problems with sockets and KDE on "MacPorts Users" a few
years back…  I will re-read that.

Cheers, Ian W.

More information about the kde-mac mailing list