Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#16814 - [imlib2] cannot display large jpg files

Attached to Project: Arch Linux
Opened by Gaetan Bisson (vesath) - Friday, 23 October 2009, 23:57 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 06 May 2010, 14:30 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


feh (1.3.4, from extra) fails to display large files (see an example attached; it was created via imagemagick's montage, but the same happens with a similar file created via "feh -m").
It just says "feh WARNING: longcat.jpg - No Imlib2 loader for that file format" whereas the file is proper jpg (it displays alright in GIMP and Firefox).

I'm aware I should report that upstream, but since I found no bugtracker there, I thought I would post it here.
   longcat.jpg (840.7 KiB)
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 06 May 2010, 14:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  this was fixed upstream and is in the 1.4.4 package
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 24 October 2009, 00:11 GMT
  • Field changed: Summary (feh/imlib2 cannot display large jpg files → [imlib2] cannot display large jpg files)
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
  • Task assigned to Ronald van Haren (pressh)
The issue is with imlib2, since I tested with qiv that uses imlib2 and closes inmediatelly without any error msg.

imlib2 is not updated in one year... Maybe you can try reporting here [#1]

Comment by Gaetan Bisson (vesath) - Saturday, 24 October 2009, 00:40 GMT
Thanks for such a quick response.
I've reported the bug there:
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 27 November 2009, 01:55 GMT
good, upstream bug is closed and marked as fixed on svn.