My mistake.
I thought Metacity played some minor role, especially since Unity is slightly
more stable after issuing compiz --replace from within a running instance of
Unity 3D. In this case, what I'm doing is simply restarting Unity 3D. Perhaps
it's a perceptual thing.
I just had compiz crash on me while logged in under the Openbox/Gnome,
which begs to question why compiz is running if openbox is being used as
a wm or how they're relegating work. But to the point, I guess my issue
was with compiz all along.
** Changed in: metacity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1031609
Title:
Metacity causes unity to crash using Gallium 0.4 on ATI RV530
Status in “metacity” package in Ubuntu:
Invalid
Bug description:
I gather the issue is with compiz because
compiz --replace
takes care of some random crashes and flickering.
Another solution is to edit
/usr/share/gnome-session/sessions/ubuntu-2d.session
so that on the line that reads
DefaultProvider-windowmanager=
metacity
is replaced with
compiz
Hardware
First generation (2006) Intel MacBook Pro (Intel Core Duo, aka Yonah based
processor) with an ATI Mbility Radeon X1600 video card.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: metacity 1:2.34.1-1ubuntu11
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic i686
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
Date: Wed Aug 1 00:38:01 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: metacity
UpgradeStatus: Upgraded to precise on 2012-03-23 (130 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1031609/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp