Similar situation here:
Dell Vostro 1320 with broadcom 4312 chipset.
It used to work fine (out of the box) with Jaunty.
The wireless device is shown in the commandline (iwconfig), but the
NetworkManager refuses to enable wireless networking. I've had exactly
the same behavior already in Hardy.
*** This bug is a duplicate of bug 236040 ***
https://bugs.launchpad.net/bugs/236040
** This bug has been marked a duplicate of bug 236040
alsa-firmware loader fails for tascam us-122 (and probably others)
--
Tascam US428 (usx2yloader-related scripts) broken in HH (and possibly II too)
The firmware portion of this bug is still open:
The tascam firmware (and other files existing in the original alsa-
firmware package) are still missing in the ubuntu packages.
Additionally, there seem to be some inconsistencies between udev-scripts and
the usx2yloader, expecting firmware files
Reverted from Fix released, since the alsa supplied firmware files are
still missing.
** Changed in: alsa-tools (Ubuntu)
Status: Fix Released = Confirmed
--
Tascam US122 won't load + alsa supplied firmware missing
https://bugs.launchpad.net/bugs/45880
You received this bug notification
*** This bug is a duplicate of bug 26294 ***
https://bugs.launchpad.net/bugs/26294
Sorry. Marked this one as duplicate of the won't fix bug Ubuntu is
missing the alsa-firmware package. It cannot be fixed, due to
licensing/copyright issues with distributing the firmwares in binary
form.
See
Public bug reported:
In KMidiMon 0.5.0 on my dual-screen setup, right-clicking on the table headers
always positions the list columns menu on my first screen.
Additionally, it even calculates the wrong position if I'm on screen 1.
Although it's just a cosmetic issue, my actual request would be
I forgot to mention that this problem is fixed in kmidimon v0.5.1
(according to the kmidimon developer).
--
Right-click menu list columns appears at wrong position
https://bugs.launchpad.net/bugs/336578
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is a sad thing - and there's still no solution.
Is there any decision yet regarding a separate libasound2-plugins-extra
package?
Just leaving libasound-jack out in the rain is a bit hard, don't you think?
Especially, because people doing audio *DO* want almost everything to go
through
