From owner-freebsd-gnome@FreeBSD.ORG Sat Nov 23 14:46:07 2013 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7AB80B8E for ; Sat, 23 Nov 2013 14:46:07 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 19E112B77 for ; Sat, 23 Nov 2013 14:46:06 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id z12so2244320wgg.15 for ; Sat, 23 Nov 2013 06:46:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=C/ttX3/d5t9ItnXwv0H/ljvOkD8gFFmFoJLaOTLGV1k=; b=EmoSSfsqtST+CYFzuotorU1RZ5p14Dbg3K9izynvBypfyyAo+S86bp7xCPAxd3SCSd 6TcarhR9oEwbS6ZDfp1E0htUH0yX+tC5taKrXrroEvfGeqHmDknzNMKIpyOGwJ6ul/lZ HFg3bOQzdFDmHcDaTpEX3OwdpPE2pMVIsIEHbg4hU3x8asnvVBeGaEGzB/4+jPr1/N9a 6qZ9nIs366odzCqZ0rBc97ILD82TQ8tissaEXPWWAAns+B7GjA131Hu1Yj7ddkGRQG7M 8Fe8JWZNtjDf0kCZxkXyQkv9qMIhv7pKEZJAEQqyV9Kd6DOM8/jL6iIBukv51oDNHqDn 1vSQ== X-Received: by 10.180.221.38 with SMTP id qb6mr6907048wic.8.1385217965574; Sat, 23 Nov 2013 06:46:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.240.198 with HTTP; Sat, 23 Nov 2013 06:45:35 -0800 (PST) In-Reply-To: References: <51BF6091.4040904@rainbow-runner.nl> From: Jia-Shiun Li Date: Sat, 23 Nov 2013 22:45:35 +0800 Message-ID: Subject: Re: Metacity fails after updates To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-gnome@FreeBSD.org" X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.16 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, 23 Nov 2013 14:46:07 -0000 On Wed, Aug 7, 2013 at 5:59 AM, Kevin Oberman wrote: > for the record, in case anyone hits it too and googles for solution. After seeing that you said it still happens after rebuilding all ports, it comes to me and I just deleted all suspicious conifig files & dirs, which begin with dot and I never altered in home dir. And then it works again. Apparently something cannot handle old configurations after being upgraded to new version, and need a fresh start. I am not interested in finding out what exactly it is as long as it works. But anyone curious is welcome to solve the mystery. Jia-Shiun.