From owner-freebsd-gnome@FreeBSD.ORG Sat Apr 9 16:30:45 2005 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDFE616A4CE for ; Sat, 9 Apr 2005 16:30:45 +0000 (GMT) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 591A943D1D for ; Sat, 9 Apr 2005 16:30:43 +0000 (GMT) (envelope-from freebsd@irotas.net) Received: from web3.messagingengine.com (web3.internal [10.202.2.212]) by frontend1.messagingengine.com (Postfix) with ESMTP id 56A26C71DD5 for ; Sat, 9 Apr 2005 12:30:42 -0400 (EDT) Received: by web3.messagingengine.com (Postfix, from userid 99) id 12DD8C8B; Sat, 9 Apr 2005 12:30:43 -0400 (EDT) Message-Id: <1113064243.1292.231492217@webmail.messagingengine.com> X-Sasl-Enc: tRz8KOKWe6BnRm0qWyHbKXRdEPeIksDUGu15pJybNPRG 1113064243 From: "Adam McLaurin" To: gnome@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.001; A1.64; B3.05; Q3.03) Date: Sat, 09 Apr 2005 12:30:43 -0400 Subject: Problems with x11-toolkits/gtk20 v2.6.5 -- Icons missing X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2005 16:30:45 -0000 Hi all, The new GTK+ seems to have partially broken displaying icon images in various applications (e.g., gaim, galeon, gedit). There is a new "feature" (that's only there to match to documentation) where GTK will show the "missing image" icon instead of a blank icon in the event that an icon image isn't found. However, for some (perhaps unrelated) reason, many icons that *do* exist are not being shown; the "missing image" icon is shown instead. This is not a problem specific to FreeBSD; one of the galeon dev's confirmed the bug on Linux. Anyhow, just wanted to give everyone a heads up before they go breaking things. If you've already upgraded, consider sysutils/portdowngrade to go back to v2.6.4_1 Thanks, Adam McLaurin