From owner-freebsd-ports@FreeBSD.ORG Thu May 24 11:53:48 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02A96106564A for ; Thu, 24 May 2012 11:53:48 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep16.mx.upcmail.net (fep16.mx.upcmail.net [62.179.121.36]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0A98FC19 for ; Thu, 24 May 2012 11:53:47 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep16-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20120524115345.DJSS15021.viefep16-int.chello.at@edge04.upcmail.net>; Thu, 24 May 2012 13:53:45 +0200 Received: from [127.0.0.1] ([178.84.137.57]) by edge04.upcmail.net with edge id Dntk1j01L1EUzH604ntk2x; Thu, 24 May 2012 13:53:45 +0200 X-SourceIP: 178.84.137.57 Message-ID: <4FBE2145.4060505@rainbow-runner.nl> Date: Thu, 24 May 2012 13:53:41 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Jeremy Messenger References: <20120522232408.31483b54.goksin.akdeniz@gmail.com> <4FBC2E67.5050403@rainbow-runner.nl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 120524-0, 24-05-2012), Outbound message X-Antivirus-Status: Clean Cc: Warren Block , ports@freebsd.org, =?UTF-8?B?R8O2a8WfaW4gQWtkZW5peg==?= Subject: Re: xorg problems 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: Thu, 24 May 2012 11:53:48 -0000 On 23-5-2012 3:46, Jeremy Messenger wrote: > On Tue, May 22, 2012 at 7:25 PM, Koop Mast wrote: >> On 22-5-2012 23:48, Warren Block wrote: >>> On Tue, 22 May 2012, Gök?in Akdeniz wrote: >>> >>>> If you downgrade "cairo port" it will be ok. If you update ports tree >>>> with csup try portdowngrade. If not try to get the old version of ciaro >>>> port as package, remove the new one and install the old one, then do >>>> nnot upgrade the cairo port. That will keep things working untill a bug >>>> fix is available. >>> >>> Yes, so far so good. Downgraded to cairo-1.10.2_3,1 and have not seen the >>> garbling problem again. >> >> Just picking the last message in the thread. >> >> I found a Xorg bug report about the cairo 1.12 corruption. I will >> investigate this more closely tomorrow since I about to fall asleep. It >> seems there is a issue in EXA. People with cairo 1.12 should try to disable >> that and see if that helps. I think that can be done by putting the line >> below in your xorg.conf. >> >> Option "NoAccel" "true" > Yes, it's what I have collected from in Google search as well. > > http://lists.x.org/archives/xorg-announce/2012-May/001943.html > -------------------- > * Pixmap (and bo leak) during fallback glyph composition > > * Remove broken acceleration for rendering glyphs directly upon the > destination pixmap, exposed by cairo-1.12.0 (and coincidentally fix > another Pixmap leak upon fallback handling). > -------------------- > > Another for xorg-server 1.12.x: > > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/EXA_Fall_back_earlier_and_more_thoroughly_from_exaGlyphsV2.diff?h=packages/xorg-server Can people try this and see if it fixes the problems? http://people.freebsd.org/~kwm/patch-cairo Just put it in x11-servers/xorg-server/files/ and rebuild xorg-server. Works for both 1.7 and 1.10. -Koop > I can't reproduce any of bug here with nvidia-driver as I have been > running for three or four days by now with GNOME 2, Firefox 12 and > etc. > > Cheers, > Mezz > > >> -Koop >