Bug#617763: possible fix... regarding #629207, #629310, #631284, #617763
- To: 617763@bugs.debian.org
- Cc: devel@tootai.net, seanius@debian.org, dawitbro@sbcglobal.net, enygma@gmx.de, joss@debian.org, Michael Schmitt <tcwardrobe@gmail.com>
- Subject: Bug#617763: possible fix... regarding #629207, #629310, #631284, #617763
- From: Sven Hartge <sven@ds9.gnuu.de>
- Date: Thu, 21 Jul 2011 00:08:11 +0200 (CEST)
- Message-id: <[🔎] alpine.DEB.2.02.1107210003270.28835@ds9.feds.ath.cx>
- Reply-to: Sven Hartge <sven@ds9.gnuu.de>, 617763@bugs.debian.org
Michael Schmitt <tcwardrobe@gmail.com> wrote:
> I had a brief conversation about that issue with a develeoper of compiz
> on IRC (#compiz@freenode):
> 14:54:12 <maniac103> you can cite: 'A simple recompile of the
> compiz(-gnome) package should be sufficient to get things in order again'
> He could confirm the bug, tried to compile with some debugging
> statements added and all of a sudden it worked again.
> 15:05:54 <maniac103> TCW: I compile with debug symbols, but it was
> consistently broken with the old binary and consistently working with
> the new one
> So basically, a fresh re-compile, and all should work again.
I tested this and recompiled compiz in a clean pbuilder chroot with the
latest metacity and everything is fine again.
So a simple BinNMU of compiz should really resolve this problem for now.
And I think compiz-gtk needs a stricter dependency on the exact metacity
version it was compiled with since it uses some internal symbols and has
to stay locked to that specific version.
Grüße,
Sven.
Reply to: