From: "Nikita N." <nikitan@operamail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: bug
Date: Tue, 31 Mar 2015 01:56:01 -0700 [thread overview]
Message-ID: <1427792161.2150884.247436393.3D8D2571@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503311008160.13892@lnxricardw1.se.axis.com>
> First of all, I can't say I'm representing the ALSA project or anyone else
> in this matter, so the following is just my personal opinion.
As we already wrote, we are not blaming you or ALSA.
> particular mixer application such as alsamixergui, but should be able to
> happen with any mixer application, given the appropriate settings.
That is indeed what we are afraid, if anybody will have the brilliant
idea to reverse engineer that tool to a more damaging level in a
virus/malware , and make its effect unstoppable.
> Secondly, if you believe that alsamixergui specifically is missbehaving,
> why don't you just take it out of your distribution (dCore)?
as we wrote, we are going to do this.
> Given the proliferation of cheap PC hardware this is not surprising
as you say, given the proliferation of cheap PC hardware, a
proliferation of such virus/malware could upset not only our users.
> it is hardly a software problem.
I personally don't agree with that.
As we wrote, not everybody is omniscient, I personally was not aware of
this issue, before was pointed out.
Without warnings, even a Teddy Bear can be dangerous.
> alsamixergui is not created by the ALSA
> project, so this mailing list is the wrong place to look if none other
> than for that particular reason.
Sure, we would be very grateful if you could point that out, so we can
contact the individual who programmed this tool
Unless it's not a secret or there is smtng to hide.
--
Nikita N.
nikitan@operamail.com
On Tue, Mar 31, 2015, at 01:24 AM, Ricard Wanderlof wrote:
>
> On Mon, 30 Mar 2015, Nikita N. wrote:
>
> > We are the devs involved in dCore porting, and that is one of our users
> > report:
> > http://forum.tinycorelinux.net/index.php/topic,18225
> >
> > We verified that in few of our legacy laptops.
> > It didn't reproduce for every laptop, but indeed in a couple of them,
> > the temperature of the speakers reached extremes levels in few seconds,
> > only unplugging the AC/DC cable saved them.
> > This is a serious problem in our opinion, and we would hate to see our
> > dCore reputation spoiled.
> > We hate to admit, but it is *NOT* our bug, and would hate to see this
> > bug reverse engineered into a virus/malware (on Linux, or other OS) and
> > see ourselves blamed for it.
> > So we would like to keep the incident quiet, and we are going to remove
> > that thread from our forum.
> > On the other side, we would expect any action from ALSA project in
> > removing that tool and/or exposing the real individual/s guilty of
> > writing that tool.
>
> First of all, I can't say I'm representing the ALSA project or anyone
> else
> in this matter, so the following is just my personal opinion. Furthermore
> I have no real experience with the mixer application under discussion
> (alsamixergui), but on the face of it it just looks like any mixer
> application.
>
> From the thread linked above, it seems that if someone maxes out all
> controls in the mixer, this results in a high-pitched whine in the
> speakers, which on certain laptops seem to cause the destruction of
> something in the machine (likely the speakers themselves). It is further
> speculated in the thread that what might be happening is acoustic
> feedback
> from the speakers to the microphone, which would make sense given the
> results, but would seem strange from a system design point of view.
>
> First of all, it would seem that this wouldn't be dependent on a
> particular mixer application such as alsamixergui, but should be able to
> happen with any mixer application, given the appropriate settings.
>
> Secondly, if you believe that alsamixergui specifically is missbehaving,
> why don't you just take it out of your distribution (dCore)?
>
> Thirdly, and perhaps most importantly, this seems to be a hardware
> problem. If the drive capability of the laptops's output stage is too
> much
> for the speakers, then there is a serious design flaw in the hardware.
> Given the proliferation of cheap PC hardware this is not surprising, but
> it is hardly a software problem.
>
> And finally, as Clemens said, alsamixergui is not created by the ALSA
> project, so this mailing list is the wrong place to look if none other
> than for that particular reason.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden www.axis.com
> Phone +46 46 272 2016 Fax +46 46 13 61 30
--
http://www.fastmail.com - Or how I learned to stop worrying and
love email again
next prev parent reply other threads:[~2015-03-31 8:56 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 14:03 bug Nikita N.
2015-03-30 7:19 ` bug Clemens Ladisch
2015-03-30 10:27 ` bug Nikita N.
2015-03-30 11:13 ` bug Clemens Ladisch
2015-03-30 14:37 ` bug Nikita N.
2015-03-31 7:18 ` bug Eliot Blennerhassett
2015-03-31 8:19 ` bug Nikita N.
2015-03-31 8:38 ` bug Clemens Ladisch
2015-03-31 9:05 ` bug Nikita N.
2015-03-31 12:42 ` bug Clemens Ladisch
2015-03-31 8:41 ` potential speaker burnout Eliot Blennerhassett
2015-03-31 8:24 ` bug Ricard Wanderlof
2015-03-31 8:56 ` Nikita N. [this message]
2015-03-31 9:14 ` bug Ricard Wanderlof
2015-03-31 10:26 ` bug Maarten de Boer
2015-03-31 10:49 ` bug Nikita N.
2015-03-31 11:05 ` bug Maarten de Boer
2015-03-31 11:44 ` bug Ricard Wanderlof
2015-03-31 8:54 ` bug Eliot Blennerhassett
2015-03-31 9:34 ` Speaker burnout David Henningsson
2015-03-31 10:06 ` Nikita N.
2015-03-31 10:43 ` David Henningsson
2015-03-31 10:57 ` Alexander E. Patrakov
2015-03-31 11:23 ` Nikolay Dimitrov
2015-03-31 11:31 ` Ricard Wanderlof
2015-03-31 11:45 ` David Henningsson
2015-03-31 13:47 ` Torsten Schenk
2015-03-31 19:14 ` Nikita N.
2015-04-05 16:36 ` Takashi Iwai
2015-04-05 16:11 ` Takashi Iwai
2015-04-07 5:30 ` Eliot Blennerhassett
2015-04-07 7:09 ` David Henningsson
2015-04-07 7:26 ` Clemens Ladisch
2015-04-07 7:49 ` Eliot Blennerhassett
2015-04-07 10:55 ` David Henningsson
2015-04-07 11:29 ` Ricard Wanderlof
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 16:10 BUG Alex Marginean
2020-11-04 17:02 ` BUG Randall S. Becker
2020-11-04 17:54 ` BUG Randall S. Becker
2020-06-26 21:11 bug Luke Knoble
2019-09-02 3:52 bug liebrecht
2016-11-02 15:04 Bug H-P.Teufel
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Bug Santiago Torres
2016-09-14 22:14 ` Bug Dennis Kaarsemaker
2016-08-19 20:44 Bug Leonard Bocock
2016-08-23 10:41 ` Bug Luiz Augusto von Dentz
2016-08-24 8:15 ` Bug Leonard Bocock
2013-11-29 11:28 Bug Otártics András
2013-11-29 11:56 ` Bug Gleb Natapov
2013-10-18 18:53 bug squadrato
2013-08-29 2:34 bug lilofile
2013-08-29 2:43 ` bug Liu Bo
2013-08-29 12:25 ` bug David Sterba
[not found] <520268D8.3000807@gmail.com>
2013-08-07 17:14 ` bug Mattia Bertoni
2013-08-08 8:44 ` bug Mattia Bertoni
2013-08-08 9:00 ` bug Takashi Iwai
2013-08-08 9:55 ` bug Mattia Bertoni
2013-08-08 10:12 ` bug Takashi Iwai
2013-08-08 10:44 ` bug Mattia Bertoni
2013-08-08 10:49 ` bug Takashi Iwai
2013-06-11 15:11 BUG Mark Murawski
2013-06-12 8:38 ` BUG Duncan
2011-12-19 18:02 Bug Володимир Остап
2011-09-10 13:13 Bug Guido Telscher
2009-11-30 20:39 BUG Plamen Vasilev
2009-07-24 20:28 Bug Steven Pratt
2009-07-24 20:29 ` Bug Chris Mason
2008-08-16 8:36 Bug Artjom
[not found] <E1JF7vM-0000k1-Mc@linuxtogo.org>
2008-01-17 11:18 ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Paul Sokolovsky
2008-01-17 11:57 ` Bug ohviey1
2006-01-12 15:23 bug Philippe Delodder
2006-01-14 1:01 ` bug Adrian Bunk
2005-05-19 6:24 bug Victor G. Marimon
2005-05-19 6:24 ` bug Victor G. Marimon
2005-05-19 6:24 ` bug Jean Delvare
2005-05-19 6:24 ` bug Jean Delvare
2005-05-19 6:24 ` bug Victor G. Marimon
2005-05-19 6:24 ` bug Jean Delvare
2005-03-23 10:41 bug Jan Boros
2005-03-23 10:54 ` bug Kay Sievers
2004-01-10 19:54 Bug Tyler Harmor
2004-01-10 21:07 ` Bug Ryan Underwood
2002-03-19 21:20 bug Виталий
2001-09-07 18:42 BUG Attila A Odry
2001-01-31 22:50 BUG Grzegorz Sojka
2001-01-31 23:18 ` BUG James Sutherland
2001-02-01 11:04 ` BUG Maciej W. Rozycki
2001-02-01 11:49 ` BUG Zdenek Kabelac
1998-09-04 18:51 Bug Ulf Carlsson
1998-09-04 21:25 ` Bug ralf
1998-04-03 22:11 fwd: Andreessen Sees Mozilla-Linux Upset Of Windows ralf
1998-04-04 16:30 ` bug Ulf Carlsson
1998-04-04 15:59 ` bug ralf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1427792161.2150884.247436393.3D8D2571@webmail.messagingengine.com \
--to=nikitan@operamail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ricard.wanderlof@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.