I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a while (I can't tell the exact point, since I've just noticed it) I can't drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in one thing: it works in oneiric at least, since I have a machine running oneiric. If I try to drag a tab in firefox (version 13, not from ubuntu but installed "manually"). The twist: I use firefox from another machine (running hardy) but via ssh X11 redirection. However, chrome is running on the local machine. In firefox if I drag a tab, nothing happens: I can see the translucent image of the page and I can drag it, I can't "dock" it between the tabs, if I release the mouse button, the image just "jumps back". With chrome, again: I can see the translucent image, and I can drag it, but again, I can't "dock" it, if I release the mouse button it creates a new window instead of docking among the already existing tabs in the already existing window at the desired position. It seems that locally launched firefox 13 (from ubuntu repo!) works however. Also tab re-arraning eg in geany seems to be OK. Btw, composite effects are enabled via gconf in metacity.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: metacity 1:2.34.1-1ubuntu11
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu9
Architecture: i386
Date: Mon Jun 11 14:25:45 2012
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2)
SourcePackage: metacity
UpgradeStatus: Upgraded to precise on 2012-03-01 (101 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.