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 167230 - rework error messages
rework error messages
Status: RESOLVED OBSOLETE
Product: totem
Classification: Core
Component: GStreamer backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks: 309714
 
 
Reported: 2005-02-13 03:29 UTC by William Jon McCann
Modified: 2008-12-05 12:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (20.89 KB, patch)
2005-02-13 03:32 UTC, William Jon McCann
rejected Details | Review

Description William Jon McCann 2005-02-13 03:29:10 UTC
Here's a patch to rework the error messages to be less technical.  The biggest
problem right now is that some messages are displayed directly from gstreamer. 
These are just too technical for the end user.
Comment 1 William Jon McCann 2005-02-13 03:32:26 UTC
Created attachment 37425 [details] [review]
patch
Comment 2 Ronald Bultje 2005-02-14 10:28:39 UTC
Hi William,

the errors in GStreamer are indeed bad. However, your patch appears to add
several layers to "hide" or "encapsulate" the error into something readable. Is
that really a solution? Isn't fixing GStreamer's error messages much better? It
is actually on my TODO list, but unfortunately there's lots of stuff on my TODO
list, kind of swamping me... :-/.
Comment 3 William Jon McCann 2005-02-14 17:41:49 UTC
I think that this actually is the correct solution.  The user should never be
forced to see sub-process errors directly.  For example, look at what nautilus
does.  When you can't eject a disc with nautilus it doesn't say
"Error unmounting /dev/hdc: device busy" or something directly in the secondary
text of the dialog.

Rather, it hides that part from the user in a details expander.  It has to be
there somewhere because it is the part that the sysadmin/tech support is going
to want to see.

Do GStreamer errors need to improve anyway?  Certainly.  And I will gladly try
to help with this.  However, they will continue to be technical in nature - as
they should be.  GStreamer is a user-invisible subsystem.
Comment 4 Ronald Bultje 2005-02-14 17:55:07 UTC
I think you are correct, yeah... I'm not sure how much detail the user will want
(obviously, if the file failed to open because it doesn't exist, the user should
know, because then he mistyped it or the webpage on which he clicked is broken;
it's not the same as 'codec not supported').

Need to rethink that for a while.
Comment 5 Bastien Nocera 2005-02-14 23:34:05 UTC
I don't know whether this has appeared in bugzilla yet, but I don't want to see
debug messages in Totem's UI (the only case where that would be useful is if
external programs are called).
So the details button is a no-no.
Comment 6 Bastien Nocera 2008-12-05 12:45:05 UTC
Let's close this, there was no new versions of the patch in a long while, and it probably got better...