Bug#609851: summary

Julien Cristau wrote: That seems fixed (at least to some extent) in 4.2.2-2: if [ -z $current_hostname ] || [ $current_hostname = '(none)' ] || [ $current_hostname = 'localhost' ] || [ $current_hostname = $old_host_name ]; then This looks good and

Bug#658264: closed by Michael Gilbert michael.s.gilb...@gmail.com (Re: Bug#658264: xpdf totally unusable due to memory corruption in globalParams class (namespace conflict with libpoppler))

problematic: globalParams = new GlobalParams(cfgFileName); I have now invested \approx 6h in this report and am 100% sure it is a grave bug. Please consider re-opening. Thanks, Wolfram Gloger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble

Bug#658264: xpdf totally unusable due to memory corruption in globalParams class (namespace conflict with libpoppler)

Package: xpdf Version: 3.02-12+squeeze1 Severity: grave After upgrading to squeeze, xpdf crashes on startup, even without any input file: % /usr/bin/xpdf any.pdf xpdf: pthread_mutex_lock.c:62: __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed. Abgebrochen (core dumped) I also

Bug#373581: freetype security update causes divide by zero (w/FIX)

Package: libfreetype6 Version: 2.1.7-2.5 Severity: grave My xserver crashes with a FPE after upgrading freetype. Cause: The very last security-releated path in freetype_2.1.7-2.5 has this patch: --- freetype-2.1.7.orig/src/raster/ftrend1.c2003-06-18 08:59:56.0 +0200 +++

Bug#373581: Acknowledgement (freetype security update causes divide by zero (w/FIX))

Actually, here is an even more correct patch which applies on top of the current ones in debian/patches. Regards, Wolfram. --- freetype-2.1.7/src/raster/ftrend1.c~Wed Jun 14 16:03:26 2006 +++ freetype-2.1.7/src/raster/ftrend1.c Wed Jun 14 16:15:41 2006 @@ -176,8 +176,11 @@