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 685046 - Report all errors/exceptions to the users
Report all errors/exceptions to the users
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks: 686781
 
 
Reported: 2012-09-28 13:48 UTC by Alexander Larsson
Modified: 2016-03-31 13:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Larsson 2012-09-28 13:48:13 UTC
We don't report any errors when trying to reconnect to a machine, only in the initial connect call.
Comment 1 Alexander Larsson 2012-10-24 10:23:05 UTC
This happens in a lot of other places too. We should never just silently swallow exceptions or just g_warn about them, that just makes it hard to figure out why something goes wrong in the field.
Comment 2 Marc-Andre Lureau 2012-10-24 10:37:33 UTC
I am not convinced by the approach that all warning should be reported to users, we need to that selectively. It's very easy for a user interested in figuring out a problem to run in the console or check it's session log / journal.
Comment 3 Alexander Larsson 2012-10-24 10:55:39 UTC
Well, obviously we should not spew internal asserts or whatnot to the user.
But, actual errors in e.g. connecting to the box or something is imho pretty bad to ignore.
But yeah, i guess its somewhat of a case-to-case thing,
Comment 4 Zeeshan Ali 2013-03-27 18:48:27 UTC
AFAIK we are doing better in this respect and don't know what would be the criteria of fixing this very generic bug. I suggest we close this and file new bugs for each unresolved case we find.