Bug#660520: marked as done (audacious: Fails to start with "FATAL: No output plugin found." due to plugins not in multiarch paths)

[Debian Bug Tracking System]

Your message dated Tue, 21 Feb 2012 15:21:00 +0100
with message-id <20120221142100.GA19910 at alessio-laptop>
and subject line Closing #660520
has caused the Debian Bug report #660520,
regarding audacious: Fails to start with "FATAL: No output plugin found." due to plugins not in multiarch paths
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 owner at bugs.debian.org
immediately.)


-- 
660520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660520
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Axel Beckert <abe at debian.org>
Subject: audacious: Fails to start with "FATAL: No output plugin found." due to plugins not in multiarch paths
Date: Sun, 19 Feb 2012 18:06:02 +0100
Size: 6706
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20120221/eadfe3ae/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Alessio Treglia <alessio at debian.org>
Subject: Closing #660520
Date: Tue, 21 Feb 2012 15:21:00 +0100
Size: 3553
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20120221/eadfe3ae/attachment-0001.mht>