Believe me I have searched forum.kde.org thoroughly.
Haven't been able to find any post on xsession-errors produced by KDE.
I have just upgraded to 4.5.1 even though Gentoo still considers it unstable.
One thing I am grateful for: The amount of nonsense in this file has greatly diminished.
Were they caused by devs inserting messages for troubleshooting ?

Here are some of the messages I get:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

krunner(3057)/libplasma Plasma::Package::isValid: Could not find required file mainscript , look in "/home/ikke/contents/code/main"

Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2 (X_ChangeWindowAttributes)
Resource id: 0x3000021
^[[31mvoid DBusMenuImporter::slotItemUpdated(int)^[[0m: No action for id 2
^[[31mvoid DBusMenuImporter::slotItemUpdated(int)^[[0m: No action for id 9
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")
Fetched layout groups from X server: layouts: ("us_intl") variants: ("")

This is just part of it.
Question: Why is it necessary to repeat the same message umpteen times?

/home/ikke is my home directory.
KDE has no business adding directories like /contents/code/main to my stuff.

I have used xsession-errors in kde-3.5 to troubleshoot misbehaving apps but since 4.x.x this has become almost impossible.
Gerard.

Run "kdebugdialog" and check the "Disable debug output" box. Logout and check to see if the output is still present. If it is, file a bug report regarding that, as that isn't warning or error output.

KDE shouldn't be using anything other than ~/.kde*/ for storing information. That looks like you may have set $KDEHOME to some value...

bcooksley wrote:Run "kdebugdialog" and check the "Disable debug output" box. Logout and check to see if the output is still present. If it is, file a bug report regarding that, as that isn't warning or error output.

KDE shouldn't be using anything other than ~/.kde*/ for storing information. That looks like you may have set $KDEHOME to some value...

Kdebugdialog was set to disable already in previous installs and still is.
Yet I still get these messages.
I cannot find $KDEHOME anywhere in my system using find,not in /home/ikke/.kde4 and not in /.
I used lower and upper case.
So thanks for the answer but it didn't help any.
Gerard.

It's an environment variable, not a file. Use "echo $KDEHOME" to show its contents.

airdrik wrote:It's an environment variable, not a file. Use "echo $KDEHOME" to show its contents.

Thanks for the reply.
That's the first thing I did:nothing nada nichts.
In the meantime I browsed the bug reports.
We'll have to live with it for a long time I guess.
It's a pity we cannot go back to kde-3.5.
I don't need all the bling bling.
My .xsession errors is still spamming about the settings of my keyboard in hal.
Gerard.

Did you file a bug report as I suggested / does a bug report exist? Developers cannot fix the issue if it hasn't been reported.

bcooksley wrote:Did you file a bug report as I suggested / does a bug report exist? Developers cannot fix the issue if it hasn't been reported.

There are so many open bug reports on xsession-errors,mine would not be looked into for a long time.
Besides I submitted a bug about kscd a long time ago:no action.

Something else for you to read: http://forums.gentoo.org/viewtopic-t-84 ... ight-.html
It used to work ok.
How long will it take to get rid of all these frustrating things?
Gerard.

That problem was fixed in KDE 4.5.0 I think, and requires a functional PolicyKit installation during kdelibs and kdebase compilation and usage.