[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2018-10-28 Thread Sergio
Ran into this issue with Audacity 2.2.1 on Ubuntu 18.04. Restarting doesn't fix it. Headphones were detected but didn't work. Steps to Fix: * Open Audacity. Set source to "default: internal mic: 0" * Close Audacity * Open Audacity again. Suddenly headphones start working -- You received this

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2018-05-29 Thread Lorenzo
Editing source in audacity to "pulse: Internal Mic 0" works on Ubuntu 18.04 and official audacity packager from their ppa version: 2.2.2-1build1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2018-02-26 Thread adrya
I just installed Audacity to make a quick edit on an a MP3 file. I installed 2.1.2 from the default Linux Mint repo, opened Audacity and selected my file. It played over my headphones just fine. I closed Audacity, then immediately opened it again to select a different file to edit. As

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2017-04-24 Thread Kay
I also ran into this issue yesterday on a Dell XPS13. It is nothing Audacity specific and you can easily trigger this yourself by just running 'amixer -c 0 set "Headphone Mic" cap' or starting alsamixer, switching to the capture devices and activating the "Headphone Mic" by pressing Space on it.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2017-04-21 Thread Anton
I just ran headlong into this same issue on Ubuntu 16.04 LTS using Audacity 2.1.2 on my Dell XPS15. When inserting a jack, I get a dialogue box asking whether I have a headphone, headset, or mic inserted (apparently an external amp with speakers should be considered 'headphones', but that's a

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-12-17 Thread Ljiljan Veselinovic
The same happened to me today when I installed audacity. I am using Ubuntu 14.10. The problem was solved from comment number #12: I went into Audacity and changed the microphone source in the drop-down menu from sysdefault: Headphone Mic:0 to sysdefault: Internal Mic:0 and it fixed it.! --

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-05-23 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-24 Thread Stéphane Guillou
Dear all, thanks to Ramond's comments, I went into Audacity and changed the microphone source in the drop-down menu from sysdefault: Headphone Mic:0 to sysdefault: Internal Mic:0 and it fixed it. I can now use my headphones, even when I restard Audacity. We should still fix that because it is

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-24 Thread Raymond
if there is only one jack , why do the driver just implement headphone mic jack mode switch since it is possible to implement a jack mode switch which allow you to retask the jack as headphone, line out, mic or line in jack. -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-24 Thread Raymond
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=7369a53ab5f606e87a3cd1cd4eebd40226bab090 http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=ca4942e89cf462e5f8c36ca9b8b689879083af6b it seem that you need to create two jack detection controls instead of one headphone mic

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-24 Thread Raymond
you should continue your discussion if you think the fix is confusing https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1018262 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-23 Thread Stéphane Guillou
Hi Raymond Thank you for looking into this. It is true that my Asus F201E has only one jack port for mic + headphones. However, I am no developer and I find it hard to understand. - What can average users do to momentarily fix the problem? - What should we do to get the issue fixed? Is the

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-23 Thread Raymond
Have you ask the author of the patch ? since it is not clear to user that switching Capture Source from headphome mic to internal mic can retasked mic to headphone it is more user friendly to use headphone mic jack mode to switch between headphone and mic -- You received this bug notification

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-23 Thread Raymond
jn addition, auto mute should be automatically disabled when the jack is retasled as mic. internal mic should be automatically be seleected when the jack is retasked as headphone -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-23 Thread Raymond
you also need pulseaudio know the jack is can be retasked as headphone or mic by user if the codec cannot differentiate the headphone and mic when plugged https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda?qt=grepq=HEADPHONE+MIC -- You received this bug notification

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-22 Thread Raymond
if your asus 1005px has only one jack for (headphone/mic in ) the jack has been retasked from headphone jack to mic jack ode 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out Control: name=Headphone Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-22 Thread Raymond
** Package changed: pulseaudio (Ubuntu) = alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-21 Thread Jean van Kasteel
I'm also affected by this, using Ubuntu Unity 13.10. The only way to make it work again is to reinstall. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-21 Thread Raymond
https://wiki.ubuntu.com/Audio/AlsaInfo https://wiki.ubuntu.com/PulseAudio/Log ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-21 Thread Jean van Kasteel
- alsa log created with 'alsa-info.sh' : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones : http://paste.ubuntu.com/7131713/ ** Description changed: I'm running 13.10 and the latest GNOME. I've just fresh

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-21 Thread Stéphane Guillou
Hi there The following was collected after using audacity, witnessing the bug (no sound on headphones), getting out of Audacity, trying sound with other software with no success, unplugging the headphones and getting sound out of the speakers, and testing the headphones again to no avail. - Alsa

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu.

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2014-03-04 Thread Stéphane Guillou
I have the exact same problem. I was not sure what it came from at the beginning but today it was clearly Audacity that stops my headphone port from working. I was listening to music before through the same headphones, with different apps. As soon as I opened the same sound with Audacity, my