Bug#321484: cupsys: No debug information logged from gs-esp

2011-01-23 Thread Roger Leigh
On Sat, Jan 22, 2011 at 08:19:18PM -0600, Jonathan Nieder wrote: > tags 321484 + moreinfo help > quit > > Hi Roger et al, > > Roger Leigh wrote: > > Ambrose Li writes: > > >> After upgrading to the new gutenprint drivers, if a Windows print > >> job causes gs-esp to crash, /var/log/cups/errors

Bug#321484: cupsys: No debug information logged from gs-esp

2011-01-22 Thread Jonathan Nieder
tags 321484 + moreinfo help quit Hi Roger et al, Roger Leigh wrote: > Ambrose Li writes: >> After upgrading to the new gutenprint drivers, if a Windows print >> job causes gs-esp to crash, /var/log/cups/errors will not log >> anything useful from gs-esp, even if the debug level is set to >> deb

Bug#321484: cupsys: No debug information logged from gs-esp

2005-08-13 Thread Roger Leigh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reassign 321484 gs-esp thanks Ambrose Li <[EMAIL PROTECTED]> writes: > After upgrading to the new gutenprint drivers, if a Windows print > job causes gs-esp to crash, /var/log/cups/errors will not log > anything useful from gs-esp, even if the debug

Bug#321484: cupsys: No debug information logged from gs-esp

2005-08-05 Thread Ambrose Li
Package: cupsys Version: 1.1.23-11 Severity: important After upgrading to the new gutenprint drivers, if a Windows print job causes gs-esp to crash, /var/log/cups/errors will not log anything useful from gs-esp, even if the debug level is set to debug2. Running gs-esp manually with the crashed