Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-28 Thread Raphael Frey 
To be honest I don’t have the time (nor the required knowledge I guess) to find 
out the cause of this bug. If you give me instructions what I shall do, I would 
like to help you. Otherwise I don’t mind because I now use the Linux Libertine 
typeface (with Xelatex) and this just works.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-25 Thread Josselin Mouette 
reassign 572708 libcairo2   1.6.4-7
fixed 572708 1.8.10-3
thanks

Le mardi 09 mars 2010 à 20:14 +0100, Raphael Frey a écrit : 
 Le mardi 09 mars 2010 à 19:09 +0100, Josselin Mouette a écrit :
  We’re getting closer. The livelock is probably in this thread. Can you
  install debugging symbols for libcairo and libpixman and try again?
  Please do it several times in a row, to see if it’s always the same
  codepath that’s involved.
 
 Done. The output of gdb (thread apply all bt full) is attached to this
 mail. (I’ve run it three times so there are three log files, one for
 each run.)

Thanks. It looks like a bug in cairo, but frankly there have been so
many changes in cairo regarding bitmap fonts, it’s like looking for a
needle in a haystack.

If you really want to investigate more, you should try to bisect which
cairo change fixed that specific bug.

Otherwise I’ll simply consider this bug fixed in unstable.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'  “If you behave this way because you are blackmailed by someone,
  `-[…] I will see what I can do for you.”  -- Jörg Schilling


signature.asc
Description: This is a digitally signed message part

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Raphael Frey 
Le lundi 08 mars 2010 à 17:21 +0100, Josselin Mouette a écrit :
 http://wiki.debian.org/HowToGetABacktrace

Thanks for this link! I followed the instructions there and here is what
I got while running bt in gdb:

(gdb) bt
#0  0xb7fa4424 in __kernel_vsyscall ()
#1  0xb739ee67 in poll () from /lib/i686/cmov/libc.so.6
#2  0xb747a702 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x08406500 in ?? ()
#4  0x0008 in ?? ()
#5  0x0c0d in ?? ()
#6  0x08406500 in ?? ()
#7  0x0009 in ?? ()
#8  0x0002 in ?? ()
#9  0xb74f25f8 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x080a37a0 in ?? ()
#11 0xbfffe944 in ?? ()
#12 0xb74f25f8 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x080a37a0 in ?? ()
#14 0x080cbb1c in ?? ()
#15 0x0001 in ?? ()
#16 0x080cbb18 in ?? ()
#17 0x08406500 in ?? ()
#18 0xb739edf0 in ?? () from /lib/i686/cmov/libc.so.6
#19 0xb742d3f0 in ?? () from /lib/i686/cmov/libpthread.so.0
#20 0xb742b980 in ?? () from /lib/i686/cmov/libpthread.so.0
#21 0x080cbb1c in ?? ()
#22 0xb7bbfaf8 in ?? ()
---Type return to continue, or q return to quit---
#23 0xbfffe980 in ?? ()
#24 0x0c0d in ?? ()
#25 0x7fff in ?? ()
#26 0xb74f2240 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0x080f2528 in ?? ()
#28 0xb742b980 in ?? () from /lib/i686/cmov/libpthread.so.0
#29 0xbfffe998 in ?? ()
#30 0xb747ad92 in g_main_loop_run ()
from /usr/lib/libglib-2.0.so.0
Backtrace stopped: frame did not save the PC

HTH.

Meilleures salutations

Raphael





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Josselin Mouette 
Le mardi 09 mars 2010 à 11:24 +0100, Raphael Frey a écrit :
 Le lundi 08 mars 2010 à 17:21 +0100, Josselin Mouette a écrit :
  http://wiki.debian.org/HowToGetABacktrace
 
 Thanks for this link! I followed the instructions there and here is what
 I got while running bt in gdb:

Sorry but this backtrace is not usable. You need to install the
debugging packages for poppler, evince and glib so that it can be of
some use.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `- as a signed contact.”  -- Jörg Schilling




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Josselin Mouette 
Le mardi 09 mars 2010 à 16:15 +0100, Raphael Frey a écrit :
 #3  0xb73eb9f2 in pthread_mutex_lock ()
 from /lib/i686/cmov/libpthread.so.0
 #4  0xb7f480c6 in ev_document_doc_mutex_lock ()
 
 at /build/buildd/evince-2.22.2/./libdocument/ev-document.c:84
 #5  0x0806a08c in ev_pixbuf_cache_get_selection_surface (
 pixbuf_cache=0x82fca00, page=0, scale=1.36380422,
 region=0xbfffe9e8)
 at /build/buildd/evince-2.22.2/./shell/ev-pixbuf-cache.c:1015

Is this the backtrace you obtain at the time of the crash? It doesn’t
look like something is crashing in it.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `- as a signed contact.”  -- Jörg Schilling




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Raphael Frey 
Le mardi 09 mars 2010 à 16:28 +0100, Josselin Mouette a écrit :
 Is this the backtrace you obtain at the time of the crash? It doesn’t
 look like something is crashing in it.

It does not really crash, Evince just does not respond anymore while
trying to print the concerning PDF file and uses 100 % of CPU so that I
have to kill the process.

Here a little description what I did:

raph...@debian-laptop:~$ gdb evince
(gdb) run

Then:

1. File open
2. [Ctrl] + [P]
3. [ENTER]

CPU now is 100 %, so killing the process:

[Ctrl] + [C] (in terminal)

And then:

(gdb) bt
#0  0xb7fd0424 in __kernel_vsyscall ()
#1  0xb73cae67 in poll () from /lib/i686/cmov/libc.so.6
#2  0xb74a6702 in g_main_context_iterate (context=0x80cbb18,
block=1, 
dispatch=1, self=0x80a4680)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2954
#3  0xb74a6d92 in IA__g_main_loop_run (loop=0x80f24f0)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2853
#4  0xb78d4c99 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#5  0x0808e3b0 in main (argc=1, argv=Cannot access memory at
address 0xc
)
at /build/buildd/evince-2.22.2/./shell/main.c:401






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Josselin Mouette 
Le mardi 09 mars 2010 à 16:45 +0100, Raphael Frey a écrit :
 It does not really crash, Evince just does not respond anymore while
 trying to print the concerning PDF file and uses 100 % of CPU so that I
 have to kill the process.

OK, so it’s a livelock, not a crash.

 Here a little description what I did:
 
 raph...@debian-laptop:~$ gdb evince
 (gdb) run
 
 Then:
 
 1. File open
 2. [Ctrl] + [P]
 3. [ENTER]
 
 CPU now is 100 %, so killing the process:
 
 [Ctrl] + [C] (in terminal)
 
 And then:
 
 (gdb) bt

Here can you try with thread apply all bt full ?

Thanks,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `- as a signed contact.”  -- Jörg Schilling




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Raphael Frey 
Le mardi 09 mars 2010 à 14:05 +0100, Josselin Mouette a écrit :
 Sorry but this backtrace is not usable. You need to install the
 debugging packages for poppler, evince and glib so that it can be of
 some use.

evince-dbg was already installed. I’ve now installed
libglib2.0-0-dbg and poppler-dbg and this is what I got:

(gdb) bt
#0  0xb7f64424 in __kernel_vsyscall ()
#1  0xb73f0c99 in __lll_lock_wait ()
from /lib/i686/cmov/libpthread.so.0
#2  0xb73ec0c4 in _L_lock_89 ()
from /lib/i686/cmov/libpthread.so.0
#3  0xb73eb9f2 in pthread_mutex_lock ()
from /lib/i686/cmov/libpthread.so.0
#4  0xb7f480c6 in ev_document_doc_mutex_lock ()

at /build/buildd/evince-2.22.2/./libdocument/ev-document.c:84
#5  0x0806a08c in ev_pixbuf_cache_get_selection_surface (
pixbuf_cache=0x82fca00, page=0, scale=1.36380422,
region=0xbfffe9e8)

at /build/buildd/evince-2.22.2/./shell/ev-pixbuf-cache.c:1015
#6  0x0806f0c5 in merge_selection_region (view=0x82a4020, 
new_list=value optimized out)
at /build/buildd/evince-2.22.2/./shell/ev-view.c:5569
#7  0x08073d2b in compute_selections (view=0x82a4020, 
style=EV_SELECTION_STYLE_GLYPH, start=0x82a41e4,
stop=0x82a41cc)
at /build/buildd/evince-2.22.2/./shell/ev-view.c:5644
#8  0x08073ed6 in selection_update_idle_cb (view=0x82a4020)
at /build/buildd/evince-2.22.2/./shell/ev-view.c:2877
#9  0xb7435291 in g_idle_dispatch (source=0x83cd990,
callback=0xfe00, 
user_data=0x82a4020)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:4090
#10 0xb74371d8 in IA__g_main_context_dispatch
(context=0x80cbb18)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:20---Type
 return to continue, or q return to quit---
12
#11 0xb743a873 in g_main_context_iterate (context=0x80cbb18,
block=1, 
dispatch=1, self=0x80a4680)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2645
#12 0xb743ad92 in IA__g_main_loop_run (loop=0x80f24f0)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2853
#13 0xb7868c99 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x0808e3b0 in main (argc=1, argv=Cannot access memory at
address 0x84
)
at /build/buildd/evince-2.22.2/./shell/main.c:401

HTH this time.

Best regards





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Raphael Frey 
Le mardi 09 mars 2010 à 16:53 +0100, Josselin Mouette a écrit:
 OK, so it’s a livelock, not a crash.

Yes, exactly.

 Here can you try with thread apply all bt full ?

(gdb) thread apply all bt full

Thread 2 (Thread 0xb6741b90 (LWP 6532)):
#0  0xb6b6c9bd in ?? () from /usr/lib/libpixman-1.so.0
No symbol table info available.
#1  0xb5cf63c0 in ?? ()
No symbol table info available.
#2  0x in ?? ()
No symbol table info available.

Thread 1 (Thread 0xb698f700 (LWP 6529)):
#0  0xb7ef7424 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb72f1e67 in poll () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2  0xb73cd702 in g_main_context_iterate (context=0x80cbb18,
block=1, 
dispatch=1, self=0x80a4680)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2954
max_priority = 2147483647
timeout = 5000
some_ready = value optimized out
nfds = 8
allocated_nfds = value optimized out
---Type return to continue, or q return to quit---
fds = (GPollFD *) 0x8410400
__PRETTY_FUNCTION__ = g_main_context_iterate
#3  0xb73cdd92 in IA__g_main_loop_run (loop=0x80f24f0)

at 
/build/buildd-glib2.0_2.16.6-3-i386-fvJQDr/glib2.0-2.16.6/glib/gmain.c:2853
self = (GThread *) 0x80a4680
__PRETTY_FUNCTION__ = IA__g_main_loop_run
#4  0xb77fbc99 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#5  0x0808e3b0 in main (argc=1, argv=Cannot access memory at
address 0xc
)
at /build/buildd/evince-2.22.2/./shell/main.c:401
enable_metadata = 1
context = value optimized out
args = (GHashTable *) 0x80d3918
program = (GnomeProgram *) 0x80ad058






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-09 Thread Josselin Mouette 
Le mardi 09 mars 2010 à 17:08 +0100, Raphael Frey a écrit : 
 Thread 2 (Thread 0xb6741b90 (LWP 6532)):
 #0  0xb6b6c9bd in ?? () from /usr/lib/libpixman-1.so.0
 No symbol table info available.
 #1  0xb5cf63c0 in ?? ()
 No symbol table info available.
 #2  0x in ?? ()
 No symbol table info available.

We’re getting closer. The livelock is probably in this thread. Can you
install debugging symbols for libcairo and libpixman and try again?
Please do it several times in a row, to see if it’s always the same
codepath that’s involved.

This confirms my idea of a bug in the handling of Type 3 bitmap fonts,
since it’s probably for them that cairo calls libpixman.

Note that this could be simply caused by the rendering engine being so
slow that it just never ends in a reasonable timeframe.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-08 Thread Josselin Mouette 
Le vendredi 05 mars 2010 à 21:08 +0100, Raphael Frey a écrit : 
 While printing a PDF document created by pdftex that consists of only
 one single sentence, I just noticed 1. that Evince does not recognize
 the name of the typeface used in the document (it is the standard
 typeface used by Latex: CM-Roman) and 2. that the letters looks very
 ugly -- like pixelated. Probably these two curiosities are related to
 this bug.

This is because you don’t use the correct fonts in latex. You need to
pick up vector fonts, such as ae, lmodern or cm-super.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-08 Thread Raphael Frey 
Le lundi 08 mars 2010 à 14:13 +0100, Josselin Mouette a écrit:
 This is because you don’t use the correct fonts in latex. You need to
 pick up vector fonts, such as ae, lmodern or cm-super.

Oh, I see! So Computer Modern causes Evince to crash while trying to
print a PDF file containing Computer Modern glyphs? Or is Computer
Modern only the reason that the letters look like pixelated? Any why
does EPDF View does not have any problems printing the same PDF file?

Meilleures salutations

Raphael





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-08 Thread Josselin Mouette 
Le lundi 08 mars 2010 à 15:04 +0100, Raphael Frey a écrit : 
 Le lundi 08 mars 2010 à 14:13 +0100, Josselin Mouette a écrit:
  This is because you don’t use the correct fonts in latex. You need to
  pick up vector fonts, such as ae, lmodern or cm-super.
 
 Oh, I see! So Computer Modern causes Evince to crash while trying to
 print a PDF file containing Computer Modern glyphs? Or is Computer
 Modern only the reason that the letters look like pixelated? Any why
 does EPDF View does not have any problems printing the same PDF file?

Type 3 fonts generated from Computer Modern are the reason why your
fonts look pixelated, so this part is not a bug.

It can also be those fonts that trigger the evince crash, but without a
backtrace of the process going wild, there’s no way we can tell what’s
happening.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-08 Thread Raphael Frey 
Le lundi 08 mars 2010 à 15:45 +0100, Josselin Mouette a écrit : 
 It can also be those fonts that trigger the evince crash, but without a
 backtrace of the process going wild, there’s no way we can tell what’s
 happening.

Is is not possible tracing back the problem with the two files
(especially with the PDF file) I attached to this bug report?
Unfortunately I am no computer specialist and I do not know how to do
this. (When starting evince in a terminal and trying to print the
concerning file I does not get any information. I also have gdb and
evince-dbg installed but I do not know how to use them.) You could
also write me what I should do.

Best regards

Raphael





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-08 Thread Josselin Mouette 
Le lundi 08 mars 2010 à 16:51 +0100, Raphael Frey a écrit : 
 Le lundi 08 mars 2010 à 15:45 +0100, Josselin Mouette a écrit : 
  It can also be those fonts that trigger the evince crash, but without a
  backtrace of the process going wild, there’s no way we can tell what’s
  happening.
 
 Is is not possible tracing back the problem with the two files
 (especially with the PDF file) I attached to this bug report?

Developers mostly use unstable, and the version in unstable seems to
work fine.

For crashers, such as this one, we might backport the change to the
version in lenny, but only if we know what change for sure.

 Unfortunately I am no computer specialist and I do not know how to do
 this. (When starting evince in a terminal and trying to print the
 concerning file I does not get any information. I also have gdb and
 evince-dbg installed but I do not know how to use them.) You could
 also write me what I should do.

http://wiki.debian.org/HowToGetABacktrace

-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-05 Thread Raphael Frey 
Package: evince
Version: 2.22.2-4~lenny1
Severity: important


If a PDF document generated by Latex does not just consist of one or a 
few sentence(s), Evince is not able to print the document. Instead 
Evince uses 100 percent CPU and I have to kill the process because 
Evince does not respond anymore. This problem occurs with PDF files 
generated by pdftex but also with PDF files converted from DVI files 
(with dvipdf) that were created by latex. EPDF View (epdfview) 
does print the same document without any problems.

I will try to add the Latex and the PDF files to this bug report as an 
attachement.

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages evince depends on:
ii  gconf2  2.22.0-1 GNOME configuration database syste
ii  gnome-icon-theme2.22.0-1 GNOME Desktop icon theme
ii  libart-2.0-22.3.20-2 Library of functions for 2D graphi
ii  libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii  libbonobo2-02.22.0-1 Bonobo CORBA interfaces library
ii  libbonoboui2-0  2.22.0-1 The Bonobo UI library
ii  libc6   2.7-18lenny2 GNU C Library: Shared libraries
ii  libcairo2   1.6.4-7  The Cairo 2D vector graphics libra
ii  libdbus-1-3 1.2.1-5+lenny1   simple interprocess messaging syst
ii  libdbus-glib-1-20.76-1   simple interprocess messaging syst
ii  libdjvulibre21  3.5.20-8+lenny1  Runtime support for the DjVu image
ii  libgcc1 1:4.3.2-1.1  GCC support library
ii  libgconf2-4 2.22.0-1 GNOME configuration database syste
ii  libglade2-0 1:2.6.2-1library to load .glade files at ru
ii  libglib2.0-02.16.6-3 The GLib library of C routines
ii  libgnome-keyring0   2.22.3-2 GNOME keyring services library
ii  libgnome2-0 2.20.1.1-1   The GNOME 2 library - runtime file
ii  libgnomecanvas2-0   2.20.1.1-1   A powerful object-oriented display
ii  libgnomeui-02.20.1.1-2   The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0  1:2.22.0-5   GNOME Virtual File System (runtime
ii  libgtk2.0-0 2.12.12-1~lenny1 The GTK+ graphical user interface 
ii  libice6 2:1.0.4-1X11 Inter-Client Exchange library
ii  libjpeg62   6b-14The Independent JPEG Group's JPEG 
ii  libkpathsea42007.dfsg.2-4+lenny2 TeX Live: path search library for 
ii  libnautilus-extensi 2.20.0-7 libraries for nautilus components 
ii  liborbit2   1:2.14.13-0.1libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0   1.20.5-5 Layout and rendering of internatio
ii  libpoppler-glib30.8.7-3  PDF rendering library (GLib-based 
ii  libpopt01.14-4   lib for parsing cmdline parameters
ii  libsm6  2:1.0.3-2X11 Session Management library
ii  libspectre1 0.2.0.ds-1   Library for rendering Postscript d
ii  libstdc++6  4.3.2-1.1The GNU Standard C++ Library v3
ii  libtiff43.8.2-11.2   Tag Image File Format (TIFF) libra
ii  libx11-62:1.1.5-2X11 client-side library
ii  libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library
ii  shared-mime-info0.30-2   FreeDesktop.org shared MIME databa
ii  zlib1g  1:1.2.3.3.dfsg-12compression library - runtime

Versions of packages evince recommends:
ii  dbus-x11  1.2.1-5+lenny1 simple interprocess messaging syst

Versions of packages evince suggests:
pn  poppler-data  none (no description available)
pn  unrar none (no description available)

-- no debconf information


test.pdf
Description: Adobe PDF document
\documentclass[a4paper]{scrartcl}
\usepackage[utf8]{inputenc}

\usepackage[english]{babel}
\usepackage[T1]{fontenc}

\begin{document}

\section{Test document}

This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a test document.
This is a test document. This is a

Bug#572708: evince: Evince does not print pdf files generated with Latex

2010-03-05 Thread Raphael Frey 
While printing a PDF document created by pdftex that consists of only
one single sentence, I just noticed 1. that Evince does not recognize
the name of the typeface used in the document (it is the standard
typeface used by Latex: CM-Roman) and 2. that the letters looks very
ugly -- like pixelated. Probably these two curiosities are related to
this bug.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org