Your message dated Sun, 7 Mar 2010 00:13:49 +0100 with message-id <20100306231349.ga15...@loulous.org> and subject line Re: Bug#482057: still reproducible? has caused the Debian Bug report #482057, regarding [compiz] compiz crashes when window are closed 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 ow...@bugs.debian.org immediately.) -- 482057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: compiz Version: 0.6.3~git20080115.0ea58487-1 Severity: grave --- Please enter the report below this line. ---Sometimes happens that compiz crashes; this happens when I close a window. In the logs I can find only: "compiz.real[3630]: segfault at 00000014 eip b79e95bb esp bfd20d70 error 4"--- System information. --- Architecture: i386 Kernel: Linux 2.6.24-1-686 Debian Release: lenny/sid 700 testing security.debian.org 700 testing ftp.it.debian.org 650 unstable ftp.it.debian.org 600 experimental ftp.it.debian.org --- Package information. --- Depends (Version) | Installed====================================================-+-================================== compiz-core (>= 0.6.3~git20080115.0ea58487-1) | 0.6.3~git20080115.0ea58487-1 compiz-gnome (>= 0.6.3~git20080115.0ea58487-1) | 0.6.3~git20080115.0ea58487-1compiz-gtk (>= 0.6.3~git20080115.0ea58487-1) | 0.6.3~git20080115.0ea58487-1compiz-plugins (>= 0.6.3~git20080115.0ea58487-1) | 0.6.3~git20080115.0ea58487-1<<attachment: paolo_sala.vcf>>
--- End Message ---
--- Begin Message ---On Fri, Jul 04, 2008 at 08:31:22PM +0200, sean finney wrote: > hi there, > > this is a bts housecleaning ping. you were asked to provide more information > on this bug but i suspect it may also be fixed in the latest version in > testing/unstable? > > could you clarify? if i don't hear back in some reasonable timeframe (say a > couple weeks) i will assume that it is fixed. of course the bug can always > be re-opened if this happens but my assumption is wrong. A couple years is not a reasonable timeframe, no reply, closing. Brice
--- End Message ---