From owner-freebsd-gnome@FreeBSD.ORG Tue Aug 6 21:59:24 2013 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 750314F5 for ; Tue, 6 Aug 2013 21:59:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4CA64278D for ; Tue, 6 Aug 2013 21:59:24 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lb1so1329828pab.12 for ; Tue, 06 Aug 2013 14:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=c85Sgs+WfXDmQs9yaaed8Nb/GyOd8KBQsQLxAGK/cTE=; b=oLv0xZag9axUFn4W4Nbba/qo8XSVW1YwYdxMptbgZR84UbK+w3++aL6nraGiq80TCY MCxclO5sxmTkILNnPlEYleuOCwV3jfidbE31O8jYr7CVhvebUsk9vmwj/F5X1Wg2Hpsg FUdAhHXWNkCJ79HdCb5lYk8QCuuvLm0Q3xCGhcup+iVOOK3dey4YoG0dUQwvh9ZZKuED rlFUVcnERUeUJuP7iw6P+bdT7fBUQYaH8kDUzvrp0++KfDR71tLpqG/ySGuweLAh98ZT 4jYkQ47+Tru+V7oMJTeT95Aw4BTDrrI1w/JYL0S4CgKKnt+UnGZeIU67FJtz1mASzEBv A41w== MIME-Version: 1.0 X-Received: by 10.68.179.36 with SMTP id dd4mr269260pbc.64.1375826363971; Tue, 06 Aug 2013 14:59:23 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Tue, 6 Aug 2013 14:59:23 -0700 (PDT) In-Reply-To: References: <51BF6091.4040904@rainbow-runner.nl> Date: Tue, 6 Aug 2013 14:59:23 -0700 X-Google-Sender-Auth: OshkYdllxBS7w-7tClrrN2sT_ME Message-ID: Subject: Re: Metacity fails after updates From: Kevin Oberman To: Koop Mast Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-gnome@FreeBSD.org" X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 21:59:24 -0000 On Sun, Jun 23, 2013 at 9:08 AM, Kevin Oberman wrote: > On Mon, Jun 17, 2013 at 12:16 PM, Koop Mast wrote: > >> On 14-6-2013 20:55, Kevin Oberman wrote: >> >>> I am no longer able to start Gnome on my desktop. I updated lot of the >>> ports while I was working remotely for a few months. When I got back, >>> metacity failed to start. My apps start and look OK, but with no window >>> manager, it's pretty useless. >>> >>> When it tries to start, metacity sends out the following: >>> metacity:ERROR:ui/ui.c:752:**meta-_ui_get_default_icon: assertion >>> failed: >>> (default_icon) >>> LibGTop-Server: pid 5978 received eof. >>> >>> This repeats every few seconds, ad infinitum. >>> >>> I have re-built metacity and all of its dependencies with no improvement >>> and i am baffled. >>> >>> I have a full Gnome installation running on FreeBSD 9.1-Stable (r249034). >>> All ports are up-to-date. Any ideas on where to look or what to kick? It >>> works fine on my other systems. >>> >> >> No clue about this, but the function in your quoted line suggests >> something involved icons? I currently don't have a gnome2 desktop setup to >> test. >> >> -Koop >> > > This one is getting frustrating. Re-built and re-installed ALL ports and > it is still happening! Maade one BIG error, though. I allowed the > portmaster run to use available packages. Re-building 1100+ ports from > source takes a long time, but I guess I'll start. :-( Should be done is two > or three days if I do the really drastic step of deleting ALL ports, > cleaning out /usr/local, and starting from scratch. > I'd just like to close this out. I tracked down the problem and it involved several twisty little passages making it unlikely that many people will hit it, though I know that some have, at least on Linux systems. The base issue is that the default icon set used when the gnome-settings-daemon does not get run. The error is actually pretty clear. The default theme (since one was not set) no longer has a default icon, so metacity dies. Prior to the round of gnome updates to gnome early this year, it did, but no longer. No idea why. But why is the gnome-settings-daemon not setting the theme? It's a race condition that was caused by my stunningly slow old graphics card. Quite simply, when the gnome-settings-daemon ran, the graphics system was still setting things up, so the daemon exited without setting a theme. In the past (when there was a default icon in the default theme, all I had to do to get things set correctly was to select System->Preferences->Appearance which would immediately fire up the setting-daemon and, like magic, everything looked fine. I found that, if I just killed all of the windows that block the top panel, I could still select System->Preferences->Appearance and metacity would start, but instead I did somehting better. I swapped in an old nVidia 9800 graphics card and now all is well. I'd love to know why no default_icon is available when the theme has not been set, as it would have made this easier to deal with, bugt at least it is now documented in case someone else hits this. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com