Results 1 to 9 of 9

Thread: Some Problems With Connecting SRS-XB30 With Blueman Manager

  1. #1
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Question Some Problems With Connecting SRS-XB30 With Blueman Manager

    I have a problem connecting my Sony SRS-XB30 Bluetooth Speaker using Blueman Bluetooth Manager in OpenSUSE Leap 42.3 on my desktop computer. About a week ago it would connect fine without a problem. However, since then there was a few software updates through SUSE on-line and Bluedevil5 was replaced with Blueman Manager and it had problems re-pairing with the SRS-XB30 bluetooth speaker. The following is my basic information:

    blueman: Version 2.0.6-2.3.1
    BlueZ: Version 5.41-6.1
    Distribution: OpenSUSE Leap 42.3 64bit
    Desktop environment: Plasma KDE Version 5.8.7-2.1

    At first the problem was pairing the SRS-XB30 with the Blueman Manager because the SRS-XB30 expected to be paired with a PIN value of 0000, which the Blueman Manager never prompted for a PIN value directly on the Desktop screen but through the Plasma KDE Notifications. By the time I clicked on Notifications and then clicked on Enter Authority and the PIN prompt window finally appears the time has expired for me to enter the 0000 PIN value. However, when I finally got PIN value entered and the SRS-XB30 device paired with the bluetoothctl text command, there is still another problem with getting the SRS-XB30 device connected. The following indicates the problem:

    Code:
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# pair B8:D5:0B:25:AA:4C
    Attempting to pair with B8:D5:0B:25:AA:4C
    [CHG] Device B8:D5:0B:25:AA:4C Paired: yes
    Pairing successful
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# list-attributes B8:D5:0B:25:AA:4C
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# info B8:D5:0B:25:AA:4C
    Device B8:D5:0B:25:AA:4C
            Name: SRS-XB30
            Alias: SRS-XB30
            Class: 0x240414
            Icon: audio-card
            Paired: yes
            Trusted: yes
            Blocked: no
            Connected: no
            LegacyPairing: yes
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# connect B8:D5:0B:25:AA:4C
    Attempting to connect to B8:D5:0B:25:AA:4C
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Modalias: bluetooth:v0039p1582d2203
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00000000-deca-fade-deca-deafdecacaff
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00001108-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
    Failed to connect: org.bluez.Error.Failed
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# connect B8:D5:0B:25:AA:4C
    Attempting to connect to B8:D5:0B:25:AA:4C
    Failed to connect: org.bluez.Error.Failed
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]#
    However, when I go back using the Blueman Manager GUI, I now see the following:

    [IMG]file:///home/davids/images/OpenSUSE-Leap/Blueman-Manager/Blueman-Manager-6.0.2-SRS-XB30-04.png[/IMG]
    I'm not sure how to insert the snapshot screen images I took in this posting?

    When I click on the "More" button, the following information is shown:

    [IMG]file:///home/davids/images/OpenSUSE-Leap/Blueman-Manager/Blueman-Manager-6.0.2-SRS-XB30-05.png[/IMG]
    I'm not sure how to insert the snapshot screen images I took in this posting?

    From what I understand from this error message displayed, it looks like the DBus support for the blueman.bluez Bluetooth Stack is missing the protocol for the Sony SRS-XB30 loudspeaker device, which is odd because the SRS-XB30 device was working fine prior to the OpenSUSE Leap 42.3 update on-line from SUSE. Can anyone correct this problem with the DBus data base?

    Thank you,

    David A. Smith

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,006
    Blog Entries
    1

    Default Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Quote Originally Posted by DavidASmith072 View Post
    When I click on the "More" button, the following information is shown:

    [IMG]file:///home/davids/images/OpenSUSE-Leap/Blueman-Manager/Blueman-Manager-6.0.2-SRS-XB30-05.png[/IMG]
    I'm not sure how to insert the snapshot screen images I took in this posting?
    Upload the image to https://susepaste.org/ (select 'Image' at top right). Change the 'Delete After' to a sensible period, and click on 'Create'. I recommend right-clicking on the image, select 'Copy Image Location', and using that URL via the 'Insert Image' button to get the image displayed here. (The susepaste generated URL is missing the file suffix which prevents it from working directly.)

    Hope that makes sense.
    openSUSE Leap 15.0; KDE Plasma 5

  3. #3
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Exclamation Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Quote Originally Posted by deano_ferrari View Post
    Upload the image to https://susepaste.org/ (select 'Image' at top right). Change the 'Delete After' to a sensible period, and click on 'Create'. I recommend right-clicking on the image, select 'Copy Image Location', and using that URL via the 'Insert Image' button to get the image displayed here. (The susepaste generated URL is missing the file suffix which prevents it from working directly.)

    Hope that makes sense.
    I understand your explanation of how to use susepaste.org to upload my screen snap-shot images to it and copy and paste it's url address string into the Insert Image url field. However, when I do, my images don't show in my posting and I have tried both png and jpeg image formats. Yet these images show on the susepaste.org web site. Why?



    David A. Smith

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,006
    Blog Entries
    1

    Default Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Quote Originally Posted by DavidASmith072 View Post
    I understand your explanation of how to use susepaste.org to upload my screen snap-shot images to it and copy and paste it's url address string into the Insert Image url field. However, when I do, my images don't show in my posting and I have tried both png and jpeg image formats. Yet these images show on the susepaste.org web site. Why?


    David A. Smith
    Because the URL provided by susepaste.org is not quite complete, hence my suggestion to right-click on the image itself, select "Copy Image Location", and use that complete URL with the "Insert Image" tool in the forum editor. (The other option is to take the susepaste URL and append with the file format extension when adding it here.)
    openSUSE Leap 15.0; KDE Plasma 5

  5. #5
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Question Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    I have a problem connecting my Sony SRS-XB30 Bluetooth Speaker using Blueman Bluetooth Manager in OpenSUSE Leap 42.3 on my desktop computer. About a week ago it would connect fine without a problem. However, since then there was a few software updates through SUSE on-line and Bluedevil5 was replaced with Blueman Manager and it had problems re-pairing with the SRS-XB30 bluetooth speaker. The following is my basic information:

    blueman: Version 2.0.6-2.3.1
    BlueZ: Version 5.41-6.1
    Distribution: OpenSUSE Leap 42.3 64bit
    Desktop environment: Plasma KDE Version 5.8.7-2.1

    At first the problem was pairing the SRS-XB30 with the Blueman Manager because the SRS-XB30 expected to be paired with a PIN value of 0000, which the Blueman Manager never prompted for a PIN value directly on the Desktop screen but through the Plasma KDE Notifications. By the time I clicked on Notifications and then clicked on Enter Authority and the PIN prompt window finally appears the time has expired for me to enter the 0000 PIN value. However, when I finally got PIN value entered and the SRS-XB30 device paired with the bluetoothctl text command, there is still another problem with getting the SRS-XB30 device connected. The following indicates the problem:

    Code:
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# pair B8:D5:0B:25:AA:4C
    Attempting to pair with B8:D5:0B:25:AA:4C
    [CHG] Device B8:D5:0B:25:AA:4C Paired: yes
    Pairing successful
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# list-attributes B8:D5:0B:25:AA:4C
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# info B8:D5:0B:25:AA:4C
    Device B8:D5:0B:25:AA:4C
            Name: SRS-XB30
            Alias: SRS-XB30
            Class: 0x240414
            Icon: audio-card
            Paired: yes
            Trusted: yes
            Blocked: no
            Connected: no
            LegacyPairing: yes
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# connect B8:D5:0B:25:AA:4C
    Attempting to connect to B8:D5:0B:25:AA:4C
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Modalias: bluetooth:v0039p1582d2203
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00000000-deca-fade-deca-deafdecacaff
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00001108-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
    [CHG] Device B8:D5:0B:25:AA:4C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
    Failed to connect: org.bluez.Error.Failed
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# connect B8:D5:0B:25:AA:4C
    Attempting to connect to B8:D5:0B:25:AA:4C
    Failed to connect: org.bluez.Error.Failed
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]#
    However, when I go back using the Blueman Manager GUI, I now see the following:



    When I click on the "More" button, the following information is shown:



    From what I understand from this error message displayed, it looks like the DBus support for the blueman.bluez Bluetooth Stack is missing the protocol for the Sony SRS-XB30 loudspeaker device, which is odd because the SRS-XB30 device was working fine prior to the OpenSUSE Leap 42.3 update on-line from SUSE. Can anyone correct this problem with the DBus data base?

    Thank you,

    David A. Smith

  6. #6
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Question Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    I just installed the pulseaudio-module-bluetooth for OpenSUSE Leap 42.3 and repaired the SRS-XB30 device but it didn't fix the connection failure of the SRS-XB30 device with the Blueman Manager. The following screen snap shots is what happens:





    When I initiate the pairing of the SRS-XB30 device, I click on the + button in the Blueman Manager window, which brings up the bluetooth device scanning window and the SRS-XB30 device is detected. Then I click on the SRS-XB30 device icon and then click on the Manual PIN option and enter 0000 for the pin number and then click on Next, which does pair the device.





    However, for some reason the rest of the setup process for the SRS-XB30 device fails but the device is added to the bluetooth device list of the Blueman Manager with the SRS-XB30 paired. When I click on Restart the wizard, the SRS-XB30 device is no longer found in the bluetooth scanning because it has been already paired. If I click on Close, the following appears:





    If I click on the SRS-XB30 device icon in the bluetooth device list, it displays the current status of the SRS-XB30 device as being Trusted and not Blocked. However, if I click on Connect, a notification message appears, saying; "The SRS-XB30 bluetooth device has failed to connect."

    If I run the bluetoothctl text-based utility and do the following:


    Code:
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# paired-devices
    Device 90:7F:61:11:47:52 ThinkPad Compact Bluetooth Keyboard with TrackPoint 
    Device B8:D5:0B:25:AA:4C SRS-XB30 [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]# info B8:D5:0B:25:AA:4C
    Device B8:D5:0B:25:AA:4C
            Name: SRS-XB30
            Alias: SRS-XB30
            Class: 0x240414
            Icon: audio-card
            Paired: yes
            Trusted: yes
            Blocked: no
            Connected: yes
            LegacyPairing: no
            UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
            UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
            UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
            UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
            UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
            UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
            UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
            Modalias: bluetooth:v0039p1582d2203
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [CHG] Device B8:D5:0B:25:AA:4C Connected: yes
    [CHG] Device B8:D5:0B:25:AA:4C Connected: no
    [ThinkPad Compact Bluetooth Keyboard with TrackPoint]#
    This is puzzling to what's wrong. However, the pulseaudio-module-bluetooth version that I installed is version 9.0-8.1 and the reason why I asked this is because the link you gave me in your previous comment took me to the download.opensuse.org web site where a direct install link is and it has a path repository error, because when I installed it, the following warning message appeared:


    Code:
    "An error occurred during repository initialization. [http-download.opensuse.org-ba4934ed|http://download.opensuse.org/ports/update/leap/42.3/] Valid metadata not found at specified URL History: - [http-download.opensuse.org-ba4934ed|http://download.opensuse.org/ports/update/leap/42.3/] Repository type can't be determined."

    I am not sure if this repository is correct for the current port updates because it wasn't directed to the OSS directory path, therefor it didn't work at first until I corrected it at my end. I would assume what I did was correct otherwise the repository for installing the pulseaudio-module-bluetooth wouldn't been able to be installed?


    Thank you,


    David A. Smith

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,286
    Blog Entries
    15

    Default Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Quote Originally Posted by DavidASmith072 View Post
    <snip>
    Code:
    "An error occurred during repository initialization.
    [http-download.opensuse.org-ba4934ed|http://download.opensuse.org/ports/update/leap/42.3/]  Valid metadata not found at specified URL History: -  [http-download.opensuse.org-ba4934ed|http://download.opensuse.org/ports/update/leap/42.3/]  Repository type can't be determined."
    I am not sure if this repository is correct for the current port updates because it wasn't directed to the OSS directory path, therefor it didn't work at first until I corrected it at my end. I would assume what I did was correct otherwise the repository for installing the pulseaudio-module-bluetooth wouldn't been able to be installed?
    Hi
    Ports is not for the standard x86_64 distribution...It's for arm, ppc, risc etc architectures.

    The standard ones are oss/non-oss and oss/non-oss-updates
    http://download.opensuse.org/distribution/leap/42.3/

    You need to clean up your repositories and update the system.

    I'd also suggest skipping the GUI tools and seeing if you can connect via command line utilities first...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #8
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Question Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Ports is not for the standard x86_64 distribution...It's for arm, ppc, risc etc architectures.

    The standard ones are oss/non-oss and oss/non-oss-updates
    http://download.opensuse.org/distribution/leap/42.3/

    You need to clean up your repositories and update the system.

    I'd also suggest skipping the GUI tools and seeing if you can connect via command line utilities first...
    Thank you for your advice to clean up my repositories. Someone from github.org gave me a link to the pulseaudio-module-bluetooth binary direct installation file for openSUSE Leap 42.3 from the https://software.opensuse.org/packag...dule-bluetooth web site. Of course not knowing what architecture it was for, I assumed it was for Intel x86_64 and I installed it and it messed me up. OpenSUSE should provide a clearer way of indicated what repository is for what hardware architecture in it's server address paths. Just a simple architecture subdirectory, such as /x86_64/ and /risc_xx_64/, would save a lot of users headaches from accidentally mixing up different architecture software.

    Anyway, I got my repositories cleaned up and uninstalled the wrong architecture software and replaced it with the correct architecture software versions. However, I still have an issue with connecting the SRS-XB30 bluetooth device using the non-gui bluetoothctl program. The following screen shot shows my results:


    I have the correct version of pulseaudio-module-bluetooth installed, which is: 'pulseaudio-module-bluetooth-9.0-8.1.x86_64', the highest available version installed from the current updated repositories that I now have installed on my system.

    What can I try next is the big question?

    David A. Smith

  9. #9
    Join Date
    Nov 2012
    Location
    Berkeley Heights, NJ
    Posts
    20

    Thumbs up Re: Some Problems With Connecting SRS-XB30 With Blueman Manager

    Well, last evening I had sometime to try different things on my system to find out why the SYS-XB30 device would not connect. So I decided to try the PulseAudio Manager app and when I brought this up on screen, I noticed the following:



    At the lower left corner of the PulseAudio Manager gave a clue. This "Access denied" failure is, from what I understand, likely caused by a mismatch in the cookie used to authenticate to the pulse daemon. I know the system must connect with the same cookie that was used by the daemon when it started. Normally when the server starts it uses the cookie in ~/.config/pulse/cookie (this can be changed with $PULSE_COOKIE). Any client that connects needs to use the same cookie.

    So this means that if I want to connect to the daemon with a different user (root, for example) than what the daemon was started with, I need to manually copy the cookie to the other users home directory or use the PULSE_COOKIE environment variable to select a cookie file.

    Lucky I made a backup of my ~/.config directory so I could restore anything that could get corrupted in this sub-directory. File by file in the ~/.config/pulse/cookie sub-directory I compared against my backup copy from an usb flash drive from about ten months ago and all files were the same size and contents except for the file dates. So I left these cookie files alone.

    However, I did spotted some interesting files in the ~/.config directory named:

    bluedevilglobalrc bluedevil.notifyrc
    bluedevilglobalrc.qV6090 bluedevilreceiverrc


    which are related to the bluedevil bluetooth device manager. I also compared these four files against my backup of ten months ago and the only difference was the current bluedevilglobalrc file had a third entity for a third usb bluetooth transceiver adapter, as shown in the following:

    Code:
    [Adapters]
    00:1C:F0:EE:B5:FB_powered=true
    00:24:7E:9E:0D:4D_powered=true
    5C:F3:70:87:F7:05_powered=true
    
    [Devices]
    connectedDevices=90:7F:61:11:47:52
    
    [Global]
    bluetoothBlocked=false
    A few weeks ago, my bluetooth Lenovo ThinkPad keyboard wouldn't connect to this computer either and I traced it down to a bad Microsoft usb bluetooth adapter, which I replaced with a Logitec usb bluetooth adapter and that was working fine with the Lenovo ThinkPad keyboard and the SRS-XB30 speaker device. With that being said, I then decided to try to un-install the PulseAudio system and re-install it and BINGO! The SRS-XB30 speaker device automatically connected as soon as I turned it on and it played from the PulseAudio system with no problems. I guess something was corrupted with the way the PulseAudio system was interfaced with the Dbus and not finding the protocol for the SRS-XB30 device because Blueman Manager doesn't report this missing in the Notifications anymore.

    I have tried shutting down my system, rebooting it and the SRS-XB30 device still connects reliably and plays without problems.

    Whooo!!! I am glad this problem is solved.

    Thanks everyone for your suggestions!

    David A. Smith

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •