This ist still not fixed
I removed fwupd and rebooted, then it worked.
ubuntu 18.04.1 LTS
In case you are helped with infos I can provide them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
T
My Usb Audio is still not working im new to ubuntu so unsure how to fix
it Please can someone help me
Im using a Logitech G930 Headset - Wireless Usb Version.
Im running Ubuntu 16.10 Xenial
Im Using a Dell Optiplex 755 DT Please see specs AT THIS LINK
http://pastebin.com/SEFMvJDq
Ubuntu Software
** Package changed: fwupdate-signed (Ubuntu) => fwupd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notif
** Package changed: fwupd (Ubuntu) => fwupdate-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notif
This bug was fixed in the package fwupd - 0.7.0-0ubuntu4.2
---
fwupd (0.7.0-0ubuntu4.2) xenial-proposed; urgency=medium
* Fix USB audio devices not working properly (LP: #1574079)
-- Mario Limonciello Wed, 08 Jun 2016
21:31:00 -0500
** Changed in: fwupd (Ubuntu Xenial)
S
Thanks. So everyone who has enabled proposed is fi Ed. I think it's safe
to roll this out to updates now. We've waited 10 says with it in
proposed and no regressions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I followed the instructions carefully and it is fixed now. My Oppo
Digital HA-1 and Chord Mojo just work right out of the box after
enabling xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I enabled xenial-proposed on my late 2015 Sager NP8657 [Clevo P650-RE3]
gaming laptop with Ubuntu 16.04.0 64 bit LTS. Should I go ahead with
sudo apt-get upgrade and sudo apt-get dist-upgrade? Is this going to
mess up my Ubuntu? So, after I enable proposed and do the upgrade, what
should I do?
--
I enabled xenial-proposed on my late 2015 Sager NP8657 [Clevo P650-RE3]
gaming laptop with Ubuntu 16.04.0 64 bit LTS. Should I go ahead with
sudo apt-get upgrade and sudo apt-get dist-upgrade? Is this going to
mess up my Ubuntu? So, after I enable proposed and do the upgrade, what
should I do?
--
The ppa doesn't actually have the same fix that went into proposed. Can you
please make sure you enable proposed and then check again?
If you are still having problems please confirm the version of fwupd that
is installed using
# apt policy fwupd
On Sun, Jun 19, 2016, 09:35 Welly Wu <1574...@bug
I read this entire bug report and I added the FWUPD PPA and followed the
directions. I own an Oppo Digital HA-1 desktop DAC and headphone
amplifier. After unplugging it, shutting down, booting up, logging in,
plugging it back in, I can not see my HA-1 in sound devices and it is
stuck at DSD 12.288
Enabled proposed and all is well! Sorry for the confusion...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notific
I'm sorry. Must have missed the package from #51.
$ apt policy fwupd
fwupd:
Geïnstalleerd: 0.7.0-0ubuntu4.1
Kandidaat: 0.7.0-0ubuntu4.1
Versietabel:
*** 0.7.0-0ubuntu4.1 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/sta
@t-no,
Since you're having the failure pre-suspend per #61, can you please
confirm you've actually installed the package from the proposed
repository as explained in #51?
You can then please confirm your package version using this command:
# apt policy fwupd
Thanks
--
You received this bug no
Got sound after resume. Still: here's the output.
11:21:55Verbose debugging enabled (on console 0)
11:21:55adding plugin
/usr/lib/x86_64-linux-gnu/fwupd-plugins-1/libfu_plugin_steelseries.so
11:21:55adding plugin
/usr/lib/x86_64-linux-gnu/fwupd-plugins-1/libfu_plugin_test
If I reconnect device after step 2) it works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notifications ab
After step 1), I have to reconnect my usb device and reselect it in
sound settings. After step 2) I don't have sound anymore. What do you
need Mario?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15740
@t-no,
Hmm OK. Can you please add --verbose output to fwupd before your
suspend?
1) sudo killall fwupd
2) sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v 2>&1 | tee fwupd_debug.log
3) make sure audio is working properly
4) suspend
5) resume
6) if it's not working still please provide the debug out
With a working USB sound device, just before suspending execute "sudo
killall fwupd", all is well after resuming.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not
** Description changed:
[Impact]
High end USB audio devices don't work properly after fwupd is started from
gnome-software.
[Test case]
Login to Ubuntu session and try to use a USB audio device. See if it works
properly.
+
+ If you are applying this upgrade and testing a regression
@t-no,
To confirm if this is caused by fwupd or caused by a general suspend bug
with that USB device, can you please kill fwupd before suspend?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
T
Focusrite Scarlett Solo USB device here. Doesn't work oob in 16.04.
Following the 3 steps from #54 enables me to select the device in sound
settings and make things work. Afer every resume from suspend or reboot,
I have to follow this procedure again. So it isn't a permenant fix.
--
You received
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manag
my cambridge audio dacmagic plus is working in usb mode 2.0
(24bit192khz) again after fwupd updating. thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not
I would suggest following 3 steps in post above, originally I just
installed the newer versions and rebooted and it did not work, as
mentioned maybe device was in bad state. After unplugging and manually
running killall it has worked in all following reboots.
--
You received this bug notificatio
It's important to killall fwupd manually, or reboot to make sure you get a
fresh fwupd process to verify this fix.
Also the USB device could possibly be in a bad state from the previous
interactions.
If you can upon update:
1) unplug your USB device
2) killall fwupd or reboot
3) plug in device
One other update, I ran reinstall again while still getting errors
related to USB when starting up it does seem to be working after a few
restarts. Probably someone else should also verify behavior.
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug
I updated fwupd (and later libdfu1 / libfwupd1) to 0.7.0-0ubuntu4.2 this
did not resolve the issue for me symptoms are the same as before and
same usb error message on startup. For clarification this audio device
is a "Native Instruments KOMPLETE Audio 6". Had been away for a few
days but can pro
Hello TheBigW, or anyone else affected,
Accepted fwupd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/0.7.0-0ubuntu4.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
This bug was fixed in the package fwupd - 0.7.0-0ubuntu6
---
fwupd (0.7.0-0ubuntu6) yakkety; urgency=medium
* Fix USB audio devices not working properly (LP: #1574079)
-- Mario Limonciello Wed, 08 Jun 2016
21:31:00 -0500
** Changed in: fwupd (Ubuntu Yakkety)
Status: Fix
I've uploaded that fix to yakkety, and started the SRU process for
Xenial.
** Also affects: fwupd (Ubuntu Yakkety)
Importance: Medium
Status: Confirmed
** Also affects: fwupd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ High end USB
I've pushed a patch to master that seems to fix the issue for me of the
2i2:
https://github.com/hughsie/fwupd/commit/d0583ae3403b904658b4ac3c10330287ccbae6c9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Seb Brosig sent me a 2i2 device for testing, I can reproduce the bug and
now have a USB analyser connected to the device. It'll take a little
while to work out, but I'm getting there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
If it makes it easier, i've backported those two patches into a PPA build on
top of what's already in Ubuntu here:
https://launchpad.net/~superm1/+archive/ubuntu/lp1574079
The version with those two patches is 0.7.0-0ubuntu4.2~lp1574079.2.
Richard, I don't think there is anything else strictly n
There's a test branch which I believe fix this problem in
https://github.com/hughsie/fwupd/issues/50#issuecomment-223222483 if
anyone can test this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157407
> can anyone reproduce the issue after killing fwupd as root, running
"sudo dfu-tool watch" and then inserting the hardware
Installed fwupd back into system.
I can reproduce the bug with "sudo dfu-tool watch". After killing everything
works again.
--
You received this bug notification because y
(For clarification)
I did the following steps:
1) Installed fwupd
2) Killed the daemon
3) "sudo dfu-tool watch"
4) Plugged-in the device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
So, nothing unexpected in those gdb traces... Perhaps it's peculiar that
there are three monitoring threads for libusb, but that's due to a
limitation in the fwupd provider structure which shouldn't be a huge
problem. To rule out that being the issue, can anyone reproduce the
issue after killing fw
Adding more info, I copied what Taras did with gdb, and added the outut
of sudo lsusb -v in three situations: "test running, card unplugged",
"test running, card plugged in" and "no test, card working".
Hope it helps.
Thanks for looking into this!
** Attachment added: "gdb trace.txt"
https:/
I just played a little with 'gdb'. Please see the attachment. Hope you will
find the information useful.
Just noticed the process has seven threads. Is it ok? Or maybe it stuck or
something?
BTW, I had to interrupt the process, since it didn't crash when I connected the
sound-card.
** Attachmen
I will try to give it a go once I get home.
I also switched to Kubuntu to avoid this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after star
If you (or anyone else) reproduce it on a "working" Kubuntu system by
running fwupdmgr as Richard mentioned it will only be temporary that it was
reproduced. fwupdmgr uses dbus activation to start fwupd. Typically fwupd
isn't run by default in Kubuntu for reasons Richard described.
When you were t
Anyone who does have the hardware and skills to be able to reproduce and
attach a debugger you need to install the debug symbols for it to be
useful. By default Ubuntu buildd's strip debug symbols and places them in
ddebs. The automatic crash retrace bot will use these symbols to generate
useful b
> even if it doesn't happen by default in Kubuntu
GNOME autostarts gnome-software, which allows you to update applications
*and* firmware on devices. The latter contacts fwupd for the list of
updates which then itself autostarts the fwupd binary. If you call
`fwupdmgr get-devices` manually on kubu
Jay,
Surely you mean 16.04 not 10.04. In Kubuntu even if fwupd is installed it
won't start up on its own.
In Ubuntu it starts up with your session by gnome-software looking for
firmware updates from fwupd.
If you could reproduce by manually running fwupd and attaching a debugger
you may still be
Thanks Richard for getting involved.
Not sure how much help I can be as although I have this problem with my
Cambridge Audio DAC and Ubuntu 10.04, with Kubuntu this is no an issue!
I am now using Kubuntu (I actually quite enjoying it now) and I notice
that the driver installation app doesn't work
Faced the same issue with Sony PHA-3 after the update from 14.04 to 16.04.
Solved by removing fwupd.
It is also worth to note that my second USB DAC, Dr. DAC Nano, works flawlessly
even with fwupd installed. However, Sony PHA-3 does not.
--
You received this bug notification because you are a m
Hi Richard, I'm glad you have paid attention to this problem.
A few weeks ago I've upgraded my Ubuntu version from 14.04 to 16.04 and faced
with this issue. Now every time before connecting my USB sound-card I have to
kill the 'fwupd' process.
Here is output from the 'dfu-tool list' command:
-
Okay, so quite a few different issues here.
* If the audio card doesn't work when fwupd is removed and there is no
fwupd process running then it's not a fwupd issue.
* Does everybody who has to replug also have an entry for the soundcard
in `dfu-tool list`? If so, please paste the output.
* If y
Here is the lsusb output after login (audio interface is plugged in) ;
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux
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
w
Great thanks, can you please also share sudo lsusb -v output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notifi
This is what I got after running
1) sudo killall fwupd
2) sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v 2>&1 | tee fwupd_debug.log
21:57:58Verbose debugging enabled (on console 0)
21:57:58adding plugin
/usr/lib/x86_64-linux-gnu/fwupd-plugins-1/libfu_plugin_steelseries.so
21:57:58
Abkishek,
Can you please try to reproduce it with fwupd running with debug flags as
listed above?
You might have to unplug it, run with debug flags and plug back in.
On Sat, May 28, 2016, 09:50 Abhishek Chaudhary
wrote:
> Confirmed bug. Audio interface "focusrite solo" isn't found on startup.
Confirmed bug. Audio interface "focusrite solo" isn't found on startup.
Have to plug it out and then in again to make it work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage not
Hi @Jay and @Kingfriday,
If this is continuously reproducible for you, it would be great to get some
debug output from fwupd to figure out why this is happening. I unfortunately
haven't been able to reproduce it using my USB audio device (Dell TB15 dock).
Can you try to follow these steps to ge
** No longer affects: fwupd (Ubuntu)
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
My usb audio is no longer working at all with 16.04. I am rolling back
to previous LTS as this sucks and has remained as unassigned for a while
now. I wonder if it is worth raising a separate bug as the fwupd "fix
released" is a misnomer for myself and others.
--
You received this bug notificatio
When is this fix actually going to be present in vanilla Ubuntu 16.04? I
have been using the "sudo killall fwupd" method to get audio working but
it would be nice to not have to do that everytime I login or update
software or resume from sleep.
--
You received this bug notification because you ar
I have a focusrite 2i2 and I'm still experiencing this.
I've even unsintalled fwupd, but the problem persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not r
I have Cambridge audio dacmagic plus and in usb 2.0 mode is not
recognized. only in usb 1.0. please please could someone fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audi
This fix does not work for Cambridge Audio dac Magic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To manage notifications a
I have reinstalled Ubuntu 16.04 afresh today and after a complete update
this is still an issue with my Cambridge Audio USB soundcard. Removing
fwupd did do the trick this time. However if I was new to Linux this
wouldn't give a good first impression and indeed could have been a deal
breaker. I not
Confirming error on Ubuntu 16.04 and Cambridge Audio DAC Magic Plus. The
USB device does not list with lsusb and removing fwupd does no
difference. Worked flawlessly with Ubuntu 15.10.
Except from syslog:
kernel: [41856.060179] usb 3-6: 1:1: usb_set_interface failed (-71)
systemd-udevd[18617]: Pr
I have a fully updated ubuntu 16.04 installation with a Focusrite 2i2
and i still have this problem, i also have a Beringher Guitar Port and
that one works fine. Can confirm that killall fwupd makes the interface
work
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Can I just add that this affects my Cambridge Audio DAC Magic100 also. I
have found that it seems to effect Ubuntu and Ubuntu mate but strangely
not Kubuntu. I tried Ubuntu again 3 days ago and this is still a
problem. In fact as I get small shocks from the case I'm a little
reluctant to pursue thi
Confirm that this fixed it for me:
killall fwupd
followed by unplugging / replugging my focusrite 2i4 into a USB2.0 port.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio dev
Same problem with a fully updated install of Ubuntu-GNOME 16.04. This
is with a Focusrite iTrack. The first time the device is attached to a
USB port it will fail. Unplugging and replugging the device into the
same USB port will succeed.
--
You received this bug notification because you are a
Same problem with Audiobox 22 VSL. Unplugged and plugged back in twice
and the device is now recognised.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recogniz
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To mana
** No longer affects: fwupd (Ubuntu)
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
To mana
I can confirm this fwupd issue for a different USB audio device, a
PreSonus AudioBox 1818 VSL.
When I connect the card I get this in /var/log/syslog [1] [2]:
Apr 24 15:41:47 yogamme kernel: [ 34.958299] usbcore: registered new
interface driver snd-usb-audio
Apr 24 15:41:47 yogamme org.freedesk
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
I read the description of what fwupd does and if it really is just UEFI BIOS
related it won't matter on my older machine I thought and just got rid of it
(apt-get purge). What shall I see: after restart my USB audio device worked out
of the box - seems this issue is not alsa - related at all.
I
76 matches
Mail list logo
