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 761397 - Images formats unsupported
Images formats unsupported
Status: RESOLVED DUPLICATE of bug 761396
Product: glom
Classification: Other
Component: data mode
1.28.x
Other Linux
: Normal normal
: ---
Assigned To: Murray Cumming
Murray Cumming
Depends on:
Blocks:
 
 
Reported: 2016-02-01 11:58 UTC by m.rick.mac
Modified: 2016-02-24 20:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description m.rick.mac 2016-02-01 11:58:18 UTC
Some images formats are unsupported when trying to import them in Glom:
JP2 (JPEG 2000), PDF, SVG, EPS.

Xunbuntu 15.04
Comment 1 Murray Cumming 2016-02-02 07:13:40 UTC
This suggest a problem with the GTK+ and/or evince build. Maybe the necessary dependencies were not installed when building GTK+, for instance. However, I might add some tests to Glom to make sure that it supports common formats.

By the way, are you running the existing tests in Glom, via "make check"?
Comment 2 Murray Cumming 2016-02-02 08:33:43 UTC
Sorry, I didn't notice the mention of Xunbuntu. I thought you were talking about your Mac build.

However, at least on Ubuntu, it works for me. I assume that you are using the PPA package for Glom, like me. Could you give me more details about what you see?
Comment 3 m.rick.mac 2016-02-15 20:19:57 UTC
Well, I tried with the example database "Small Business Example"
And click on the Image field and tried to load some JP2, PDF, SVG, EPS files. Nothing loaded in the field, the loading window appears and seems to load and that's it.
Comment 4 Murray Cumming 2016-02-24 20:27:33 UTC
Just to be completely sure, could you please upload one file that you have this problem with. For instance, a PDF.
Comment 5 Murray Cumming 2016-02-24 20:41:04 UTC
Nevermind. There seems to be a problem with all image formats that need use to use evince's EvinceView. Let's deal with this in bug #761396 .

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