brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

js: Use Shell.util_spawn_async functions to launch external processes

Browse Source 
As explained in previous commits, it's not safe to use JS code in child
function callbacks, so let's use the safer version of it.

Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6698
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3293>
This commit is contained in:
Marco Trevisan (Treviño)
2024-05-01 01:14:43 +02:00
committed by Marge Bot
parent 781010be66
commit 26e8fb90fb
3 changed files with 8 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
js/misc/util.js
View File

@ -118,19 +118,12 @@ export function spawnApp(argv) {
* this will throw an error.
*/
export function trySpawn(argv) {
let success_, pid;
let pid;
try {
const launchContext = global.create_app_launch_context(0, -1);
[success_, pid] = GLib.spawn_async(
pid = Shell.util_spawn_async(
null, argv, launchContext.get_environment(),
GLib.SpawnFlags.SEARCH_PATH | GLib.SpawnFlags.DO_NOT_REAP_CHILD,
() => {
try {
global.context.restore_rlimit_nofile();
} catch (err) {
}
}
);
GLib.SpawnFlags.SEARCH_PATH | GLib.SpawnFlags.DO_NOT_REAP_CHILD);
} catch (err) {
/* Rewrite the error in case of ENOENT */
if (err.matches(GLib.SpawnError, GLib.SpawnError.NOENT)) {