Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 103542 - updating Severn to today's RHN updates removes all panel customizations
Summary: updating Severn to today's RHN updates removes all panel customizations
Keywords:
Status: CLOSED DUPLICATE of bug 102530
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: gnome-panel
Version: beta1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-02 02:54 UTC by Alexandre Oliva
Modified: 2007-04-18 16:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:58:23 UTC
Embargoed:

Attachments (Terms of Use)
Panel screenshot before update (deleted)
2003-09-02 02:56 UTC, Alexandre Oliva 		no flags Details
Panel after post-update login (deleted)
2003-09-02 02:56 UTC, Alexandre Oliva 		no flags Details
Contents of .gconf/apps/panel prior to update (deleted)
2003-09-02 03:00 UTC, Alexandre Oliva 		no flags Details
Changes introduced with the first login after update (deleted)
2003-09-02 03:03 UTC, Alexandre Oliva 		no flags Details
View All

Description Alexandre Oliva 2003-09-02 02:54:54 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
Updating a Severn full install (without any previous updates related with gnome)
to everything new in Sept 1st's RHN severn-updates channel causes the next login
to have all gnome-panel customizations to be dropped.

Version-Release number of selected component (if applicable):
gnome-panel-2.3.7-1

How reproducible:
Always

Steps to Reproduce:
1.Customize gnome-panel on vanilla Severn
2.Update to current Severn updates
3.Log in again
    

Actual Results:  gnome-panel configurations are all gone

Expected Results:  I suppose they should have been preserved

Additional info:

I'll attach a screenshot of the previous panel, the uncustomized panel, my
original .gconf/apps/panel contents, and the diffs introduced during the first
log in.
Comment 1 Alexandre Oliva 2003-09-02 02:56:02 UTC 
Created attachment 94131 [details]
Panel screenshot before update
Comment 2 Alexandre Oliva 2003-09-02 02:56:43 UTC 
Created attachment 94132 [details]
Panel after post-update login
Comment 3 Alexandre Oliva 2003-09-02 03:00:21 UTC 
Created attachment 94133 [details]
Contents of .gconf/apps/panel prior to update
Comment 4 Alexandre Oliva 2003-09-02 03:03:14 UTC 
Created attachment 94134 [details]
Changes introduced with the first login after update

Nothing was removed, but the configuration in there seems to no longer be used.
 Why?
Comment 5 Alexandre Oliva 2003-09-02 03:07:53 UTC 
I guess I should have mentioned...  The before-update screenshot was taken on my
desktop box, that still hasn't been updated, whereas the post-update one was
taken on the laptop.  That's why the resolutions are different.  The .gconf* and
.gnome* directories' contents were identical before I logged in after the
update.  Hmm...  Could the fact that I was logged in on the desktop when I
rsynced the config dirs to the laptop have broken the update?  I'll try logging
out before the rsync next.
Comment 6 Alexandre Oliva 2003-09-02 03:17:41 UTC 
Nope, no difference.
Comment 7 George Lebl 2003-09-02 16:29:23 UTC 
if you make any changes to ~/.gconf make sure that gconfd-2 is not running at
the time.
Comment 8 Alexandre Oliva 2003-09-02 18:11:45 UTC 
Confirmed, it wasn't running at the time I made the changes.
Comment 9 Alexandre Oliva 2003-09-04 21:55:29 UTC 
gnome-panel-2.3.90-1 fixed it for me, so I assume it was the same problem as bug
102530

*** This bug has been marked as a duplicate of 102530 ***
Comment 10 Red Hat Bugzilla 2006-02-21 18:58:23 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.