Ubuntu
kdebase package

Kpersonalizer start every boot AND after resolution issue

Bug #60311 reported by Martijn van Vliet
12
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I installed

apt-cache policy kpersonalizer
kpersonalizer:
  Geïnstalleerd: 4:3.5.4-0ubuntu1~dapper2
  Kandidaat: 4:3.5.4-0ubuntu1~dapper2
  Versietabel:
 *** 4:3.5.4-0ubuntu1~dapper2 0
        500 http://kubuntu.org dapper/main Packages
        100 /var/lib/dpkg/status
     4:3.5.4-0ubuntu1~dapper1 0
        500 http://kubuntu.org dapper/main Packages
     4:3.5.2-0ubuntu27 0
        500 http://security.ubuntu.com dapper-security/main Packages
     4:3.5.2-0ubuntu26 0
        500 http://nl.archive.ubuntu.com dapper/main Packages

So i look into the tool and feel i don't want to use it, i quit it and continue.
Now i reboot and bang, there the Kpersonaliser popup before the desktop is actually launched. So i think "ok, i'll do cancel and this popup is probably only once". But nope, every time i have to cancel it.

I keep on the habbit of canceling the bloody tool, and try to lower the screenresolution in system setting. This didn't work anymore seeing that the preview before the deside dialog was not working at all. (it did before the Kpersonaliser installation)

So i think, "ok, maybe i have to reboot because of an update i just did... so i reboot and bang, the black screen with no login at all. So i do dpkg-reconfigure xserver-xorg and reboot again into my desktop without issues.

After that i had another time the annoying popup of Kpersonalizer (*@#$%!@#^), and i deside to follow the Kpersonalizer wizard now so maybe it would shut it. After doing so, previewing altered resolutions do work again, but i still have to watch the Kpersonalizer popups at bootup.

This is a relative new dapper 6.06.1 with kde 3.5.4, and i have not played with xorg.conf by hand.

Revision history for this message
Martijn van Vliet (mvanvliet) wrote :

Hmm, the restart on every boot of kpersonalizer seems to be "normal". (not so pretty! )
And the preview resolution problem seems to only be there when i activate "framebuffer-interface in the kernel".
Still dunno where the black screen came from though....

Revision history for this message
Carlos Diener / emonkey (emonkey) wrote :

Do you made some changes on the KDE design, theme or colors? I've got the same problem since I've done some changes on the KDE design. Maybe there's some problem with write permissions on a configuration file. I've done the changes with root rights (kdesu systemsettings) because without the changes had no effect. Since this work I've several other problems. For example, the hotkeys doesn't work anymore.

I don't know If there's a relation between my changes and this problem, maybe I've done some upgrades on the same day. Fact is that I've heard the story with kpersonalizer more than one times in forums out there.

Revision history for this message
Loïc Corbasson (cnb) wrote :

I had a similar problem, kpersonalizer starting after each logon and the accessx pop-up appearing a few minutes after starting kde. Upgrading to kde 3.5.5 fixed the problem.

If you think it's a permissions error you may want to execute the following command to locate such files:

find ~/.kde \! -type d -exec ls -al {} \; | sed '/^.rw....... [^ ][^ ]* yourusername/d'

(don't forget to replace yourusername by sth suitable)

Hope that helps.

Loïc

Revision history for this message
Wilfred (whjudoka) wrote :

I've also experience this bug twice, once on dapper and now again on a fresh install of edgy. It seems to occur when installing the kde-devel package using apt-get.

Following the instructions here (http://ubuntuforums.org/showthread.php?t=262758) fixes it, but KPersonalizer should set the FirstLogin value itself.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I can't reproduce this on Kubuntu Feisty Herd 4.
I installed kpersonalizer, logged out, logged in, hit quit wizard, logged out, logged in again and kpersonlizer did not come back.

This or a similar issue was fixed in bug 56206.

Does anybody have this issue in Feisty or in latest Edgy + KDE 3.5.6?

Changed in kdebase:
status: Unconfirmed → Needs Info
Yuriy Kozlov (yuriy-kozlov)
Changed in kdebase:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.