All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten de Boer <maarten@resorama.com>
To: "Nikita N." <nikitan@operamail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: bug
Date: Tue, 31 Mar 2015 13:05:53 +0200	[thread overview]
Message-ID: <677D3730-B814-4E64-8746-12FE30C13C23@resorama.com> (raw)
In-Reply-To: <1427798995.588863.247475933.12C0B9B0@webmail.messagingengine.com>

Hi,

As I tried to explain, this is not specific for alsamixergui, and it is not a bug, as it is a hardware problem. There is no way for the software to know what would be these “hazardous” levels, as this is hardware specific. And again, alsamixergui is just a graphical frontend. The command line alsamixer does the same thing.

Maarten

On 31 Mar 2015, at 12:49, Nikita N. <nikitan@operamail.com> wrote:

> Dear Maarten de Boer,
> as you read from many voices here, your software is verified can damage
> the speakers, if not used somehow correctly.
> The definition of correctly is still to us unknown, nor you are giving
> us any hope in that.
> We were hoping in some form of amend from yourself, about the dangerous
> software you produced and distributed to public.
> We were hoping in some form of bug fix or any professional approach to
> solving that issue.
> We were hoping at least in a simple warning popping up from your tool,
> when user sets any "hazardous" levels.
> We were hoping at least-least in a warning popping up from your tool at
> runtime, something like "Warning: improper settings for this level, this
> level and this might result in damages to your audio devices".
> But, we only see a nice turnaround "There is not much that I can add".
> Your program does not respect the minimum requirement for a software to
> be published, such as being "reasonably" bug free.
> As for "bug" is intended a software which is limited in creating
> software problems.
> While instead, your tool expands to a whole new, and more dangerous
> level - hardware damage.
> Hence your software, as is, doesn't respect our Debian/Ubuntu
> philosophy.
> So, at this point "There is not much that" we can add.
> We also wish you "Good luck with that."
> 
> On Tue, Mar 31, 2015, at 03:26 AM, Maarten de Boer wrote:
>> Hello,
>> 
>> I am the author of alsamixergui. I am not actively maintaining
>> alsamixergui anymore (and haven’t been for years). It is pretty much
>> coincidence that I saw this mail thread; a slightly more informative
>> subject would have helped.
>> 
>> There is not much that I can add to this thread (thanks everyone for your
>> replies), but in short:
>> 
>> - alsamixergui is just a graphical frontend, and exposes the mixer
>> capabilities of the sound card in the same way alsamixer, amixer or any
>> other alsa mixer does, so this is not alsamixergui specific. (strongly
>> based on the alsamixer code (verbatim) with fltk gui code added to it.).
>> 
>> - this is not a software problem, this is a hardware problem. The user
>> adjusts the mixer to cause a feedback between speaker and internal
>> microphone, and leaves this running for >30 seconds, and his hardware
>> can’t deal with it. It is probably not even operating system specific.
>> 
>> Finally, I really don’t like the tone you use, Nikita, particularly your
>> talk of “exposing the individuals guilty” and your accusations of
>> secrecy. And "expose clearly to the public that tool as a virus/malware,
>> and inform the antivirus authorities about it.”, really? Good luck with
>> that.
>> 
>> If you want to blacklist alsamixergui from your distro, please go ahead,
>> but don’t forget to blacklist alsamixer and amixer too, as well as any
>> other alsa mixer front ends.
>> 
>> Maarten
>> 
>> 
>> On 31 Mar 2015, at 11:14, Ricard Wanderlof <ricard.wanderlof@axis.com>
>> wrote:
>> 
>>> 
>>> On Tue, 31 Mar 2015, Nikita N. wrote:
>>> 
>>>>> 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.
>>> 
>>> I have no idea who wrote it, Clemens posted a link but at to me it seems 
>>> dead, there should be something in the source code (perhaps that's where 
>>> he got it frome?). Could very well be that it was written by someone who 
>>> has since moved on to other things so that any links or email adresses are 
>>> outdated. It's not necessarily a secret, it could just be unknown at this 
>>> point, and if the person who wrote it is not actively maintaining it any 
>>> more there's probably little to be gained from contacting him.
>>> 
>>> /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
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>> 
> 
> -- 
> http://www.fastmail.com - Access all of your messages and folders
>                          wherever you are
> 

  reply	other threads:[~2015-03-31 11:06 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           ` bug Nikita N.
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                   ` Maarten de Boer [this message]
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 Jean Delvare
2005-05-19  6:24 ` bug Victor G. Marimon
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=677D3730-B814-4E64-8746-12FE30C13C23@resorama.com \
    --to=maarten@resorama.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nikitan@operamail.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.