From owner-freebsd-current@FreeBSD.ORG Wed Feb 11 11:29:42 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A504D3C for ; Wed, 11 Feb 2015 11:29:42 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id D0D4DC3 for ; Wed, 11 Feb 2015 11:29:41 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.60.3]) by phk.freebsd.dk (Postfix) with ESMTP id A49AD3B8A2; Wed, 11 Feb 2015 11:29:33 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id t1BBTWpk020908; Wed, 11 Feb 2015 11:29:32 GMT (envelope-from phk@phk.freebsd.dk) To: Beeblebrox Subject: Re: Some unresolved but important X.org problems In-reply-to: <20150211132039.42665673@rsbsd.rsb> From: "Poul-Henning Kamp" References: <20150211132039.42665673@rsbsd.rsb> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20906.1423654172.1@critter.freebsd.dk> Date: Wed, 11 Feb 2015 11:29:32 +0000 Message-ID: <20907.1423654172@critter.freebsd.dk> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 11:29:42 -0000 -------- In message <20150211132039.42665673@rsbsd.rsb>, Beeblebrox writes: >PROBLEMS: >1. PDF viewers fail to display pdf/ps files correctly. Many files >get displayed as blank pages, and I can only get the pdf to display >after closing/re-opening the file several times, or by repeatedly >scrolling up/down past the seemingly blank page. Pages with an image >have more problems than pages with text-only. evince crashes for me about 1 out of two but files with purely images seems to fare slightly better than others. people have pointed fingers in the general direction of gtk/cairo >2. With the exception of Opera (which is out-dated), all remaining >Browsers fail to display most web pages in a sane manner (Firefox, >Seamonkey, Epiphany, Midori). Chrome is the worst because even with >just a blank page it flickers, goes completely white, comes back >as a partial image and sometimes locks X for 1/2 second or so. I'm running firefox 35 on current and that seems to be working OK. My guess is that your problems are specific to your graphics hardware, and therefore it could be valuable if you could try, just as an experiment, to move your diskdrive to different hardware, just to see if the problems comes along for the ride. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.