From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 68949138A1A for ; Mon, 19 Jan 2015 22:19:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 61CDDE09F0; Mon, 19 Jan 2015 22:19:41 +0000 (UTC) Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [69.252.207.38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C18BCE09DC for ; Mon, 19 Jan 2015 22:19:40 +0000 (UTC) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-06v.sys.comcast.net with comcast id hyJ61p0042GyhjZ01yKgcJ; Mon, 19 Jan 2015 22:19:40 +0000 Received: from ajax ([73.191.154.251]) by resomta-ch2-09v.sys.comcast.net with comcast id hyKf1p00S5Rihs901yKfwW; Mon, 19 Jan 2015 22:19:40 +0000 Date: Mon, 19 Jan 2015 17:19:34 -0500 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Nvidia or Xorg Problem with GLX Message-Id: <20150119171934.1d509df7c2899f9af29d7e26@comcast.net> In-Reply-To: References: <20150119135640.fdd9ba2ceb30c931034454d8@comcast.net> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; x86_64-unknown-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1421705980; bh=56jZHhKSTePZL0yqommUT2IDlm67QdZSSROoqbiMIZc=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=PtRtpsalVuznHComp0CkN1q0gFIeZFZmdGWqICUSQDKbqKy6nBHEiDx/eqND94UVX bOKixPPURuEfbU3z5qHt0krwAORMq1Ikx8sYH/8oANOioijUxwzeWUJGpRGaLL12aJ qJb7J9h7jC+/L+kN43vfuq9LtTYbUEJD+qdUTdxLq8PjSUxrQ+6yqnQC23PyTk/jzh LjVH9fTeXUZGmk1Q9utH4sOi5A3tbRlE1eWbdkQArQDSAbPf4V1MCHT4noamzEjIxm 41ZQfUo65SF4sKF2gjUW3bIYUPXyGBzNj2+t1JPYK7ReL6GEX0ku/Na8O6hdPc8Y+l A6d17M0QoKn6w== X-Archives-Salt: 25b3fd1e-1b37-4385-bbb4-f5f717e93166 X-Archives-Hash: 0a9343c86e057470b24c10e6109d8710 On Mon, 19 Jan 2015 12:37:49 -0700 Brandon Vincent wrote: > > Looks like a known bug [1]. > A few of the reports on this issue that I've found date back to 2010 and even earlier: https://forums.geforce.com/default/topic/369385/geforce-drivers/failed-to-initialize-the-glx-module-can-39-t-init-glx-driver-on-fedoracore-6/ I would doubt that this problem is really new, but it has never affected me before. Frank Peters