From owner-freebsd-xfce@freebsd.org Fri Jan 8 19:33:58 2021 Return-Path: Delivered-To: freebsd-xfce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 396F64D43B2 for ; Fri, 8 Jan 2021 19:33:58 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DCCvm0xMNz4t1s for ; Fri, 8 Jan 2021 19:33:56 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by mailman.nyi.freebsd.org (Postfix) id 202214D43AF; Fri, 8 Jan 2021 19:33:56 +0000 (UTC) Delivered-To: xfce@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1FE534D470A for ; Fri, 8 Jan 2021 19:33:56 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DCCvl6LLyz4tBr for ; Fri, 8 Jan 2021 19:33:55 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4DCCvk0kj7z6frf; Fri, 8 Jan 2021 20:33:54 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id 1-X5CxuVS2Cr; Fri, 8 Jan 2021 20:33:52 +0100 (CET) Subject: Re: XFCE upgraded to 4.16 To: Andrea Venturoli , xfce@freebsd.org References: <46a21428-a640-f895-0f3b-f44c09497bf5@madpilot.net> <747ecac6-6d60-6143-1ae1-47801299b59b@netfence.it> <1502a321-02c0-13e9-16b3-6f11da9de3af@madpilot.net> <47ede65d-817a-8d80-a582-660d43ac6ac3@andreaventuroli.it> <45c74d5a-909b-8905-6673-b340e1d976b4@netfence.it> <989cf919-245c-61f9-3091-b0933849093b@netfence.it> <2b8631d8-479b-15ee-1efd-cc4bffd14710@madpilot.net> <838b577f-eb40-2776-19d4-2fb5f71611b3@netfence.it> From: Guido Falsi Message-ID: <3655b4f7-0012-424b-7aa6-1d85fa2e9021@madpilot.net> Date: Fri, 8 Jan 2021 20:33:51 +0100 In-Reply-To: <838b577f-eb40-2776-19d4-2fb5f71611b3@netfence.it> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DCCvl6LLyz4tBr X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-xfce@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: XFCE for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2021 19:33:58 -0000 On 08/01/21 17:02, Andrea Venturoli wrote: > On 1/8/21 4:00 PM, Guido Falsi wrote: > >>> My home is on NFS4 in case it matters. >>> If you want other info or would like me to do some tests, just ask. >> >> It definitely matters. chflags is not supported by NFS. > > I thought so... > > > >> But I have no idea why and where chflags is performed. I suspect it's >> mv(1) doing that > > Does mv ever change flags? > There's no mention of it in the man page and I thought it didn't. > > In any case I'd be curious which flags the script would want to set. Not sure, maybe the archive you are using when extracted causes some flag to be activated and mv tries to replicate it. >> COuld you try creating a temporary directory in your home and pointing >> TMPDIR there? > > Sure. > Now it just dumps core without giving any message. > A subfolder briefly appears in TMPDIR, but then it's gone. > ~/.themes gets populated (as it did when TMPDIR was on local ZFS). > The theme is then selectable in "Window Manager" settings, but doesn't > appear in xfce4-appearance-settings' list. > > So, in the end, I think the messages about chflags were just warnings > and could be ignored; the problem lies elsewhere. > I agree. There is no way then to diagnose this any further without a backtrace. > > >> The script does require a change to accomodate for not having any of >> the variables it checks set, but you will need to define TMPDIR anyway >> in your setup most probably to have it working. > > I've got no problem with that, altough I suggest specifying this in > pkg-message. > I don't agree. Using a network file system for home directory if problematic at present. Most software uses sqlite databases for configurations which explicitly does not support networked file systems. and other problems could arise. Such a note should be attached to most software in the ports tree. Firefox and thunderbird (and most other browsers AFAIK) just to name two which use sqlite DBs heavily. My personal opinion is home directories on NFS made sense in the ninties, but now disks are big and inexpensive and using syncronization software (syncthing, unison) to replicate them locally makes much more sense and avoids many issue. -- Guido Falsi