Sign up now! · Forgot password?
RSS/Atom feed Twitter

HEIC or HEIF Files Not Opened

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

7 of 7 messages available
Toggle history

Please log in to manage your subscriptions.

HEIC or HEIF Files Not Opened TonyS 02 Mar 15:13
  HEIC or HEIF Files Not Opened rich404 02 Mar 16:28
   HEIC or HEIF Files Not Opened TonyS 02 Mar 19:53
    HEIC or HEIF Files Not Opened alexatkin 10 Mar 23:14
     HEIC or HEIF Files Not Opened rich404 11 Mar 09:24
      HEIC or HEIF Files Not Opened TonyS 11 Mar 14:44
     HEIC or HEIF Files Not Opened TonyS 11 Mar 14:46
2019-03-02 15:13:26 UTC (23 days ago)
postings
4
contact
Send private message

HEIC or HEIF Files Not Opened

I am using GIMP 2.10.8 on Fedora 29. This version is supposed to be able to import .HEIC files. I have found, however, that these files are not recognized by GIMP when I to to folders that contain them in the File menu. Am I missing something? Does GIMP in the Fedora 29 repositories not have some dependency for this?

2019-03-02 16:28:25 UTC (22 days ago)
postings
365
contact
Send private message

HEIC or HEIF Files Not Opened

I am using GIMP 2.10.8 on Fedora 29. This version is supposed to be able to import .HEIC files. I have found, however, that these files are not recognized by GIMP when I to to folders that contain them in the File menu. Am I missing something? Does GIMP in the Fedora 29 repositories not have some dependency for this?

Caveat - I do not use Fedora however checking with my Kubuntu 16.04 (deb packages) and PClinuxOS (rpm packages) Gimp(s) 2.10.8

Are you using a flatpak? Unlikely to work, much missing from the org.gnome.Platform runtime. Although you can get it to work if you slip a few extra files in here-and-there (at least as far as 'buntu is concerned).

A regular install? Check that you have libheif and libx265 installed.

Probably better asking this question on a Fedora forum.

2019-03-02 19:53:42 UTC (22 days ago)
postings
4
contact
Send private message

HEIC or HEIF Files Not Opened

Caveat - I do not use Fedora however checking with my Kubuntu 16.04 (deb packages) and PClinuxOS (rpm packages) Gimp(s) 2.10.8

Are you using a flatpak? Unlikely to work, much missing from the org.gnome.Platform runtime. Although you can get it to work if you slip a few extra files in here-and-there (at least as far as 'buntu is concerned).

A regular install? Check that you have libheif and libx265 installed.

Probably better asking this question on a Fedora forum.

Thanks, Rich. I have libheif, but not libx265. Will install same. Am not using a Flatpak. My GIMP was originally an older version, installed from the Fedora repositories, and updated over the past couple years via the usual Fedora process. If I still have problems, will refer to a Fedora forum. Thanks again.

2019-03-10 23:14:33 UTC (14 days ago)
postings
1
contact
Send private message

HEIC or HEIF Files Not Opened

Thanks, Rich. I have libheif, but not libx265. Will install same. Am not using a Flatpak. My GIMP was originally an older version, installed from the Fedora repositories, and updated over the past couple years via the usual Fedora process. If I still have problems, will refer to a Fedora forum. Thanks again.

You have to install gimp-heif-plugin I believe but when I try to load an image after doing that my entire desktop crashes needing a reboot to get back in. I'm guessing the maintainer compiled it wrong or messed up the dependencies.

2019-03-11 09:24:53 UTC (14 days ago)
postings
365
contact
Send private message

HEIC or HEIF Files Not Opened

You have to install gimp-heif-plugin I believe but when I try to load an image after doing that my entire desktop crashes needing a reboot to get back in. I'm guessing the maintainer compiled it wrong or messed up the dependencies.

As with much of Gimp it depends. Gimp version and distro.

An Ubuntu 18.10 (VM) and all works as expected. The gimp package contains the file-heif plugin and pulls in libheif as a dependency, which in turn pulls in libx265..and so on. see screenshots.

However, I mostly use a kubuntu 16.04 and a Gimp 2.10.8 flatpak. The Gimp package also contains the file-heif plugin but the org.gnome.runtime does not have those dependencies. I can add those, the file-heif plugin now opens heif files but crashes on export. Solution for that is disable the built-in file-heif and add a separate heif-gimp-plugin as a replacement.

There are other linux distros that work out-the-box, PClinuxOS Gimp 2.10.8 for example, but I have no knowledge of Fedora so can not comment.

For say, Gimp 2.8.22 (kubuntu 16.04) then all needs adding, heif-gimp-plugin plus the dependencies.

2019-03-11 14:44:33 UTC (14 days ago)
postings
4
contact
Send private message

HEIC or HEIF Files Not Opened

Thanks, Rich, I'll keep working on it as time permits and will post when and if I solve it.

As with much of Gimp it depends. Gimp version and distro.

An Ubuntu 18.10 (VM) and all works as expected. The gimp package contains the file-heif plugin and pulls in libheif as a dependency, which in turn pulls in libx265..and so on. see screenshots.

However, I mostly use a kubuntu 16.04 and a Gimp 2.10.8 flatpak. The Gimp package also contains the file-heif plugin but the org.gnome.runtime does not have those dependencies. I can add those, the file-heif plugin now opens heif files but crashes on export. Solution for that is disable the built-in file-heif and add a separate heif-gimp-plugin as a replacement.

There are other linux distros that work out-the-box, PClinuxOS Gimp 2.10.8 for example, but I have no knowledge of Fedora so can not comment.

For say, Gimp 2.8.22 (kubuntu 16.04) then all needs adding, heif-gimp-plugin plus the dependencies.

2019-03-11 14:46:49 UTC (14 days ago)
postings
4
contact
Send private message

HEIC or HEIF Files Not Opened

Thanks, Alex. I think you are right.

You have to install gimp-heif-plugin I believe but when I try to load an image after doing that my entire desktop crashes needing a reboot to get back in. I'm guessing the maintainer compiled it wrong or messed up the dependencies.