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 784896 - Don't crash when failing to setup default broker
Don't crash when failing to setup default broker
Product: gnome-boxes
Classification: Applications
Component: general
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on: 784798
Reported: 2017-07-13 09:49 UTC by Felipe Borges
Modified: 2018-01-11 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

app, window: Introduce troubleshoot view (9.66 KB, patch)
2017-07-13 09:49 UTC, Felipe Borges
none Details | Review
screenshot (29.86 KB, image/png)
2017-07-13 09:50 UTC, Felipe Borges

Description Felipe Borges 2017-07-13 09:49:01 UTC
Instead we could show a "Oops, something went wrong" screen and link to GNOME Logs.
Comment 1 Felipe Borges 2017-07-13 09:49:35 UTC
Created attachment 355490 [details] [review]
app, window: Introduce troubleshoot view

Sometimes we are not able to launch the application due to issues
down the stack that we cannot ignore in Boxes.

This patch introduces an error message when Boxes is not able to
start which allows launching GNOME Logs.
Comment 2 Felipe Borges 2017-07-13 09:50:33 UTC
Created attachment 355491 [details]
Comment 3 Piotr Drąg 2017-07-13 14:34:24 UTC
<property name="label" translatable="yes">Consult %s for details.</property>

What’s under %s?
Comment 4 Piotr Drąg 2017-07-13 14:35:54 UTC
Oh, I see the screenshot now. “Logs” needs to be translatable (preferably without markup in the string) and “Consult %s for details.” could use a translator comment.
Comment 5 GNOME Infrastructure Team 2018-01-11 10:55:38 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: