Bug 164656

when you do the logout, does plasma crash?

I noticed that plasma would crash on logout if i removed the dolphin and systemsettings buttons, changing other settings like the size and start menu type, and leaving the buttons meant it didnt crash and the settings were saved.

Plasma is crashing for me because of bug #164653 which has been fixed in svn now. Even then, what if I press Ctrl-Alt-Backspace, will I then also loose all changes I have made during that session? I would expect settings to be saved as soon as I make them and not only at a proper logout.

Frederik:
iirc if there was a change done that needs to be saved, plasma will do so some minutes later (to prevent writes e.g. each 10 seconds if someone does e.g. rearrange it's plasmoids). So, if you do Ctrl-Alt-Backspace you may lose changes (as in e.g. changed settings for plasmoids) done in the last few minutes only.
re systemtray; probably also already fixed but I am not sure there since it seems the systemtray has more bugs and problems then lines-of-code :-/
re 2 panels && black text on black background; seems I am not able to reproduce this :-/

Adam:
yo, hi! :-) and hmmm... what does "dolphin and systemsettings buttons" mean in that context? icons on the desktop? icons on the panel? icons in the folderview? icons in the favorite-tab in kickoff? probably a separate bugreport or how is this related?!

I do not think this can all be explained by a lack of saved settings because of a plasma crash: I certainly do not have the habit of changing Plasma settings, and then logging out/crashing Plasma only a few minutes later. Also, I don't think this can explain the black-text-on-black-panel problem, as there is no such theme AFAIK. However, reconfiguring the theme in the Desktop Settings configuration panel, fixes the problem. A lot of people are complaining about this particular problem on Mandriva's Cooker mailing list and IRC channel. Maybe we should concentrate on that particular problem here in this bug report.

Frederik: thanks for the additional info re Mandriva cause Adam is using Mandriva too and now I do understand the context there.
Well, it sounds for me like a distributor aka upstream bug/problem rather then a KDE-one cause it seems only Cooker-users have it... Anyway, this sounds like a good excuse to give Mandriva 2008.1 a try. So, I am downloading it right now :) btw, any special actions I need todo after installation to update to 4.0.83?! and also it seems I still don't got what the diff between "Cooker" and 2008.1 is.

reassign from plasma-devel to me since imho upstream-bugs are not something the other devels could deal with anyway.

2008.1 is the previous stable version, cooker is the current development tree (compare with Fedora Rawhide or OpenSuse Factory).

to upgrade from 2008.1 to Cooker with kde 4:

# urpmi.removemedia -a
# urpmi.addmedia --distrib --mirrorlist 'http://api.mandriva.com/mirrors/basic.cooker.$ARCH.list'
# urpmi task-kde4

I forgot one command, before running urpmi task-kde4, run
# urpmi --auto-select
to bring everything up to date.

*** Bug 164786 has been marked as a duplicate of this bug. ***

Frederik: did you perhaps run Amarok2? if so, that bug was fixed just a few days ago in trunk.

Oh yes, Amarok was active in the system tray.

uh, *huge* thanks to Aaron for that hint! Yay, now the remaining question is, if the systray-issue named here too ( and at bug #164786 ) is independend of this?

p.s. I am still on "urpmi task-kde4" and so far the Mandriva KDE3-default feels really great. Will be interesting to see what KDE4+powerpack does provide :)

oh, seems the report was still open. So, let's mark it as fixed then :) Thanks frederik, aaron, finex and rex :)