This seems to be triggered by connecting an external monitor over
DisplayPort, then disconnecting. And rebooting does indeed clear the
problem.

-- 
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/1737264

Title:
  ALSA output is silent but SDL works fine

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Gnome error sounds do play, but sound output from Firefox and other
  applications doesn't work unless they can support a non-ALSA sound
  driver. E.g. mplayer makes no sound unless the "-ao sdl" or "-ao
  openal" parameter is added. ALSA and PulseAudio don't work.

  Reloading the ALSA kernel modules doesn't fix the problem.

  # alsa force-reload
  /sbin/alsa: Warning: Processes using sound devices: 1808(pulseaudio). 
  Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-soc-rt5640 
snd-soc-rl6231 snd-soc-core snd-hda-codec-conexant snd-hda-codec-generic 
snd-hda-intel snd-hda-codec snd-compress snd-pcm-dmaengine snd-hda-core 
snd-hwdep snd-seq-midi snd-seq-midi-event snd-pcm snd-rawmidi snd-seq 
snd-seq-device snd-timer snd-soc-sst-acpi snd-soc-sst-match (failed: modules 
still loaded: snd-hda-codec-hdmi snd-hda-codec-conexant snd-hda-codec-generic 
snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer).
  Loading ALSA sound driver modules: snd-hda-codec-hdmi snd-soc-rt5640 
snd-soc-rl6231 snd-soc-core snd-hda-codec-conexant snd-hda-codec-generic 
snd-hda-intel snd-hda-codec snd-compress snd-pcm-dmaengine snd-hda-core 
snd-hwdep snd-seq-midi snd-seq-midi-event snd-pcm snd-rawmidi snd-seq 
snd-seq-device snd-timer snd-soc-sst-acpi snd-soc-sst-match.

  Unloading the kernel modules manually also fails.

  # rmmod snd-hda-codec-hdmi snd-hda-codec-conexant snd-hda-codec-generic 
snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer
  rmmod: ERROR: Module snd_hda_codec_hdmi is in use
  rmmod: ERROR: Module snd_hda_codec_conexant is in use
  rmmod: ERROR: Module snd_hda_codec_generic is in use by: 
snd_hda_codec_conexant
  rmmod: ERROR: Module snd_hda_intel is in use
  rmmod: ERROR: Module snd_hda_codec is in use by: snd_hda_intel 
snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_codec_generic
  rmmod: ERROR: Module snd_hda_core is in use by: snd_hda_intel 
snd_hda_codec_conexant snd_hda_codec snd_hda_codec_hdmi snd_hda_codec_generic
  rmmod: ERROR: Module snd_hwdep is in use by: snd_hda_codec
  rmmod: ERROR: Module snd_pcm is in use by: snd_hda_intel snd_hda_codec 
snd_pcm_dmaengine snd_hda_core snd_soc_rt5640 snd_hda_codec_hdmi snd_soc_core
  rmmod: ERROR: Module snd_timer is in use by: snd_seq snd_pcm

  No HDMI device is currently connected, but one was a few days ago.
  There have been several suspend-resume cycles since then.

  I expect that rebooting will clear this issue, however obviously that
  shouldn't be needed with Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  pmj        1808 F.... pulseaudio
   /dev/snd/pcmC1D0c:   pmj        1808 F...m pulseaudio
   /dev/snd/controlC1:  pmj        1808 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Dec  9 10:03:15 2017
  InstallationDate: Installed on 2016-12-02 (370 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [UX303LAB, Conexant CX20751/2, Black Headphone Out, Right] Playback 
problem
  UpgradeStatus: Upgraded to artful on 2017-10-12 (57 days ago)
  dmi.bios.date: 08/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LAB.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LAB.210:bd08/25/2015:svnASUSTeKCOMPUTERINC.:pnUX303LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737264/+subscriptions

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

Reply via email to