Testers needed for blueman and modem-manager-gui

Forum Forums antiX-development Development Testers needed for blueman and modem-manager-gui

  • This topic has 27 replies, 7 voices, and was last updated Jan 11-5:40 pm by Xecure.
Viewing 13 posts - 16 through 28 (of 28 total)
  • Author
    Posts
  • #49376
    Moderator
    Brian Masinick
      Helpful
      Up
      0
      ::

      Thanks, I made the changes and I will test again today.

      --
      Brian Masinick

      #49384
      Moderator
      Brian Masinick
        Helpful
        Up
        0
        ::

        I don’t know what is STILL wrong. I did
        sudo apt purge policykit-1
        and then

        wget https://download.tuxfamily.org/antix/Testing/blueman_2.1.4-1.0antix1_amd64.deb
        sudo apt install ./blueman_2.1.4-1.0antix1_amd64.deb

        and I confirm that
        $ `apt policy blueman
        blueman:
        Installed: 2.1.4-1.0antix1
        Candidate: 2.1.4-1.0antix1
        Version table:
        *** 2.1.4-1.0antix1 100
        100 /var/lib/dpkg/status`

        although I also see:

             2.1.4-1+b1 500
                500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages
             2.0.8-1.antix1 500
                500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 Packages

        Could that be what is causing me problems? I STILL see
        “Connection Failed, Protocol not available”

        dmesg shows a few Bluetooth messages, but I did not see any obvious error indications.

        I’m going to check another system that I previously thought was working and see if it is still working on this hardware.
        If it is, I have something set up wrong on this system. If the other system doesn’t work anymore, I may have another issue.
        I’ll follow up when I have more diagnostic details available.

        --
        Brian Masinick

        #49396
        Member
        Robin
          Helpful
          Up
          0
          ::

          Since I have already tested blueman on 17.4.1 version, I could check your new version also. On 17.4.1 the cellphone paired and connected without any problems, but when it came to transfer files there was no way to make this work. I had to use an old Win2000 in Virtualbox in order to transfer files finally. So it would be interesting to find out whether your new version will do the job.
          So my question is: Will this version of yours work on 17er antiX also, or do I have to create an 19er stick for this testing?
          If 19 is necessery, I’ll have to check whether graphics driver is fixed for this nvidia go 6600 card, before I can proceed to bluetooth tests therein.
          Greetings and best wishes for the New Year
          Robin

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

          #49397
          Member
          Xecure
            Helpful
            Up
            0
            ::

            Best wishes to you too, Robin.
            This thread is related to the future antiX21, that is being tested in its alpha1 version here: https://www.antixforum.com/forums/topic/antix-bullseye-a1-x64-bullseye-full-available/
            I doubt it will work on antiX 19 and even less on antiX 17.

            antiX Live system enthusiast.
            General Live Boot Parameters for antiX.

            #49399
            Member
            Xecure
              Helpful
              Up
              0
              ::

              Could that be what is causing me problems? I STILL see
              “Connection Failed, Protocol not available”

              You need pulseaudio and pulseaudio-module-bluetooth for a bluetooth headset to work, as indicated by other threads (that is why it worked on MX, which does, as far as I know, use pulseaudio).

              Off-topic: A bluez-alsa .deb package would make it possible to stream audio to the headphones using alsa + bluetooth without pulseaudio. I was trying to use the raspberry pie build as reference to build a .deb for antiX, but that requires systemd, so I will continue investigating (didn’t have much time to experiment) on the weekend and possibly come with something that does not require pulseaudio. But this is not related to this thread.

              antiX Live system enthusiast.
              General Live Boot Parameters for antiX.

              #49400
              Member
              Robin
                Helpful
                Up
                0
                ::

                Is there a 32bit version of antiX21 available? I could put it to an usb-stick for testing. Otherwise I’ll have to step back, since I don’t have access to any 64bit machines.

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

                #49401
                Member
                Xecure
                  Helpful
                  Up
                  0
                  ::

                  Is there a 32bit version of antiX21 available?

                  Don’t worry. Right now is for general ISO feedback. During the beta period there usually is a 32 and 64 bit ISO, so you will have your chance then.

                  antiX Live system enthusiast.
                  General Live Boot Parameters for antiX.

                  #49403
                  Member
                  Robin
                    Helpful
                    Up
                    0
                    ::

                    OK, I only thought of helping in test of bluetooth as asked here. But never mind, I’ll wait for things to happen 🙂

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

                    #49406
                    Moderator
                    Brian Masinick
                      Helpful
                      Up
                      0
                      ::

                      I womder if there has been a Debian-wide regression? It is not working any more on MX Linux and I was pretty sure it was working.
                      So I went to Debian and found the same thing.
                      Then I went to EndeavorOS, where it was not set up, so I exhaustively went through the steps and I think I just got it going; will test.
                      If so, it’s not hardware, it’s Debian infrastructure software. I’ll let you know once I have finished this effort.
                      I think I am getting somewhere on this at last…

                      --
                      Brian Masinick

                      #49407
                      Moderator
                      Brian Masinick
                        Helpful
                        Up
                        0
                        ::

                        Yes, I got it working on Endeavor OS, so now I will go back and see why it is or wasn’t working elsewhere. My headset is working, it’s working with my phone, my Chromebook, and now on the same hardware with Endeavor OS, so I will look into what else could be wrong.

                        --
                        Brian Masinick

                        #49409
                        Moderator
                        Brian Masinick
                          Helpful
                          Up
                          0
                          ::

                          In spite of getting Bluetooth to work and to achieve listening with my Soundcore Life Q10 headset on Endeavor OS, the same hardware where I’ve been running MX Linux, antiX 19.3, antiX Alpha Bullseye and Debian Bullseye Alpha 3, only Endeavor OS is working, suggesting something is wrong with the entire set of packages available with Debian-based systems (sample size 4) yet working with another OS on the same hardware.

                          Has anyone seen anything else? Any other thoughts on what has caused this apparent regression?

                          --
                          Brian Masinick

                          #49411
                          Moderator
                          Brian Masinick
                            Helpful
                            Up
                            0
                            ::

                            I’m giving up for today but I will come back to this. It sure looks like a software problem since I have three different systems and two different Bluetooth devices that can communicate, and I’ve been able to get one of my operating systems on the problem system to work.

                            If you have any ideas or see any clear issues, let me know and I’ll try again soon.

                            --
                            Brian Masinick

                            #49618
                            Member
                            Xecure
                              Helpful
                              Up
                              0
                              ::

                              Some of the feedback was split to: https://www.antixforum.com/forums/topic/split-bluetooth-testing/

                              If your post is missing and you didn’t know where it went, it is there now.

                              antiX Live system enthusiast.
                              General Live Boot Parameters for antiX.

                            Viewing 13 posts - 16 through 28 (of 28 total)
                            • You must be logged in to reply to this topic.