Bug 225423

Summary: Crash with dashboard showing a different set of elements
Product: [I don't know] kde Reporter: Bruno Almeida <bruno.r.almeida>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: plasma-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Bruno Almeida 2010-02-03 19:35:58 UTC
Version:            (using KDE 4.4.0)
Compiler:          gcc (SUSE Linux) 4.4.1 [gcc-4_4-branch revision 150839]
OS:                Linux
Installed from:    openSUSE RPMs

The following problem occurs with KDE 4.4 RC3 under openSUSE 11.2. Steps to reproduce it:

1. Go to System Preferences > Workspace and set the dashboard to show an independent set of elements.

2. Add a random plasmoid to the dashboard. I tested this with stock plasmoids such as the Analog Clock and the "Now Playing" plasmoid.

3. Close the dashboard and exit your session to KDM.

4. This should cause a segmentation fault in kdeinit4.

5. After starting a new session, your plasmoid will not be visible in the dashboard.

This happens to me everytime I set the dashboard to show an independent set of elements. Also, if I make changes to other plasmoids in my desktop activities they will be lost after starting a new session. When I change the dashboard settings back to default everything seems to be fine.
Comment 1 Christoph Feck 2010-02-04 21:08:18 UTC
Could you add the backtrace of the kdeinit4 crash, if possible?
Comment 2 Bruno Almeida 2010-02-06 19:13:59 UTC
(In reply to comment #1)
> Could you add the backtrace of the kdeinit4 crash, if possible?

The problem is the crash occurs just before exiting the session, so I don't think I can do it with KDE Crash Handler. Is there a way I can prevent the session from closing, or perhaps pickup the crash from another session?
Comment 3 Bruno Almeida 2010-02-10 19:25:31 UTC
This issue seems to be resolved with the stable KDE SC 4.4. However I opened another bug regarding the dashboard: https://bugs.kde.org/show_bug.cgi?id=226178