Bug 246855

Summary: Plasma panel disappeares after upgrade to 4.5 RC2 or RC3
Product: [Plasma] plasma4 Reporter: Unknown <null>
Component: panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: aseigo
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Plasma configuration files

Description Unknown 2010-08-06 00:38:45 UTC
Created attachment 49852 [details]
Plasma configuration files

Version:           unspecified (using KDE 4.4.95) 
OS:                Linux

After I upgraded to KDE 4.5 RC 2 and RC 3, plasma panel simply disappeared, and I had to create it again, from scratch.

I attach the plasma configuration files from the time I had no panel at all (after upgrading to RC 3).

Reproducible: Always
Comment 1 Aaron J. Seigo 2010-08-06 19:16:18 UTC
"After I upgraded to KDE 4.5 RC 2 and RC 3"

to RC2 and RC3 from what previous release?

it's evident why there is no panel: the configuration file is empty. why that would happen during upgrade, i'm uncertain. the upgrade path is certainly a well tested one, though.

if you can give a way to reproduce, that would be great. otherwise, we'll have to close this report as unreproduceable.
Comment 2 Unknown 2010-08-06 20:28:26 UTC
If I'm not mistaken, it appeared first when I upgraded from RC 1 to RC 2 (see Bug 243003, too). Then I created the panel, and after upgrading from RC 2 to RC 3, this bug happened again, panel is gone.

Since I cannot downgrade to RC 2 (or 1) there are two solutions, I think:
- wait until the final 4.5 comes out and logging
- force the RPM-reinstall (maybe the upgrade scripts run again) and also logging

Is there any program which observes the file changes and logs them (eg. which program created, modified, deleted a file etc.)?
Comment 3 Aaron J. Seigo 2010-08-06 20:48:12 UTC
there is no central logging for config file write. upgrades between RC's/beta's are not well supported (and things may break while doing so: they are not stable releases). let's see with 4.5.0 and if the issue does not present, then we can cal this closed.
Comment 4 Unknown 2010-10-08 07:35:15 UTC
I could not reproduce it when I upgraded to 4.5 final, so I close this bug.