Bug#400583: Bug#390929: compiz: "Another window manager is already running on screen: 0"
On Fri, Jun 15, 2007 at 09:02:23AM +0200, Michel Dänzer wrote:
> On Fri, 2007-06-15 at 08:47 +0200, Brice Goglin wrote:
> > Michel Dänzer wrote:
> > > On Thu, 2007-06-14 at 23:52 +0200, Stéphane Rosi wrote:
> > >
> > >> After I run 'compiz --replace', gtk-window-decorator takes nearly 100%
> > >> of my cpu resources...
> > >>
> > >
> > > Some folks on the upstream compiz mailing list indicated this could
> > > happen if libdecoration0 is not the same version as the other compiz
> > > components.
> > >
> >
> > And we have a bug about our dependency on libdecoration0 not being
> > versioned:
> > #425463 compiz-plugins: Versioned depends on libdecoration
>
> Which implies the above can't be caused by an old libdecoration0
> though...
In fact, I'm experiencing the same problem (100% cpu from
gtk-window-decorator and no window borders) and I can guarantee that I
have the compiz suite all coming from unstable.
BTW: this is when replacing metacity in my case.
--
mattia
:wq!
Reply to: