From owner-freebsd-questions@freebsd.org Tue Dec 4 17:36:32 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4BD11313B42 for ; Tue, 4 Dec 2018 17:36:32 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25DCF844EC for ; Tue, 4 Dec 2018 17:36:30 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.193.252.129]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPA (Nemesis) id 1MtwlO-1hM3j80UUG-00uFTa; Tue, 04 Dec 2018 18:36:22 +0100 Date: Tue, 4 Dec 2018 18:36:21 +0100 From: Polytropon To: B J Cc: freebsd-questions Subject: Re: Fresh Installation Of FreeBSD 11.2--Mate Not Working Properly Message-Id: <20181204183621.9358c17e.freebsd@edvax.de> In-Reply-To: References: <20181202231414.bc873ae8.freebsd@edvax.de> <3b1f0a32-175e-2535-ce70-ac8935cf85eb@yandex.com> <20181203184153.b37810d9.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:HDcqGGJR9gEVwUmeBbgJda7tzybFp3in4oR3BHKzyv3CtJHXfvK uSarAfqhwFvWsspktD6Hsx5tI9Kh7oH6opr2QpasU4+h0SCC6vIdLaWRUkpe6Is17Iyz5RU YZGJfjck/acOIN3xzqHe+H+EBRoxt7jj4EUSeTQR7pAkK/0CP15krkDwU6uYmzG8NDgR+cD 7F8GCmdc7z8J7/afTaLTg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:dKKpUl9AiOE=:v/lOCw88a1Aqs686dPhu78 w2kRH4RRTcpPCDzh/1MHSZ58T658PrzL5Loj47S8QmvGm81C/nTZ3ThLAeJ6hRR0tsetOvwKp UG0FVMVqtWi94dKaPoC57rlZYm0R+bk4+Ie2+XmSPScW4VS8/bVsTMiJj1VrPFYSF29ESRFFn 8CuOYgv+nyKJ/14coKMOxnoRFxSPId6YjwQqYq2FPBNdv6Vu8HlsUfesPCm/1kwGJ9PH2DK+Z zkl1fuV1+Dwpnn7d2zIn5iPIMB+hQQnBfWqJKLdW1l5VKjPNbEnAslzz0Kk/SnKrjxkxySoJe QCSgdJisKDzxl9CrY37BsC3PcPIKmU4YPP2uM4hgTB0xQ5IR5RN2IK0XKB88UgXI7xViAJguC xwYifdCdMaGA1lS8q4CLxUvQQPWZS082EgxJn8RE5zItkmIWDFpoLhs7jc0o7Ur2WARIgiFQt azDTCX8SnR0SVJIGBdzR5PMLDhFxK1A3uhLQSg0+QRO6H+VKolSyi888tUlDCnUWIvQhlpdAd DFqLaUfD+4J88tHJktZadVOsObtoMSi++P6GK1LEkDdEmK6elfSx37jAmMUCBiof7Zhknuqc+ Kt3K9wdXFlVy9lvLpe3/rQJyo7V6Ke5OkLfsu2WsjQtiJYpVAi91sEHDBgzxm/E/UEt8YEI7k 8Skyg3iFJxVyZU5xYyQusnmj338Cdr+wUEg/HuDulFzeUYNvKUGYyJc2d+MZpyAjwU/+Y7g+9 WrN2t5neDwTA9p89ivJxUq6pZkHQ9fLjp61d39H63aPEtD4HKRo1IofmBxM= X-Rspamd-Queue-Id: 25DCF844EC X-Spamd-Result: default: False [-0.44 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mx00.schlund.de,mx01.schlund.de]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.80)[-0.800,0]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[129.252.193.92.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; IP_SCORE(-0.10)[ipnet: 212.227.0.0/16(-0.51), asn: 8560(0.01), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.971,0]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.95)[-0.952,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[10.17.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2018 17:36:32 -0000 On Tue, 4 Dec 2018 02:25:47 +0000, B J wrote: > > > > For better diagnostics, use the following entry in ~/.xinitrc: > > > > exec xterm > > > > Then use "startx", and run "mate-session" from within the > > terminal. You should be able to see _why_ MATE isn't starting > > properly, while Xfce does. > > > > AS I said in a previous message, the age of the system probably > > is not the reason for MATE not working. Maybe something has > > changed in its configuration, so maybe renaming MATE's settings > > subtree to .old and starting with no configuration at all will > > work. Incompatibility of older settings sometimes leads to > > software not starting after an upgrade (e. g., CUPS). So this > > is something you could try. > > > > I re-installed Mate and modified the installation as you suggested. > After running "startx", followed by "mate-session" in the terminal, I > got a number of messages, including the following: > > mate-session[844]: WARNING: Unable to determine session: Unable to > lookup session information for process '844' > mate-session[844]: WARNING: Unable to find provider ' ' of required > component 'dock' > ** (mate-settings-daemon:862): WARNING**: : There was a > problem when setting QT_AUTO_SCREEN_SCALE_FACTOR=0: > GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv > interface is only available during the Initialization phase > ** (mate-settings-daemon:862): WARNING**: : There was a > problem when setting QT_SCALE_FACTOR=0: > GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv > interface is only available during the Initialization phase > This libgtop was compiled on FreeBSD 11.2-RELEASE-p5 amd64 > If you see strange problems caused by it, you should recompile libgtop > and dependent applications. > [15433888288,000,xklavier.c:xkl_engine_start_listen/] The backend > does not require manual layout management - but it is provided by the > application > Initializing caja-image-convertor extension > Initializing caja-open-terminal extension > Initializing caja-xattr-tags extension > > ** Message:: Initializing gksu extension.... > > (polkit-mate-authentication-agent-1:883): polkit-mate-1-WARNING**: > : Unable to determine the session we are in: > GDBus.Error:org.freedesktop.ConsoleKit.Manager.Error.General: Unable > to lookup session information for process '883' Isn't that scary? All those messages are usually hidden. You can even get more shocked when you build from source, then you'll see tons of warnings... terrible attitude... Part of the error messages aren't even helpful, like the inability to "find provider ' '" - that's really great! It seems the times of usable and bloat-reduced software is long gone... :-/ > Then there were some messages regarding the location of > GNOME_KEYRING_CONTROL and SSH_AUTH_SOCK, followed by: > > Connection failure: Connection refused > pa_context_connect() failed: Connection refused Check in /etc/rc.conf for the presence of the following settings, which I found from a reference MATE system (which uses slim instead of gdm, as Gnome was removed due to the Gnome 2 -> Gnome 3 trouble): hald_enable="YES" dbus_enable="YES" polkitd_enable="YES" volmand_enable="YES" slim_enable="YES" That last line refers to slim, a display manager (GUI login). Anyway, make sure HAL (deprecated), DBus (obsoleted), PolKit (nonsense) are actually installed on your system. Then check your ~/.xinitrc for those entries: dbus-launch exec ck-launch-session mate-session I have left out additional programs (xset, xbindkeys, xmodmap, > The Mate desktop starts with its default configuration except that the > size was for a larger monitor display. I was able to start Mate > Terminal, but it was sluggish moving the window. You can use xrandr interactively from a terminal to set the correct screen size. You can make the setting permanent by adding it to your ~/.xinitrc, for example: xrandr --fb 1400x1050 xrandr --size 1400x1050 There is also a Mate setting for this. If it doesn't work, use xorg.conf hard-coded values, for example /usr/local/etc/X11/xorg.conf.d/screen-resolution.conf: Section "Screen" Identifier "Screen0" Device "Card0" SubSection "Display" Modes "1280x800" EndSubSection EndSection That isn't nice, but it works. ;-) > I was able to restart my machine twice from Mate, so that function > appears to work. There is some documentation regarding Gnome on how to deal with HAL, which scatters its stupid XML configuration across the /usr/local subtree. This documentation also seems to work with MATE. https://www.freebsd.org/gnome/ https://www.freebsd.org/gnome/docs/faq2.html https://www.freebsd.org/gnome/docs/halfaq.html Relevant files can be found in /usr/local/share/polkit-1/actions, they should already be installed by MATE. > So, what does this all mean and would it be possible to salvage the > installation? Yes. ;-) You are more or less fighting the narrow view of programmers who primarily develop for Linux. In order to get MATE working on FreeBSD, there is some work you need to do, messing with stupid XML files, running outdated system services that were abolished in Linux years ago... but yes, sure, it is of course possible to get MATE running on FreeBSD, as I refered to from an older reference system running MATE; I'm not sure I would be able to get a similar system installed and configured on a more recent FreeBSD version from scratch... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...