Depending on your system config, `xdg-open` may stay open for extended periods, and potentially log more than the 50kb of output that we were previously able to deal with. This changes `open()` so that output on `stdout` is just directly ignored. Any output from `stderr` is immedialy logged rather than collected for later logging. Note that this will generally occur if your system is not configured with the DBus portals that `xdg-open` uses to open URLs rather than launching programs like your web browser directly. This could be seen as user misconfiguration but we should deal with it robustly anyway.