On Thu, Mar 05, 2009 at 12:10:05PM -0600, Chris Lawrence wrote: > severity 518362 important > thanks > > Note that this bug does not affect all usage of the package, and thus > is not "grave." > > You can turn debugging on in CUPS with: > > LogLevel debug > > in /etc/cups/cupsd.conf. >
Hello Chris, attached you will find some debugging output from error_log for the test page. > Please also see if foomatic-rip segfaulted by checking /var/log/syslog > or /var/log/kern.log. > Nothing in there with signal and ... > I think this is related to #518117 (segfault in foomatic-rip). My > strong suspicion is that you need to delete the printer from the CUPS > web interface (or your favorite GUI, like foomatic-gui) and reinstall > it. > > Unfortunately without a backtrace of the segfault there isn't much I > can figure out. > Is it a segfault, if there is nothing respectively in syslog or kern.log? Dont know if it must end up in there ... Regards Thomas
161_error_log.gz
Description: Binary data
