Well that's interesting, it looks like your audio device might have a dfu mode. I wonder if that's the case for the other reporters. Can you please also share lsusb output? Everyone affected it would be great to share both of these so that upstream can make sense of common denominations to figure what's actually going on.
On Sat, May 28, 2016, 13:50 Taras <taras.za...@gmail.com> wrote: > Hi Mario, I believe the > https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1574079/comments/20 > debug output is not complete. Please see the log: > > ... > 21:26:16 15 com.hughski.ColorHugALS.firmware ColorHugALS > 21:26:30 waiting a small time for other providers > 21:26:30 using b69159f2-3778-5728-80d0-01be18b2ea30 for > USB\VID_1397&PID_0501 > 21:26:30 emit added from DFU: usb:00:01:03 > 21:26:31 no product string descriptor > 21:26:33 Called GetUpdates() > (END) > > Here I've also tried to connect my USB sound-card BEHRINGER UMC204 at > 21:26:30. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1574079 > > Title: > USB audio device is not recognized after startup in 16.04 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+subscriptions > -- 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/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Confirmed Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F.... pulseaudio /dev/snd/controlC0: tobias 1553 F.... pulseaudio /dev/snd/controlC2: tobias 1553 F.... pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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
