Your message dated Fri, 6 Jan 2012 17:08:05 +0100
with message-id <[email protected]>
and subject line Re: wmaker: Autoraising clip icons freeze with kernel 2.6.5
has caused the Debian Bug report #245409,
regarding wmaker: Autoraising clip icons freeze with kernel 2.6.5
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.)
--
245409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245409
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wmaker
Version: 0.80.1-8
Severity: important
With 2.6.5 kernel, when hovering mouse over clip to raise icons, it
freezes with cpu usage going up. It is possible to Ctrl-Alt-F1 to
console though
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.4-1-k7
Locale: LANG=C, LC_CTYPE=C
Versions of packages wmaker depends on:
ii cpp 4:3.3.3-2 The GNU C preprocessor (cpp)
ii debianutils 2.8.1 Miscellaneous utilities specific t
ii hermes1 1.3.3+really1.3.2-2 The Hermes pixel-format library
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpng12-0 1.2.5.0-5 PNG library - runtime
ii libtiff3g 3.6.1-1 Tag Image File Format library
ii libungif4g 4.1.0b1-6 shared library for GIF images (run
ii libwraster2 0.80.1-8 Shared libraries of Window Maker r
ii xlibs 4.3.0-7 X Window System client libraries m
ii zlib1g 1:1.2.1-5 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2006-10-16 Srdjan <[email protected]> wrote:
> Gürkan Sengün wrote:
>> So this bug doesn't happen since some time? Can we close it?
>>
> Sure, it went away with the next version.
[...]
Let's actually close it, then.
cu andreas
--- End Message ---
