From owner-freebsd-gnome@FreeBSD.ORG Wed Jun 7 19:38:33 2006 Return-Path: X-Original-To: freebsd-gnome@freebsd.org 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 58042170737 for ; Wed, 7 Jun 2006 17:47:14 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2681943D4C for ; Wed, 7 Jun 2006 17:47:14 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Wed, 07 Jun 2006 10:47:06 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 91DC545043; Wed, 7 Jun 2006 10:47:06 -0700 (PDT) To: "Kiffin Gish" In-reply-to: Your message of "Wed, 07 Jun 2006 13:43:45 +0200." <000001c68a27$a226b080$2101a8c0@ZGISH> Date: Wed, 07 Jun 2006 10:47:06 -0700 From: "Kevin Oberman" Message-Id: <20060607174706.91DC545043@ptavv.es.net> Cc: freebsd-gnome@freebsd.org Subject: Re: Gnome 2.14 is as slow as molasses ... X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2006 19:38:37 -0000 > From: "Kiffin Gish" > Date: Wed, 7 Jun 2006 13:43:45 +0200 > Sender: owner-freebsd-gnome@freebsd.org > > Ever since I upgraded from Gnome 2.12 to 2.14 on top of FreeBSD 6.1, > I've > been disappointed with the VERY slow performance of the Gnome Desktop. > > Not only is it very sluggish in general, but most applications take > anywhere > from 30-60 secs to start. > > I thought that Gnome 2.14 was supposed to have all these exceptional > performance tweaks, but for some reason my system is doing the exact > opposite. > > Can anyone help me? This sounds like what I had after the upgrade. I re-installed all ports to fix it, but that is rather painful. If you look in the archives of this list, there is a posting with a shell script to rebuild the icon cache and that is reported to fix the problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634