On Mon, 2004-10-04 at 19:45, Owen Taylor wrote:
On Mon, 2004-10-04 at 18:55 +0100, Mark McLoughlin wrote:
> > I was an existing user. I don't mind the change, and I like the
> > canned packages direction, but don't know if the change to my existing
> > panel layout was supposed to happen.
> You're right - if it screwed up your existing configuration, then
> that's a bug:
Doesn't look like the right link...
Yeah, sorry. Its:
> But I don't mind telling you that scratching my head
> produced any viable ideas for fixing said bug :/
Could it simply be users that haven't changed their configuration at
all? Seems unlikely, but I suppose possible.
No, the problem is that they've only changed *some* of their panel
I've updated the bug report with an explanation:
What's going on here is the panel configuration consists of a large
set of inter-related GConf keys. Lets think about just two of them for
a minute - toplevel_id_list and object_id_list. The former contains
the list of panels in the configuration and the latter contains the
list of launchers, menu buttons, menu bars etc. (everything but bonobo
These GConf keys individually inherit their default values from
defaults database. If you set one of the keys, it no longer matters
what the default is, but the other one still inherits the default.
So, looking at Stephen's screenshot, its obvious what happened. He
added a new launcher to his panel at some point, setting
object_id_list to contain all the default launchers and his new one.
toplevel_id_list remained unset, inheriting the default.
Now, when the panel package was updated the defaults changed, adding
an extra panel to toplevel_id_list, removing the menu button from
object_id_list and adding the menu bar to object_id_list. End result
is that Stephen sees the new panel, but still sees the menu button
when he should be seeing the menu bar.