blueman-applet not starting

Forum Forums General Hardware blueman-applet not starting

Tagged: 

  • This topic has 13 replies, 4 voices, and was last updated Jul 8-7:59 pm by olsztyn.
Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #83953
    Member
    symbol

      Hi there, I am on macbook (antix 21) with a bluetooth device:

      $ sudo dmesg | grep -i blue
      [    3.343276] usb 2-1.8.1.3: Product: Bluetooth USB Host Controller
      [    5.638226] Bluetooth: Core ver 2.22
      [    5.638250] Bluetooth: HCI device and connection manager initialized
      [    5.638255] Bluetooth: HCI socket layer initialized
      [    5.638257] Bluetooth: L2CAP socket layer initialized
      [    5.638261] Bluetooth: SCO socket layer initialized
      [    5.754062] Bluetooth: hci0: BCM: chip id 63 build 1805
      [    5.755058] Bluetooth: hci0: BCM: product 05ac:8286
      [    5.756061] Bluetooth: hci0: BCM: features 0x07
      [    5.772060] Bluetooth: hci0: Apple Bluetooth Device
      [    6.492371] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [    6.492372] Bluetooth: BNEP filters: protocol multicast
      [    6.492375] Bluetooth: BNEP socket layer initialized
      

      However neither my blueman-manager or blueman-applet is starting

      $ blueman-manager
      blueman-manager version 2.1.4 starting
      Blueman applet needs to be running
      $ blueman-applet 
      blueman-applet version 2.1.4 starting
      blueman-tray version 2.1.4 starting
      blueman-applet 02.11.44 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:
      
      Traceback (most recent call last):
        File "/usr/lib/python3/dist-packages/blueman/plugins/BasePlugin.py", line 70, in _load
          self.on_load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 24, in on_load
          self.load_nap_settings()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 45, in load_nap_settings
          m = Mechanism()
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 15, in __call__
          cls._instance = super().__call__(*args, **kwargs)
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 43, in __init__
          super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 38, in __init__
          raise DBusProxyFailed(e.message)
      blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Launch helper exited with unknown return code 1
      blueman-applet 02.11.44 ERROR    PluginManager:162 __load_plugin: Failed to load Networking
      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:
      
      Traceback (most recent call last):
        File "/usr/lib/python3/dist-packages/blueman/main/PluginManager.py", line 160, in __load_plugin
          inst._load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/AppletPlugin.py", line 57, in _load
          super()._load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/BasePlugin.py", line 70, in _load
          self.on_load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 24, in on_load
          self.load_nap_settings()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 45, in load_nap_settings
          m = Mechanism()
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 15, in __call__
          cls._instance = super().__call__(*args, **kwargs)
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 43, in __init__
          super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 38, in __init__
          raise DBusProxyFailed(e.message)
      blueman.main.DBusProxies.DBusProxyFailed: 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.Error: 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:
      
      Traceback (most recent call last):
        File "/usr/bin/blueman-applet", line 42, in <module>
          BluemanApplet()
        File "/usr/lib/python3/dist-packages/blueman/main/Applet.py", line 34, in __init__
          self.Plugins.load_plugin()
        File "/usr/lib/python3/dist-packages/blueman/main/PluginManager.py", line 122, in load_plugin
          self.__load_plugin(cls)
        File "/usr/lib/python3/dist-packages/blueman/main/PluginManager.py", line 160, in __load_plugin
          inst._load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/AppletPlugin.py", line 57, in _load
          super()._load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/BasePlugin.py", line 70, in _load
          self.on_load()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 24, in on_load
          self.load_nap_settings()
        File "/usr/lib/python3/dist-packages/blueman/plugins/applet/Networking.py", line 45, in load_nap_settings
          m = Mechanism()
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 15, in __call__
          cls._instance = super().__call__(*args, **kwargs)
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 43, in __init__
          super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
        File "/usr/lib/python3/dist-packages/blueman/main/DBusProxies.py", line 38, in __init__
          raise DBusProxyFailed(e.message)
      blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Launch helper exited with unknown return code 1
      • This topic was modified 11 months ago by symbol. Reason: Update the code blocks
      • This topic was modified 11 months ago by symbol. Reason: Spaces
      #83964
      Moderator
      caprea
        Helpful
        Up
        1
        ::

        I faced the same problem this week after autoremoving elogind and some libpolkit stuff.
        After installing them again bluemanapplet started to work again.This was not a PC of mine, so I didn’t start experiments to look further whats the problem, but was happy it was working as before.

        #83990
        Member
        symbol
          Helpful
          Up
          0
          ::

          This does not work for me. I autoremove the blueman and reinstalled it and the error message remains the same.

          #84023
          Moderator
          caprea
            Helpful
            Up
            1
            ::

            Reinstalling blueman does not help.I can look for what was deinstalled on the system where this happened the next days.I hope it’s still in the logs.
            Is elogind installed on your system?

            #84251
            Member
            symbol
              Helpful
              Up
              0
              ::

              Yes, thanks for instant reply!
              Yes, my elogind is still installed in the system.

              sudo apt list --installed | grep elogind
              
              WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
              
              elogind/bullseye,now 246.10-3.0antix1 amd64 [installed]
              libelogind0/bullseye,now 246.10-3.0antix1 amd64 [installed]
              libpam-elogind/bullseye,now 246.10-3.0antix1 amd64 [installed]
              libpolkit-gobject-elogind-1-0/bullseye,now 0.105-31.1.0nosystemd0 amd64 [installed,automatic] 

              Attached apt.log is my apt log which records what I have installed and uninstalled in history.

              $ grep "install " /var/log/dpkg.log > apt.log
              ...
              2022-06-07 13:57:41 install libqmobipocket2:amd64 <none> 4:20.12.0-1
              2022-06-07 13:57:41 install okular:amd64 <none> 4:20.12.3-2
              

              Reinstalling blueman does not help.I can look for what was deinstalled on the system where this happened the next days.I hope it’s still in the logs.
              Is elogind installed on your system?

              • This reply was modified 11 months ago by symbol. Reason: Replace attachement
              Attachments:
              #84271
              Member
              symbol
                Helpful
                Up
                0
                ::

                I found the blueman issue got resolved mysteriously.

                #85220
                Member
                olsztyn
                  Helpful
                  Up
                  0
                  ::

                  I apologize for being late to this conversation, so revisiting this thread…

                  I faced the same problem this week after autoremoving elogind and some libpolkit stuff.
                  After installing them again bluemanapplet started to work again.This was not a PC of mine, so I didn’t start experiments to look further whats the problem, but was happy it was working as before.

                  Behavior reported in the initial post of this thread appear to be also the case for my *elogind*-free systems. I remember giving up bluetooth, when going to completely *elogind*-free antiX some half a year ago. Being *elogind*-free was more important to me than bluetooth…
                  However: Is there any update to antiX bluetooth infrastructure that would let antiX run *elogind*-free, using seatd instead?

                  • This reply was modified 10 months, 1 week ago by olsztyn.

                  Live antiX Boot Options (Previously posted by Xecure):
                  https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

                  #85740
                  Forum Admin
                  rokytnji
                    Helpful
                    Up
                    0
                    ::

                    I deleted my posts in this thread because

                    inxi -E

                    Told me I had not plugged in a bluetooth dongle. What I plugged in was wireless mouse dongle instead.
                    Sorry. 🙁

                    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

                    #85781
                    Forum Admin
                    rokytnji
                      Helpful
                      Up
                      0
                      ::

                      Ok, Found me a dongle

                      harry@biker:~
                      $ rfkill list
                      0: dell-wifi: Wireless LAN
                      	Soft blocked: no
                      	Hard blocked: no
                      1: dell-bluetooth: Bluetooth
                      	Soft blocked: yes
                      	Hard blocked: no
                      2: phy0: Wireless LAN
                      	Soft blocked: no
                      	Hard blocked: no
                      8: hci0: Bluetooth
                      	Soft blocked: yes
                      	Hard blocked: no
                      harry@biker:~
                      $ dmesg | grep -iC 3 "bluetooth"
                      dmesg: read kernel buffer failed: Operation not permitted
                      harry@biker:~
                      $ sudo dmesg | grep -iC 3 "bluetooth"
                      [    2.596322] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
                      [    2.609920] usb 2-1.7: New USB device found, idVendor=413c, idProduct=8187, bcdDevice= 5.17
                      [    2.609926] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                      [    2.609929] usb 2-1.7: Product: DW375 Bluetooth Module
                      [    2.609932] usb 2-1.7: Manufacturer: Dell Computer Corp
                      [    2.609934] usb 2-1.7: SerialNumber: 1C659D02317F
                      [    2.675330] usb 2-1.8: new full-speed USB device number 5 using ehci-pci
                      --
                      [    3.540482] dell_wmi: Unknown key with type 0x0011 and code 0xffd0 pressed
                      [    3.577644] input: AlpsPS/2 ALPS DualPoint Stick as /devices/platform/i8042/serio1/input/input13
                      [    3.590996] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input2
                      [    4.998225] Bluetooth: Core ver 2.22
                      [    4.998261] NET: Registered protocol family 31
                      [    4.998262] Bluetooth: HCI device and connection manager initialized
                      [    4.998267] Bluetooth: HCI socket layer initialized
                      [    4.998272] Bluetooth: L2CAP socket layer initialized
                      [    4.998277] Bluetooth: SCO socket layer initialized
                      [    5.025887] Console: switching to colour frame buffer device 170x48
                      [    5.045648] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
                      [    5.047789] dell_wmi: Unknown key with type 0x0011 and code 0xffd1 pressed
                      --
                      [    6.139631] elogind-daemon[1980]: Watching system buttons on /dev/input/event1 (Lid Switch)
                      [    6.139706] elogind-daemon[1980]: Watching system buttons on /dev/input/event3 (Sleep Button)
                      [    6.140341] elogind-daemon[1980]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
                      [    6.196210] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                      [    6.196214] Bluetooth: BNEP filters: protocol multicast
                      [    6.196220] Bluetooth: BNEP socket layer initialized
                      [    6.204863] NET: Registered protocol family 38
                      [    6.252072] random: crng init done
                      [    6.252076] random: 7 urandom warning(s) missed due to ratelimiting
                      --
                      [  625.572470] usb 2-1.7: new full-speed USB device number 6 using ehci-pci
                      [  625.656097] usb 2-1.7: New USB device found, idVendor=413c, idProduct=8187, bcdDevice= 5.17
                      [  625.656101] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                      [  625.656104] usb 2-1.7: Product: DW375 Bluetooth Module
                      [  625.656106] usb 2-1.7: Manufacturer: Dell Computer Corp
                      [  625.656108] usb 2-1.7: SerialNumber: 1C659D02317F
                      [  625.906411] usb 2-1.7: USB disconnect, device number 6
                      [  627.724483] Bluetooth: hci1: command 0x0c14 tx timeout
                      [  627.724556] Bluetooth: hci1: sending frame failed (-19)
                      [  629.772498] Bluetooth: hci1: command 0x0c25 tx timeout
                      [  629.772533] Bluetooth: hci1: sending frame failed (-19)
                      [  631.820469] Bluetooth: hci1: command 0x0c38 tx timeout
                      [  631.820499] Bluetooth: hci1: sending frame failed (-19)
                      [  633.868419] Bluetooth: hci1: command 0x0c39 tx timeout
                      [  633.868448] Bluetooth: hci1: sending frame failed (-19)
                      [  635.916381] Bluetooth: hci1: command 0x0c05 tx timeout
                      [  635.916405] Bluetooth: hci1: sending frame failed (-19)
                      [  676.515896] usb 2-1.7: new full-speed USB device number 7 using ehci-pci
                      [  676.598895] usb 2-1.7: New USB device found, idVendor=413c, idProduct=8187, bcdDevice= 5.17
                      [  676.598899] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                      [  676.598902] usb 2-1.7: Product: DW375 Bluetooth Module
                      [  676.598904] usb 2-1.7: Manufacturer: Dell Computer Corp
                      [  676.598906] usb 2-1.7: SerialNumber: 1C659D02317F
                      [  676.845212] usb 2-1.7: USB disconnect, device number 7
                      [  678.667878] Bluetooth: hci1: command 0x0c14 tx timeout
                      [  678.667910] Bluetooth: hci1: sending frame failed (-19)
                      [  680.715856] Bluetooth: hci1: command 0x0c25 tx timeout
                      [  680.715934] Bluetooth: hci1: sending frame failed (-19)
                      [  682.763827] Bluetooth: hci1: command 0x0c38 tx timeout
                      [  682.763853] Bluetooth: hci1: sending frame failed (-19)
                      [  684.812243] Bluetooth: hci1: command 0x0c39 tx timeout
                      [  684.812261] Bluetooth: hci1: sending frame failed (-19)
                      [  874.202396] usb 2-1.7: new full-speed USB device number 8 using ehci-pci
                      [  874.285300] usb 2-1.7: New USB device found, idVendor=413c, idProduct=8187, bcdDevice= 5.17
                      [  874.285304] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                      [  874.285307] usb 2-1.7: Product: DW375 Bluetooth Module
                      [  874.285310] usb 2-1.7: Manufacturer: Dell Computer Corp
                      [  874.285312] usb 2-1.7: SerialNumber: 1C659D02317F
                      [  874.531508] usb 2-1.7: USB disconnect, device number 8
                      [  876.298400] Bluetooth: hci1: command 0x0c14 tx timeout
                      [  876.298484] Bluetooth: hci1: sending frame failed (-19)
                      [  878.346396] Bluetooth: hci1: command 0x0c25 tx timeout
                      [  878.346429] Bluetooth: hci1: sending frame failed (-19)
                      [  880.394395] Bluetooth: hci1: command 0x0c38 tx timeout
                      [  880.394426] Bluetooth: hci1: sending frame failed (-19)
                      [  882.442394] Bluetooth: hci1: command 0x0c39 tx timeout
                      [  882.442424] Bluetooth: hci1: sending frame failed (-19)
                      [  901.178677] usb 2-1.3: USB disconnect, device number 3
                      [  913.822369] usb 2-1.1: new full-speed USB device number 9 using ehci-pci
                      [  914.051772] usb 2-1.1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
                      harry@biker:~
                      
                      harry@biker:~
                      $ sudo lsusb -t
                      /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
                          |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
                              |__ Port 1: Dev 9, If 0, Class=Wireless, Driver=btusb, 12M
                              |__ Port 1: Dev 9, If 1, Class=Wireless, Driver=btusb, 12M
                              |__ Port 8: Dev 5, If 0, Class=Application Specific Interface, Driver=, 12M
                              |__ Port 8: Dev 5, If 1, Class=Chip/SmartCard, Driver=, 12M
                      /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
                          |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
                      harry@biker:~
                      $ inxi -E
                      Bluetooth:
                        Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
                          driver: btusb
                        Report: hciconfig ID: hci0 rfk-id: 8 state: down bt-service: running
                          rfk-block: hardware: no software: yes address: 00:1A:7D:DA:71:13
                      harry@biker:~
                      

                      On to a next post for more command line readouts and explanations because forum spam software might freak out. To save me time. I copy and past this post and save it in text file using geany. So I don’t lose it. I keep a folder in ~/home named forum to keep track.

                      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

                      #85784
                      Forum Admin
                      rokytnji
                        Helpful
                        Up
                        0
                        ::

                        Computer I am testing with

                        harry@biker:~
                        $ sudo inxi -zv8
                        System:
                          Kernel: 5.10.57-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
                            v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.57-antix.1-amd64-smp
                            root=UUID=f8bed57e-e7fa-4754-b8eb-33b70943f063 ro quiet
                          Desktop: IceWM v: 2.9.7 dm: slimski v: 1.5.0
                            Distro: antiX-21_x64-full Grup Yorum 31 October 2021
                            base: Debian GNU/Linux 11 (bullseye)
                        Machine:
                          Type: Laptop System: Dell product: Latitude E4310 v: 0001 serial: <filter>
                            Chassis: type: 9 serial: <filter>
                          Mobo: Dell model: 0T6M8G v: A01 serial: <filter> BIOS: Dell v: A03
                            date: 07/08/2010
                        Battery:
                          ID-1: BAT0 charge: 38.6 Wh (100.0%) condition: 38.6/48.8 Wh (79.0%)
                            volts: 12.4 min: 11.1 model: Samsung SDI DELL RM6618A type: Li-ion
                            serial: N/A status: full
                        Memory:
                          RAM: total: 7.7 GiB used: 1.04 GiB (13.5%)
                          Array-1: capacity: 8 GiB slots: 2 EC: None max-module-size: 4 GiB
                            note: est.
                          Device-1: DIMM_A type: DDR3 detail: synchronous size: 4 GiB
                            speed: 1067 MT/s volts: N/A width (bits): data: 64 total: 64
                            manufacturer: SK-Hynix part-no: HMT351S6BFR8C-H9 serial: <filter>
                          Device-2: DIMM_B type: DDR3 detail: synchronous size: 4 GiB
                            speed: 1067 MT/s volts: N/A width (bits): data: 64 total: 64
                            manufacturer: SK-Hynix part-no: HMT351S6CFR8C-H9 serial: <filter>
                        PCI Slots:
                          Slot: 0 type: PCIe lanes: 16 status: available info: J5C1 length: long
                            volts: 3.3 bus-ID: ff:00.0
                          Slot: 1 type: PCIe lanes: 1 status: available info: J6C2 length: short
                            volts: 3.3 bus-ID: 01:00.0
                          Slot: 2 type: PCIe lanes: 1 status: in use info: J6D2 length: short
                            volts: 3.3 bus-ID: 02:00.0
                          Slot: 3 type: PCIe lanes: 1 status: in use info: J7C1 length: short
                            volts: 3.3 bus-ID: 03:00.0
                          Slot: 4 type: PCIe lanes: 1 status: available info: J7D2 length: short
                            volts: 3.3 bus-ID: 04:00.0
                        CPU:
                          Info: model: Intel Core i5 M 520 bits: 64 type: MT MCP arch: Westmere
                            gen: core 1 built: 2010-11 process: Intel 32nm family: 6
                            model-id: 0x25 (37) stepping: 5 microcode: 0x7
                          Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
                            L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
                            L3: 3 MiB desc: 1x3 MiB
                          Speed (MHz): avg: 2400 min/max: 1199/2400 boost: enabled
                            base/boost: 2399/4000 scaling: driver: acpi-cpufreq governor: performance
                            volts: 0.0 V ext-clock: 533 MHz cores: 1: 2400 2: 2400 3: 2400 4: 2400
                            bogomips: 19151
                          Flags: acpi aes aperfmperf apic arat arch_perfmon bts clflush cmov
                            constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est
                            flexpriority flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx
                            monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs
                            pge pni popcnt pse pse36 pti rdtscp rep_good sep smx ssbd sse sse2 sse4_1
                            sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc vme vmx vnmi vpid
                            xtopology xtpr
                          Vulnerabilities:
                          Type: itlb_multihit status: KVM: VMX disabled
                          Type: l1tf
                            mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
                          Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
                            SMT vulnerable
                          Type: meltdown mitigation: PTI
                          Type: spec_store_bypass
                            mitigation: Speculative Store Bypass disabled via prctl and seccomp
                          Type: spectre_v1
                            mitigation: usercopy/swapgs barriers and __user pointer sanitization
                          Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
                            IBRS_FW, STIBP: conditional, RSB filling
                          Type: srbds status: Not affected
                          Type: tsx_async_abort status: Not affected
                        Graphics:
                          Device-1: Intel Core Processor Integrated Graphics vendor: Dell
                            driver: i915 v: kernel arch: Gen5.75 process: Intel 45nm built: 2010 ports:
                            active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, VGA-1
                            bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
                          Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: intel gpu: i915
                            display-ID: :0.0 screens: 1
                          Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
                            s-diag: 414mm (16.31")
                          Monitor-1: eDP-1 mapped: eDP1 model: Seiko Epson 0x5441 built: 2010
                            res: 1366x768 hz: 60 dpi: 118 gamma: 1.2 chroma: red: x: 0.592 y: 0.349
                            green: x: 0.322 y: 0.537 blue: x: 0.153 y: 0.114 white: x: 0.314 y: 0.329
                            size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9
                            modes: 1366x768
                          EDID-Warnings: 1: parse_edid: unknown flag 0
                          OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
                            direct render: Yes
                        Audio:
                          Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell 5
                            driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b57
                            class-ID: 0403
                          Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes
                          Sound Server-2: PulseAudio v: 14.2 running: no
                        Network:
                          Device-1: Intel 82577LM Gigabit Network vendor: Dell driver: e1000e
                            v: kernel port: 6040 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
                          IF: eth0 state: down mac: <filter>
                          Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel
                            modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
                            chip-ID: 8086:422c class-ID: 0280
                          IF: wlan0 state: up mac: <filter>
                          IP v4: <filter> scope: global broadcast: <filter>
                          IP v6: <filter> scope: link
                          WAN IP: <filter>
                        Bluetooth:
                          Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
                            driver: btusb v: 0.8 bus-ID: 2-1.1:9 chip-ID: 0a12:0001 class-ID: e001
                          Report: hciconfig ID: hci0 rfk-id: 8 state: down bt-service: running
                            rfk-block: hardware: no software: yes address: <filter>
                          Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
                            link-mode: slave accept
                        Logical:
                          Message: No logical block device data found.
                        RAID:
                          Message: No RAID data found.
                        Drives:
                          Local Storage: total: 55.9 GiB used: 30.69 GiB (54.9%)
                          ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SV300S37A60G
                            family: Driven SSDs size: 55.9 GiB block-size: physical: 512 B
                            logical: 512 B sata: 3.0 speed: 3.0 Gb/s type: SSD serial: <filter>
                            rev: BBF0 temp: 39 C scheme: MBR
                          SMART: yes state: enabled health: PASSED on: 127d 0h cycles: 1032
                            read: 524 GiB written: 1074 GiB
                          Optical-1: /dev/sr0 vendor: TSSTcorp model: DVD+-RW TS-U633F rev: D500
                            dev-links: cdrom,cdrw,dvd,dvdrw
                          Features: speed: 24 multisession: yes audio: yes dvd: yes
                            rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
                        Partition:
                          ID-1: / raw-size: 53.02 GiB size: 51.88 GiB (97.86%)
                            used: 30.69 GiB (59.2%) fs: ext4 block-size: 4096 B dev: /dev/sda1
                            maj-min: 8:1 label: rootantiX21
                            uuid: f8bed57e-e7fa-4754-b8eb-33b70943f063
                        Swap:
                          Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100)
                          ID-1: swap-1 type: partition size: 2.87 GiB used: 0 KiB (0.0%)
                            priority: -2 dev: /dev/sda2 maj-min: 8:2 label: swapantiX
                            uuid: 1e9cc9ac-922d-4be4-92f4-8de90b7bcd7a
                        Unmounted:
                          Message: No unmounted partitions found.
                        USB:
                          Hub-1: 1-0:1 info: Full speed or root hub ports: 3 rev: 2.0 speed: 480 Mb/s
                            chip-ID: 1d6b:0002 class-ID: 0900
                          Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
                            speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900
                          Hub-3: 2-0:1 info: Full speed or root hub ports: 3 rev: 2.0
                            speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
                          Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
                            speed: 480 Mb/s chip-ID: 8087:0020 class-ID: 0900
                          Device-1: 2-1.1:9
                            info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: Bluetooth
                            driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA
                            chip-ID: 0a12:0001 class-ID: e001
                          Device-2: 2-1.8:5 info: Broadcom BCM5880 Secure Applications Processor
                            with fingerprint swipe sensor
                            type: Smart Card driver: N/A interfaces: 2 rev: 1.1 speed: 12 Mb/s
                            power: 100mA chip-ID: 0a5c:5801 class-ID: 0b00 serial: <filter>
                        Sensors:
                          System Temperatures: cpu: 51.0 C mobo: N/A sodimm: SODIMM C
                          Fan Speeds (RPM): cpu: 3062
                        Repos:
                          Packages: apt: 1636 lib: 779
                          No active apt repos in: /etc/apt/sources.list
                          Active apt repos in: /etc/apt/sources.list.d/antix.list
                            1: deb http://la.mxrepo.com/antix/bullseye/ bullseye main nosystemd nonfree
                          No active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
                          Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
                            1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
                          Active apt repos in: /etc/apt/sources.list.d/debian.list
                            1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free
                            2: deb http://security.debian.org/ bullseye-security main contrib non-free
                          Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
                            1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
                          No active apt repos in: /etc/apt/sources.list.d/various.list
                        Processes:
                          CPU top: 5 of 161
                          1: cpu: 17.3% command: firefox-esr pid: 8615 mem: 190.4 MiB (2.4%)
                          2: cpu: 9.8% command: firefox-esr pid: 6220 mem: 461.9 MiB (5.8%)
                          3: cpu: 2.8% command: firefox-esr pid: 6287 mem: 172.1 MiB (2.1%)
                          4: cpu: 2.2% command: xorg pid: 2057 mem: 41.0 MiB (0.5%)
                          5: cpu: 1.0% command: sudo pid: 10319 mem: 4.87 MiB (0.0%)
                          Memory top: 5 of 161
                          1: mem: 461.9 MiB (5.8%) command: firefox-esr pid: 6220 cpu: 9.8%
                          2: mem: 190.4 MiB (2.4%) command: firefox-esr pid: 8615 cpu: 17.3%
                          3: mem: 172.1 MiB (2.1%) command: firefox-esr pid: 6287 cpu: 2.8%
                          4: mem: 127.4 MiB (1.6%) command: firefox-esr pid: 6357 cpu: 0.3%
                          5: mem: 86.2 MiB (1.0%) command: firefox-esr pid: 8101 cpu: 0.0%
                        Info:
                          Processes: 161 Uptime: 41m wakeups: 3 Init: SysVinit v: 2.96 runlevel: 5
                          default: 5 tool: service Compilers: gcc: 10.2.1 alt: 10 Shell: Bash (sudo)
                          v: 5.1.4 running-in: roxterm inxi: 3.3.19
                        harry@biker:~
                        

                        I run elogind and pulseaudio

                        harry@biker:~
                        $ sudo lsusb -t
                        /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
                            |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
                                |__ Port 1: Dev 9, If 0, Class=Wireless, Driver=btusb, 12M
                                |__ Port 1: Dev 9, If 1, Class=Wireless, Driver=btusb, 12M
                                |__ Port 8: Dev 5, If 0, Class=Application Specific Interface, Driver=, 12M
                                |__ Port 8: Dev 5, If 1, Class=Chip/SmartCard, Driver=, 12M
                        /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
                            |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
                        harry@biker:~
                        $ inxi -E
                        Bluetooth:
                          Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
                            driver: btusb
                          Report: hciconfig ID: hci0 rfk-id: 8 state: down bt-service: running
                            rfk-block: hardware: no software: yes address: 00:1A:7D:DA:71:13
                        harry@biker:~
                        $ apt-cache policy elogind
                        elogind:
                          Installed: 246.10-3.0antix1
                          Candidate: 246.10-3.0antix1
                          Version table:
                         *** 246.10-3.0antix1 500
                                500 http://la.mxrepo.com/antix/bullseye bullseye/nosystemd amd64 Packages
                                100 /var/lib/dpkg/status
                             246.10-2.0antix4 500
                                500 http://la.mxrepo.com/antix/bullseye bullseye/main amd64 Packages
                             246.9.1-1+debian1 500
                                500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
                        harry@biker:~
                        $ apt-cache policy pulseaudio
                        pulseaudio:
                          Installed: 14.2-2.0nosystemd1
                          Candidate: 14.2-2.0nosystemd1
                          Version table:
                         *** 14.2-2.0nosystemd1 500
                                500 http://la.mxrepo.com/antix/bullseye bullseye/nosystemd amd64 Packages
                                100 /var/lib/dpkg/status
                             14.2-2 500
                                500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
                        harry@biker:~
                        

                        On to next post

                        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

                        #85785
                        Forum Admin
                        rokytnji
                          Helpful
                          Up
                          0
                          ::

                          Had to use my admin rights to whitelist that last post. Those commands and readouts triggered the spam filters. Hence why I mentioned I temp save my posts.
                          Now where was I ? Oh yeah. bluetooth speaker in question being used is.

                          https://allsoundlab.net/ultimate-review-skullcandy-soundmine-portable-speaker/

                          To explain my reasoning. Just trying to teach members how to post a problem. Instead of just

                          bluetooth 2.14 starting
                          bluetooth applet needs to be started 1st
                          It was fixed mysteriously.
                          Now I know bluetooth-applet is running because in command line it says a instance is already running.
                          For some reason bluetooth-manager does not see it running.
                          So. Mysterious aint gonna cut it.
                          I have already paired and played my skullcandy bluettoth speaker on my samsung s10e phone.
                          So not a hardware problem.
                          inxi sees it.
                          lsusb lists the driver being used.

                          But. Rfkill list won’t listen to me either today.

                          harry@biker:~
                          $ rfkill list
                          0: dell-wifi: Wireless LAN
                          	Soft blocked: no
                          	Hard blocked: no
                          1: dell-bluetooth: Bluetooth
                          	Soft blocked: yes
                          	Hard blocked: no
                          2: phy0: Wireless LAN
                          	Soft blocked: no
                          	Hard blocked: no
                          8: hci0: Bluetooth
                          	Soft blocked: yes
                          	Hard blocked: no
                          harry@biker:~
                          $ rkill unblock all
                          bash: rkill: command not found
                          harry@biker:~
                          $ rfkill unblock all
                          harry@biker:~
                          $ rfkill list
                          0: dell-wifi: Wireless LAN
                          	Soft blocked: no
                          	Hard blocked: no
                          1: dell-bluetooth: Bluetooth
                          	Soft blocked: yes
                          	Hard blocked: no
                          2: phy0: Wireless LAN
                          	Soft blocked: no
                          	Hard blocked: no
                          8: hci0: Bluetooth
                          	Soft blocked: yes
                          	Hard blocked: no
                          9: hci1: Bluetooth
                          	Soft blocked: yes
                          	Hard blocked: no
                          harry@biker:~
                          

                          So that is all I know about bluetooth troubleshooting in antiX. As you can see from readouts. More than one thing wrong. But at least I supply info.
                          Don’t be shy folks. My speakers work ok so this is just exercise.
                          Happy trails, rok

                          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

                          #85788
                          Moderator
                          caprea
                            Helpful
                            Up
                            1
                            ::

                            The software block could be triggered by connman
                            By default bluetooth is turned off in connman-system-tray Status.

                            #85791
                            Forum Admin
                            rokytnji
                              Helpful
                              Up
                              0
                              ::

                              Thanks caprea.

                              harry@biker:~
                              $ rfkill list
                              0: dell-wifi: Wireless LAN
                              	Soft blocked: no
                              	Hard blocked: no
                              1: dell-bluetooth: Bluetooth
                              	Soft blocked: no
                              	Hard blocked: no
                              2: phy0: Wireless LAN
                              	Soft blocked: no
                              	Hard blocked: no
                              8: hci0: Bluetooth
                              	Soft blocked: no
                              	Hard blocked: no
                              10: hci1: Bluetooth
                              	Soft blocked: no
                              	Hard blocked: no
                              

                              Now back to trouble shooting. I was wondering if I should have hit the tethering on button so I turned it on for now. Easy enough to turn off later on if need be.

                              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

                              #85798
                              Member
                              olsztyn
                                Helpful
                                Up
                                0
                                ::

                                caprea wrote:
                                I faced the same problem this week after autoremoving elogind and some libpolkit stuff.
                                After installing them again bluemanapplet started to work again.This was not a PC of mine, so I didn’t start experiments to look further whats the problem, but was happy it was working as before.

                                Behavior reported in the initial post of this thread appear to be also the case for my *elogind*-free systems. I remember giving up bluetooth, when going to completely *elogind*-free antiX some half a year ago. Being *elogind*-free was more important to me than bluetooth…

                                Sorry for my above confusion…
                                After further investigation it turns out that my similar issue with Bluetooth had nothing to do with being *elogind*-free. It turns out that compatibility of my Bluetooth adapter was causing this. Although seen by Connman, it did not actually work. Replacing Bluetooth adapter fixed the problem in my case.
                                This confirmed in my experiment that the Bluetooth is working perfectly fine in my *elogind*-free antiX 21.
                                Understandably this my report does not contribute anything to solution of issues experienced by others but at least I want to clear up my previous confusing experience…

                                Live antiX Boot Options (Previously posted by Xecure):
                                https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

                              Viewing 14 posts - 1 through 14 (of 14 total)
                              • You must be logged in to reply to this topic.