Please backport evince 2.24.1 from Intrepid to Hardy

[Bill Harris]

Hardy contains evince 2.22.2. According to http://mail.gnome.org/archives/evince-list/2008-November/msg00008.html andhttp://svn.gnome.org/viewvc/evince/trunk/NEWS?revision=3225&view=markup , 2.22.2 contains bug that prevents evince from launching external applications, as one might want to do when preparing presentations with LaTeX beamer or OO.o Impress. 2.24.1 is in Intrepid (http://packages.ubuntu.com/intrepid/evince), but I don't want to upgrade until it's clear that the NVidia drivers are ready.

[Bill Harris (bill-harris)]

More investigation suggests that evince 2.22.2 _can_ launch an external document from a PDF presentation created by OO.o, but it cannot do the same from a PDF presentation created by beamer. It appears that the problem I am having lies with beamer, not with evince 2.22.2

[John Dong (jdong)]

The evince 2.24.x release also provides some new format support, multimedia hotkeys, and other goodness. If the backport works it actually would be quite nice to have it.

[Chris Coulson (chrisccoulson)]

Evince 2.24 depends on libpoppler (>=0.8), but Hardy only has 0.6.4

[Alex Korobkin (korobkin)]

Evince >= 2.25.4 also has the bug with saving default paper size fixed:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/224882

Since LTS release is mainly used in corporate environments with inexperienced users, where they print PDF documents a lot, making Evince able to store selected paper size will be a very convenient paper cut.

[Evan Broder (broder)]

It looks like this bug requests a backport from Ubuntu 8.10 (Intrepid
Ibex). However, as Intrepid is no longer supported, such a backport is
no longer possible.

This bug is being set to "Won't Fix". If you would still like to move
forward with this backport request, please re-open the bug and adjust
it to request a backport from a current release.

(This change is being made by an automated bot run by Evan Broder, who
is now subscribed to the bug; if you think the change was made in
error, please feel free to re-open the bug)