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 153428 - Include md5sum property
Include md5sum property
Status: RESOLVED DUPLICATE of bug 125470
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on: 125470
Blocks:
 
 
Reported: 2004-09-22 13:34 UTC by Reinout van Schouwen
Modified: 2008-02-03 20:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Reinout van Schouwen 2004-09-22 13:34:19 UTC
(Not sure if this is the right component, please re-assign if it isn't)

Since ISO images often have md5sums it would be very useful if the nautilus
properties tab for an application/x-cd-image would also show the md5sum for that
particular file. 

Since it takes some time to calculate, I imagine that at first the MD5sum field
would say something like 'Calculating...' perhaps with an indefinite progress
bar widget which would be replaced by the md5sum when the calculation has finished.
Comment 1 Reinout van Schouwen 2004-10-26 15:03:40 UTC
typo fix
Comment 2 William Jon McCann 2005-03-30 23:27:33 UTC
What is the actual use case for this?  I don't think most people are going to
know or care what an MD5SUM is.  If there is a compelling reason for this then
we can reopen this bug.
Comment 3 Reinout van Schouwen 2005-03-31 09:11:57 UTC
My compelling reason is that people currently are forced to use the command line
to see if the ISO they've downloaded has the correct checksum. It should be 
GNOME's goal to remove the need for the end user to ever having to open a terminal.
Comment 4 Bastien Nocera 2007-05-16 11:15:31 UTC
I think this would be useful to be able to check the md5sum/sha1sum after the burn has been verify (as in bug 125470)
Comment 5 Pavel Šefránek 2008-02-03 20:20:45 UTC
Described functionality should be supported via some third-party plugin. Makes no sense to have this upstream.

*** This bug has been marked as a duplicate of 125470 ***