Bugzilla

I think I wanted to say something on the lines of:

1. check if we understand which conditions can lead to an error
2. check if those have distinct error codes/messages
3. verify if some of those are potentially avoidable (like checking something before launching)
4. verify if some of those are potentially recoverable (like retrying)
5. check then if all callers are checking well for error conditions and how they react and if we should tell something to the user (if we are not in shutdown)

So having something better than opaque `LaunchError` is definitely an improvement in that direction, as you would touch at least 1., 2. and a bit of 5. of the above list, yeah.

I think I wanted to say something on the lines of:

1. check if we understand which conditions can lead to an error
2. check if those have distinct error codes/messages
3. verify if some of those are potentially avoidable (like checking something before launching)
4. verify if some of those are potentially recoverable (like retrying)
5. check then if all callers are checking well for error conditions and how they react and if we should tell something to the user (if we are not in shutdown)

So having something better than opaque `LaunchError` is definitely an improvement in that direction, as you would touch at least 1., 2. and a bit of 5. of the above list, yeah.

(this would alter the scope of this bug quite heavily, btw)