|
2009-04-18
, 21:58
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#2
|
|
2009-04-19
, 08:58
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#3
|
Tags |
hildon, low level, maemo-launcher, osso |
Thread Tools | |
|
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.
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.
I notice that one of the parameters of maemo-launcher is "--pidfile" which has the following listed in the help file:
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 them and says, "I'm sorry, do I know you?"
Any suggestions?
Perhaps this is a request I should be making to the Mer team? ("Make maemo-invoker capable of choosing which maemo-launcher to use")
By the way, I notice this same behaviour when running apps in Fremantle Alpha Scratchbox...
UPDATE: Interesting behaviour if I try to run a Diablo maemo-launcher on top of the Mer version:
I issue the following command:
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
Last edited by qole; 2009-04-17 at 16:41. Reason: update: error code