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 739204 - Fails at benchmarking on 32-bit architectures
Fails at benchmarking on 32-bit architectures
Status: RESOLVED FIXED
Product: gnome-disk-utility
Classification: Core
Component: Disks UI
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2014-10-26 10:46 UTC by intrigeri
Modified: 2015-12-23 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 3.13/3.14

Attachments
patch proposed on the Debian bug tracker (343 bytes, patch)
2014-10-26 10:46 UTC, intrigeri 		committed Details | Review

Description intrigeri 2014-10-26 10:46:35 UTC 
Created attachment 289337 [details] [review]
patch proposed on the Debian bug tracker

Hi,

it was reported to Debian that Disks can't benchmark on 32-bit architectures.
More details can be found on https://bugs.debian.org/765643. The bug reporter proposed a one-line patch that fixes the problem for them. I'm attaching it here.

Thanks for maintaining Disks :)
Comment 1 Ivan Baldo 2015-05-13 21:05:23 UTC 
Hello.
Is there a reason to not include that patch or has this bug just been forgotten?
Hope someone can commit that single-line patch or tell why is it wrong or dangerous or whatever...
Thanks!!!
Comment 2 Michael Catanzaro 2015-05-13 22:43:37 UTC 
Looks sane, thanks!
Comment 3 morepenguinthanman 2015-12-23 13:23:19 UTC 
Hello. I am like the picture of the dog that doesn't have any idea what it is doing. I want to make a disk image and copying and pasting the error message got me here. But I don't understand how to install this patch. I would be most grateful if anybody could explain this to me. 

I can copy and paste into terminal. I can download a file and run it. But a lot of the terminology here doesn't mean anything to me. 


I don't understand why this bug is even there when it is more than a year old and I have updated everything and the solution is apparently known. Isn't making a disk image quite a basic feature? Why would this not already be sorted out?

thank you
Comment 4 Michael Catanzaro 2015-12-23 14:21:35 UTC 
Can you copy/paste the error message you see here, please? This bug isn't related to making disk images.