From owner-freebsd-ports@FreeBSD.ORG Fri Dec 25 15:40:18 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 297F41065670; Fri, 25 Dec 2009 15:40:18 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2FCF68FC1A; Fri, 25 Dec 2009 15:40:16 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA13540; Fri, 25 Dec 2009 17:40:14 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B34DCDE.2080607@icyb.net.ua> Date: Fri, 25 Dec 2009 17:40:14 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: FreeBSD Ports X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Dirk Meyer , Michael Johnson Subject: cups issue after gutenprint-cups update 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: Fri, 25 Dec 2009 15:40:18 -0000 I recently upgraded gutenprint* ports, including gutenprint-cups-5.2.4, and after that I couldn't print to my CUPS/SMB printer any more. In cups logs I found that it tried to execute /usr/local/libexec/cups/filter/rastertogutenprint.5.1, but it was replaced by /usr/local/libexec/cups/filter/rastertogutenprint.5.2. I also noticed that the following files had references to rastertogutenprint.5.1: etc/cups/printers.conf etc/cups/printers.conf.O etc/cups/ppd/printer.ppd I did some googling and performed the following steps: $ /usr/local/etc/rc.d/cupsd stop [edit printers.conf and printers.conf.O to replace 5.1 with 5.2] $ cups-genppdupdate $ /usr/local/etc/rc.d/cupsd start That fixed the problem for me. So I decided to share this information. If this issue was not caused by my local misconfiguration, and other users might also run into it, then it might be a good idea to mention this in UPDATING. -- Andriy Gapon