Date: Sat, 20 Jan 2018 17:32:07 +0100 From: Ralf Mardorf <ralf.mardorf@rocketmail.com> To: freebsd-questions@freebsd.org Subject: Re: xfce4 reverts to mirrored dislays Message-ID: <20180120173207.3fb817f2@archlinux.localdomain> In-Reply-To: <20180120170942.532834dd.freebsd@edvax.de> References: <c89fe0ea-d072-2a4b-ad02-74041e3bd181@nethead.se> <20180120125636.6ad88128.freebsd@edvax.de> <20180120134001.65ddb697@archlinux.localdomain> <20180120141518.7a85ed99@planb.netng.org> <2c24a50e-c7d1-0841-bee6-9f015d48a927@nethead.se> <20180120170942.532834dd.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Jan 2018 17:09:42 +0100, Polytropon wrote: >As root, chown the file to root:wheel, then make it r--/r--/r--, >and finally use chflags to apply the noschg flag. This should >make the file immutable to any write attempts. There might be a file in some temporarily location more important, assuming that powering down the monitor happens during running user session. Btw. this kind of opacity of desktop environments, especially such as Xfce, that are migrating from GTK2 to GTK3, is a good reason to migrate to a window manager without a desktop environment. Actually making a config file a desktop environment wants to access immutable, could cause issue and might not help at all, since the relevant file anyway could be in a temporarily cache. Does Xfce on FreeBSD and/or Linux already suffer from dconf(/gsettings)/dbus and Co. issues? I decided to migrate to openbox, when Xfce didn't suffer from those culprits(/crap).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180120173207.3fb817f2>