[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#551654: marked as done (Compiz won't start/won't load properly)

Your message dated Sun, 7 Mar 2010 12:30:25 +0100
with message-id <20100307113025.GA5336@loulous.org>
and subject line Re: Bug#551654: Compiz won't start/won't load properly
has caused the Debian Bug report #551654,
regarding Compiz won't start/won't load properly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
551654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551654
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: compiz
Version: 0.8.2-6
Justification: renders package unusable
Severity: grave

After last upgrade, compiz just stopped working.

First problem was that compiz wouldn't start at all, output is in
http://foolcontrol.org/img/bug/mesa%20bug.txt, which I fixed.

Second problem came that compiz would start automatically (I didn't
invoke it) and that once it starts, windows can't be minimized or moved
or anything and are surrounded by these black thick "borders/edges".

http://foolcontrol.org/img/bug/compiz_edges_problem.png

It came to my attention that the same bug is present in latest Ubuntu,
9.10:

https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/178953
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/363517
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/363821=20

compiz-check would warn me on "Checking for hardware/setup problems..."
but after I disabled /apps/metacity/general/compositing_manager
(gconf-editor) compiz-check does not issue any problems (see
http://foolcontrol.org/img/bug/compiz-check%20report.txt)

There are no problems with metacity (metacity --replace), which I'm
currently using without any problems, however when I issue "compiz
--replace" compiz starts and is displayed as you can see on screenshot
above (also see: http://foolcontrol.org/img/bug/compiz%20--replace.txt)


Adnan


Graphics: Intel Corporation Mobile GM965/GL960 Integrated Graphics
Controller (rev 0c)

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=3Den_US.UTF-8, LC_CTYPE=3Den_US.UTF-8 (charmap=3DUTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages compiz depends on:
di  compiz-core                   0.8.2-6    OpenGL window and
compositing mana
ii  compiz-gnome                  0.8.2-6    OpenGL window and
compositing mana
di  compiz-gtk                    0.8.2-6    OpenGL window and
compositing mana
di  compiz-plugins                0.8.2-6    OpenGL window and
compositing mana

compiz recommends no packages.

Versions of packages compiz suggests:
di  compizconfig-settings-manager 0.8.2-2    Compizconfig Settings
Manager

-- no debconf information

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Version: 0.8.4-2

On Mon, Oct 19, 2009 at 09:07:45PM +0200, Adnan Hodzic wrote:
> Package: compiz
> Version: 0.8.2-6
> Justification: renders package unusable
> Severity: grave
> 
> After last upgrade, compiz just stopped working.
> 
> First problem was that compiz wouldn't start at all, output is in
> http://foolcontrol.org/img/bug/mesa%20bug.txt, which I fixed.
> 
> Second problem came that compiz would start automatically (I didn't
> invoke it) and that once it starts, windows can't be minimized or moved
> or anything and are surrounded by these black thick "borders/edges".

This is caused by the first run of compiz no enabling enough plugins.
Fixed in 0.8.4. You may have to enable decoration, move, ... in cssm.

Looks like you fixed other problems, so I am closing this bug.

Brice

--- End Message ---
Reply to: