Um.. You better contact #ubuntu-motu irc://chat.freenode.net/ubuntu-motu and ask for help (mention the bug link!) Do *not* set it as fix released in "compiz (ubuntu)", bug still exists in lucid package. Thanks for the patch! :-)
On 5/3/10, Guido I <guido...@guidoi.com.ar> wrote: > @Omar, AbtZ > > Patch was commited upstream :D > http://git.compiz.org/fusion/compizconfig/compizconfig-backend-gconf/commit/?id=74c3fd404f0879b5d36c1167d0b43986d949fad4 > > So now you only need to clone the last revision, no need to apply the > patch > > $ git clone > git://anongit.compiz.org/fusion/compizconfig/compizconfig-backend-gconf > $ cd compizconfig-backend-gconf/ > $ ./autogen.sh > $ make > $ metacity --replace & > $ for file in /usr/lib/compizconfig/backends/libgconf.* ; do sudo mv $file > $file.backup ; done > $ sudo cp settings-backend/.libs/libgconf.* /usr/lib/compizconfig/backends/ > $ compiz --replace & > > Or, alternatively, wait till the next release of compiz, where it will > be fixed already. > > Don't know how to proceed now, should this bug be marked as fixed? (it > is indeed fixed upstream, but) on current version of compiz included in > Lucid repos, bug still present so patch needed. Advice anyone? > > -- > Bad Compiz Bindings Bug > https://bugs.launchpad.net/bugs/207065 > You received this bug notification because you are a direct subscriber > of the bug. > -- Bad Compiz Bindings Bug https://bugs.launchpad.net/bugs/207065 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
