Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • L libtiff
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 159
    • Issues 159
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libtiff
  • libtiff
  • Issues
  • #454
Closed
Open
Issue created Aug 21, 2022 by Johann Popper@lethedrinker999

Error interpreting JPEG image file (Backing store not supported)

Summary

Opening any jpg over ~7mb fails with the error: "Error interpreting JPEG image file (Backing store not supported)".

In the latest updates to Fedora 36 stable today & 37 branched since yesterday at least, there is evidently a regression where jpgs over ~7mb can no longer be opened, viewed, or used in any way, either in GNOME Shell, GNOME Image Viewer, any software dependent on libtiff. I hypothesize this by tracing the error's history, showing the exact same thing in October 2017 caused by an accidental change to libtiff that caps max_memory_to_use, which libjpeg-turbo follows. Thus, the easy answer is it happened again, so I wanted you to be aware.

The latest flatpak on GNOME Image Viewer, which looks to be about 2 weeks old, does not have this problem and can open any large jpg. I presume the libtiff packaged in the flathub flatpak predates the regression.

Hope this is enough of a description to be helpful, if indeed libtiff is the cause.

Version Fedora 36 latest repo version = 4.4.0-4

Steps to reproduce

Install Fedora 36, update, try to open a large JPG with the default image viewer, or see if preview loads in Files, or try to apply as Background, etc. Perhaps Arch and the like are similarly affected.

Platform

I presume any up-to-date distro repo app or flatpak app, etc, utilizing the latest libtiff.

Assignee
Assign to
Time tracking