Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any
Instead of the Xbluetooth manager hack, my hack is to just put a return
in that inner function. But I can report that this hack also fixes it
for me. In theory, the body of that function should just be a pass...
Or maybe the whole thing removed?
--
You received this bug notification because
The Bug is fixed in Debian an will be backported to Trusty (hopefully).
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003/comments/107
** No longer affects: blueman
** Bug watch added: Debian Bug tracker #743568
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743568
** Also
** Changed in: blueman (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1199059
Title:
blueman and pulse's module-bluetooth-discover (A2DP
I uninstalled blueman, installed pavucontrol, reboot my PC and then
turned on my bluetooth speaker to solve this issue.
I also believe that blueman is the main culprit and that blueman keeps
unloading the module-bluetooth-discover module.
So I agree with remark #28 in this thread.
--
You
I am using a fresh installed Xubuntu 14.04 LTS, after running Ubuntu 10.04 LTS
for quite a while on the same laptop Lenovo R500.
Everything worked great after installation, until I came to blueman...
Connecting to two different audio-devices( headset nokia 905i+,
bluetooth-speaker DOSS Alonso )
** Also affects: blueman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1199059
Title:
blueman and pulse's module-bluetooth-discover (A2DP
I am using Xubuntu 14.04 LTS (trusty) and running the new lxqt desktop.
I also still need to use the workaround in post #13 to get my bluetooth
speaker to work correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
The issue persists in Trusty as well, unfortunately. The magic in #13
(https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/13)
to the rescue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
According to David Henningsson Blueman seems to unload
module-bluetooth-discover:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003/comments/52
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
It seems to be a bit more complex than simply running that.. the
bluetooth device needs to be restarted as well (I cycle the wireless
switch on my laptop) and then the device connected/disconnected a few
times in order to get it to successfully connect to Pulseaudio.
--
You received this bug
Well, I think those issues are more typical with associating a bluetooth
device with the computer, no? I mean, if the loadmodule were part of a
startup script (as it should be), then when you turned on your bluetooth
device, the system would at least be ready to interact with it. You may
still
It seems some of the issues I was having seem to have stemmed from being
in standby mode and resuming thereafter.
From a clean boot, here's my current steps/output to get the BT device
working:
1. Power on system, wait to 'settle':
May 21 15:00:46 chrispad bluetoothd[832]: Endpoint registered:
13 matches
Mail list logo
