ok found a little info/workaround
cp index.theme index.desktop
this will eliminate the log in .xsession-errors
but fix the problem/bug? dont know cause the program "smb4k"
hangs upon launch with no output in the terminal until a kill command is issued.
another fix/workaround to have it not flood xsession-errors is to
"kdebugdialog --fullmode". Look for debug area 264, and change the combobox for the warning to "None"
but it just seems to hide the problem still
The errors went unnoticed until i installed smb4k (cause linneghborhood dont like samba3 too much)
Theese fixes just seem like they hide the problem and if anyone has any further info it will be appreciated.
thanks for all the replys