Unity sets the wrong metacity keyboard shortcut defaults

Bug #856884 reported by Jeremy Bícha
144
This bug affects 43 people
Affects Status Importance Assigned to Milestone
Unity
Triaged
Low
Unassigned
unity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

UPDATE: This affects first login of new users also.

Running unity --reset breaks Alt-F2 for the run command, Meta+D to show desktop, and Alt+F1 to show the main menu. I believe Unity itself ignores these metacity settings, but this breaks GNOME Shell & other similar sessions.

See also https://launchpad.net/ubuntu/+source/compiz/1:0.9.5.94+bzr2803-0ubuntu4 which I guess "fixed" the Ctrl-Alt-T shortcut.

TEST CASE
1. cd ~/.gconf/apps
2. mv metacity metacity-old
3. unity --reset
4. Within a minute or so, a new metacity folder is created
5. cat metacity/global_keybindings/%gconf.xml
<?xml version="1.0"?>
<gconf>
 <entry name="panel_run_dialog" mtime="1316732563" type="string">
  <stringvalue>disabled</stringvalue>
 </entry>
 <entry name="run_command_terminal" mtime="1316732563" type="string">
  <stringvalue>&lt;Control&gt;&lt;Alt&gt;T</stringvalue>
 </entry>
 <entry name="panel_main_menu" mtime="1316732563" type="string">
  <stringvalue>disabled</stringvalue>
 </entry>
 <entry name="show_desktop" mtime="1316732562" type="string">
  <stringvalue>&lt;Control&gt;&lt;Alt&gt;d</stringvalue>
 </entry>
</gconf>

What should happen:
I think unity --reset should delete these strings which will reset settings to their defaults instead of setting new, wrong settings.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.16.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
Date: Thu Sep 22 19:05:28 2011
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jeremy Bícha (jbicha) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Omer Akram (om26er)
Changed in unity (Ubuntu):
assignee: nobody → Jeremy Bicha (jbicha)
Changed in unity:
status: New → Confirmed
Changed in unity (Ubuntu):
importance: Undecided → Low
Changed in unity:
importance: Undecided → Low
assignee: nobody → Jeremy Bicha (jbicha)
status: Confirmed → In Progress
Changed in unity (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I'm unassigning myself, in case someone is able to fix this before I get to it and figure out what's going on.

summary: - Running unity --reset breaks metacity keyboard shortcut defaults
+ Unity sets the wrong metacity keyboard shortcut defaults
description: updated
Changed in unity (Ubuntu):
status: In Progress → Triaged
Changed in unity:
assignee: Jeremy Bicha (jbicha) → nobody
Changed in unity (Ubuntu):
assignee: Jeremy Bicha (jbicha) → nobody
Omer Akram (om26er)
Changed in unity:
status: In Progress → Triaged
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Workaround:

mv .gconf/metacity .gconf/metacity-old

And you can remove .gconf/metacity-old if you don't have any other Metacity settings (like customized destkop keyboard shortcuts).

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Changing importance to Medium as this is a pretty common bug that breaks usability and core functionality of at least GNOME Shell and GNOME Fallback (Fallback is shipped in Edubuntu).

Changed in unity (Ubuntu):
importance: Low → Medium
Revision history for this message
Roger Binns (ubuntu-rogerbinns) wrote :

I'm using Gnome Shell. After deleting the directory as mentioned in comment #4 I logged out and back in again and everything was working fine. The only gotcha was that Chrome put the window buttons on the left while all other windows had them on the right. Editing the relevant metacity key in gconf-editor then convinced Chrome to put them on the right too. Presumably there are several interrelated keys which can cause inconsistencies like this if just flat out deleting the directory.

Revision history for this message
RavanH (ravanhagen) wrote :

I can confirm that removing the metacity config directory solved the issue (after a reboot because alt+f2 then r and enter to reload shell does not work at that point)

rm -R ~/.gconf/apps/metacity

Paul White (paulw2u)
tags: added: i386 precise
Changed in unity (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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