Bug 133734 - Kpersonalizer starts all the time since Kubuntu KDE 3.5.4
Summary: Kpersonalizer starts all the time since Kubuntu KDE 3.5.4
Status: RESOLVED NOT A BUG
Alias: None
Product: kpersonalizer
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Carsten Wolff
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-07 23:29 UTC by Iñaki Baz Castillo
Modified: 2006-09-08 16:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iñaki Baz Castillo 2006-09-07 23:29:11 UTC
Version:           desconocido (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

Just it, Kpersonalizer starts all the time I start my KDE session.

I've realized that the files "startupconfig", "startupconfigkeys" and "startupconfigfiles" are modified JUST in the moment I log into KDM. They change in this way:

  kpersonalizerrc_general_firstlogin="true"  <-- before it was "false"
  kpersonalizerrc General FirstLogin true    <-- before it was false
  kpersonalizerrc General FirstLogin true    <-- before it was false

Of course, I've tried to change manually them but they change again when I log into KDM. If I set root as these files owner there appears an error when logging in KDM about "Couldn't start Kpersonalizer...".

A temporal solution is to uninstall Kpersonalizer but...


MAYBE IMPORTANT: I upgraded to KDE 3.5.4 same days ago, but this bug doesn't occur to me since that moment, it was a days after that. I remember what I did exactly the day I saw this bug for the first time:
- I was at work an opened a ssh agains my home machine. I logged as other user (the user who was using KDE in that moment), I did "export DISPLAY=:0,0" and "xhost +" to allow my real user to start a graphic app (Ktorrent) in a session of other user. I run Ktorrent with "nohup ktorrent".
When I arrived at home I started my KDE session and the problem occurred for the first time.

I don't know if this maybe important, it could just a coincidence.
Comment 1 Philip Rodrigues 2006-09-08 16:05:33 UTC
Create ~/.kde/share/config/kpersonalizerrc and put the following two lines in it:

[General]
FirstLogin=false
Comment 2 Carsten Wolff 2006-09-08 16:30:15 UTC
Nothing changed in this mechanism in kpersonalizer or startkde since ages. This is either a local or distributor problem.

Please try Philip's hint and please also check the permissions of ~/.kde/share/config/kpersonalizerrc.