On Thu, Mar 13, 2008 at 6:36 AM, Roger Leigh <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 12, 2008 at 11:06:58AM +1100, Bernard Gray wrote: > > It's been almost 4 weeks with no response from the printer people on > > this issue, should we just wait? or can anyone recommend a more > > productive avenue for resolution? > > Sorry for delay (to both you and Klaus). I've been away in the US and > only just got back.
Hi Roger, no probs (and I apologise for my delayed response too :/ ) > Firstly, about the printer models. I don't own either a Stylus Photo > 915, nor an R300, which means I can't personally do much about the > problems. If you subscribe to the gimp-print-devel mailing list at > sourceforge.net > (https://lists.sourceforge.net/lists/listinfo/gimp-print-devel), you > will be able to ask the developers directly--it's likely this will be > rather quicker than for me acting as a go-between). However, see below > before you do this: > > All of the Epson printers which gimp-print supported should continue to > work in gutenprint. So, the developers will be interested in fixing any > problems with particular printers which don't work. > > Klaus: you will need to set LogLevel to debug in cupsd.conf, restart > cups and then look at the log file after printing a file. It should > show you what's going wrong. Just send the whole log to this bug > address if you're unsure. > > Bernard: the same applies here, but from your mail, the device URI: > > Device URI: epson:/dev/usb/lp0 > > looks wrong. The "epson" backend should be replaced by the "usb" > backend. You can do this by editing /etc/cups/printers.conf and > restarting cups, or by modifying the printer in the web interface. I emailed the gimp-print-devel list with some updated info (included testing on an Epson Stylus Photo RX590 as well) - but I think they are waiting on a response from you? http://sourceforge.net/mailarchive/forum.php?thread_name=c058e98e0803242056m1775bbc2jd0249198c07d8141%40mail.gmail.com&forum_name=gimp-print-devel Also, I'll prepare a debug level log for you at some stage today or tomorrow and post it. I didn't have any luck finding anything pertinent when I looked. Regards, Bernie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
