Your message dated Wed, 03 Aug 2011 12:22:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#613771: muroard takes too much CPU time
has caused the Debian Bug report #613771,
regarding muroard takes too much CPU time
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.)


-- 
613771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613771
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: muroard
Version: 0.1.3-2
Severity: normal

In its default configuration, muroard constantly takes about 45% CPU
(even when there's no sound).

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages muroard depends on:
ii  libao4                        1.0.0-5    Cross Platform Audio Output Librar
ii  libc6                         2.11.2-11  Embedded GNU C Library: Shared lib

muroard recommends no packages.

Versions of packages muroard suggests:
pn  libmuroar0                    <none>     (no description available)
pn  roaraudio                     <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
reassign 613771 linux-latest-2.6
thanks

On Thu, 2011-02-17 at 04:38 +0100, Vincent Lefevre wrote:
> Package: muroard
> Version: 0.1.3-2
> Severity: normal
> 
> In its default configuration, muroard constantly takes about 45% CPU
> (even when there's no sound).

This bug was not a µRoarD bug but somethin within ALSA somwhere within
the kernel. I was told it was fixed in 2.6.39. It seems it can not be
reproduced by new kernels.

Thanks for everyone who was working on this bug!

-- 
Philipp.
 (Rah of PH2)

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


--- End Message ---

Reply via email to