Bug 220300 - okular does not display multi-page tiffs
Summary: okular does not display multi-page tiffs
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-27 18:47 UTC by hadmut
Modified: 2009-12-28 21:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hadmut 2009-12-27 18:47:29 UTC
Version:           4:4.3.2-0ubuntu1 (using KDE 4.3.2)
Installed from:    Ubuntu Packages

Hi, 

when opening a multi-page tiff, which is generated by most scanners/scanning software (you can construct a multi-tiff from single-tiffs with tiffcp and disassemble with tiffsplit), okular displays only the first page.

Since okular is a document viewer and should support tiff, I'd rather consider this as a bug than as a wish. 

regards
Comment 1 Pino Toscano 2009-12-27 18:53:33 UTC
Did you actually install the distro package providing the TIFF backend?
Comment 2 hadmut 2009-12-28 21:49:35 UTC
That's a pretty good hint, that was the problem. Thanks.  

okular is able to read a tiff even without that package, so it is not obvious that there is something missing. Even installing that package does not help immediately, okular still reads /usr/lib/kde4/okularGenerator_kimgio.so on one of my computers, but then it worked on my other computer where I installed the package before starting okular for the first time. 

Seems as if okular would not recognize the tiff backend without a complete restart of the Desktop.
Comment 3 Pino Toscano 2009-12-28 21:58:41 UTC
(In reply to comment #2)
> That's a pretty good hint, that was the problem. Thanks.

Ok, closing then.

> Seems as if okular would not recognize the tiff backend without a complete
> restart of the Desktop.

Or, if you have a 2.6.31 or 2.6.32 Linux kernel, KDE's file change notification system does not cope to its behaviour change. Manually running `kbuildsycoca4 --noincremental` will do the job, in any case.