- This topic has 27 replies, 7 voices, and was last updated Jan 11-5:40 pm by Xecure.
-
Posts
-
anticapitalista
For those using the bullseye alpha (or testing/sid users).
I made versions of blueman and modem-manager-gui removing the hard dependency on policykit-1.
I don’t use blueman nor modem-manager-gui.
Could someone who does use these apps check that the policykit-1 free versions work as expected.
You will probably need to remove policykit-1 after installation.
Thanks.Get debs here: https://download.tuxfamily.org/antix/Testing/
- This topic was modified 2 years, 3 months ago by anticapitalista. Reason: remove policykit-1
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
I have tested the new blueman version and works perfectly (live-USB with persistence). I tried to pair for the first time a Bluetooth ps3 controller, and it worked very well.
Had to first enable Bluetooth using cmst and then added blueman-applet to the startup file. The first time it launches, it will ask to enable the bluetooth service at startup, (first time I said no, and it didn’t ask again, so I had to enable the service manually). Tried it on two computers (different bluetooth cards) and it works. I don’t have any keyboard or mouse that uses bluetooth technology, but will try to transfer files t/from my mobile phone in a bit.Once I figure out how to package bluez-alsa, I will also test with a bluetooth headphone, but the interface worked for me well to conned/disconnect, pair and unpair, remove and add Devices, etc, so I don’t expect any trouble there.
Cannot give any feedback for modem-manager-gui (sorry).
antiX Live system enthusiast.
General Live Boot Parameters for antiX.anticapitalista
Thanks Xecure. I should have added to (I’ll add it to the O/P) make sure policykit-1 is removed before testing.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
make sure policykit-1 is removed before testing.
Ups. Will try again. I will also reinstall once I remove policykit-1.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
Tested again, first purging blueman and policykit-1, reboot, reinstall blueman, and got to set up the wireless controller again. This worked. Could scan and find my mobile phone, trust, pair and connect, but couldn’t send or receive files. This may be me not knowing how to do it properly, so don’t trust this result.
I will ask tomorrow to borrow a bluetooth keyboard (and maybe even a mouse) and see if I can pair and use them.Pairing bluetooth headset with bluez-alsa will have to wait. I will try to see tomorrow if with pulseaudio I can stream audio through bluetooth (paring with blueman and such) and report my findings.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.BobC
I will try it tomorrow with my android phone and a bluetooth headset I have.
Xecure
I was lucky and got to borrow for today a bluetooth keyboard.
I am writing with it from antiX bullseye alpha write now, while also listening to music on my bluetooth headset (though I needed puseaudio, but this is not related to this blueman software.
Pairing and connecting worked perfectly at first go for both, so at least on these cases, your blueman package works perfectly.
You can see that policykit-1 is not installed:$ apt policy policykit-1 policykit-1: Installed: (none) Candidate: 0.105-29+antix1 Version table: 0.105-29+antix1 500 500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/testing testing/nosystemd amd64 Packages 0.105-29 500 500 http://ftp.de.debian.org/debian bullseye/main amd64 Packagesand that I have the correct blueman version:
$ 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 2.1.4-1+b1 500 500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages 2.0.8-1.antix1 500 500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/testing testing/main amd64 PackagesThanks for everything you do anticapitalista.
PD: Wasn’t able to get pairing with the android mobile phone, but that may be related to incompetence (I had never done it before). If someone who knows how to and has done it before on antiX 19, please see if that works on the alpha with the blueman package built by anticapitalista.
- This reply was modified 2 years, 3 months ago by Xecure. Reason: adding blueman policy
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Brian Masinick
apt policy policykit-1 policykit-1: Installed: 0.105-29+antix1 Candidate: 0.105-29+antix1 Version table: *** 0.105-29+antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/nosystemd amd64 Packages 100 /var/lib/dpkg/status 0.105-29 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packagesapt policy blueman blueman: Installed: 2.1.4-1+b1 Candidate: 2.1.4-1+b1 Version table: *** 2.1.4-1+b1 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status 2.0.8-1.antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 PackagesI am able to see my “Soundcore Life Q10” Bluetooth headset, which I have used many times on the same computer, (definitely with MX Linux, possibly with other distros too. I’ve also used this device (and others) successfully with my Google Pixel 3 Android Phone and my Acer Chromebook 715.
I cannot connect to this device:
“Connection Failed, Protocol not available”--
Brian MasinickBrian Masinick
inxi -Fzx System: Host: antix-alpha Kernel: 4.9.240-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: IceWM 2.0.1 Distro: antiX-bullseye-a1_x64-full Grup Yorum 3 January 2021 base: Debian GNU/Linux bullseye/sid Machine: Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <filter> Mobo: Dell model: 086DKN v: A00 serial: <filter> UEFI: Dell v: A04 date: 08/06/2015 Battery: ID-1: BAT0 charge: 33.9 Wh condition: 33.9/41.4 Wh (82%) model: Samsung SDI DELL 07G07587587 status: Full CPU: Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell rev: 4 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 2547 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 2547 2: 2436 3: 2611 4: 2456 Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: N/A bus ID: 00:02.0 Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus ID: 08:00.0 Display: x11 server: X.Org 1.20.10 driver: none unloaded: fbdev resolution: 1366x768~N/A OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 direct render: Yes Audio: Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.9.240-antix.1-amd64-smp Network: Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus ID: 06:00.0 IF: wlan0 state: up mac: <filter> Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 07:00.0 IF: eth0 state: down mac: <filter> Drives: Local Storage: total: 931.51 GiB used: 44.14 GiB (4.7%) ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB Partition: ID-1: / size: 97.93 GiB used: 34.93 GiB (35.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 7.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 65.0 C mobo: N/A sodimm: 2.0 C Fan Speeds (RPM): cpu: 2200 Info: Processes: 196 Uptime: 1h 05m Memory: 7.77 GiB used: 1.44 GiB (18.5%) Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Shell: bash v: 5.1.0 inxi: 3.0.36--
Brian MasinickBrian Masinick
I am able to listen to audio and video on this release, just not via Bluetooth. That’s the only capability I have tried that definitely is not working on my system.
I will try the same on antiX 19.3 to compare.--
Brian Masinick
rokytnji
Just wondering if dmesg readout Brian would help ya or not. 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 problemsBrian Masinick
It may help.
Quick check in antiX 19.3 shows the same problem though.
I’ll check out more tomorrow.
--
Brian MasinickI got it working on up to date bullseye and was able to pair and send a file to my phone. then i removed the policykit-1, but that also removed blueman and modem-manager-giu. i then tried to reinstall those two, but it said package blueman has no installation candidate, and unable to locate package modem-manager-gui
I’m remastering and will reboot and try again
After rebooting and updating, i went to install blueman and modem-manager-gui, but it says its going to install policykit-1 as an additional package, so I didn’t say yes.
Let me know what to do next…
From my bullseye test system:
Fetched 23.4 MB in 7s (3,573 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. demo@antix1:~ $ sudo apt install blueman modem-manager-gui Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: policykit-1 Suggested packages: evolution-data-server libindicate5 | libmessaging-menu0 Recommended packages: pulseaudio-module-bluetooth modem-manager-gui-help yelp policykit-1-gnome | polkit-1-auth-agent The following NEW packages will be installed: blueman modem-manager-gui policykit-1 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 1,213 kB of archives. After this operation, 5,250 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. demo@antix1:~ $ apt policy blueman modem-manager-gui policykit-1 blueman: Installed: (none) Candidate: 2.1.4-1+b1 Version table: 2.1.4-1+b1 500 500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status 2.0.8-1.antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 Packages modem-manager-gui: Installed: (none) Candidate: 0.0.20-2 Version table: 0.0.20-2 500 500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages policykit-1: Installed: (none) Candidate: 0.105-29+antix1 Version table: 0.105-29+antix1 500 500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/nosystemd amd64 Packages 100 /var/lib/dpkg/status 0.105-29 500 500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages demo@antix1:~- This reply was modified 2 years, 3 months ago by BobC.
- This reply was modified 2 years, 3 months ago by BobC.
Xecure
Let me clear the confusion here.
To test, you first need to purge policykit-1 (as BobC did)
sudo apt purge policykit-1
and then manually download and install the .deb file for blueman packaged by anticapitalista, found in the link he provided in the first post: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.debAnd then you test the software as best you can.
You can see by my apt policy output that the blueman package didn’t come from the repo, but was manually installed
$ 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/statusantiX Live system enthusiast.
General Live Boot Parameters for antiX.
- You must be logged in to reply to this topic.
