Description of problem:

> I ran alsa-info.
>
> First it tells me that it's going to automatically upload the results to a
> pastebin site, then it asks me if I want to continue to run the script.
> Strike 1.  It should have defaulted to no, and just ran.  It's just
> outputting info, there's no need to protect me from myself.
>
> Next, I run with the --no-upload option, cursing the damn thing out while I
> do, and then it asks me again, do I want to run the script?  Yeah I want to
> run the script, I *typed the command*.  What is it protecting me from???
>
> So then, it runs, and outputs the data into a file.  Into a *file*?  WTF
> happened to the unix idiom of sending things to stdout unless you
> specifically give it a "-f" option?
>
> I know you guys don't write alsa.  I'm not saying you're responsible for
> this.  What I am saying is that for a long time sysadmin like me, this is
> really a step backwards.  I just want to debug a fricking pulseaudio/alsa
> problem.  Don't protect me from myself when the worst that's going to happen
> is that I get stuff printed to the screen that I don't care about.
>
Version-Release number of selected component (if applicable):

1.0.16-3

How reproducible:

Completely.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: