** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth he
** Package changed: ubuntu => bluez (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
upstream ticket https://github.com/blueman-project/blueman/issues/64
** Also affects: blueman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.n
Reading the comments it isn't clear the problem is on pulseaudio. In my
case sometimes when I try to connect to my headset I get a crash on
unity-control-center (not sure yet if it is related). After upgrading
from Ubuntu 12.x I started to have this issue. I can pair my headset but
when I try to co
This bug wasn't fixed yet.
** Changed in: pulseaudio (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04
It is a bug, should be reopened.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
couple of updates
I discovered this problem this morning while trying to set up my laptop
with a bluetooth headset (Moto S305) for a pending video conference.
Some Googling led me to this thread and comment #93, and the fix works
just fine. "Trusty" being a LTS release, there are sure to be many other
people affecte
# 14 worked for me...
Had the same problem fixed it with:
"pactl list cards short" to get the device id
then I did "pactl set-card-profile x a2dp"
where X is your device id
found it by reading
http://askubuntu.com/questions/203272/no-a2dp-streaming-audio-from-12-04-to-bluetooth-headset
--
You r
Bluemanversion 1.23-git201403102151-1ubuntu1 from CSCHRAMM fixed
my problem with my Monoprice BT headphones not wanting to connect as
high fidelity playback A2DP.Using Linux Mint 17. Thank you
Christopher!
--
You received this bug notification because you are a member of Desktop
Pa
I can connect using Blueman... but if I actually use the headset it
starts distorting the audio after a minute or so and then disconnects.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bu
I confirm I can connect using Blueman. In that case though, I have to
load the bluetooth module on PulseAudio manually.
I guess this is an acceptable work around for now, but it would be nice
if it simply worked like it did on 13.10.
--
You received this bug notification because you are a member
** Changed in: blueman (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are no
Should I create a new bug or do you think this is the same bug?
Jul 29 13:46:22 imac kernel: [ 9194.185587] Bluetooth: Unexpected continuation
frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.269541] Bluetooth: Unexpected continuation
frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.594437] Bl
** Changed in: blueman (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not
I don't know if my problem is related to this one bug (any ideas?), I'm
having lots of problems with Bluetooth since the update to 14.04.
Just a few minutes ago, I turned my bluetooth headset on; it connected,
I verified it was working correctly; I went to a Google Hangout... and
the headset disco
I went out of range and lost the connection. It would not reconnect.
Now when I run:
pactl load-module module-bluetooth-discover
Failure: Module initialization failed
I tried:
pulseaudio -k
pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.
pactl load-module module-bluetooth-discove
I tried everything on this list up to comment #59 then it started
working!
Bluetooth Headset: BT-BSH10 http://amzn.com/B0059NF3PU
Laptop: ASUS X201E 11.6" Celeron 4GB/320GB Ubuntu Laptop
http://amzn.com/B00B1N92ZY
OS: Ubuntu 14.04 with all updates as of today.
On comment #29 I had to add the et
I think you're always gonna have to choose the BT headset, because you just
mounted it.
If you're using ubuntu in sound settings you can set a2dp, provided its already
active(as in set through blueman or whatnot).
Also bear in mind that having a2dp means no mic on the headset, you have to use
th
@cschramm
Despite originally not working (post #93) the ppa version of blueman is
now working without me doing anything (possibly simply a reboot was
needed). I'm also only getting one Headset entry in Sound Settings
whereas previously I was getting two.
The system connects upon powering up the h
** No longer affects: blueman
** Changed in: blueman (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth
Today it worked again. I tried connecting as headset instead of a2dp and it
worked, but no high def audio, then i typed:
sudo pactl load-module module-bluetooth-discover
and it returned:
26
whatever that means, after that, got full a2dp BT sound again...
So clearly there is a pulseaudio issue stil
I still get this:
blueman-mechanism: Starting blueman-mechanism
dbus[709]: [system] Successfully activated service 'org.blueman.Mechanism'
blueman-mechanism: loading Network
blueman-mechanism: loading Config
blueman-mechanism: loading Ppp
blueman-mechanism: loading RfKill
bluetoothd[772]
Hi there, still can't connect anymore, with or without blueman.
got this in the log "bluetoothd[766]: Connection refused (111)"
And found this bug:
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/198494
Might be related, there might be more out there.
Cheers.
--
You received this bug
It's now in Debian unstable and should automatically make it into
testing in about 10 days. Ubuntu probably syncs from there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
T
> @David: If you like I'll push the fix to Debian testing. That's
probably the cleanest way to also get it into Ubuntu, isn't it?
Sounds like a plan, thanks!
Not sure if we sync from Debian unstable or Debian testing these days,
but I assume you upload the fix to both. That will bring it into uto
Disabling the unload is the best guess yet, although I do not know how
and why the rest of the plugin can still work then. ;) But I can figure
that out afterwards.
(If anybody wants to help with that, please send me the blueman-applet
output of when you successfully connect your audio device using
Hi cschramm and thanks for looking at this bug!
How do you think we should proceed to release a fix/workaround? Should
we just upload the code that disables the module unload, or do you have
a better suggestion?
--
You received this bug notification because you are a member of Desktop
Packages,
Today for whatever reason after a few updates(sadly i didn't check what
was updated) BT no longer works.
Tried a few commands, like restarting pulse, removed blueman, you name it, i
prob did it. Nothing even worked.
Here is the end result:
Jun 30 01:05:00 lorien bluetoothd[705]: Adapter /org/blu
That blueman ppa version works for me, also.
But, I had to reboot to have it working, restarting blueman and pulseaudio did
not do the job.
Strange enough that it now works with blueman. Despite i never use blueman, its
startup seems necessary.
--
You received this bug notification because you
@cschramm
I just installed the blueman package from your ppa and it works for me.
Thanks a lot :-)
For people who still have issues, see #92.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.
@cschramm
I've just received a new version of the ppa which seems to include
additional debugging messages.
I've attached the output from the new version
Regards
** Attachment added: "blueman-messages-2"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003/+attachment/4140447/+
Thanks for the output!
Did you connect the audio device? Then it looks like the applet plugin
indeed does not do anything... But then again the version without the
plugin (1.23-git201406231750-nopahandling) should not make any
difference... :/
--
You received this bug notification because you ar
@Kiori
audio.conf is attached. This is as installed as standard as far as I
know.
@cschramm
As a simple user I'm starting to get out of my depth with the diagnostic
procedures, please bear that in mind if I've misinterpreted your instructions.
When I originally ran blueman-applet in terminal I
When using the deb version (1.23-git201406261335-deb-1) and running
blueman-applet in a terminal, what output do you get?
There should be things like:
Starting source redirector
Found source
Source not found :(
module-loopback load result
Loopback module unload result
Dest
@zig59, please post you audio.conf.
To me the new ppa blueman is working flawlessly, and it doesnt bug out
on me anymore, it used to crash now and then. However, before using it I
was careful to get my audio.conf back to its original state of basically
no config, so it leaves everything to blueman
The nopahandling does not include the plugin, while the deb version does
and only hasn't got the pulseaudio module unload. So it should be
identical to David Henningsson's PPA version.
Since the nopahandling branch did not work for zig59, I'm going for this
minimalistic approach. Although I'm not
@cschramm
The package from your PPA (version 1.23-git201406261335-deb-1) works for me (on
XFCE, no gnome-bluetooth installed). Pairing with speakers is possible and i'm
able to select them in pavucontrol and play back audio.
I have to do this manually, so the PulseAudio manager plugin doesn't see
Hi cschramm,
Have installed your ppa version of Blueman and it is not working for me.
The manager allows me to find, pair and connect to my headphones but
there is no entry in Sound Settings (there was before) to allow me to
route to the headphones.
In addition I now have 2 bluetooth icons on th
Hi all,
blueman maintainer here. I understand this is not 100 % a blueman
problem, but blueman is definitely having its part.
As you found out, there is a blueman applet plugin that unloads
pulseaudio's bluetooth-discover module and handles devices manually. The
original author let me know that t
Also, remember that after you set that and basically restart, when you're all
set and your bt headset is paired you still have to go to sound options and
select it as an output and select A2DP or you won't be getting any sound out of
it.
Every time you play with something you have to go back the
---
Guys if you're still having issues and using gimmicks i guess you missed the
post that talked about adding this:
[General]
Enable = Source,Sink,Headset,Gateway,Control,Media
Disable = Socket
HFP=false
[A2DP]
SBCSources=1
MPEG12Sources=0
To audio.conf.
I discovered a solution which worked for me. It is from this youtube video
http://www.youtube.com/watch?v=YgFoWmeFqaI .
All you have to do is :
1- Install PulseAudio Volume Control from Ubuntu Software Center
2- Open it and select Configuration tab
3- Switch the paired Bluetooth device's Profile f
Sorry for my english. I have two bluetooth devices, a headphone and a
bluetooth audio receiver that i bought in china. The first device pair
but a cannot select the profile a2dp, it only work for the first time
when a add a device, after on reconnect it wont work anymore. The second
device work fla
I suffer the same symptoms. Used it in 14.04 (Ubuntu GNOME over here)
and stopped working (though I did change lots of PPAs). Device is
detected, paired correctly but it won't show up in Preferences > Sound.
Running 'paclt list cards short' (per #14) does not list this (only the
built-in card), wh
With the Blueman package from Davids PPA, I'm able to connect with my bluetooth
speakers again. I only have to choose them manually as default output.
On a sidenote: The Blueman deb should depend on pulseaudio-module-bluetooth. I
removed it previously (or it isn't even installed as default on Xub
Thank you, David!
I installed blueman from your ppa (#75), reboot, and all works fine.
(Mint 17 (2014-03) Mate 32bit)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
@David Henningsson
Hi David,
Have installed the new bluemantest from the ppa and for me it works. Thank you.
It works in the same way that editing the Pulseaudio.py file worked as
specified by Hartmut. I.e. there are quirks (specified in post #81) to navigate
to actually get the sound routed to
Guys lets just not forget that there are people that have issues with
blueman, and people that have issues even without blueman(with bluez and
gnome stuff instead).
Just making sure this wont be forgotten.
--
You received this bug notification because you are a member of Desktop
Packages, which
> > Sorry: IndentationError: expected an indented block (PulseAudio.py, line
> > 235)
> Oops, then I screwed up. Please do not use the package.
This should now be fixed. A new package is currently building in the
ppa.
--
You received this bug notification because you are a member of Desktop
Pac
Thank you Hartmut, this works for me too.
In addition to rebooting I also had to remove and then re-
add/pair/connect/select the headphones in Sound Settings/switch to A2DP
before the headphones would work.
As a note there are some peculiar quirks for me:
For some reason I have 2 headphone entri
@Harmut (hesse-hsr)
Thank you! I just tried your "hacking fix" and it works very nicely indeed
:) .
Now the bluetooth headset shows up fine in the sound settings panel
and I can switch on A2DP profile; without problems.
Incidently, I did not encounter the reported Blueman crash,
#78 > a hacking fix:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/31
That causes Blueman to crash at startup, but for Pulseaudio, it seems
tyo work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
a hacking fix:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/31
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth
> Sorry: IndentationError: expected an indented block (PulseAudio.py,
line 235)
Oops, then I screwed up. Please do not use the package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs
Hi David,
I'm not expecting bluemantest to actually resolve my problem as I can already
pair and connect but not route to my headphones. Anyway anything is worth a
shot at the moment so I tried to install the file through Synaptic but am
getting a fail with the message "E: blueman: subprocess i
Thanks Sebastian! Based on what was written in the github report, I've
just commented out the module unloading that blueman does, built the
result and put it in a ppa here:
https://launchpad.net/~diwic/+archive/bluemantest
It is possible that blueman messes with more stuff so that just
commenting
I created an upstream bugreport for blueman:
https://github.com/blueman-project/blueman/issues/64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04]
** Also affects: blueman (Ubuntu)
Importance: Undecided
Status: New
** Changed in: blueman (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchp
** Package changed: blueman (Ubuntu) => blueman
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
co
Hi all,
I have been following this discussion for a while because the connection to my
A2DP device was broken after upgrading to 14.04 with all the symptoms
described above.
Following David Henningsson's suggestion in post #71, I used "apt-get
purge blueman" to fully uninstall blueman from my
Well, since the Linux kernel and PulseAudio both are in main and officially
supported, but blueman is not, and one of the problems seems to be that blueman
unloads module-bluetooth-discover,
how well do things work *without* blueman?
I e, uninstall blueman and reboot and see how well the headset
What is disturbing here is the fact that this bug is unassigned or (in case of
pulseaudio) marked invalid.
That means nobody feels responsible and takes care.
We - most probably - will have to wait a long time for this problem to be
solved.
Since the manual loading of module-bluetooth-discove
Well I now have BT working in A2DP mode. Hopefully it will stay working.
There was never any problem pairing or connecting, just no sound would
come out and the sound settings screen did not offer any choices.
So, once paired and "pulseaudio -k" issued (but I don't know if that is
needed or not):
Neither does not work with a bluetooth headset BeeWi BBh100. Not in headset
mode, and not in a2dp mode.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth +
However, the headset seems to work properly if the command
pactl load-module module-bluetooth-discover
is executed directly after startup/login before any paired BT device tries to
connect - from a terminal window, returning "24".
It should be called automatically, but that doesn't seem to happ
syslog entries:
grep "pulseaudio.*bluetooth" /var/log/syslog
Jun 4 09:57:52 xxx-Linux pulseaudio[3248]: [pulseaudio]
module-bluetooth-device.c: 12:02:21:B1:40:5E is not known.
Jun 4 09:57:52 xxx-Linux pulseaudio[3248]: [pulseaudio] module.c: Failed to
load module "module-bluetooth-device" (argu
update:
After power down and restart this morning I tried again:
Bluetooth recognized my paired headset as connected, displayed the lock in the
icon, but in sound settings the headset did not show up, no sound from headset.
After
pactl load-module module-bluetooth-discover
24
After that the h
Bluetooth worked well in 13.04 and 13.10, but after upgrade to 14.04 it does
not work anymore.
I am using a generic USB dongle (CSR) on an old 32 bit system.
grep "pulseaudio.*bluetooth" /var/log/syslog
pulseaudio[3094]: [pulseaudio] module.c: Module "module-bluetooth-discover"
should be loaded
Bluetooth working well for a headset on 12.04, not working on 14.04,
either as new install or as upgrade. It pairs normally, but on one
machine (new install) does not appear in sound settings, on the other it
appears but in neither case does it switch sound from speakers to the
headset when on.
--
Another update... I've lost the connection twice now. It works for a
couple days, then breaks. Now I'm at the point where Blueman doesn't
even find the device. I've been playing with it--reversing, repeating,
reinstalling--but I can't get it back.
Bearing in mind that I know next to nothing abo
@aanno
Bluez 4 is being used because 5 lacks many needed features, such as having the
headphone and mic working at once.
The devs say its working, but i've read its really not. I read a few months ago
that the guys at pulse audio were working to change that, maybe in a few months
we'll see the r
As David said in post #34 there appears to be a number of bugs going on
here.
I've not had any trouble pairing and connecting my BT headphones (Motorola
S805) 'out of the box' but it simply won't route the output to them even
manually through Sound Settings. I've tried a number of the solutions
Well, IMHO bluetooth is one big mess in ubuntu. I'm using a BT headset
for nearly 7 years now, and it has NEVER worked without some quirks.
Even this would be OK for me, but the quirks differ not only between
releases but also between updates. Hence you can never be sure if the
headset will work o
Tried a few edits, the bottom line is that if we want both on at the
same time, they both need to be loaded, which you can do with blueman,
and i have no idea how to do this without it.
I'm posting about this, because its ideal to have the best sound AND your
headphone's mic work at the same time
Tried what Mr Lee said, and indeed its works nows. But the problem
remains that crapware bluetooth-wizard is unable to pair the device,
after its paired, the above setup works 'out of the box'.
The only downside so far is that without it, i could toy with blueman and get
a2dp AND hsp or wahtever
Update: I had success by following #15 from
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1181106.
What's new was modifying audio.conf with these lines:
[General]
Enable = Source,Sink,Headset,Gateway,Control,Media
Disable = Socket
HFP=false
[A2DP]
SBCSources=1
MPEG12Sources=0
And
I'm struggling with this bug as well. My situation seems to be nearly
the same as Kiori's, except that even with Blueman pairing the speaker
successfully, it still doesn't show up in PulseAudio control.
It did work for a short while about a week ago, but then it stopped, and
though I've tried to
Updating my feedback.
I tried the above suggestions and indeed module-bluetooth-discover was not
loaded by default, had to manually load it, but it makes no difference.
The bottom line is my headset works ok with blueman, but if i remove
blueman and try built in standard bluez with standard gnome
CG: @David, OK & Thanks for your work to investigate/clarify this case.
Colum
On 14 May 2014 00:55, "David Henningsson" <1283...@bugs.launchpad.net>
wrote:
> @Colum, thanks - from the log we can see that module-bluetooth-discover
> is unloaded manually. The program unloading it is "python2.7" whic
@Colum, thanks - from the log we can see that module-bluetooth-discover
is unloaded manually. The program unloading it is "python2.7" which
unfortunately does not tell us exactly from where this comes, just that
it is some software written in python...
May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2
@David ... I carried out the modification to the /etc/pulse/default.pa file as
requested.
I re-booted system and observed problem still on. After getting the
Bluetooth Headset to
pair with Blueman. Using sound control panel, the bluetooth headset still
not recognised.
Cannot get A2D
CG: Seeing this quite late tonight. I will try to action your request
soon. BR. Colum
On 11 May 2014 22:20, "David Henningsson" <1283...@bugs.launchpad.net>
wrote:
> @Colum, thanks. Could you try the following:
> edit /etc/pulse/default.pa and above the line that says "###
> Automatically load dr
@Colum, thanks. Could you try the following:
edit /etc/pulse/default.pa and above the line that says "### Automatically load
driver modules for Bluetooth hardware", add a line with this text:
set-log-level 4
Reboot your computer and confirm that the bug is still present. Then do a
grep pulseaudi
Sorry for a delayed response to comment #43. The suggested command:
grep "pulseaudio.*bluetooth" /var/log/syslog
produced NO OUTPUT.
The output from "pactl list" is uploaded as attachment, but there is no sign of
any entry with text:
module-bluetooth-discover
-Colum
** Attachment added: "pactl
I know that - it was my attempt to restore original configuration and
forget about it until some sort of fix is available.
Unfortunately I have no idea what caused my machine to act different
this time. The only thing that changed is that I have played music from
youtube using chromium and flash p
Thanks for posting that Martin, I hope it helps others.
Unfortunately, that audio.conf file seems to be the same as mine from standard
(attached in post #36) but in my case I still can't route through my headphones
even though the system is showing it as paired and connected. Manually
selecting
Few days ago after tinkering with bluetooth audio configuration I made
to the point where nothing worked, headset wouldn't even connect. Then I
replaced broken audio.conf with
https://launchpadlibrarian.net/174137125/audio.conf and forgot about it.
Today after I connected my headset i got AD2P up
i have the same issue using LG HBS-250
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not working after last
couple of u
> Could you please consider to reverse the status back from
'INCOMPLETE' to 'CONFIRMED' (again).
I will do so for PulseAudio if I get the requested information, which
is:
"if you can verify that module-bluetooth-discover is indeed *not* loaded (i e
does not show up in "pactl list modules"), hope
I see this problem (the "re-auth of legacy device is not
possible/Protocol not supported" one) when using a Motorola H300 headset
which previous to 14.04 worked fine. On the same machine, a Samsung
HM1700 works perfectly.
--
You received this bug notification because you are a member of Desktop
P
Me too. A have already connected my BT headset using Bluez and I can see
it in the audio devices list. But when I trying to set it as audio
input/output device then nothing happens.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaud
Hi, I'm also having issues with Bluetooth on a fresh install of Ubuntu
14.04. I have the RT3290 chipset and had to patch and compile the
Bluetooth driver from source. After installing the Bluetooth driver, the
Bluetooth icon shows up as expected and I can try to pair with other
devices. I tested wi
CG: @David:
Could you please consider to reverse the status back from
'INCOMPLETE' to 'CONFIRMED' (again).
There would /seem/ to be a real issue which has been confirmed
by several contributors
in this thread...
Regards Colum
On 29.04.2014 12:58, David Henning
I can confirm the problem exists with my hardware as well.
Medion MD86751, Ubuntu 14.04 with latest updates.
How do I report this upstream? I am fairly inexperienced with submitting
bugs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
> Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy
> device is not possible.
> Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)
This indeed looks like the kernel is at fault. I don't know much
bluetooth (I'm more into the audio side of things), so
David, in response to comment #34 the log entries prior to the bluetooth error
are showing:
Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy
device is not possible.
Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)
I'm not exactly sure what to be loo
Incidentally, (follow-up from comment #33), in my case, "pactl load-module
module-bluetooth-discover" as per RazTaz's post #29 simply throws up the
message:
pulseaudio[1928]: [pulseaudio] module.c: Module "module-bluetooth-discover"
should be loaded once at most. Refusing to load.
--
You recei
Ok, so this is several bugs in one then...
> pulseaudio[1928]: [pulseaudio] module-bluetooth-device.c: Failed to
acquire transport /org/bluez/716/hci0/dev_00_0C_55_D1_91_ED/fd0
For this error, if it appears when you're trying to switch to the
headset, it looks like something on the bluez side. L
Like you David, my BT headset is paired and connecting when switched on.
The profile is also showing up in Sound Settings.
In my case though, the profile is not being autoselected in Sound
Settings and manually selecting it does nothing. Sound is still routed
through the wired amplified speakers.
Ok, I first did a quick test here and my BT headset paired, showed up in
sound settings, worked as usual, and profile was selectable. So at least
the problem is not *that* generic.
Anyway, module-bluetooth-discover is loaded from /etc/pulse/default.pa,
which is run every time pulseaudio starts. If
1 - 100 of 135 matches
Mail list logo
