Re: Re: bluetooth audio
Thanks! -- WLM
Re: bluetooth audio
Luis Mochan wrote: > After a recent update/upgrade in debian/bookworm my bluetooth > earphones and my bluetooth earphones stopped working. > I found a solution in the discussion of at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=no > > related to bug #997862 which seemed to work for me, that is, > installing a package libspa-0.2-bluetooth. FYI: Same is up on the pulseaudio devel list Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones
bluetooth audio
After a recent update/upgrade in debian/bookworm my bluetooth earphones and my bluetooth earphones stopped working. I found a solution in the discussion of at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=no related to bug #997862 which seemed to work for me, that is, installing a package libspa-0.2-bluetooth. I'm not sure what is happening, but I guess it should have been installed automatically if it was required not to break my system (and I guess others). I would like to file a bug report, but I'm not sure the origin is in the wireplumber package (I don't know why it got installed in my system). I will appreciate any advice. Regards, Luis -- o W. Luis Mochán, | tel:(52)(777)329-1734 /<(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\ Av. Universidad s/n CP 62210 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16 C2DF 5F0A C52B 791E B9EB
Re: Bluetooth audio periodic disconnect
Bhasker C V wrote: > Hi all, > I am on bullseye. > I have tried and tested this with many headphones > > When on bluetooth the audio gets periodically disconnected and > re-connects > to audio after 5 seconds. > During the time the bluetooth per-say does not get disconnected but just > the audio stops and then starts again in 5 seconds. > I have already set laptop-mode tools to blacklist usb power management > for > my usb adapter. > There are no issues with bluetooth lag or connection issues. My > headphones > connect fine and work fine except for the intermittent disconnects. > > Please could someone help me fix this ? > One option would be to get debian stable somehow and try if it is reproducible there. Another option would be to look at what the underlaying systems are doing there. For example start pulse audio with -vvv to get more output or inspect the data flow. Use dbus-monitor --system and --session or other to inspect dbus event. All components in the chain could cause the issue - kernel/driver, systemd, dbus, pulse and bluez. You have to find out which system is causing the connection drop. I am on buster and I play recently more with bluetooth and the phone. I noticed that when I connect two profiles (A2DP and HFP) the audio is lagging. When A2DP or HFP is connected only, audio is fine. When I make a call via HFP and I finish the call, connection to phone drops. >From what you write, I assume you use A2DP and may be it is pulse not able to process or too sensitive, but this suggestion is just fortune telling. I am personally disappointed by the move to bluez5 in the whole linux world - not that bluez4 was OK, but after a lot of effort things were working. Now bluez5 is better, but other systems are still improving to match the new design - we pay the price. regards
Bluetooth audio periodic disconnect
Hi all, I am on bullseye. I have tried and tested this with many headphones When on bluetooth the audio gets periodically disconnected and re-connects to audio after 5 seconds. During the time the bluetooth per-say does not get disconnected but just the audio stops and then starts again in 5 seconds. I have already set laptop-mode tools to blacklist usb power management for my usb adapter. There are no issues with bluetooth lag or connection issues. My headphones connect fine and work fine except for the intermittent disconnects. Please could someone help me fix this ? Regards Bhasker C V
Re: iPhone as bluetooth audio source for buster
Mark Fletcher wrote: > Anyone have any advice what I should check to find what's missing? most likely you need to connect with the appropriate profile. I forgot already how the gnome gui looked like for it, but there was a pop up menu where you can select sink or source for the audio. I also think it is a shame - bluez5 seems to be much better etc. etc., but unfortunately works worse with pulse audio :( I don't use iPhone but doesn't matter - same problem, so what I do is to choose the audio profile for source and connect the phone. Might be the phone can also tell which profile to use. You can try this in bluetoothctl. "110a--1000-8000-00805f9b34fb" => "A2DP Source" "110b--1000-8000-00805f9b34fb" => "A2DP Sink" I am not sure if the following works, cause no one knows what happens in the background, but I tried it and it plays fine here. [bluetooth]# menu advertise Menu advertise: Available commands: --- uuids [uuid1 uuid2 ...] Set/Get advertise uuids service [uuid] [data=xx xx ...] Set/Get advertise service [...] exportPrint evironment variables [bluetooth]# service 110b--1000-8000-00805f9b34fb then connect from the phone the PC Let me know if it works - just curious - I spent many days with Bluetooth last year :) bringing BT manager for TDE back to life and buteo-syncml on the Sailfish. As for the command related to PA https://askubuntu.com/questions/765233/pulseaudio-fails-to-set-card-profile-to-a2dp-sink-how-can-i-see-the-logs-and pactl load-module module-loopback source=bluez_source.xx_xx_xx_xx_xx_xx.a2dp_source sink=alsa_output.pci-_00_1b.0.analog-stereo Last but not least, remove the directory and cookie ~/.pulse* and reboot or restart PA.
iPhone as bluetooth audio source for buster
Hello Recently I wanted to connect my iPhone 7 to a new Buster install in the same way I had many years before with an earlier iPhone and earlier Debian, so I could play music from it through my speakers. Bluetooth setup on the Debian machine is basically working; I can connect to a variety of devices and can play audio from the PC through bluetooth headphones etc. Bluetooth setup on the phone also seems to be fine as it can connect to and use bluetooth headphones, speaker, my car etc. I have successfully paired and connected my phone and my Debian machine, but the Debian machine doesn't seem to recognise the phone as an audio source. Once paired and connected, my GNOME seems ready to use a network through the phone's bluetooth, but if I start to play audio on the phone, I get silence -- which tells me the phone expects it to work as it isn't using its speaker, but something isn't right at the computer end. Instructions on the internet are, I suspect, out of date, referring to older versions of bluez. In particular I see references to adding text to /etc/bluetooth/audio.conf, but that file does not exist on my system and according to apt-file there is no package in Buster that would put it there. Nonetheless following the possibly-antiquated instructions, after connecting the phone to the computer I try to create a loopback device for pulseaudio with: $ pactl load-module module-loopback \ source=bluez_source.XX_XX_XX_XX_XX_XX \ sink=alsa_output.pci-_00_1b.0.analog-stereo which gives me the response: Failure: Module initialization failed Anyone have any advice what I should check to find what's missing? Thanks in advance Mark
Re: Bluetooth audio problem
On Sat, Mar 23, 2019 at 08:24:30AM -0500, Nicholas Geovanis wrote: > On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher wrote: > > > > > So this turned out to be a weirdie -- if I dropped the "sudo" my > > original command worked. > > So now, suddenly from that update that started this thread, if I run the > > pactl command as an unprivileged user, it works fine. > > > Is it possible that you had previously started pulseaudio as root, and > could no longer communicate with it as an unprivileged user? > I ask this having been a pulseaudio victim myself sometimes. > > Hmm, interesting idea, but the situation I was previously in pertained over a period since Stretch became Stable until shortly before my original mail in this thread (sometime in February if I recall correctly). Over, naturally, multiple reboots. For that period, I had to use sudo when issuing the pactl command (in Jessie and previously, the pactl command wasn't necessary at all). So I guess I could have had some sort of configuration which repeatedly put me in that situation on every reboot, and the update that "created the problem" actually fixed whatever *that* problem was... otherwise, no I don't think so. Thanks for the suggestion though Mark
Re: Bluetooth audio problem
On Fri, Mar 22, 2019 at 9:29 AM Mark Fletcher wrote: > > So this turned out to be a weirdie -- if I dropped the "sudo" my > original command worked. > So now, suddenly from that update that started this thread, if I run the > pactl command as an unprivileged user, it works fine. Is it possible that you had previously started pulseaudio as root, and could no longer communicate with it as an unprivileged user? I ask this having been a pulseaudio victim myself sometimes. > Mark > >
Re: Bluetooth audio problem
On Fri, Mar 22, 2019 at 08:44:46PM +0100, deloptes wrote: > Mark Fletcher wrote: > > > So this turned out to be a weirdie -- if I dropped the "sudo" my > > original command worked. > > > > So now, suddenly from that update that started this thread, if I run the > > pactl command as an unprivileged user, it works fine. I have no idea why > > it changed but I'm just happy I have it working again. > > you can mark also as solved, if solved > True, I could have. But I don't think it will kill interested people who follow after to read a 3-mail thread to see the resolution.
Re: Bluetooth audio problem
Mark Fletcher wrote: > So this turned out to be a weirdie -- if I dropped the "sudo" my > original command worked. > > So now, suddenly from that update that started this thread, if I run the > pactl command as an unprivileged user, it works fine. I have no idea why > it changed but I'm just happy I have it working again. you can mark also as solved, if solved
Re: Bluetooth audio problem
On Sun, Mar 03, 2019 at 06:04:05PM +0100, deloptes wrote: > Mark Fletcher wrote: > > > Hello > > > > Since upgrading to Stretch shortly after it became stable, I have had to > > execute the following after a reboot before being able to connect to > > bluetooth devices using the Gnome bluetooth applet: > > > > $ sudo pactl load-module module-bluetooth-discover > > > > Now, when I run the above command it is erroring out with: > > > > xcb_connection_has_error() returned true > > Connection failure: Connection refused > > pa_context_connect() failed: Connection refused > > > > > When I want to debug pulse I do > > echo "autospawn = no" > ~/.pulse/client.conf > > kill PA and run it from command line with -v option you can also > use --log-level (man pulseaudio) > > perhaps you can see what is the problem there. If not it might be dbus issue > with permissions - check the dbus settings > > Also some times it helps to remove the ~/.pulse directory and restart > pulseaudio. > So this turned out to be a weirdie -- if I dropped the "sudo" my original command worked. So now, suddenly from that update that started this thread, if I run the pactl command as an unprivileged user, it works fine. I have no idea why it changed but I'm just happy I have it working again. Mark
Re: Bluetooth audio problem
Mark Fletcher wrote: > Hello > > Since upgrading to Stretch shortly after it became stable, I have had to > execute the following after a reboot before being able to connect to > bluetooth devices using the Gnome bluetooth applet: > > $ sudo pactl load-module module-bluetooth-discover > > Without that command, needed once only after each reboot, the Gnome > applet is unable to connect to any bluetooth audio devices, eg my > headphones to be used as an audio sink, or my iPhone to be used as an > audio source. Once that command has been issued once, everything works > as it should, and continues to do so until the next reboot. > > I've been away for a couple of weeks and so hadn't installed updates to > my stretch installation for something like 3 weeks, until Saturday this > week when I installed updates. Unfortunately I didn't pay enough > attention to exactly what was upgraded but I _believe_ I saw udev in the > list of things getting upgraded. > > Now, when I run the above command it is erroring out with: > > xcb_connection_has_error() returned true > Connection failure: Connection refused > pa_context_connect() failed: Connection refused > > Googling for this has only turned up old information which does not seem > to relate to the problem I am facing. In most cases the context is audio > not working; in my case audio output through speakers plugged into the > sound card is working fine, USB mic connected by a wire is working > fine, the only problem is anything bluetooth. > > Bluetooth on this machine is provided by a USB bluetooth dongle which I > have been using for ages. > > Can anyone suggest steps to diagnose? > When I want to debug pulse I do echo "autospawn = no" > ~/.pulse/client.conf kill PA and run it from command line with -v option you can also use --log-level (man pulseaudio) perhaps you can see what is the problem there. If not it might be dbus issue with permissions - check the dbus settings Also some times it helps to remove the ~/.pulse directory and restart pulseaudio. regards
Bluetooth audio problem
Hello Since upgrading to Stretch shortly after it became stable, I have had to execute the following after a reboot before being able to connect to bluetooth devices using the Gnome bluetooth applet: $ sudo pactl load-module module-bluetooth-discover Without that command, needed once only after each reboot, the Gnome applet is unable to connect to any bluetooth audio devices, eg my headphones to be used as an audio sink, or my iPhone to be used as an audio source. Once that command has been issued once, everything works as it should, and continues to do so until the next reboot. I've been away for a couple of weeks and so hadn't installed updates to my stretch installation for something like 3 weeks, until Saturday this week when I installed updates. Unfortunately I didn't pay enough attention to exactly what was upgraded but I _believe_ I saw udev in the list of things getting upgraded. Now, when I run the above command it is erroring out with: xcb_connection_has_error() returned true Connection failure: Connection refused pa_context_connect() failed: Connection refused Googling for this has only turned up old information which does not seem to relate to the problem I am facing. In most cases the context is audio not working; in my case audio output through speakers plugged into the sound card is working fine, USB mic connected by a wire is working fine, the only problem is anything bluetooth. Bluetooth on this machine is provided by a USB bluetooth dongle which I have been using for ages. Can anyone suggest steps to diagnose? TIA Mark
no bluetooth audio in jessie
A few days ago, I upgraded my laptop from wheezy to jessie. After that I noticed that audio to my bluetooth speaker didn't work anymore. I had been using alsa audio and had a bluetooth type entry in my .asoundrc for my speaker. After a bit of digging it turned out that I had lost bluetooth audio, because bluez-alsa package does not exist in jessie. If I understood correctly, the reason is that bluez version 5 does not support alsa anymore. So I decided to try if my bluetooth speaker would work in jessies with pulseaudio. Unfortunately that was not the case. I got an error message: Apr 12 12:22:02 lohi pulseaudio[6318]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist After a bit more digging, i found this thread that went way above my understanding: https://github.com/ev3dev/ev3dev/issues/198 Long story short: it would be nice if bluetooth audio would just work in jessie like it did in lenny and wheezy for years. -- Juha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21804.44040.420994.694...@tutpro.com
Re: no bluetooth audio in jessie
Juha Heinanen wrote: A few days ago, I upgraded my laptop from wheezy to jessie. After that I noticed that audio to my bluetooth speaker didn't work anymore. I had been using alsa audio and had a bluetooth type entry in my .asoundrc for my speaker. After a bit of digging it turned out that I had lost bluetooth audio, because bluez-alsa package does not exist in jessie. If I understood correctly, the reason is that bluez version 5 does not support alsa anymore. So I decided to try if my bluetooth speaker would work in jessies with pulseaudio. Unfortunately that was not the case. I got an error message: Apr 12 12:22:02 lohi pulseaudio[6318]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist After a bit more digging, i found this thread that went way above my understanding: https://github.com/ev3dev/ev3dev/issues/198 Long story short: it would be nice if bluetooth audio would just work in jessie like it did in lenny and wheezy for years. -- Juha I had similar issue with upower where it lost the methods exposed to dbus. The solution was to downgrade upower (install older version known to work). Perhaps same is doable with the bluez package. then mark the packages as hold so they don't get upgraded until solution is provided. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mgjo4v$r35$1...@ger.gmane.org
Re: Painful BlueTooth Audio
This is a linux kernel problem created by whoever made the decision that speakers must connect through the quarter-inch jack on the sound card by default. A little more work must have been done to that end since though I was able to connect usb speakers to a linux box and configure alsa to use them and was able to reboot and have that configuration change honored, that was only a temporary condition. Some random reboot later and I had to plug in the old style speakers into that sound card again. I suppose Linux accessibility for us screen reader users will only last until the last sound card with a quarter-inch jack is off the market at this rate. On Mon, 13 Oct 2014, Leslie Rhorer wrote: I have a little Intel NUC running Debian Jessie whose purpose is to control a multimedia show using DMX for lighting and BLueTooth A2DP for audio. It's a wireless, headless box that sits in a corner and does its job. Well, it should be. The problem is the BlueTooth audio is far from automatic and also far from stable. I would like to be able to turn on the BlueTooth speakers, power up the NUC, start the application, and let it do its thing. This is not the case. In the best of times, I have to bring up BlueTooth Manager and manually connect to the loudspeaker. Then I have to bring up Settings = System Settings = Multimedia and select Technical Pro as the default sound device. Then I have to run Pulse Audio Volume Control and select Technical Pro as the output device. Is there any way (preferably a non graphical one) to put all this into one operation? I am ambivalent as to whether it should run automatically at start-up, but I definitely would like to have some way of running it without all the rigamarole on the desktop. The above procedure is what has to happen, as I said, in the best of times. In the worst, things are much less smooth. One thing that happens regularly is BlueTooth Manager fails to come up properly. The little bouncing icon does its happy little dance of a bit, and then just disappears. An attempt to run BlueTooth Manager again results in an error, saying it is already running. I have to grep for blue in the running processes and then kill blueman-manager and blueman-applet. After that, I can usually start the app. If the unit sits for a while without playing any audio, the link to the loudspeaker freezes, and I have to re-start the loudspeaker and reconnect to it, sometimes manually. Here is the log for blue from Start-up: Oct 13 16:51:58 DMXHost kernel: [2.638950] Bluetooth: Core ver 2.19 Oct 13 16:51:58 DMXHost kernel: [2.638976] Bluetooth: HCI device and connection manager initialized Oct 13 16:51:58 DMXHost kernel: [2.638985] Bluetooth: HCI socket layer initialized Oct 13 16:51:58 DMXHost kernel: [2.638989] Bluetooth: L2CAP socket layer initialized Oct 13 16:51:58 DMXHost kernel: [2.639006] Bluetooth: SCO socket layer initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Starting SDP server Oct 13 16:51:58 DMXHost kernel: [7.171984] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Oct 13 16:51:58 DMXHost kernel: [7.171989] Bluetooth: BNEP filters: protocol multicast Oct 13 16:51:58 DMXHost kernel: [7.172000] Bluetooth: BNEP socket layer initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Bluetooth management interface 1.6 initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Sap driver initialization failed. Oct 13 16:51:58 DMXHost bluetoothd[619]: sap-server: Operation not permitted (1) Oct 13 16:51:58 DMXHost bluetoothd[619]: hci0 Load Connection Parameters failed: Unknown Command (0x01) Oct 13 16:52:11 DMXHost pulseaudio[1142]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist Oct 13 16:52:11 DMXHost bluetoothd[619]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSource Oct 13 16:52:11 DMXHost bluetoothd[619]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSink Oct 13 16:52:13 DMXHost dbus[634]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) Oct 13 16:52:14 DMXHost blueman-mechanism: Starting blueman-mechanism Oct 13 16:52:14 DMXHost dbus[634]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 13 16:52:14 DMXHost blueman-mechanism: loading Config Oct 13 16:52:14 DMXHost blueman-mechanism: loading Ppp Oct 13 16:52:14 DMXHost blueman-mechanism: loading RfKill Oct 13 16:52:14 DMXHost blueman-mechanism: loading Network Oct 13 16:52:14 DMXHost kernel: [ 23.394518] Bluetooth: RFCOMM TTY layer initialized Oct 13 16:52:14 DMXHost kernel: [ 23.394535] Bluetooth: RFCOMM socket layer initialized Oct 13 16:52:14 DMXHost kernel: [ 23.394549] Bluetooth: RFCOMM ver 1.11 and from pulseaudio: Oct 13 16:52:11 DMXHost pulseaudio[1142]: Failed to open
Painful BlueTooth Audio
I have a little Intel NUC running Debian Jessie whose purpose is to control a multimedia show using DMX for lighting and BLueTooth A2DP for audio. It's a wireless, headless box that sits in a corner and does its job. Well, it should be. The problem is the BlueTooth audio is far from automatic and also far from stable. I would like to be able to turn on the BlueTooth speakers, power up the NUC, start the application, and let it do its thing. This is not the case. In the best of times, I have to bring up BlueTooth Manager and manually connect to the loudspeaker. Then I have to bring up Settings = System Settings = Multimedia and select Technical Pro as the default sound device. Then I have to run Pulse Audio Volume Control and select Technical Pro as the output device. Is there any way (preferably a non graphical one) to put all this into one operation? I am ambivalent as to whether it should run automatically at start-up, but I definitely would like to have some way of running it without all the rigamarole on the desktop. The above procedure is what has to happen, as I said, in the best of times. In the worst, things are much less smooth. One thing that happens regularly is BlueTooth Manager fails to come up properly. The little bouncing icon does its happy little dance of a bit, and then just disappears. An attempt to run BlueTooth Manager again results in an error, saying it is already running. I have to grep for blue in the running processes and then kill blueman-manager and blueman-applet. After that, I can usually start the app. If the unit sits for a while without playing any audio, the link to the loudspeaker freezes, and I have to re-start the loudspeaker and reconnect to it, sometimes manually. Here is the log for blue from Start-up: Oct 13 16:51:58 DMXHost kernel: [2.638950] Bluetooth: Core ver 2.19 Oct 13 16:51:58 DMXHost kernel: [2.638976] Bluetooth: HCI device and connection manager initialized Oct 13 16:51:58 DMXHost kernel: [2.638985] Bluetooth: HCI socket layer initialized Oct 13 16:51:58 DMXHost kernel: [2.638989] Bluetooth: L2CAP socket layer initialized Oct 13 16:51:58 DMXHost kernel: [2.639006] Bluetooth: SCO socket layer initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Starting SDP server Oct 13 16:51:58 DMXHost kernel: [7.171984] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Oct 13 16:51:58 DMXHost kernel: [7.171989] Bluetooth: BNEP filters: protocol multicast Oct 13 16:51:58 DMXHost kernel: [7.172000] Bluetooth: BNEP socket layer initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Bluetooth management interface 1.6 initialized Oct 13 16:51:58 DMXHost bluetoothd[619]: Sap driver initialization failed. Oct 13 16:51:58 DMXHost bluetoothd[619]: sap-server: Operation not permitted (1) Oct 13 16:51:58 DMXHost bluetoothd[619]: hci0 Load Connection Parameters failed: Unknown Command (0x01) Oct 13 16:52:11 DMXHost pulseaudio[1142]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist Oct 13 16:52:11 DMXHost bluetoothd[619]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSource Oct 13 16:52:11 DMXHost bluetoothd[619]: Endpoint registered: sender=:1.22 path=/MediaEndpoint/A2DPSink Oct 13 16:52:13 DMXHost dbus[634]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) Oct 13 16:52:14 DMXHost blueman-mechanism: Starting blueman-mechanism Oct 13 16:52:14 DMXHost dbus[634]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 13 16:52:14 DMXHost blueman-mechanism: loading Config Oct 13 16:52:14 DMXHost blueman-mechanism: loading Ppp Oct 13 16:52:14 DMXHost blueman-mechanism: loading RfKill Oct 13 16:52:14 DMXHost blueman-mechanism: loading Network Oct 13 16:52:14 DMXHost kernel: [ 23.394518] Bluetooth: RFCOMM TTY layer initialized Oct 13 16:52:14 DMXHost kernel: [ 23.394535] Bluetooth: RFCOMM socket layer initialized Oct 13 16:52:14 DMXHost kernel: [ 23.394549] Bluetooth: RFCOMM ver 1.11 and from pulseaudio: Oct 13 16:52:11 DMXHost pulseaudio[1142]: Failed to open cookie file '/root/.config/pulse/cookie': No such file or directory Oct 13 16:52:11 DMXHost pulseaudio[1142]: Failed to load authorization key '/root/.config/pulse/cookie': No such file or directory Oct 13 16:52:11 DMXHost pulseaudio[1142]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist When an attempt to run bluetooth-manager fails, I get this: Oct 13 16:52:44 DMXHost blueman-mechanism: Exiting Oct 13 16:52:44 DMXHost org.blueman.Mechanism[634]: Exception AttributeError: 'NoneType' object has no attribute 'stdout' in bound method Tee.__del__ of __main__.Tee object at 0xb6d08a2c ignored Oct 13 16:52:44 DMXHost org.blueman.Mechanism[634]: Starting blueman
Re: Jessie Bluetooth audio : Unable to select SEP ou Failed to open module module-bluetooth-device
Bonjour, La solution proposée a très bien fonctionné... Il reste à l'automatisée à la main : bashrc ou bien démarreur de session ou bien démarreur de pulseaudio... Quoiqu'il devrait l'être automatiquement (cf. default.pa)... À suivre... Yann. Le lundi 23 juin 2014 à 09:24 +0200, Bernardo a écrit : Bonjour, c'est vrai que ce n'est pas simple et que j'ai galéré longtemps. Je suis en Sid, à jour. j'utilise Blueman pour gérer le bluetooth et associer ma chaine hifi. je lance la commande : % pactl load-module module-bluetooth-discover Je connecte audiosink avec blueman. je lance la commande : % pulseaudio --start J'ouvre le Contrôle de volume Pulseaudio Onglet Configuration. J'éteins le canal audio interne et je lance celui de chaine. Si je m'ai pas gourré en route, ça fonctionne ! ;-D Je n'ai plus qu'a lancer le player (Clementine en ce qui me concerne). Je me suis basé sur la note en pièce jointe, issue d'un site dont j'ai perdu le signet. [...] -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/1403762577.6199.4.ca...@yan.ianco.homelinux.org
Jessie Bluetooth audio : Unable to select SEP ou Failed to open module module-bluetooth-device
Bonjour, Cela fait maintenant quelques heures que je lutte pour retrouver une configuration qui fonctionnait sous wheezy : la connexion via bluetooth sur un belkin I54 (interface avec une chaîne audio). Il y a pas mal de littérature sur ces problèmes, mais je n'ai pas trouvé de solution. Sur plusieurs machines jessie je rencontre le même soucis avec plusieurs adaptateurs bt. Dans /etc/bluetooth/audio.conf * soit je mets un Disable=Socket et alors j'ai Unable to select SEP (que je ne comprends pas : SEP c'est quoi ?) * soit avec Enable=Socket je rencontre un Failed to open module module-bluetooth-device, et si je pousse un peu en mettant un lien sur module-bluez5-device alors j'ai un : [pulseaudio] module.c: Failed to load module module-bluetooth-device: symbol pa__init not found. J'avoue ne plus savoir que tester et que cela ne m'arrange pas car je voulais monter une plateforme de musique pour l'anniv de mon fils avec mixxx en utilisant la liaison bluetooth mais bon on ferra cela avec une rallonge jack ! Mon second essai, en créant un lien entre module-bluez5-device et module-bluetooth-device, me laisse penser qu'il y a un problème de version entre pulseaudio et bluez5. Quelle est la configuration à mettre en œuvre pour retrouver cette connexion ? Cordialement. Yann. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/1403505636.11880.44.ca...@yan.ianco.homelinux.org
Re: Jessie Bluetooth audio : Unable to select SEP ou Failed to open module module-bluetooth-device
Bonjour, c'est vrai que ce n'est pas simple et que j'ai galéré longtemps. Je suis en Sid, à jour. j'utilise Blueman pour gérer le bluetooth et associer ma chaine hifi. je lance la commande : % pactl load-module module-bluetooth-discover Je connecte audiosink avec blueman. je lance la commande : % pulseaudio --start J'ouvre le Contrôle de volume Pulseaudio Onglet Configuration. J'éteins le canal audio interne et je lance celui de chaine. Si je m'ai pas gourré en route, ça fonctionne ! ;-D Je n'ai plus qu'a lancer le player (Clementine en ce qui me concerne). Je me suis basé sur la note en pièce jointe, issue d'un site dont j'ai perdu le signet. Yann COHEN a écrit : Bonjour, Cela fait maintenant quelques heures que je lutte pour retrouver une configuration qui fonctionnait sous wheezy : la connexion via bluetooth sur un belkin I54 (interface avec une chaîne audio). Il y a pas mal de littérature sur ces problèmes, mais je n'ai pas trouvé de solution. Sur plusieurs machines jessie je rencontre le même soucis avec plusieurs adaptateurs bt. Dans /etc/bluetooth/audio.conf * soit je mets un Disable=Socket et alors j'ai Unable to select SEP (que je ne comprends pas : SEP c'est quoi ?) * soit avec Enable=Socket je rencontre un Failed to open module module-bluetooth-device, et si je pousse un peu en mettant un lien sur module-bluez5-device alors j'ai un : [pulseaudio] module.c: Failed to load module module-bluetooth-device: symbol pa__init not found. J'avoue ne plus savoir que tester et que cela ne m'arrange pas car je voulais monter une plateforme de musique pour l'anniv de mon fils avec mixxx en utilisant la liaison bluetooth mais bon on ferra cela avec une rallonge jack ! Mon second essai, en créant un lien entre module-bluez5-device et module-bluetooth-device, me laisse penser qu'il y a un problème de version entre pulseaudio et bluez5. Quelle est la configuration à mettre en œuvre pour retrouver cette connexion ? Cordialement. Yann. -- Cordialement, Bernardo. Réacter : L'être humain, en général, dans la vie, réacte. On réacte, c'est à dire qu'on fait ce qu'on est supposé faire. Travailler, manger... J'm'excuse de l'expression ; chier, mais je trouve qu'un être humain doit créer. -+- Jean-Claude VanDamme -+- Hi, I show below the method which I checked with pluseaudio. Could you check with this? - 0. install packges. $ sudo apt-get install pulseaudio pulseaudio-module-bluetooth 1. setup /etc/bluetooth/audio.conf Please add the following line to the General. [General] Disable=Source,Socket 2. reboot bluetooth daemon and pulseaudio $ su $ saisir le mdp root # /etc/init.d/bluetooth restart # ctrl + d $ pactl load-module module-bluetooth-discover 3. Pairing , trust and check $ bluez-simple-agent hci0 00:XX:XX:XX:XX:58 $ bluez-test-device trusted 00:XX:XX:XX:XX:58 yes You can check with the following command: the list of devices that are paired. $ bluez-test-device list 00:XX:XX:XX:XX:58 LBT-AR200C2 4. connect to audio device. $ bluez-test-audio connect 00:XX:XX:XX:XX:58 5. confirmation of the device that is recognized by pulseaudio $ pactl list cards short 0 alsa_card.pci-_00_08.0 module-alsa-card.c 2 bluez_card.00_XX_XX_XX_XX_58module-bluetooth-device.c If a list of Bluetooth does not come out as follows, there is a possibility that Bluetooth device is not recognized, or is incorrectly configured. $ pactl list cards short 0 alsa_card.pci-_00_08.0 module-alsa-card.c 6. Change profile to a2dp $ pactl set-card-profile bluez_card.00_XX_XX_XX_XX_58 a2dp 7. Play music.
