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 754155 - Disk Image Mounter: Value too large for define data type
Disk Image Mounter: Value too large for define data type
Status: RESOLVED FIXED
Product: gnome-disk-utility
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2015-08-27 07:19 UTC by carlosprgms
Modified: 2017-05-29 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Enable large file support patch (1.39 KB, patch)
2017-05-26 01:34 UTC, Mitchell Horne
committed Details | Review

Description carlosprgms 2015-08-27 07:19:23 UTC
When I try to open an .iso file in Files with Disk Image Mounter I got the following message:
An error ocurred. Value too large for defined data type

maybe that the iso file is too large
Comment 1 Mitchell Horne 2017-05-26 01:34:32 UTC
Created attachment 352602 [details] [review]
Enable large file support patch

This error occurs when trying to open an image file larger than 2GB on a 32-bit system. Looks like the reason for this is disks was missing the proper flags to enable support for files of this size. 

One way of fixing this is adding a #define _FILE_OFFSET_BITS 64 line to each file requiring support, but after some reading it seems the more complete and portable way is grabbing the flags in the autoconf script. I tested this in a VM and it fixes the issues with both mounting and creating files. That being said I am far from an expert with autotools so I would appreciate someone checking this over.

Here's a couple relevant pages on LFS:
http://users.suse.com/~aj/linux_lfs.html
https://people.redhat.com/berrange/notes/largefile.html
Comment 2 Kai Lüke 2017-05-29 11:40:37 UTC
Review of attachment 352602 [details] [review]:

Hi,

great that you worked on it, thanks a lot! I've also tested it now with the cases I could think of and all were solved :)

Regards,
Kai
Comment 3 Kai Lüke 2017-05-29 11:44:27 UTC
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.