From owner-freebsd-questions@FreeBSD.ORG Tue Jan 3 02:08:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D480D16A41F for ; Tue, 3 Jan 2006 02:08:19 +0000 (GMT) (envelope-from fj@panix.com) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECAFC43D5E for ; Tue, 3 Jan 2006 02:08:18 +0000 (GMT) (envelope-from fj@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail3.panix.com (Postfix) with ESMTP id 42A4913A9F1 for ; Mon, 2 Jan 2006 21:08:18 -0500 (EST) Received: (from fj@localhost) by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k0328I215940 for freebsd-questions@freebsd.org; Mon, 2 Jan 2006 21:08:18 -0500 (EST) Date: Mon, 2 Jan 2006 21:08:18 -0500 From: Joe Altman To: freebsd-questions@freebsd.org Message-ID: <20060103020818.GA6411@panix.com> Mail-Followup-To: Joe Altman , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.10i Subject: Scanning: Sane-Backends: from 1.0.16 to 1.0.17 or Xsane: 0.97 to 0.98 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 02:08:20 -0000 One of the two recent portupgrades seems to have broken scanning for an HP 2200C using the Plustek backend. One of the issues I face is that I don't recall if the upgrade for Xsane occurred before or after I last used the scanner successfully. 0.98a was released twice, in late November; followed closely by 0.98b in early December. However: prior to the port upgrade for the Plustek backend (this was released/ported on or about 2005-12-26th) XSane and the appropriate Sane backend worked fine. After the backend upgrade, the best behavior I can obtain from Xsane is a core dump. Before I submit a bug report to the Sane maintainer or the Xsane maintainer, I thought I'd ask if anyone else is seeing this or similar behavior: Xsane will just appear to hang, as will xscanimage. The light for the scanner comes on, and sometimes the scan will begin; if it does, the light stays on after the core dump and does not return to its bay. Both sane-find-scanner and scanimage -L work, but Xsane sometimes eventually dumps core and xscanimage doesn't do much of anything. Thanks in advance, and best regards... Joe