From owner-freebsd-gnome@FreeBSD.ORG  Sat Sep 14 17:41:16 2013
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
Delivered-To: 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 ESMTP id 67B62244
 for <gnome@freebsd.org>; Sat, 14 Sep 2013 17:41:16 +0000 (UTC)
 (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 2C4A22176
 for <gnome@freebsd.org>; Sat, 14 Sep 2013 17:41:15 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id CF13A4275
 for <gnome@freebsd.org>; Sat, 14 Sep 2013 17:41:14 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id 6DC9136180; Sat, 14 Sep 2013 19:40:32 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: gnome@freebsd.org
Subject: gvfsd-trash considered harmful
Date: Sat, 14 Sep 2013 19:40:31 +0200
Message-ID: <86wqmj1euo.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
 <freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-gnome>,
 <mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
 <mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2013 17:41:16 -0000

Lately, I've been having no end of trouble with gvfsd-trash
(gvfs-1.12.3_1 on 9.2-RC).  It automatically latches onto any new
mounted filesystem and prevents unmounting, either permanently or, in
the case of various nullfs mounts poudriere creates, just long enough
for poudriere to fail and hose my package repo.  In addition, starting
poudriere on 9.2-RC while gvfsd-trash is running it triggers a kernel
panic - 100% reproducible, as soon as poudriere starts the builder
jails.

Google shows many similar complaints about gvfsd-trash from other OSes,
but no solutions other than 'pkill -STOP gvfsd-trash'.  Killing it
outright won't work, since gnome-session will just start a new instance.

What can we do about this?

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no