Ubuntu
kdebase package

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

Bug #56206 reported by David Solbach on 2006-08-13

Affects

Status

Importance

Assigned to

Milestone

kdebase (Ubuntu)

Fix Released

Undecided

Kubuntu Bugs

You need to log in to change this bug's status.

Affecting:	kdebase (Ubuntu)
Filed here by:	David Solbach
When:	2006-08-13
Confirmed:	2006-08-17
Assigned:	2006-08-30
Started work:	2006-09-11
Completed:	2006-09-11

Target

Distribution
Package	(Find…)
Project	(Find…)

Status	Importance
	Undecided

Assigned to

	Me
	Kubuntu Bugs (kubuntu-bugs)

Comment on this change (optional)

Email me about changes to this bug report

(?)

Bug Description

Binary package hint: kpersonalizer

I upgraded to kde 3.5.4 and after that I experienced problems with the package personalizer (3.5.4-0ubuntu1~dapper2).

KDEs first time wizard starts every time I start KDE. Expected behaviour would be, that it starts only the first time or even once more after an upgrade.

I tried to delete ~/.kde/config/startup* to fix it, but that didn't help.

the files where recreated and contained lines like "kpersonalizerrc General FirstLogin true" afterwards.

I'm not sure if this is an upstream bug, so i'm reporting it as a package bug.

Add tags Tag help

PascalC (p92) wrote on 2006-08-17:

same problem here after upgrading to kde 3.5.4

Changed in kdebase:
status:	Unconfirmed → Confirmed

Niko Lewman (niko-lewman-webbitakomo) wrote on 2006-08-28:

I confirm this.

Rocco Stanzione (trappist) wrote on 2006-08-30:

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

Rocco Stanzione (trappist) wrote on 2006-08-30:

kpersonalizer_firstlogin.diff Edit (863 bytes, text/plain)

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

Changed in kdebase:
assignee:	nobody → kubuntu-team

David Solbach (d-vidsolbach) wrote on 2006-08-30:

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?

Rocco Stanzione (trappist) wrote on 2006-08-31:

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.

Nx (kovacsnn) wrote on 2006-09-02: A solution

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.

Sarah Kowalik (hobbsee-deactivatedaccount) wrote on 2006-09-03:

patch Edit (1.3 KiB, text/plain)

tentative patch. feedback seems okay on it so far.

Anthony Mercatante (tonio) wrote on 2006-09-11:

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 :)

Changed in kdebase:
status:	Confirmed → Fix Released

Alejandro Díaz-Caro (janus) wrote on 2008-04-08:

#10

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.