Red Hat Bugzilla – Bug 103542
updating Severn to today's RHN updates removes all panel customizations
Last modified: 2007-04-18 12:57:18 EDT
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):
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
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
Created attachment 94131 [details]
Panel screenshot before update
Created attachment 94132 [details]
Panel after post-update login
Created attachment 94133 [details]
Contents of .gconf/apps/panel prior to update
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.
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.
Nope, no difference.
if you make any changes to ~/.gconf make sure that gconfd-2 is not running at
Confirmed, it wasn't running at the time I made the changes.
gnome-panel-2.3.90-1 fixed it for me, so I assume it was the same problem as bug
*** This bug has been marked as a duplicate of 102530 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.