Date: Sun, 1 Nov 2009 10:32:24 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Matthias Apitz <guru@unixarea.de> Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: [kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED) Message-ID: <alpine.BSF.2.00.0911010853050.2930@fledge.watson.org> In-Reply-To: <20091101072629.GA2334@current.Sisis.de> References: <20091030151754.GA5849@current.Sisis.de> <20091101072629.GA2334@current.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Nov 2009, Matthias Apitz wrote: >> i.e. it brings up this xmessage box and in the log files I can see that >> 'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up fine. >> This is, as I said, after compiling the port x11/kde4. The file >> /usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 >> and neither the shared libs it is depending: >> >> $ ldd /usr/local/bin/start_kdeinit_wrapper >> /usr/local/bin/start_kdeinit_wrapper: >> libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x2808e000) >> libc.so.7 => /lib/libc.so.7 (0x280c2000) Could you show us readelf -l /usr/local/bin/start_kdeinit_wrapper > it does not abort when you set > > # sysctl security.bsd.map_at_zero=1 > security.bsd.map_at_zero: 0 -> 1 > > I think that security.bsd.map_at_zero was already 0 before compiling > x11/kde4, i.e. no part of KDE4 changed this sysctl value; so it remains > open, what caused this effect, but at least it is working again; Could you confirm you are running with a userspace/kernel of at least r198203 (the date of the last PIE-related fix following a move to disallowing NULL mappings). Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0911010853050.2930>