Hi, <br><br>I'm trying to run Mer apps and Maemo apps side by side, but there seems to be some conflict between the two versions of maemo-launcher.<br><br>Once the Mer maemo-launcher starts running, Maemo apps (the ones dependent on maemo-launcher) quit launching, even though the Maemo version of maemo-launcher is still running.<br>
<br>I notice that one of the parameters of maemo-launcher is "--pidfile" which has the following listed in the help file:<br><br> --pidfile FILE Specify a different pid file (default /tmp/maemo-launcher.pid).<br>
<br>It would seem that this has the possibility for two or more maemo-launchers to share the system, by using two different "PID files," but I can't see any way to specify which maemo-launcher to use in the documentation of maemo-invoker.<br>
<br>As it is now, the most recently launched maemo-launcher takes all the maemo-invoker calls, leaving the older maemo-launcher (still running, in the shadows) leaning against the wall, feeling lonely. And so the non-Mer apps fail to start, because the Mer maemo-launcher stares blankly at the Maemo apps and says, "I'm sorry, do I know you?"<br>
<br>Any suggestions?<br><br>Perhaps this is a request I should be making to the Mer team? ("Make a mer version of maemo-invoker that is capable of choosing which maemo-launcher to use")<br><br>By the way, I notice this same behaviour when running apps in Fremantle Alpha Scratchbox...<br>
<br>Interesting behaviour if I try to run a Diablo maemo-launcher on top of the Mer version:<br><br>I issue the following command:<br><br>~ $ maemo-invoker browser<br><br>maemo-launcher responds with:<br><br>maemo-launcher: invoking '/usr/bin/browser'<br>
maemo-launcher: died loading invoked application: '/usr/bin/browser: cannot dynamically load executable'<br>maemo-launcher: child (pid=2657) terminated due to exit()=1<br><br>-- <br><font size="1">enthusiast, n. "One whose mind is wholly possessed
and heated by what engages it; one who is influenced by a peculiar
fervor of mind; an ardent and imaginative person."</font>