[hafqa] [hafqa] [Bug 808] process silently killed if no osso_initialize

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Thu Oct 19 09:37:21 EEST 2006
https://maemo.org/bugzilla/show_bug.cgi?id=808


lemody at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kimmo.hamalainen at nokia.com




------- Additional Comments From lemody at gmail.com  2006-10-19 09:37 -------
First of all, which version are you using? is it IT-2006? I think this kind of
thing shouldn't be happening anymore. IIRC it happens because .desktop file
contained a service, and this service is not being launched.

If application startup takes long time you should propably show some kind of
infoprint or 'splashscreen' dialog and handle the initialization asynchronously,
otherwise also the user will think your application is jammed.

In this case however, application is not killed by the window-manager. 

---------------------------------8<-----------------------------
not relevant for this issue but FYI

Window-manager initiates killing _only_ when user presses 'x' to close app and
it does not respond OR if application is switched to another using
task-navigator and that one does not respond. Way of detecting the
responsiveness is done through Gtk using WM_PING. To make your application
responsive, all you have todo is to have gtk_main() iterating. If you block
somewhere (rendering, initialization, loading stuff etc.) there is no answer to
ping's from window-manager.


-- 
Configure bugmail: https://maemo.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list