[kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED)

[Matthias Apitz]

El día Friday, October 30, 2009 a las 04:17:55PM +0100, Matthias Apitz escribió:

> 
> Hello,
> 
> I have in a VM a 9-CURRENT and compiled/installed from the ports first
> x11/kde3 (which worked fine) and now in addition x11/kde4 (which comes
> up also fine).
> 
> But,
> 
> A start of KDE3 from ~/.xinitrc via exec /usr/local/bin/startkde
> complains in the following code:
> 
> # We set LD_BIND_NOW to increase the efficiency of kdeinit.
> # kdeinit unsets this variable before loading applications.
> LD_BIND_NOW=true start_kdeinit_wrapper --new-startup +kcminit_startup
> if test $? -ne 0; then
>   # Startup error
>   echo 'startkde: Could not start kdeinit. Check your installation.' 1>&2
>   xmessage -geometry 500x100 "Could not start kdeinit. Check your installation."
> fi
> 
> 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)
> 
> What could cause this behaviour? Thanks

+Cc: freebsd-current

I digged into that deeper with the sources...
start_kdeinit_wrapper -> start_kdeinit -> kdeinit
is (on non-Linux) just an execvp(2) chain of the above three programs; on
FreeBSD it would not even be necessary because non of them runs with
setuid on execution.

As mentioned, the three programs
/usr/local/bin/start_kdeinit_wrapper
/usr/local/bin/start_kdeinit
/usr/local/bin/kdeinit
have been compiled on -CURRENT r197801 and have been untouched and
working since October, 16. On October 30, I compiled in addition the
port x11/kde4, which does not touch the above programs and also not the
shared libs used by them;

after the installation of x11/kde4 the start_kdeinit_wrapper now aborts:

$ /usr/local/bin/start_kdeinit_wrapper
Abort trap: 6

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;

Thx

	matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru at unixarea.de> - w http://www.unixarea.de/
Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu