Just to be clear, these are the errors I'm seeing:
root@n1:~# dmesg | grep -i blue
[9.402011] Bluetooth: Core ver 2.21
[9.402031] Bluetooth: HCI device and connection manager initialized
[9.402034] Bluetooth: HCI socket layer initialized
[9.402037] Bluetooth: L2CAP socket layer
I applied the patched /lib/firmware/intel/ibt-
hw-37.7.10-fw-1.80.2.3.d.bseq as mentioned by @7oby in comment #4 on
Ubuntu 16.04.3. No Joy. My control, is a newer:
[9.468054] iwlwifi :02:00.0: Detected Intel(R) Dual Band
Wireless AC 7265, REV=0x210
but the patched firmware seems to
Thanks Daniel. Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP
seemed to fix the problem. Upgrading to 4.4.0-91 also seemed to cause
other problems: My system started overheating, eventually slowed to a
crawl (i.e., over a matter of minutes after each reboot slowed to the
point of being
Public bug reported:
Bluetooth connection to Bose Soundlink II have been fine for years.
Applied a few new updates in the last day or two --- system was
generally up to date, I don't often wait more than a week or so --- and
now I can no longer connect. Removed the device and re-paired just
@Daniel van Vugt (vanvugt): Thanks for your assistance!
I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.
I didn't subscribe to this bug, I didn't even know about it. I report
bug 1691556 and you marked it a duplicate of this one.
As
The problem appears to be with setting up the input sink, which I
couldn't care less about. If any knows of a way for bluez / pulseaudio
to force a device to just connect as an output-only device (e.g., normal
bluetooth speaker), I think I'd be fine, as I have no problems with
numerous other
@hife and @Mary Sherman (spot9019): Thanks for the speedy replies!
@hife: Thanks for describing your workaround in greater detail.
I've already tried the a2dp.py script, it doesn't fix the problem for
me. I just downloaded again the latest version and
@hife and @Mary Sherman (spot9019):
You both indicate that the latest pulse-testing ppa fixes the problem
for you.
Can you both indicate whether you are running Unity as the desktop or
KDE or perhaps some other?
I still have suspicions that there may be a permissions issue that is
specific to
I must unfortunately report that that the recently reported fix does not
work for me. Ubuntu 16.04 LTS connecting to Amazon Echo. Pulseaudio
1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from
ppa:ubuntu-audio-dev/pulse-testing as of today.
The problem appears to result in
Additionally, this issue also appeared along the line with Ubuntu+KDE
and apparently was easily resolved, as described in ubuntuforums.org,
[link](https://ubuntuforums.org/showthread.php?t=2318966). Quoting
another ubuntuforums.org post (also KDE),
I should also note that on the askubuntu.com site, I speculate that it
may just be some permission issue deep down somewhere, and why.
** Description changed:
- Pairing and coupling to Amazon Echo works, but sound is heard.
+ Pairing and coupling to Amazon Echo works, but no sound is heard.
Public bug reported:
Pairing and coupling to Amazon Echo works, but no sound is heard.
I believe the issue is related to the fact that Amazon Echo is paired as
a handset (i.e., speaker + microphone) rather than just as a speaker. I
believe the critical error is found in a dmesg line such as:
Hi Christopher,
Yes, apparently it does. Kindly see the attached screenshot, which
again shows 12gb using 'lshw' but 'free' and 'cat /proc/meminfo' show
only 8gb. This is from having booted the iso file 'utopic-desktop-
amd64+mac.iso' (downloaded yesterday) by installing grml-rescueboot and
Hi Christopher,
I'm a bit confused. Don't you mean a reporting discrepancy between
'lshw' vs. '/proc' and procps tools like 'free'. BOTH 'free' and 'cat
/proc/meminfo' show the WRONG info, whereas 'lshw' shows the correct
info.
Just to be clear, I'm rather confident that this is not a
Oops, forgort the dmesg.txt attachment, now attached here.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321938/+attachment/4119503/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Hi Christopher,
OK, great, thanks! And done (see results below). Unfortunatley, the
problem is to be found in the upstream kernel as well. :(
I'll change the tags as you direct momentarily.
What happens next?
Thanks,
Doug
- BEGIN: RESULTS FROM UPSTREAM KERNEL TEST -
root@s3:~#
Kernel bug report emailed to linux...@kvack.org.
I will report back with a Kernel Bug Tracker
(https://bugzilla.kernel.org/) report URL once I have one.
Thanks.
** Attachment added: kernel-bug-report.txt
Hi Christopher,
Makes sense.
Here is the requested URL for the upstream kernel bug report in their
email list archives (linux-mm):
http://marc.info/?l=linux-mmm=140105784328583w=2
The file 'kernel-bug-report.txt' I attached in my previous post contains
the exact same information.
Thanks,
Doug
Public bug reported:
Hi,
My motherboard died and Gigabyte had to replace it with a newer model
(specifically, a GA-970A-UD3 replacing a GA-870A-UD3). After installing
the replacement motherboard, the system boot and operated just fine. I
did notice after a few days, however, that free and cat
Oops, I should have also mentioned:
Of course, all 12gb were being recognized before the motherboard (MB)
replacement. No kernel updates or any other kind of updates were
applied during the 2-3 day period between when I installed the new MB
and noticed the lacking 4gb of RAM.
I did force a
20 matches
Mail list logo
