evince 2.28.1 fails to render binary eps files on amd64

Bug #479674 reported by Chuong
This bug report is a duplicate of:  Bug #552990: evince does not display EPS file. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libspectre (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: evince

Hi all,

Karmic's evince (version up to 2.28.1) can not render several eps files I have, including the eps file attached, which however can be opened and rendered correctly by Hardy's evince (2.22.2). The eps files it can render are the ones whose text content can be viewed in Gedit. The eps files it cannot render are the binary ones which cannot be opened by Gedit. Nautilus also cannot render the icons of these later files.

If I run Karmic's evince from terminal to open the attached eps file, it produces these error messages:
---------------------------------------------------------------------------------------
$ evince Histogram_ImgOvl2.eps
undefined -21
undefined -21
undefined -21

** (evince:3061): WARNING **: Error rendering thumbnail
undefined -21

** (evince:3061): WARNING **: Error rendering thumbnail
--------------------------------------------------------------------------------------

In contrast, with Hardy's evince the same file can be opened without any error.

Chuong

Tags: amd64 eps
Revision history for this message
Chuong (vinhchuong) wrote :
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

The file renders fine on Karmic here, without those errors on the console.

Evince uses libspectre for rendering postscript files. Can you please check that you have libspectre1 version 0.2.2.ds-2 installed on your system?

Thank you

tags: added: packaging
Changed in evince (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Chuong (vinhchuong) wrote : RE: [Bug 479674] Re: evince 2.28.1 fails to render binary eps files

Thanks for your reply. Yes I have libspectre1 0.2.2.ds-2 installed. I don't understand how I have this problem as evince came with Karmic default installation (mine is 64bit version). I reinstalled evince from synaptic but nothing changes.

Chuong

> Date: Tue, 10 Nov 2009 13:42:34 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 479674] Re: evince 2.28.1 fails to render binary eps files
>
> The file renders fine on Karmic here, without those errors on the
> console.
>
> Evince uses libspectre for rendering postscript files. Can you please
> check that you have libspectre1 version 0.2.2.ds-2 installed on your
> system?
>
> Thank you
>
> ** Tags added: packaging
>
> --
> evince 2.28.1 fails to render binary eps files
> https://bugs.launchpad.net/bugs/479674
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “evince” package in Ubuntu: New
>
> Bug description:
> Binary package hint: evince
>
> Hi all,
>
> Karmic's evince (version up to 2.28.1) can not render several eps files I have, including the eps file attached, which however can be opened and rendered correctly by Hardy's evince (2.22.2). The eps files it can render are the ones whose text content can be viewed in Gedit. The eps files it cannot render are the binary ones which cannot be opened by Gedit. Nautilus also cannot render the icons of these later files.
>
> If I run Karmic's evince from terminal to open the attached eps file, it produces these error messages:
> ---------------------------------------------------------------------------------------
> $ evince Histogram_ImgOvl2.eps
> undefined -21
> undefined -21
> undefined -21
>
> ** (evince:3061): WARNING **: Error rendering thumbnail
> undefined -21
>
> ** (evince:3061): WARNING **: Error rendering thumbnail
> --------------------------------------------------------------------------------------
>
> In contrast, with Hardy's evince the same file can be opened without any error.
>
> Chuong

_________________________________________________________________
Hotmail: Trusted email with Microsoft's powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/
http://clk.atdmt.com/GBL/go/177141664/direct/01/

tags: removed: and evince packaging
Revision history for this message
Dimitrios Symeonidis (azimout) wrote : Re: evince 2.28.1 fails to render binary eps files

Confirmed on an amd64 machine, marking as such
Thank you, Chuong

tags: added: amd64
summary: - evince 2.28.1 fails to render binary eps files
+ evince 2.28.1 fails to render binary eps files on amd64
affects: evince (Ubuntu) → libspectre (Ubuntu)
Changed in libspectre (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
krahim (karim-rahim) wrote :

Hi,

I had the identical problem, and well I have an odd work around that I can repeat.
I install evince on my 32bit chroot and now evince works everywhere. I install it with the command
sudo aptitude install invance and it installs the following packages

The following NEW packages will be installed:
  devicekit-disks{a} evince ghostscript{a} gnome-icon-theme{a}
  gnome-keyring{a} gsfonts{a} gvfs{a} gvfs-backends{a} libarchive1{a}
  libatasmart4{a} libbluetooth3{a} libcdio-cdda0{a} libcdio-paranoia0{a}
  libcdio7{a} libcupsimage2{a} libdjvulibre-text{a} libdjvulibre21{a}
  libevdocument1{a} libevview1{a} libexif12{a} libffi5{a} libgcr0{a}
  libgd2-noxpm{a} libgdu0{a} libgnome-keyring0{a} libgp11-0{a}
  libgphoto2-2{a} libgphoto2-port0{a} libgraphviz4{a} libgs8{a}
  libgsf-1-114{a} libgsf-1-common{a} libgudev-1.0-0{a} libgvfscommon0{a}
  libilmbase6{a} libkpathsea4{a} libmagickcore2{a} libmagickwand2{a}
  libopenexr6{a} libopenobex1{a} libpam-gnome-keyring{a} libparted1.8-12{a}
  libpolkit-agent-1-0{a} libpolkit-backend-1-0{a} libpoppler-glib4{a}
  libpoppler5{a} libproxy0{a} librsvg2-2{a} librsvg2-common{a}
  libsgutils2-2{a} libsoup-gnome2.4-1{a} libsoup2.4-1{a} libspectre1{a}
  libwmf0.2-7{a} obex-data-server{a} policykit-1{a} policykit-1-gnome{a}
  psfontmgr{a} python-dbus{a} python-gobject{a}

During the setup I can watch my 64 bit version of evince actually show the image correctly. If I remove this evince it doesn't work.

To reproduce it. First have evince not working on a valid eps file in 64 bit. Setup a 32 bit chroot and install evince and see what happens.

Let me know if you want any other info.

Karim

Revision history for this message
Chuong (vinhchuong) wrote : RE: [Bug 479674] Re: evince 2.28.1 fails to render binary eps files on amd64
Download full text (3.8 KiB)

Hi Karim,

Thanks for the solution. Actually I can survive with this bug as I can open eps files by importing them in Gimp. Without this bug, it would easier for me to select correct eps files by just looking at their icons, but this is not crucial. I am writing articles in Latex and have no problem to compile with eps files to create usable pdf files.

Chuong

> Date: Wed, 20 Jan 2010 19:15:38 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 479674] Re: evince 2.28.1 fails to render binary eps files on amd64
>
> Hi,
>
> I had the identical problem, and well I have an odd work around that I can repeat.
> I install evince on my 32bit chroot and now evince works everywhere. I install it with the command
> sudo aptitude install invance and it installs the following packages
>
>
> The following NEW packages will be installed:
> devicekit-disks{a} evince ghostscript{a} gnome-icon-theme{a}
> gnome-keyring{a} gsfonts{a} gvfs{a} gvfs-backends{a} libarchive1{a}
> libatasmart4{a} libbluetooth3{a} libcdio-cdda0{a} libcdio-paranoia0{a}
> libcdio7{a} libcupsimage2{a} libdjvulibre-text{a} libdjvulibre21{a}
> libevdocument1{a} libevview1{a} libexif12{a} libffi5{a} libgcr0{a}
> libgd2-noxpm{a} libgdu0{a} libgnome-keyring0{a} libgp11-0{a}
> libgphoto2-2{a} libgphoto2-port0{a} libgraphviz4{a} libgs8{a}
> libgsf-1-114{a} libgsf-1-common{a} libgudev-1.0-0{a} libgvfscommon0{a}
> libilmbase6{a} libkpathsea4{a} libmagickcore2{a} libmagickwand2{a}
> libopenexr6{a} libopenobex1{a} libpam-gnome-keyring{a} libparted1.8-12{a}
> libpolkit-agent-1-0{a} libpolkit-backend-1-0{a} libpoppler-glib4{a}
> libpoppler5{a} libproxy0{a} librsvg2-2{a} librsvg2-common{a}
> libsgutils2-2{a} libsoup-gnome2.4-1{a} libsoup2.4-1{a} libspectre1{a}
> libwmf0.2-7{a} obex-data-server{a} policykit-1{a} policykit-1-gnome{a}
> psfontmgr{a} python-dbus{a} python-gobject{a}
>
>
> During the setup I can watch my 64 bit version of evince actually show the image correctly. If I remove this evince it doesn't work.
>
> To reproduce it. First have evince not working on a valid eps file in 64
> bit. Setup a 32 bit chroot and install evince and see what happens.
>
> Let me know if you want any other info.
>
> Karim
>
> --
> evince 2.28.1 fails to render binary eps files on amd64
> https://bugs.launchpad.net/bugs/479674
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “libspectre” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: evince
>
> Hi all,
>
> Karmic's evince (version up to 2.28.1) can not render several eps files I have, including the eps file attached, which however can be opened and rendered correctly by Hardy's evince (2.22.2). The eps files it can render are the ones whose text content can be viewed in Gedit. The eps files it cannot render are the binary ones which cannot be opened by Gedit. Nautilus also cannot render the icons of these later files.
>
> If I run Karmic's evince from terminal to open the attached eps file, it produces these error messages:
> --------------------------------------------------------------------...

Read more...

Revision history for this message
Rogério Theodoro de Brito (rbrito) wrote :

I'm looking for some files that may present a problem to evince (under lucid) and, with the patch that I proposed on bug LP #298139, it works fine under PowerPC. Can anybody test if that patch fixes the issue here?

I don't have a 64-bit arch handy here.

Regards,

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.