freebsd stable - Mar 2013 - Functional KDE desktop

Hi,
I am in the process of upgrading all the ports on a 9.1-PRERELEASE system and I
am having a lot of trouble building or running KDE 4.9.5.

I couldn't build it due to x11/xsd not building (didn't make a necessary
header), or if I worked around that libkonq was not found by cmake. If I manage
to work around that I get an error dialogue when logging in.

In the end I gave up and installed packages (version 4.8.4) however that does
work as startkde gives..
[midget 22:10] ~ >env PATH=$PATH:/usr/local/kde4/bin
/usr/local/kde4/bin/startkde
xset:  bad font path element (#12), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
startkde: Starting up...
/usr/local/lib/libkdeui.so.7: Undefined symbol
"_ZN6Attica15ProviderManagerC1ERK6QFlagsINS0_12ProviderFlagEE"
startkde: Could not start kdeinit4. Check your installation.

c++filt says this symbol is..
Attica::ProviderManager::ProviderManager(QFlags<Attica::ProviderManager::ProviderFlag>
const&)

Also, the startkde script does not set the pass so it never finds kcheckrunning.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

On Sun, 17 Mar 2013 22:35:02 +1030
"Daniel O'Connor" <doconnor at gsoft.com.au> wrote:
> Hi,
> I am in the process of upgrading all the ports on a 9.1-PRERELEASE
> system and I am having a lot of trouble building or running KDE 4.9.5.
> 
> I couldn't build it due to x11/xsd not building (didn't make a
> necessary header), or if I worked around that libkonq was not found
> by cmake. If I manage to work around that I get an error dialogue
> when logging in.
> 
> In the end I gave up and installed packages (version 4.8.4) however
> that does work as startkde gives.. [midget 22:10] ~ >env
> PATH=$PATH:/usr/local/kde4/bin /usr/local/kde4/bin/startkde xset:
> bad font path element (#12), possible causes are: Directory does not
> exist or has wrong permissions Directory missing fonts.dir
>     Incorrect font server address or syntax
> startkde: Starting up...
> /usr/local/lib/libkdeui.so.7: Undefined symbol
> "_ZN6Attica15ProviderManagerC1ERK6QFlagsINS0_12ProviderFlagEE"
> startkde: Could not start kdeinit4. Check your installation.
> 
> c++filt says this symbol is..
>
Attica::ProviderManager::ProviderManager(QFlags<Attica::ProviderManager::ProviderFlag>
> const&)
> 
> Also, the startkde script does not set the pass so it never finds
> kcheckrunning.
> 
> --
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
>   -- Andrew Tanenbaum
> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
> 
I have it working fine here. I originally was using it on 9.0 then I
upgraded everything but that didn't work well for the KDE 4.8->4.9
update in ports. Too many ports were split and moved around so I ended
up removing all ports and remaking them all. One big gotcha is make
sure you force a reconfigure on everything. 

My small nightmare was kdepim,kdepim-runtime and kdepimlibs
there are now two deferment types of PIM you can built the old "4.8
style" and the new. Make sure you are consistent as these packages are
deps for many others. For a while I was still picking up settings for
the old style and it was breaking all over the place.

If you want I can send you a list of all the stuff I have installed off
list and you can see if you're somehow missing important bits...