kpersonalizer (the first time wizard) starts every time I start KDE

same problem here after upgrading to kde 3.5.4

I confirm this.

Ditto on kde 3.5.4 on current dapper.
~/.kde/share/config/startupconfig and ~/.kde/share/config/startupconfigfiles both say:
kpersonalizerrc_general_firstlogin="true"

I haven't yet tested this, but I believe this should fix it.

I'd like to disagree with the patch.

Are you sure you need to fix kpersonalizer for this?

According to this svn-log:
http://websvn.kde.org/tags/KDE/3.5.4/kdebase/kpersonalizer/kpersonalizer.cpp?rev=565692&view=log

kpersonalizer.cpp hasn't changed a line in KDE since 2003 or so. Since It worked for me all the previous releases until 3.5.4 came out, I'd suggest the error could be found somewhere in the environment of kpersonalizer? The initial creation of the config files maybe?

Please feel free to disagree with the patch. I haven't been able to get kdebase to build to test it, and I don't know how false vs. "false" would be treated. On the other hand, I suspect the problem is due to the startupconfig saying firstlogin="true" when it should say "false", and the patched line is apparently supposed to be changing that, but isn't. I spent some time looking at the problem, and this patch is still my best guess.

Thanks to http://www.kde-forum.org/thread.php?threadid=15137

The problem is that ~/.kde/share/config/kpersonalizerrc does not have a [General] section, which should look like this by default:

[General]
FirstLogin=true

Because it is not there kpersonalizer cannot set it to false. Add this to kpersonalizerrc to fix the problem for one user:

[General]
FirstLogin=false

The real bug is how the user's kpersonalizerrc is generated:
The default kpersonalizerrc is generated from /usr/share/kubuntu-default-settings/kde-profile/default/share/config/kpersonalizerrc. That file looks like this:

[General]
FirstLogin=false

(i.e. Kubuntu maintainers don't want kpersonalizer starting for every user)
For some reason this doesn't work and the generated kpersonalizerrc doesn't contain the [General] section, causing this problem. If you change false to true in the global kpersonalizerrc, new users' generated kpersonalizerrc will contain the [General] section.

tentative patch. feedback seems okay on it so far.

I simply removed kpersonalizerrc from kubuntu-system-settings package.
Now it isn't shiped by default, this is not of any use and generates the bug.
If you experience issues after this update, simply remove your ~/.kde/share/config/kpersonalizerrc, reload kde, see kpersonalizer once and for all :)

That happened to me in Hardy (updated from Feisty, after several starts without kpersonalizer). I did what Anthone Mercatante said and the problem is gone.