After upgrading from KDE 3.3. to KDE 3.4 under Fedora Core 3 I get a crash when starting the kicker program from my user account (kicker is the KDE panel application and it's started automatically)
If I log in as root it works fine.
The error is the following :

------------------------------------------------------------
$ kicker
Link points to "/tmp/ksocket-matteo"
Link points to "/tmp/kde-matteo"
kbuildsycoca running...
$ terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
kicker: crashHandler called
KCrash: Application 'kicker' crashing...
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc

$
-----------------------------------------------------------------

Has anybody found something like this or some ideas for this purpose ?

Thanks

Just a long shot - make sure /tmp is still writeable by your account. I found after an upgrade, I no longer had write access to /tmp, and all sorts of odd KDE crashes were occuring until I found and fixed it.

HTH

Just to add to that:

Use:

"chmod +w /tmp" or "chmod 775 /tmp" to enable write support if it is not already enabled.

Good answers because it could be the solution, as it looks to be some kind of protection error (root works fine), but unfortunately this is not the solution : my /tmp and /usr/tmp -> /var/tmp are both rwxrwxrwt..

Regards

mtpz

That's a good clue. Now check your rights in ~.kde, and everything beneath it.

Found the workaround !
The answer is under the thread "Kicker needs more RAM? St9bad_alloc" on Linux Software Forum.

It's enough to delete the file history.lst located in ~/.kde/share/apps/kicker and kicker works.

Why ?

The important for now it's that it works.

Thanks to the list

mtpz