[Touch-packages] [Bug 912232] Re: Audio output fails on resume from hibernate, Dell Vostro, Ubuntu 11.10

2017-07-09 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/912232

Title:
  Audio output fails on resume from hibernate, Dell Vostro, Ubuntu 11.10

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Platform: Ubuntu 11.10 running latest ALSA, PulseAudio and outputting
  via a M-Audio Delta 1010LT soundcard.

  Trigger: On resuming a session from hibernate

  Expected behaviour: I should be able to output audio from the selected
  default device in Settings -> Sound, much as I was able to do so
  before hibernating.

  Actual behaviour: Unable to get any audio from M-Audio 1010LT. Going
  to Settings -> Sound and reselecting the device fails to enable audio
  output. Killing pulseaudio from terminal (pulseaudio -k) which causes
  a respawn fails to correct issue.

  
  Essentially it's high time we sorted out this Linux audio joke of a 
configuration. Many many people have spoken about and recognised the need to do 
this, but only Canonical & Ubuntu really have the power to do it. PulseAudio / 
ALSA / Jack constantly compete for exclusive access to sound devices, which is 
no wonder the spaghetti network fails on resume.

  I'd suggest binning Pulseaudio / Gstreamer etc entirely, and reducing
  audio management down to two layers: the driver, and the mixer. ALSA
  does both nicely. Develop a GUI mixer for ALSA as the standard Ubuntu
  desktop mixer, and develop a Pulseaudio like ALSA plugin that allows
  programs which will normally only talk to Pulseaudio, think that ALSA
  is Pulseaudio. Also force ALSA to select default sound device by name
  rather than by hw:# identity which can change on reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/912232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 912232] Re: Audio output fails on resume from hibernate, Dell Vostro, Ubuntu 11.10

2017-05-10 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/912232

Title:
  Audio output fails on resume from hibernate, Dell Vostro, Ubuntu 11.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Platform: Ubuntu 11.10 running latest ALSA, PulseAudio and outputting
  via a M-Audio Delta 1010LT soundcard.

  Trigger: On resuming a session from hibernate

  Expected behaviour: I should be able to output audio from the selected
  default device in Settings -> Sound, much as I was able to do so
  before hibernating.

  Actual behaviour: Unable to get any audio from M-Audio 1010LT. Going
  to Settings -> Sound and reselecting the device fails to enable audio
  output. Killing pulseaudio from terminal (pulseaudio -k) which causes
  a respawn fails to correct issue.

  
  Essentially it's high time we sorted out this Linux audio joke of a 
configuration. Many many people have spoken about and recognised the need to do 
this, but only Canonical & Ubuntu really have the power to do it. PulseAudio / 
ALSA / Jack constantly compete for exclusive access to sound devices, which is 
no wonder the spaghetti network fails on resume.

  I'd suggest binning Pulseaudio / Gstreamer etc entirely, and reducing
  audio management down to two layers: the driver, and the mixer. ALSA
  does both nicely. Develop a GUI mixer for ALSA as the standard Ubuntu
  desktop mixer, and develop a Pulseaudio like ALSA plugin that allows
  programs which will normally only talk to Pulseaudio, think that ALSA
  is Pulseaudio. Also force ALSA to select default sound device by name
  rather than by hw:# identity which can change on reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/912232/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp