Ubuntu
nautilus package

GConf schemas not installed

Bug #62982 reported by Luca Ferretti
2
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

I updated my Ubuntu-box from dapper to edgy. Now all my nautilus Gconf keys are disappeared from gconf-editor. The only key still available is /apps/nautilus/preferences/show_special_flags

I'm able to change Nautilus behavior using its preferences window: the key/value changed in preferences will appear in gconf-editor, but selecting it, in documentation pane of gconf-editor appear the warning message "This key has no schema".

I noticed this due to the switch to "close window after double click on folder" behavior using spatial interface after the upgrade to edgy. I dislike this behavior so I tried to change it in gconf-editor.

I tried to reinstall nautilus and gconf2 packages (apt-get --reinstall install), but this issue is still here.

PS of course gconftool2 has the same behavior of gconf-editor.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Could you run "sudo sh -x /var/lib/dpkg/info/nautilus-data.postinst configure" and copy that to a comment?

Changed in nautilus:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) wrote :

the schemas is shipped by nautilus-data, not nautilus btw, you probably want to reinstall that package instead of nautilus to get a new schemas registration

Revision history for this message
Luca Ferretti (elle.uca) wrote :

Now schemas are registred. This is the log of *postinst

luca@redrum:/~$ sudo sh -x /var/lib/dpkg/info/nautilus-data.postinst configure
+ set -e
+ [ configure = configure ]
+ gconf-schemas --register apps_nautilus_preferences.schemas
luca@redrum:/~

Maybe this isn't an bug related to nautilus package. I had some issue while upgrading (network down and power down) so maybe there are some broken stuff (even after a "apt-get install -f" too?)

Revision history for this message
Sebastien Bacher (seb128) wrote :

it looks like the schemas registration didn't work on first run for whatever reason. That seems to happen sometimes, marking as duplicate of bug #50150. That might be local issues on the concerned machines or a gconf bug not easy to triger

Revision history for this message
Sebastien Bacher (seb128) wrote :

not a nautilus bug

Changed in nautilus:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.