After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678054 - Provide a synchronous version of g_app_info_launch*
Provide a synchronous version of g_app_info_launch*
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
2.32.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks: 652262
 
 
Reported: 2012-06-13 21:37 UTC by Vincent Bernat
Modified: 2018-05-24 14:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vincent Bernat 2012-06-13 21:37:39 UTC 
Hi!

g_app_info_launch() and g_app_info_launch_uris() end with the invocation of g_spawn_async(). A synchronous version of those two functions would be appreciated. g_app_info_launch_uris() does some complex operations (parameter expansion, environment, terminal handling) which are difficult to mimic.

This would allow gvfs-open to terminate only when the invoked application terminates. See bug #652262 for the rationale for this.
Comment 1 Matthias Clasen 2012-06-15 10:33:49 UTC 
that is really not what the 'launch' apis are about, I'm afraid.
Comment 2 Vincent Bernat 2012-07-13 20:21:50 UTC 
In this case, feel free to close the bug. I still have other options like using `g_desktop_app_info_launch_uris_as_manager()` with
`G_SPAWN_DO_NOT_REAP_CHILD` flag and using `waitpid(-1)` to get a synchronous behavior.
Comment 3 GNOME Infrastructure Team 2018-05-24 14:16:32 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/555.