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
