Your message dated Wed, 25 Aug 2010 05:51:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#431694: Windec broken when maximized
has caused the Debian Bug report #431694,
regarding Windec broken when maximized in compiz/nvidia
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 [email protected]
immediately.)


-- 
431694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: compiz-kde
Version: 0.5.0.dfsg-1
Severity: normal

--- Please enter the report below this line. ---
Here's a screenshot of the problem, the iceweasel window is maximized.
As you can see the windec has a black irritation. I'm using the plastic
windec, but the problem is reproducible with many others. If you set the
windowborder thicker on windecs where this option is available, the
black line becomes thicker too.

  http://debian.org/~venthur/stuff/2007-07-compiz-windec-bug.png

I'm invoking compiz the following way:

  compiz --replace gconf & kde-window-decorator --replace &

the problem is always reproducible with all windows. It does not appear
to happen when using the gkt-window-decorator.

Cheers,

Bastian

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.18-4-686

Debian Release: lenny/sid
  500 unstable        www.debian-multimedia.org
  500 unstable        ftp.de.debian.org
    1 experimental    ftp.de.debian.org

--- Package information. ---
Depends                           (Version) | Installed
===========================================-+-=======================
compiz-core                (= 0.5.0.dfsg-1) | 0.5.0.dfsg-1
kdelibs4c2a                  (>= 4:3.5.6-1) | 4:3.5.7.dfsg.1-1
kwin                         (>= 4:3.5.5-1) | 4:3.5.7-1
libaudio2                                   | 1.9-2
libc6                            (>= 2.5-5) | 2.5-11
libdbus-1-3                       (>= 0.94) | 1.1.1-3
libdbus-qt-1-1c2     (>= 0.62.git.20060814) | 0.62.git.20060814-2
libdecoration0                              | 0.5.0.dfsg-1
libfontconfig1                   (>= 2.4.0) | 2.4.2-1.2
libgcc1                 (>= 1:4.2-20070516) | 1:4.2-20070627-1
libice6                        (>= 1:1.0.0) | 1:1.0.3-2
libpng12-0                    (>= 1.2.13-4) | 1.2.15~beta5-2
libqt3-mt                      (>= 3:3.3.7) | 3:3.3.7-5
libsm6                                      | 2:1.0.3-1
libstdc++6                (>= 4.2-20070516) | 4.2-20070627-1
libx11-6                                    | 2:1.0.3-7
libxcomposite1                 (>= 1:0.3-1) | 1:0.3.2-1
libxcursor1                      (>> 1.1.2) | 1:1.1.8-2
libxdamage1                      (>= 1:1.1) | 1:1.1.1-3
libxext6                                    | 1:1.0.3-2
libxfixes3                     (>= 1:4.0.1) | 1:4.0.3-2
libxft2                          (>> 2.1.1) | 2.1.12-2
libxi6                                      | 1:1.0.1-4
libxinerama1                                | 1:1.0.2-1
libxrandr2                     (>= 2:1.2.0) | 2:1.2.1-1
libxrender1                                 | 1:0.9.2-1
libxt6                                      | 1:1.0.5-3
zlib1g                         (>= 1:1.2.1) | 1:1.2.3.3.dfsg-3


-- 
Bastian Venthur                                      http://venthur.de
Debian Developer                                 venthur at debian org



--- End Message ---
--- Begin Message ---
Hi,

this bug was reported against a very old version of the 
nvidia-graphics-drivers package in Debian. We asked some months ago whether 
this problem is still reproducible in the current version of the driver, but 
didn't get any new information. Therefore, I assume the problem has been 
solved by a new upstream release and/or packaging updates and I'll close this 
report now.

If you are still able to reproduce this problem with current versions of the 
driver, kernel and X.Org, feel free to provide additional information and 
reopen this report.


Andreas


--- End Message ---

Reply via email to