Whats even more interesting, Apport was able to play test noise via USB
headset right after connecting but Settings nor Firefox cant.

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

Title:
  USB headset doesnt work after connecting

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After connecting USB headset ubuntu doesnt switch to it but rather
  audio goes completely nuts. Changing output device in settings doesnt
  help, audio is gone. After several replugs and system reboot audio is
  back on usb headset but then after disconnecting it I cant get my rear
  jack to work without juggling with output device in settings and
  (again) a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.7.15-xanmod1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 26 23:04:38 2020
  InstallationDate: Installed on 2019-11-19 (281 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Device successful
  Symptom_Card: Bloody Gaming Audio Device - Bloody Gaming Audio Device
  Symptom_DevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC2:  andrzej    1465 F.... pulseaudio
   /dev/snd/controlC1:  andrzej    1465 F.... pulseaudio
   /dev/snd/controlC0:  andrzej    1465 F.... pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - Bloody Gaming Audio Device, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-15 (103 days ago)
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.J0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd10/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-11-21T21:34:52.015266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893134/+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

Reply via email to