From owner-freebsd-chromium@FreeBSD.ORG Mon Oct 6 21:23:08 2014 Return-Path: Delivered-To: freebsd-chromium@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 A1ED4233 for ; Mon, 6 Oct 2014 21:23:08 +0000 (UTC) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [IPv6:2001:bf0:c000::1:8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.in-berlin.de", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3220EC23 for ; Mon, 6 Oct 2014 21:23:03 +0000 (UTC) X-Envelope-From: h2+lists2011@fsfe.org X-Envelope-To: Received: from [192.168.3.80] (brln-4db92813.pool.mediaWays.net [77.185.40.19]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-4) with ESMTP id s96LMlF5027271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Mon, 6 Oct 2014 23:22:48 +0200 Message-ID: <54330827.2040805@fsfe.org> Date: Mon, 06 Oct 2014 23:22:47 +0200 From: Hannes MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Re: chromium-37.0.2062.124 window becomes black or transparent when maximized or un-maximized References: <54271A28.4020900@rawbw.com> <1768561.mPjJgo3sPr@quad> In-Reply-To: <1768561.mPjJgo3sPr@quad> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2014 21:23:08 -0000 On 28.09.2014 12:07, Maxim V FIlimonov wrote: > On Saturday 27 September 2014 13:12:24 Yuri wrote: >> Resizing the window by hand fixes the problem. >> In problematic state, it also gets the window frame which it is normally >> missing. >> This began happening with some recent update, never happened before. >> > > Got the same problem with 10.0-RELEASE. Began after a recent update. > >> 10.1-BETA2 >> Same here, nvidia blob, 10.0-RELEASE. Best, Hannes