Ubuntu
metacity package

keybindings not working any more

Bug #66825 reported by Jochen Martin Eppler
2
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

My install is current Edgy. Since an update a few days ago, the keybindings for metacity don't work anymore (i.e. changing workspaces with ctrl+alt+cursor is disfunct)
Also the section for the window management shortcuts in the keyboard-shortcuts-capplet is empty.

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

Thanks for your bug. Could you run those commands and copy that to a comment?
- gconftool-2 --get /apps/metacity/global_keybindings/switch_to_workspace_left
- gconftool-2 --get-schema-name /apps/metacity/global_keybindings/switch_to_workspace_left

Does "sudo gconf-schemas --register /usr/share/gconf/schemas/metacity.schemas" fixes the issue?

Changed in metacity:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Jochen Martin Eppler (jochen-eppler) wrote :

- gconftool-2 --get /apps/metacity/global_keybindings/switch_to_workspace_left

No value set for `/apps/metacity/global_keybindings/switch_to_workspace_left'

- gconftool-2 --get-schema-name /apps/metacity/global_keybindings/switch_to_workspace_left

No schema known for `/apps/metacity/global_keybindings/switch_to_workspace_left'

Revision history for this message
Jochen Martin Eppler (jochen-eppler) wrote :

> Does "sudo gconf-schemas --register
> /usr/share/gconf/schemas/metacity.schemas" fixes the issue?

Yes! Calling this command and logging out and in again solved the issue! Also the above commands give the correct results now. Thanks!

Revision history for this message
Jochen Martin Eppler (jochen-eppler) wrote :

Unfortunately there are more problems related to gconf.

When running gnome-theme-manager I get the following error:
    The default theme schemas could not be found on your system.
    This means that you probably don't have metacity installed, or
    that your gconf is configured incorrectly.

Also I have been affected by #59079 which seems to indicate some more global gconf problems in edgy.

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

marking as duplicated of bug #50150. That's probably not a new gconf issue specific to edgy, looks like gconf either has a bug difficult to triger or is sensible to local issue on the machine

Changed in metacity:
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.