evince in Hardy does not render multi-page tiffs

The backends have been splitted in hardy, you should have a libtiffdocument.so installed, isn't that the case?

yes, i have libtiffdocument.so in /var/lib
$ ls -al /usr/lib/evince/backends/libtiffdocument.so
-rw-r--r-- 1 root root 37184 Mar 11 06:54
/usr/lib/evince/backends/libtiffdocument.so

but it still open multi-page tiff as only one page .
what information you need more ?

Sebastien Bacher 提到, 於 2008年03月13日 01:06:
> The backends have been splitted in hardy, you should have a
> libtiffdocument.so installed, isn't that the case?
>
> ** Changed in: evince (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
>

the bug description is not correct then, what is your issue exactly? the multipage tiff not rendered correctly? could you attach an example to the bug?

yes , evince in hardy doesn't render multipage tiff correctly .

attachement is a two pages tiff .

Sebastien Bacher 提到, 於 2008年03月13日 16:33:
> the bug description is not correct then, what is your issue exactly? the
> multipage tiff not rendered correctly? could you attach an example to
> the bug?
>
>

there is no attachment to this bug

here is attachment

hi there ,
will this bug be fixed before hardy officially release ???

Hi all,

Disabling pixbuf support in debian/rules ( remove --enable-pixbuf ) solves this issue.

This is not related to Ubuntu because the same happens with svn copy of evince:
Multipage tiff support OK :
./configure --disable-scrollkeeper --enable-djvu --enable-dvi --enable-comics --enable-impress

Multipage tiff support not OK :
./configure --disable-scrollkeeper --enable-djvu --enable-dvi --enable-pixbuf --enable-comics --enable-impress

Regards,

This bug has been fixed upstream. It should be fixed now in svn trunk and gnome-2-22 branches.

The issue has been fixed upstream now

This is still present in 2.22.1.1

Second that, bug is still present in 2.22.1.1

yes, bug is still present in latest evince in hardy

why did you re-assign this bug without asking? fixing that again

the bug has been fixed upstream now

Sebastien, there are three people who claim this is *NOT* fixed. How about a little respect for them?

I reassigned to you because you were the last person to upload, not some group "Ubuntu desktop bugs" which likely has many other things on their mind besides evince. If that was incorrect, please change it, fine. No reason to make a fuss about it. Although I have to accept my part of the blame, since that group is listed as Maintainer. I guess I did not look closely enough. Mea culpa.

could you stop changing the bug settings over the maintainer? the desktop team uses "Fix Committed" to indicate that the bug has been fixed upstream and to make easy to list fix available to consider for the next upload, the bug is not closed

note that I don't think anybody has been unrespectful there, if you don't know how bugs are handled that's fine but you should let the maintainer do their job and not insist on changing the settings against their will, better to discuss and explain your issue if you disagree with a change so you will not come comfrontational and get nicer replies

Well, the claim, that the fix is committed has been there for close to one month now, yet nothing has changed.

Frankly, I do a lot of bug triage in LP and even if you are the Maintainer, I am sorry I have to disagree with you here. Whether or not a bug is fixed upstream is indicated by the "also affects project" additional (!) field. And it is tracked just fine for this very bug. That is one of the strong points of Launchpad over bugzilla. I have never come across any project here in Launchpad that already closes bugs where there is a fix upstream but where the fix has not made it into ubuntu. That also completely defeats the nice feature of LP of "bugs fixed elsewhere". So, please don't blame me for using LP the way it was supposed to be used.

BTW, why we don't we actually see the fix that has been sitting there for so long? (I don't mind to sound unappreciative, I am merely curious. Can't it be applied without the full upgrade easily?)

s/mind/mean/

completely changes the tone ;-) I should proofread more carefully before hitting the submit button.

you don't get the information about upstream tasks in the bug lists though that's why the desktop team uses bug fixed when a fix is available, I don't blame you to triage bugs the way you think is right but you should not be trying to force the settings over the maintainer though

the issue is a small one and sru require quite some extra work so we don't backport every trivial fix, this change will be available in hardy when GNOME 2.22.2 is uploaded in some weeks

Okay, this is fixed in what upstream package? I know that it is important to only assign levels of importance above "Low" for severe issues, but I think that the importance of this bug might be underestimated.

TIFF and PDF are the primary ways of exchanging documents and scanned images in organizations. A very important business function.

To have to wait weeks for a 'proper' fix for the GNOME release seems like a while, especially when I am not even running GNOME (I'm on Xubuntu). Is there a way we can patch and compile the necessary package manually?

I rely heavily on Tiff files as all my incoming faxes are in a tif format (via email). I have a work-a-round that I've started using. It's not the most elegant thing but suffices until a fix for evince is in..

First install ImageMagick.. Part of that package has a utility called "convert". Since all my faxes are B&W this fix is primarily for non-color multipage tiffs. It might work on multipage color tiff's but will render them in B&W I think.

I first save the file then open terminal and manuver (sp?) to the correct directory.. Now initiate the command.. "convert -monochrome <input_file_name.tif> <output_file_name.pdf>" Ofcourse leave out the quotes (") and the <>'s. This command will convert the file from tif to pdf and allow evince to open it will all pages accessable.

There are ways to use the convert command without -monochrome. However, I've found that it defaults to color and will render the new pdf with much less clarity. -monochrome keeps the clarity of the original as much as possible..

By the way, 28 pages convert in apx 15 seconds.. I wish I could script well enough to implement this in a gui situation by highlighting the saved file and right mouse clicking then choosing my "new" option of conversion. Unfortunatly I'm not that talented.

This bug should be critical, I'm a system administrator for a ISP company, and all your helpdesk laptops have been migrated from Windows to ubuntu.

I now nobody can open TIFF (FAXES) with the last version of evince it is very anoying.

I have to manually fetch the Gutsy release of evince and apply to all this computers....

So is ubuntu for kids or it is ready for bussiness ??? It takes so long to correct this damn thing.... It looks like MS correcting some bugs it take ages

those comments are not really useful, there is thousand of bugs open and the team is pretty small and can't work on everything immediatly, a new version should be uploaded next week, the bug is low priority because it's not a data loss nor crasher issue and get few user requests

@Mauro: In the meantime (waiting for a fix) you can use gimp.. read my post here: http://ubuntuforums.org/showthread.php?t=106380
for a simple workaround. I'm using it for reading my incoming faxes too

Thank you very Much, I will have a look to your post.

2008/5/23 Virtual DarKness <email address hidden>:

> @Mauro: In the meantime (waiting for a fix) you can use gimp.. read my post
> here: http://ubuntuforums.org/showthread.php?t=106380
> for a simple workaround. I'm using it for reading my incoming faxes too
>
> --
> evince in Hardy does not render multi-page tiffs
> https://bugs.launchpad.net/bugs/201345
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Accepted into -proposed, please test and give feedback here

Thanks.

Can you give a download URL so we don't have to hunt around?

Hi,
Rolf Leggewie [2008-05-29 9:19 -0000]:
> Can you give a download URL so we don't have to hunt around?

Just enable proposed updates in System -> Administration -> Software
Sources -> Updates.

Martin,

thank you for the quick response. Essentially, I had already done the equivalent change to /etc/apt/sources.list. There was nothing there, yet. At any rate, I'd prefer to download this package only and not enable hardy-proposed in general which is why I was asking for an URL. Others may feel the same way.

I looked around further, but was still unable to find this updated package. Maybe it has not reached the download servers, yet?

Hello Rolf,

You should take the most recent evince in the pool of archive.ubuntu.com.

Here is the link to download it : http://archive.ubuntu.com/ubuntu/pool/main/e/evince/evince_2.22.2-0ubuntu1_i386.deb

Hope that it helps you.

--kalon33

Nicolas, thank you for the link.

I am happy to report that the sample tif attached to this bug report displays two pages just fine now.

"Image Viewer" which was the default in FF for me still displays only one page :-( -> bug 50929

verification done

- test with evince from hardy (2.22.1.1-0ubuntu1), followed the test case, only 1 page is shown.
- test with evince from proposed (2.22.2-0ubuntu1), opened the tif file and now 2 pages are shown instead of 1, bug is fixed. thanks.

Works fine here, too.

I confirm : bug seems fixed.

Copied to hardy-updates and intrepid.

I am sorry to say that I can see all pages within one TIF file in EVince now, but they are all "flipped" (left <->right).
Please, try to open the enclosed file in Evince to see what I mean (it is like a mirror reflection).
Note: KFaxView can display the file in the same Ubuntu Hardy 64-bit installation properly.

Vladimir, "one issue, one report". Please open a new bug. I can confirm the problem you were seeing. But nobody will work on this bug, because this particular has been fixed and is marked as "fix released"

Hello Rolf,
Thanks for your advice. I will open a new bug.
Regards
Vladimir
On Sat, 2008-08-09 at 01:53 +0000, Rolf Leggewie wrote:

> Vladimir, "one issue, one report". Please open a new bug. I can
> confirm the problem you were seeing. But nobody will work on this bug,
> because this particular has been fixed and is marked as "fix released"
>