67c5be9c53
Unlike for plain JS Errors, the `message` property of GLib.Errors is read-only, so the intent to replace it with a nicer message triggers an Error itself. We could create a new GLib.Error with the changed message instead, but as it turns out, none of the parse errors contain the technical prefix we want to strip out, so we can simply drop the special-casing altogether. This is also consistent with `spawnCommandLine()`, which never had special treatment of parse errors. Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8146 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3593>