From owner-freebsd-questions@FreeBSD.ORG Sun Sep 11 12:07:38 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83D1B106564A for ; Sun, 11 Sep 2011 12:07:38 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 324DD8FC08 for ; Sun, 11 Sep 2011 12:07:38 +0000 (UTC) Received: from r56.edvax.de (port-92-195-14-151.dynamic.qsc.de [92.195.14.151]) by mx02.qsc.de (Postfix) with ESMTP id 09BA61D8ED for ; Sun, 11 Sep 2011 14:07:30 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id p8BC7UqK004193 for ; Sun, 11 Sep 2011 14:07:30 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 11 Sep 2011 14:07:30 +0200 From: Polytropon To: FreeBSD Message-Id: <20110911140730.4a86ae49.freebsd@edvax.de> In-Reply-To: <20110911072140.17d8ec2d@scorpio> References: <4E6A3504.6020002@eskk.nu> <20110909191726.4af3e660@debiand1.localdom.ain> <4E6A6152.5070703@eskk.nu> <20110909222951.45a29861.freebsd@edvax.de> <4E6B324F.8030700@eskk.nu> <20110910082446.0e8280eb@scorpio> <4E6C56D5.4030600@eskk.nu> <20110911085342.3c820f79.freebsd@edvax.de> <20110911072140.17d8ec2d@scorpio> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Printing from Firefox broken after update. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 12:07:38 -0000 On Sun, 11 Sep 2011 07:21:40 -0400, Jerry wrote: > On Sun, 11 Sep 2011 08:53:42 +0200 > Polytropon articulated: > > > Do you get better results when printing to a file (PS) and > > then sending it directly to the printer (via lpr)? Maybe > > this problem is comparable to my Opera printing problem > > (where I could identify Opera being the source of invalid > > PS data). > > Wow, what a waste of time that is. I just use MS Windows when I have to > print and avoid all that rigmarole. Fully agree. I just use a PS printer (networked) and can print directly from any system and any application, no need for any rigmaroles. :-) > Firefox use to work correctly; however, it no longer does. At first I > thought it was a localized phenomena; however, after checking on > several different forums I have concluded that it is far more wide > spread than I had originally thought. This seems to be typical for development project that focus on "development at any cost", dropping functionality or accidentally losing some. Sadly such behaviour is not limited to Firefox, but also to other programs many users consider essential. > There have been reports filed against this behavior. If and when they > are acted upon is anyone's guess. In the mean time, I just use what is > convenient and works reliably without adding an undo burden upon > myself. Well, I always have problems understanding why functionality that has been working perfectly for years stops working, especially when changes that programmers made are in _no_ obvious relation to that functionality... This means: Don't update your software if you want to keep it working. And use a real printer that JUST WORKS. :-) > Continual use of broken software effectively makes the end > user and enabler; something I have no desire to invest my time in. Also agree. Firefox is not the only web browser available and usable (although it might be the world's favourite one). And finally, it wouldn't be the first product that users abandon due to such lack of... quality? Is this correct? I'd say yes. Coming back on topic: It would be useful to identify Firefox as initiator of the printing problems (if that isn't clear yet), just to make sure that it isn't CUPS (which often is used for its printer filters when using "winprinters"). That's why involving the "Print to file" step sounds useful here. In case Firefox produces defective Postscript, that would indicate that it's really a Firefox thing that should be fixed as soon as possible. This step of diagnostics should help to be sure _what_ to fix. By the way, I'm still using Firefox 6.0.1 here and don't have printing problems, even using with CUPS 1.4.6. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...