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
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
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
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
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
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
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
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
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 ?? ()
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.
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:
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
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
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
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
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
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.
17 matches
Mail list logo
