[SOLVED] Single instance applications on N950
-
Hi matrixx,
you are great!!! Really it was not so unclear, is that the first was a known problem while this was totally unexpected. I am seeing the canges, now I am sure what it should be. I test and tell you what's happen.
Many thanks. Enrico
-
Hi I changed as you suggested. The program works, and in the installed application list I see the application and the correct icon. In the main page I don't see any icon at all. If I launch from the terminal the program starts correctly.
Icon is (checked on the terminal) in /usr/share/icons/hicolor/64×64/apps/QtComplexHarmattan.png
while the progam is in /opt/QtComplexHarmattan/bin/QtComplexHarmattan
The QtComplexHarmattan.desktop file is
@
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Terminal=false
Name=QtComplexHarmattan
Exec=invoker --single-instance --type=d /opt/QtComplexHarmattan/bin/QtComplexHarmattan
Icon=/usr/share/icons/hicolor/64×64/apps/QtComplexHarmattan.png
X-Window-Icon=
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
@
and all seems correct. -
I am rechecking this post from the top. I have set QtComplexHarmattan without - characters because they don 't exist in the files wen the program is installed. But I see that in my original file (when it was working as multi-instance with the correct icon) the names was having the - I put them againg to test (bit it is strange). Then, the real strange thing is that in the first file (multi instance and correct icon on the main device page) was with the "wrong" icon name as you can see.
Is there a logic ???
-
Last test
- Created a new project at all
- Added all the sources
- Changed the .desktop file
- Added the double space in rules file
... Program is launched by the Qt-Creator and the correct icon is shown on the installed application list. The green empty icon is shown on the device main page. The green icon don't start, the applicaiton starts only from the terminal.
- Removed the double space in the rule file: now the rule file is as original.
- Left the desktop file with the changes to the icon path and name.
... Program icon is shown correctly and the program, as usual, can start multiple instances.
Conclusion: sure the double space after the $(MAKE) instruction in the rule files changes the behaviour of the package but not as we want.
Note: The icon is correct, the name is correct and the file on the device is where we expect it is. The same for the application binary.
No more ideas...
-
[quote author="matrixx" date="1311683781"]Check from terminal if the installed .desktop file is exactly looking same on device than it's on QtCreator. If not, this trick will install the file correctly: edit rules file adding a space after MAKE, but remember to preserve the tab between MAKE and the following word, otherwise the rules file will break. Then clean and rebuild everything. It's a bug in QtCreator which will be fixed for next version. This lifesaver tip was provided by my friend, Attila Chipa :)[/quote]
Hi matrixx, Alicemirror,
I had the same problem and this thread helped me a lot to solved it so I want to say Thank you :)
-
Hi leon,
I am happy that at least we are useful for somone :)
Later I will try with different operating systems than Mac, What platform do you used ? Mac or Win?
-
Linux :P
-
Ok, thank you.
I am using all the three main platforms. Mac, Linux (Ubuntu lucid 10.4) and Windows7. Matrixx wrote that she is using windows and all works, now I should try with windows and linux then I will update the post.
Cheers. Enrico
-
Hi,
Tested the changes under windows. The application is created regularly and the icon works.
Edited the .desktop file so it point to the right place for the application, for the icon and saw that changing the Application name the value changes on the icon text in the device.
Checked that the .desktop file is the same on my Windwos development project and on the device too.
If I add the "space" character after the $(MAKE) command in the rules the application never starts from the icon: only starts from the Qt-Creator environment and the terminal
If I remove the "space" added from the rules file all works but - as usual - the application run only in multiinstance mode. Also leaving intact the .desktop file with the changes.
-
I don't actually know from where QtCreator grabs the default .desktop file which doesn't have the invoker line on exec. It might be created by a script, haven't checked it more closely yet. If you have to choose either 1) single instance, 2) working icon, I would choose #1. After you've done the "rules hack", you are the one who's controlling the contents of the .dekstop file which is going to be installed on the device. If there's still bugs left, they can be sorted out.
-
Matrixx, the fact is that the icon or none is uninfluent.
If I put the changes manually, the icon is shown correctly in all cases. If I don't the icon is shown only in the multi-instance case.
I think that we can consider this .desktop file problema as a minotr bug or an undocumentated detail of the packager. Nothing more than to know what should be done.
Regardless of this question the program has the following behavior:
- Without any change the application works starting from the main page but the icon launch the application in multi-instance.
- With the changes to the rules file the program can be started only from the terminal or from the Qt-Creator environment. Ths means that with the single-instance correction (with of without the correction to the .desktop file) the program don't start from the graphic interface. The icon seems unreactive
Investigating on this aspect I have another detail to add to this strange behavior:
Compiling the application with the changes in the rules file so we expect that it runs in single-instance mode tapping on the icon with the icon nothing happens.
But in the meantime it seems that some taks is started because trying to restart the application from the Qt-Creator (that launch a ssh call to the device) I receive the error that due to a locked file the application can't be uninstalled This happens when the application is running.At this point, if I stop the app as it was launched from the Qt-Creator environment the package can be uninstalled / reinstalled.
This means that somewhere a piece of the program is running on the device. Analizing the .desktop file again you see that the command that should launch the application is the following line:
@
invoker --single-instance --type=d /opt/QtComplexHarmattan/bin/QtComplexHarmattan
@If whe thought to what happens foucsing the attention on this aspect it seems the following:
- When the program runs in multi-instance mode it is sure that for some reason the invoker is not called at all or is called in a manned different thant we se in the .desktop file and the application starts
- When the program is package with the workaround the invoker is really called as we see in the line of the .desktop file and the application don't start in a visibile way for some reasons but a task is launched.
Can be a problem of the invoker ?
-
SOLUTION
The solution can be focused in a problem of the invoker command. Then remains the detail that for some reason not yet clear the icon is not shown correctly - as we expect to be precise - when the workaround is applied.
The workaround suggested by matrixx is correct. The problem that the compilation won't work correctly when the program is package by Qt-Creator so the application runs in multi-instance mode on the device can be solved by the workaround of the double space in the rules file. See in the previous posts of this thread for details.
Then as supposed in the previous post when all is sure is correct the application can't start from the icon. as the .desktop file is very short I have analized the only element that is related to the application launch: the invoker
The sympthoms are the following: The desktop icon launch something but the application don't start.
The application launch in the .desktop file is in the following line:
@
invoker --single-instance --type=d /opt/QtComplexHarmattan/bin/QtComplexHarmattan
@As you can read in the Harmattan Meego 1.2 documentation pages the option --type=d means that the invoked application is a QtDeclarative program. But from the terminal of the device if you launch the command help $>invoker --help you can read that the parameter <d> means QtDeclarative application but the parameter <e> means any kind of application (including the QtDeclarative applications)
Take in account that when the application runs in a multi-instance mode as a matter of fact this parameter is ignored as the --single-instance option so the application starts and run.
At this point when the single-instance application that we suppose should run correctly but don't start tapping the corresponding icon on the device we try to launch the invoker command exactly as it appear in the .desktop file. The result is the following:
@
$ invoker --single-instance --type=d /opt/QtComplexHarmattan/bin/QtComplexHarmattan
invoker: Invoking execution: '/opt/QtComplexHarmattan/bin/QtComplexHarmattan'
Booster: Loading symbol 'main' failed: '/opt/QtComplexHarmattan/bin/QtComplexHarmattan: undefined symbol: main'
@
Instead if we try to launch manually the command with the <e> option we obtain the following result and the application start:
@
$ invoker --single-instance --type=e /opt/QtComplexHarmattan/bin/QtComplexHarmattan
invoker: Invoking execution: '/opt/QtComplexHarmattan/bin/QtComplexHarmattan'
Using the meego graphics system
Successfully resolved MeeGo graphics system: /usr/lib/qt4/plugins/graphicssystems/libqmeegographicssystem.soFound SGX/MBX driver, enabling FullClearOnEveryFrame
Found v1.4 driver, enabling brokenTexSubImage
MeegoGraphics: found EGL_NOK_image_shared
MeegoGraphics: found EGL_KHR_lock_surface2
MeegoGraphics: found EGL_KHR_fence_sync
hijackWindow() context created for QDeclarativeView(0xae8189d4) 1
Found SGX/MBX driver, enabling FullClearOnEveryFrame
Found v1.4 driver, enabling brokenTexSubImage
QGLWindowSurface: Using plain widget as window surface QGLWindowSurface(0x1fb89b08)
Found EGL_KHR_image_pixmap & GL_OES_EGL_image extensions (preferred method)!
Found texture_from_pixmap EGL extension!
Meego graphics system destroyed
@ -
APPENDIX
In the post "Someone tried to publish N9 applications?":http://developer.qt.nokia.com/forums/viewthread/8248 kkrzewniak experienced the same problem that is related to the workaround that should be done in the roles file due to the Qt-Creator packager bug.
Respect to the Booster error matrixx suggested the following:bq. @kkrzewniak If you get the error Booster: Loading symbol ‘main’ failed: ‘/opt/CoolApp/bin/CoolApp undefined symbol: main’
(read the full post in the link above)This is the last test that will be done to complete this solution.
-
BOOSTER ERROR - SOLVED
@
Q_DECL_EXPORT int main(int argc, char *argv[])
@Declaring the main function in the main.cpp program of the application the .desktop file works fine also with the --type=d option. Remain unclear what we can do to have the icon shown correctly on the desktop.
-
DESKTOP ICON - SOLVED
The problem of the lost desktop icon depends on a strange behavior, probably a bug in Qt-Creator. When the icon is selected in the project window of Qt-Creator the file is encoded and set at the bottom of the control file in the folder qtc_packaging/debian_harmattan
Managing the packagin files for some reason - else if the icon remain the same and the file too - the value in the control file don't match resulting in the green icon on the device instead of the correct icon file.The workaround is simple: it is sufficient to follow the instructions of the Qt-Creator documentation explained in packaging your applications section regarding how-to change the icon file.
Opening the project window the icon file should be reloaded and after repackaging the application the icon is shown correctly. And obviously the application runs in single-instance mode.
Many thansk to matrixx !!! :)
-
Me too, this is the great of this tricks of Nokia :)
Cheers
-
Invoker use requires that your application is relocatable, which can be done by adding @CONFIG+= declaratibe-boostable@ to .pro. This only works with harmattan-nokia-meego-api target. harmattan-platform-api target does not have requiret package installed and you have to set flags manualy eg something like:
@QMAKE_CXXFLAGS += -fPIC -fvisibility=hidden -fvisibility-inlines-hidden
QMAKE_LFLAGS += -pie -rdynamic@
I think the bug which removes invoker line from .desktop is caused by too smart buildsystem =)
You can try running your application from terminal with invoker and it should tell you why it fails.edit:
Oh sorry there was multiple pages =) but still those two targets have some differences. -
Thank you Tomma,
me too sometimes see too late that a thread is multipage ;)
At this point I have not clear what you means. The essential steps are the following:
Starting point
- The compiled/packaged applications for Qt-Meego are not single-instance
- Multi-instance is prohibitied
- This is a bug of Qt-Creator (or the SDK or both, not sure of the origin)
Workaround
-
Open with a external editor the rules file in the qtc_packaging/debian_harmattan folder changing the following line
@
[TAB]$(MAKE)*[SPACE]*INSTALL_ROOT="$(CURDIR)"/debian/<application_name> install
@
to
@
[TAB]$(MAKE)[SPACE][SPACE]INSTALL_ROOT="$(CURDIR)"/debian/<application_name> install
@
as is add a second SPACE character after $(MAKE) leaving the initial TAB character
_This solve the problem of the multi-instance but at this point the .desktop file don'work correctly -
Edit in Qt-Creator the .desktop file setting the correct Icon pointer that should be
@
Icon=/usr/share/icons/hicolor/64x64/apps/<application_name>.png
@
At this point it is probable that the icon is now shown in the program. As a matter of fact the application icon (those shown on the device main page) depends from the encoded icon in the control file. To avoid this problem it is necessary to open the project section in Qt-Creator, open the run tab in the Harmattan target expanding the Create Package group. Select the icon again and confirm. -
The .desktop file at this point works correctly trying to launch the application using the invoker command in a line like the following:
@
Exec=invoker --single-instance --type=d /opt/<application_name>/bin/<application_name>
@
Tapping on the application icon the program don't start. Launching the invoker with the same command line from the device terminal this is the received error:
@
invoker: Invoking execution: '/opt/<application_name>/bin/<application_name>'
Booster: Loading symbol 'main'
failed: '/opt/<application_name>/bin/<application_name>:
undefined symbol: main'
@ -
The QtDeclarative main() is not exported by default so - as explained by matrixx - it is necessary to change the main() function declaration in the main.cpp source as follows:
@
Q_DECL_EXPORT int main(int argc, char *argv[])
{
...
}
@
At this point, recompiling, packaging and deploying to the device the application works fine.
Returning to the initial comment Tomma it is not clear how your suggestion can take place in this procedure. Please can you explain?Many thanks.
Hopefyully this procedure may be good for other developers so I have added the how-to page in the wiki "How to create single-instance applications for N9 Harmattan Meego 1.2":http://developer.qt.nokia.com/wiki/Single_Instance_Harmattan_Applications
Due that it is originated by a bug I have no idea for how much time this problem will persist in the future versions/updates of the packages. -
@Alicemirror: If you are creating an application with the "Harmattan Application" template on QtCreator, you don't have to care about those lines Tomma mentioned, they are automatically added to your .pro file by QtCreator.
Instead, if you are porting an existing application and want to use your original .pro file, you need to add those lines manually to be able to use the single-instance invoker.
That might be a good addition to the wiki, if someone wants to port apps without creating a new project template and copying over existing files of the project.
