Blueman cannot detect the headphone

Forum Forums General Software Blueman cannot detect the headphone

Tagged: 

  • This topic has 16 replies, 4 voices, and was last updated Mar 29-6:28 pm by symbol.
Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #101893
    Member
    symbol

      My blueman cannot detect my headphone while windows bluetooth can?

      What I am going to do?

      • This topic was modified 1 month, 3 weeks ago by symbol.
      • This topic was modified 1 month, 3 weeks ago by symbol.
      #101901
      Forum Admin
      rokytnji
        Helpful
        Up
        0
        ::

        Howdy.

        Post back this info before running blueman

        sudo /etc/init.d/bluetooth status

        inxi -Fxz -r

        # bluetoothctl show

        then when trying pairing. Launch blueman from command line so you can see what is happening
        blueman-manager

        Also you need to unblock and turn on bluetooth in conman
        rfkill list

        will show it’s current status. Good Luck.

        `

        Sometimes I drive a crooked road to get my mind straight.
        Not all who Wander are Lost.
        I'm not outa place. I'm from outer space.

        Linux Registered User # 475019
        How to Search for AntiX solutions to your problems

        #101926
        Member
        Robin
          Helpful
          Up
          0
          ::

          Additionally, please make sure your user is member of the group “bluetooth“.

          antiX main menu → “maintenance” → “user management” → Tab: “tribal identity”
          From dropdown menu select your user and check the box “bluetooth”, then click “apply”.

          user management add goup

          Change of your current user’s group membership will take place only after logging out and log in again (no full reboot needed).

          Windows is like a submarine. Open a window and serious problems will start.

          #101944
          Moderator
          caprea
            Helpful
            Up
            0
            ::

            You could try another kernel.
            We need more information.

            #101968
            Forum Admin
            rokytnji
              Helpful
              Up
              0
              ::

              @ robin.

              I thought checking the box and hitting apply would remove bluetooth from the owners group.

              Plus I read that lp is what is needed on group to tether to bluetooth

              @shop:~
              $ groups
              harry lp dialout cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner

              am I mistaken thinking this? Or does this only apply to live sessions.

              `

              • This reply was modified 1 month, 3 weeks ago by rokytnji.

              Sometimes I drive a crooked road to get my mind straight.
              Not all who Wander are Lost.
              I'm not outa place. I'm from outer space.

              Linux Registered User # 475019
              How to Search for AntiX solutions to your problems

              #101999
              Member
              Robin
                Helpful
                Up
                1
                ::

                Hello rokytnji,

                I thought checking the box and hitting apply would remove bluetooth from the owners group.

                How this? Checking a box adds the user to the group, making him member of the very group, while unchecking the box removes the user from a group membership. (The box in my screenshot shows unchecked state, since the PC doesn’t have bluetooth.)

                Or does this only apply to live sessions.

                No, that’s all the same for any linux, regardless whether live or installed. Merely the group names might differ. And programs may add their private groups (example: vboxusers), as well as users can add groups as needed. This is useful for e.g. excluding users from access to and reading (or writing) in specific directories (then these users should not have root access and not being member of the sudo group, which would render it useless). On multi user systems this way you can easily grant access to different services or tools or folders to different users, simply based on their group membership.

                I read that lp is what is needed on group to tether to bluetooth

                This is true, strange enough, arch linux instructions say so, and it’s probably also true for antix (have not tested this, no bluetooth device around). But nevertheless, basically the group management works this way: If you want to use the line-printer (lp), which means to have access to the parallel port device, you need to be member if the group lp. If you want to use a document scanner, you need to be member of the group scanner, and possibly also member of sane, and so on. So, if you want to use the bluetooth device… just check the box to be member of that group the same way.

                Further reading (a list of default debian user groups and how to make use of them)
                https://wiki.debian.org/SystemGroups#Other_System_Groups

                Many greetings
                Robin

                Windows is like a submarine. Open a window and serious problems will start.

                #102076
                Forum Admin
                rokytnji
                  Helpful
                  Up
                  0
                  ::

                  Thanks robin. Gonna see if this fixes my bluetooth problem on my chromebook and other antiX installs.

                  Well no joy on the shop computer. I don’t have bluetooth dongle inserted though

                  harry@shop:~
                  $ inxi -E
                  Bluetooth:
                    Message: No bluetooth data found.
                  

                  But I added bluetooth to the group

                  harry@shop:~
                  $ groups
                  harry lp dialout cdrom floppy sudo audio dip video plugdev users netdev bluetooth lpadmin scanner
                  

                  and logged in and out and tried to launch blueman anyways

                  harry@shop:~
                  $ blueman-manager
                  blueman-manager version 2.1.4 starting
                  Blueman applet needs to be running
                  harry@shop:~
                  $ blueman-applet
                  blueman-applet version 2.1.4 starting
                  blueman-applet 19.16.15 WARNING  PluginManager:148 __load_plugin: Not loading PPPSupport because its conflict has higher priority
                  blueman-applet 19.16.15 WARNING  PluginManager:148 __load_plugin: Not loading DhcpClient because its conflict has higher priority
                  blueman-tray version 2.1.4 starting
                  blueman-applet 19.16.30 ERROR    BasePlugin:76 _load     : Error calling StartServiceByName for org.blueman.Mechanism: Launch helper exited with unknown return code 1
                  Traceback (most recent call last):
                    File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 36, in __init__
                      self.init()
                  gi.repository.GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.blueman.Mechanism: Launch helper exited with unknown return code 1 (25)
                  
                  During handling of the above exception, another exception occurred:
                  

                  I coulda posted more traceback errors but I figure you get the idea. No Worky even with a dongle unplugged. Besides this is not my thread.

                  • This reply was modified 1 month, 3 weeks ago by rokytnji.
                  • This reply was modified 1 month, 3 weeks ago by rokytnji.

                  Sometimes I drive a crooked road to get my mind straight.
                  Not all who Wander are Lost.
                  I'm not outa place. I'm from outer space.

                  Linux Registered User # 475019
                  How to Search for AntiX solutions to your problems

                  #103321
                  Member
                  symbol
                    Helpful
                    Up
                    0
                    ::
                    $ sudo /etc/init.d/bluetooth status
                    bluetooth is running.
                    $ inxi -Fxz -r
                    ...
                    Bluetooth:
                      Device-1: Apple Bluetooth Host Controller type: USB driver: btusb v: 0.8
                        bus-ID: 2-1.8.1.3:8
                      Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
                        bt-v: 2.1 lmp-v: 4.0
                    ...
                    
                    #103322
                    Member
                    symbol
                      Helpful
                      Up
                      0
                      ::

                      Finally my JBL headset appears in the blueman manager, it hardly appears.
                      The error shows: Connection Failed: Protocol not available
                      Many posts suggest me to install pulseaudio-module-bluetooth:
                      https://askubuntu.com/questions/1421089/cant-connect-bluetooth-headphones-anymore

                      While I cannot install it with command line:

                      $ sudo apt-get install pulseaudio-module-bluetooth
                      
                      Reading package lists... Done
                      Building dependency tree... Done
                      Reading state information... Done
                      Some packages could not be installed. This may mean that you have
                      requested an impossible situation or if you are using the unstable
                      distribution that some required packages have not yet been created
                      or been moved out of Incoming.
                      The following information may help to resolve the situation:
                      
                      The following packages have unmet dependencies:
                       pulseaudio-module-bluetooth : Depends: libpulse0 (= 14.2-2) but 14.2-2.0nosystemd1 is to be installed
                                                     Depends: pulseaudio (= 14.2-2)
                      E: Unable to correct problems, you have held broken packages.
                      #103324
                      Member
                      symbol
                        Helpful
                        Up
                        0
                        ::

                        Thanks, some other devices are detectable through bluetooth, while Connection Failed: Protocol not available happens often.

                        #103326
                        Moderator
                        caprea
                          Helpful
                          Up
                          1
                          ::

                          It was asked for
                          inxi -Fxz -r
                          but you posted only a small part of the output.
                          We still don’t even know which version of antiX is installed.
                          pulseaudio-module-bluetooth is required for audio bluetooth devices, if it can’t get installed probably the repos is wrong. The inxi -Fxz -r output would allow a look.

                          #103382
                          Member
                          symbol
                            Helpful
                            Up
                            0
                            ::

                            $ inxi -Fxz -r

                            Bluetooth:
                            Device-1: Apple Bluetooth Host Controller type: USB driver: btusb v: 0.8
                            bus-ID: 2-1.8.1.3:8
                            Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
                            bt-v: 2.1 lmp-v: 4.0

                            Attached is the full output, when I paste the whole output, antix linux prohibit me doing this indicating there is a security issue.

                            cat /etc/antix-version
                            antiX-21_x64-full Grup Yorum 31 October 2021
                            
                            Attachments:
                            #103388
                            Moderator
                            caprea
                              Helpful
                              Up
                              0
                              ::

                              From the output.txt

                              Repos:
                                Packages: 1919
                                No active apt repos in: /etc/apt/sources.list.d/antix.list

                              You somehow disabled the antiX sources. Please use repo-manager, control-centre > Software > Repo Manager
                              On the antiX Repos tab click on the button for “Automatic selection of the fastest currently available antiX repo server”

                              Afterwards sudo apt update from terminal and then try again to install
                              pulseaudio
                              gstreamer1.0-pulseaudio
                              pulseaudio-module-bluetooth
                              pavucontrol

                              To make pulseaudio autostart at boot you have to go to
                              control-centre > session > User-desktop-session
                              On the startup tab search for pulseaudio and make it look like that

                              ## Uncomment if using pulseaudio (you need to install it). Make sure it starts before volumeicon.
                              pulseaudio -D &

                              Reboot
                              Now you can try again blueman

                              #103389
                              Member
                              symbol
                                Helpful
                                Up
                                0
                                ::

                                I don’t think I disable the antix repo. The updated output.txt still shows No active apt repos in: /etc/apt/sources.list.d/antix.list

                                You somehow disabled the antiX sources

                                #103391
                                Moderator
                                caprea
                                  Helpful
                                  Up
                                  0
                                  ::

                                  That’s strange, if you open the list in geany

                                  sudo geany /etc/apt/sources.list.d/antix.list
                                  

                                  it should contain this

                                  # Use with Debian Bullseye repositories. 
                                  deb http://ftp.osuosl.org/pub/mxlinux/antix/bullseye/ bullseye main nosystemd nonfree 
                                  #deb-src http://ftp.osuosl.org/pub/mxlinux/antix/bullseye/ bullseye main nosystemd nonfree 
                                Viewing 15 posts - 1 through 15 (of 17 total)
                                • You must be logged in to reply to this topic.