From owner-freebsd-ports@FreeBSD.ORG Sun Nov 7 20:47:34 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06CCA10656C5 for ; Sun, 7 Nov 2010 20:47:34 +0000 (UTC) (envelope-from jason@naughton.ca) Received: from trooper.naughton.ca (naughton.ca [206.248.137.184]) by mx1.freebsd.org (Postfix) with ESMTP id 9B2978FC25 for ; Sun, 7 Nov 2010 20:47:33 +0000 (UTC) Received: from webmail.jnaughton.com (localhost [127.0.0.1]) by trooper.naughton.ca (8.14.4/8.14.4) with ESMTP id oA7Kle41042979; Sun, 7 Nov 2010 15:47:40 -0500 (EST) (envelope-from jason@naughton.ca) Received: from 192.168.1.2 (SquirrelMail authenticated user jnaughto) by webmail.jnaughton.com with HTTP; Sun, 7 Nov 2010 15:47:41 -0500 Message-ID: <9b2674dec7bc07ff484a306046fe3a77.squirrel@webmail.jnaughton.com> In-Reply-To: References: Date: Sun, 7 Nov 2010 15:47:41 -0500 From: "Jason Naughton" To: "Warren Block" User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: ports@freebsd.org Subject: Re: sane-backend 1.0.21 broke on 8.0? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2010 20:47:34 -0000 Hi Warren, > One last thing, then I'm out of tricks. After the change to FreeBSD 8, > did you rebuild all, yes all, of your ports? I did a complete re-install. I didn't upgrade. So when I installed Freebsd 8 the ports were built with that version of the OS. > Also (two! two last tricks!) you should not have the libusb port > installed, since libusb is now part of the OS. # pkg_info |grep libusb # Not installed. I've managed to solve the problem but at the same time definitely find a bug with the sane-backend 1.0.21. I wanted to isolate where the seg fault was occurring as it was not occurring when I moved everything out of /usr/local/etc/sane.d and just left epson.conf which was indicated from the sane support page that my scanner was to be apart of. With only epson.conf inside of the /usr/local/etc/sane.d folder I had the following results: # sane-find-scanner -q found USB scanner (vendor=0x04b8 [EPSON], product=0x011e [EPSON Scanner]) at libusb:/dev/usb:/dev/ugen3.2 # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). I could do this as root or as user. Now if I put everything back into /usr/local/etc/sane.d I would get a seg fault. So I did the following: # cd /usr/local/etc/sane.d # mkdir ../orig # mv * ../orig # mv ../orig/epson.conf . # mv ../orig/epson2.conf . # mv ../orig/dll* . So now: # ls /usr/local/etc/sane.d dll.conf dll.d epson.conf epson2.conf # scanimage -L device `epson2:libusb:/dev/usb:/dev/ugen3.2' is a Epson GT-8300 flatbed scanner Now both xsane and scanimage work fine without a seg fault. Odd that the same scanner that was under epson is now seen as an epson2. So using trial a process of elimination I moved one file at a time back into the sane.d folder. What I found was when the microtek2.conf file was added to the sane.d folder the following would occur: # scanimage -L zsh: segmentation fault scanimage -L My quick and simple solution would be to simply delete the microteck2.conf file and I can now use my scanner. Yet what is in this file that would make scanimage seg fault: # grep -v "#" microtek2.conf option dump 1 option no-backtrack-option on option lightlid-35 on option toggle-lamp on option lineart-autoadjust on option backend-calibration on scsi * * Scanner One of the above lines is causing scanimage to segfault. As I move this file outside of the sane.d folder I can now: # scanimage -L device `epson2:libusb:/dev/usb:/dev/ugen3.2' is a Epson GT-8300 flatbed scanner and everything works again... Just to recap my scanner is an EPSON Perfection 1660 Photo usb scanner which is supposedly completely compatible with sane-backends. Cheers Jason Naughton, P.Eng, M.E.Sc, Professional Contractor, JMN Planning, Pickering, Ontario, Office: (416)-509-4886 Fax: (905)-831-3810