Hello,
I installed KDE4.5 on Mandriva 2010.1
My pc is a HP laptop 9670 with a HP dock and HP large external screen 1900x1200.

I use mainly the external screen.
I'm supposed to have 2 activities:
- one for the laptop screen 1440x900
- one for the external srceen 1900x1200

Problem:
At start: most of the time the desktop is blank (no icon, blue-grey default wallpaper) and KDE does not boot on the last used activity.

If I click on activies: no activity shown... need to reboot
after reboot: 2 new activies created each time (but blank desktop)
I have to click on each of them to find my own activity!!

Then the X process is huge: 200 to 300 MB

I installed KDE4.5 also on the same mandriva but HP laptop DV9680 with normal 1400x900 screen: no problem and X uses 70-80 MB only.

Both use NVIDIA video card (7600M and 8600M).

Thanks for help

If you create a new user, does the problem persist?

If it doesn't, try moving ~/.kde4/share/config/plasm* elsewhere in your normal user.

Hi,
I did what you said. The X ram consumption is now normal.
I have re-created 2 activities. One for each screen resolution.
At boot: exactly the same, it may works or blank desktop and no activity to choose from.
I log-off/login and it works with my 2 activities to choose from but with also one more activity created at each restart.

This is most definitely a bug in Activities, as it should try to assign from existing activities before creating new ones.

Please file a bug at bugs.kde.org.

Bug confirmed on my machine.

Is it necessary to create again a new account for bugs.kde.org???

At this time, KDE uses seperate accounts for each of it's web services, so it will be needed to.

I resolved this bug by "simply" deleting everything plasma related in ~/.kde4
Since then I don't have this problem anymore.

Primoz wrote:I resolved this bug by "simply" deleting everything plasma related in ~/.kde4
Since then I don't have this problem anymore.

No way, this is not enough and one more time "X"reach 400 Mb

A similar bug has been filed yesterday;
https://bugs.kde.org/show_bug.cgi?id=248386

Up!