Bug#257659: epiphany-browser: Unable to print

[Edd Dumbill]

--=-pnEEnbGgtuc7tdBjnkBu
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2004-07-04 at 22:06 -0400, John Stilian wrote:
> Package: epiphany-browser
> Version: 1.2.6-3
> Severity: normal
>=20
> If I attempt to print from Epiphany, anything at all, I get back an
> error message that reads "There was a problem printing. The printer
> could not be found."

This happens because the maintainers of the mozilla package have
switched off postscript printing, and the epiphany developers have not
implemented XPrint printing, which is the only kind Mozilla supports
now.

I asked the Mozilla developers to re-enable postscript printing so sarge
would ship with an epiphany that could print, but they did not want to,
citing security concerns.

Responding to the wishes of the epiphany upstream developers, I then
asked the parties who reported such concerns for details of the security
issues at hand, but nobody responded to me, which I find strange.  I
sent mail to the mozilla maintainers and the commenters on the bug
report concerned 10 days ago.  The report on 256072 says "Epiphany
upstream knows about the issue since *years*", something upstream flatly
denies.  So it's important to get to the bottom of it.

Perhaps this mail will cause them to send a response, because until I
get it I can only see their actions in disabling the postscript printing
as somewhat arbitrary and their non-response to me contrary to Debian's
commitment to handling things in public.

If we find evidence of these security concerns then obviously we
completely endorse the disabling of the postscript printing.

In any event, epiphany upstream are experimenting with solutions to the
issue, as are galeon upstream.  But they are running into difficulties,
and furthermore are concerned about adding large code changes to a
stable release series.

Therefore, if Debian sarge releases before GNOME 2.8 gets into testing
(a very real possibility, curiously enough) then I don't see how we can
ship anything but Firefox as the recommended GNOME browser.  Shipping a
browser that doesn't print is unacceptable.

regards

-- Edd


--=-pnEEnbGgtuc7tdBjnkBu
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA6PXirxbtsbubhxERAh6TAJ9CdxDnycpvVZuQXRUogaeNI65rMwCff/dZ
NR06M3QIm99Tv4WTw+yE7wQ=
=8uyy
-----END PGP SIGNATURE-----

--=-pnEEnbGgtuc7tdBjnkBu--