faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Saving widgets in plasma
by metellius on Wednesday 07/May/2008, @20:23
|
Seeing as there are no updated to plasma, does this mean that 4.0.4, just like 4.0.3 still doesnt save widgets on the desktop between sessions?
If this is the case, hasn't anyone considered backporting this fix from svn?
Personally, this is the simple bug that is keeping me from using the kde 4.0.x releases. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Saving widgets in plasma
by sebas on Thursday 08/May/2008, @03:03
|
There are updates to Plasma, though I don't know if your bug has been corrected. It could well be that the bug is not in plasma, but somewhere else, so it's worth checking in any event.
In the changelog, there's a link to all changes in SVN, there are a couple of things changed in plasma, just have a look at the file for kdebase.
|
[
Reply To This | View ]
|
Re: Saving widgets in plasma
by Aaron Seigo on Thursday 08/May/2008, @14:24
|
Plasma does save widgets in between; the problem is that on your system it's evidently crashing on log out. To find the problem, try running command from a console in a session: kquitapp plasma. You can start Plasma up again quite easily with `plasma` so don't freak out when your desktop goes all white (or whatever). You should then see the crash; and you should also get a crash dialog that will let you get to the backtrace.
Most likely scenarios: you are using composite with the taskbar tooltips which is crashing somewhere in the X11 code; you have stale plasmoids sitting around somewhere and bringing your system down.
|
[
Reply To This | View ]
|
Re: Saving widgets in plasma
by Morty on Saturday 10/May/2008, @12:22
|
> Plasma does save widgets in between;
Then this is the actual problem, that Plasma only saves configuration changes between sessions. This sounds like the same flaw that Kicker had, any crashes could mess up your configuration. This is specially a problem on systems where the users stays logged in for long periodes of time, basicly a very common usage pattern on *nix systems.
And on modern computers with suspend to ram/disk logouts should not be necessary at all. And since the suspend features generally seem somewhat unrealible over the range of different hardware, this increases the problem by vanishing configurations, making it even worse.
Simply making Plasma/plasmoids save it's configuration when changed, rather than waiting for logout would remove the problems. By nature the configurations will be fairly static, and any changes will only happen at one item at the time making the resource usage small.
|
[
Reply To This | View ]
|
Re: Saving widgets in plasma
by Ian Monroe on Saturday 10/May/2008, @15:01
|
The correct place to fix this would be the KConfig backend, not plasma. Like a sqlite kconfig backend wouldn't have this issue, it's good at crash-recovery.
|
[
Reply To This | View ]
|
Re: Saving widgets in plasma
by Morty on Monday 12/May/2008, @13:03
|
No, it does not seem like the problem is about crash-recovery. A crash on logout should never make configuration changes dissappear, since any changes should have been saved long before you log out. Plasma and plasmoids should behave like regular applications. Take Konqueror, it does not lose changes made to it's settings if it crashes before you exit.
If you save when configurations are changed instead of waiting for exit, any crashes on exit or before will not loose settings.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
