Your message dated Fri, 13 Jan 2012 22:03:43 +1300
with message-id <20120113220343.29cbfff1@sidspace>
and subject line Re: using much too much CPU
has caused the Debian Bug report #434000,
regarding using much too much CPU
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.)
--
434000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434000
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vodovod
Version: 1.05-1
Severity: important
While using vodovod my system is more or less dead since vodovod
together with Xorg are using roughly 100% CPU:
10015 root 5 -10 85680 30m 5528 S 75.1 4.0 29:46.65 Xorg
11696 tpo 19 0 21416 9048 4288 R 22.1 1.2 10:54.50 vodovod
I don't know whether that is vodovod or whether it has to do with my
Xorg setup. Can others confirm this.
Nice, "simple" and stressy game otherwise,
*t
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages vodovod depends on:
ii libc6 2.6-2 GNU C Library: Shared libraries
hi libgcc1 1:4.2-20070712-1 GCC support library
ii libsdl-image1.2 1.2.5-3 image loading library for Simple D
ii libsdl1.2debian 1.2.11-8 Simple DirectMedia Layer
ii libstdc++6 4.2-20070712-1 The GNU Standard C++ Library v3
vodovod recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.10-2
Hi,
I have been unable to reproduce this bug using version 1.10-2 of
vodovod, I get a reasonable CPU usage of 10%~. The bug submitter was
using version 1.05-1 and there have been no further reports of this
issue.
On that basis I am closing this bug and marking it fixed
in the current version.
If you believe this is a mistake please reopen the bug by sending an
email to [email protected] with the pseudo-headers:
reopen 434000
thanks
--
Thanks,
Dean
--- End Message ---
