-
AuthorSearch Results
-
March 21, 2022 at 3:28 pm #79502
In reply to: antix et Bluetooth
Moderator
caprea
Le bluetooth doit être activé dans connman.
connman est par exemple aussi responsable de ta connexion Internet.
control-centre > réseau > wifi connman > statut
activer le bluetoothEnsuite, essaie le blueman-manager
blueman-managerEdit: S’il te plaît, également depuis le terminal, afin que nous sachions quel antiX.
inxi -zv7- This reply was modified 1 year, 1 month ago by caprea.
March 21, 2022 at 2:04 pm #79491In reply to: antix et Bluetooth
Membermadibi
Le modèle d’EEEPC que j’avais avait le bluetooth et n’avait pas le bouton pour l’activer.
Dans tous les cas, je recommande de vérifier la présence, soit sur l’ordinateur, soit dans son manuel d’instructions.
Si vous avez installé la version complète d’antix 21, le bluetooth se trouve sous “paramètres” “gestionnaire bluetooth” (notez que ces mots sont traduits de l’italien, en anglais ce sont “settings” et “bluetooth manager”. Ainsi, tu peux démarrer le programme Bluetooth sans utiliser la ligne de commande.Et si aprés tu rencontres des problèmes pour connecter ton objet (clavier, écouteur, etc, chéz pas quoi car tu l’as pas écrit), fais moi savoir que j’essaierai de t’aider.
Dans le cas que la question soit sulement de l’activer en automatique toutes les fois que tu fais partire antix:
Control Centre -> Session -> Session de bureau utilisateur ->
comment dérniére ligne tu dois écrire:blueman-manager &
et puis enregistrer.
Et voilà: a prochaine fois, le bluetooth démarrera automatiquement.
mMarch 21, 2022 at 11:51 am #79487In reply to: antix et Bluetooth
MemberPPC
Bonjour.
La première partie de la recommandation de madibi fonctionne sur n’importe quel système, même Windows – vérifiez que votre ordinateur n’a pas un bouton qui active/désactive le bluetooth.
Blueman est le programme qui gère les connexions bluetooth. Ce programme (ou un autre ayant les mêmes fonctions) doit être installé sur votre ordinateur pour pouvoir se connecter aux appareils Bluetooth.
Si vous ne savez pas comment installer des applications sous linux/antiX, veuillez lire les entrées du forum qui expliquent comment faire…Ex: Pour installer blueman (et dependencies)
antiX menu > Terminal:
sudo apt update && sudo apt install bluemanPour activer “blueman”, dans le terminal:
blueman-managerP.
Traduit avec http://www.DeepL.com/Translator (version gratuite)
- This reply was modified 1 year, 1 month ago by PPC.
- This reply was modified 1 year, 1 month ago by PPC.
March 21, 2022 at 9:07 am #79477In reply to: antix et Bluetooth
Member
cyrilus31
Bonjour papizac,
Tout d’abord il serait intéressant que vous fournissiez le détail de votre matériel avec le résultat de la commande inxi -F.
Concernant le bluetooth, mon portable n’a pas de bluetooth fonctionnel donc je ne vais pas être d’une grande aide. De ce que j’ai pu lire sur le forum, il faut passer par le gestionnaire blueman.
March 21, 2022 at 8:21 am #79475Topic: antix et Bluetooth
in forum FrenchMemberpapizac
Bonjour
je viens d’installer AntiX sur un vieux PC portable,ça traine un peu ,mais ça fonctionne.Seulement, je débute avec AntiX et je ne vois pas comment accéder au paramètres du Bluetooth. Tout ce que j’ai trouvé c’est une commande pour activer en automatique le Bluetooth.Mais je ne sais pas quand et comment voir si un périphérique est connecter ou pas.
Merci de vos réponses.March 20, 2022 at 7:00 am #79407In reply to: antiX transformation pack – antiX FT 10
Membermadibi
@PPC
results of test of ft10-transformation_1.4.b5_all.deb, after 150′, this morning:
– installation: ok;
– look: great. I like the selection of choices too;
– localization: the Italian one is not so good. My fault, in the latest 2 weeks I didnt look at transiflex.
– usage: responsive, fast. Bluetooth works, sound too. Antix 21 + FT10is installed in my external HD usb, I saw some youtube with no probs through FFox esr. (And meteo is 7° sunny day – before I did never use meteo app on pc 🙂 )mini DISCUSSION ON BLOAT
I hope to not be OT writing the following, that was also discussed in 2 others treads.What is a perfect system: the one that has the number of programs that I like (P = N)
what is a bloated system: the one that has Programs P > N
what is a barebone system: the one that has Programs P < NUnfortunately I searched in the Museum of weights and measures in Paris, and I didn’t find nor the definition of bloat, neither the measure of what I think P should be.
That said,
@oltsztyn wrote:
My take on gnome-maps: It would be great to have this latest in antiX
I’m not sure that to insert Open Source Map application in antix ootb, fits with what @anticapitalista wrote on December 01, 2020 as a guideline for antix: it may be considered a bloat. If the question is whether to insert it in the app centre, my answer is a big yes.
On the other hand, I think that the inclusion of this program is consistent with your idea of what FT10 should be (see your post 79197). So I agree that it should be immediately included in the transformation pack FT10.Little note aside
The ram usage indicator in the bottom tray gives results different from the ones of conky.Par contre coincides with the one given by lxtask.
When I did searches for a distro, I saw that the indication of ram usage differs according to the tool used. So I decided to stick to lxtask, in order to avoid to “compare pears with potatoes”.m
- This reply was modified 1 year, 1 month ago by madibi.
- This reply was modified 1 year, 1 month ago by madibi.
- This reply was modified 1 year, 1 month ago by madibi.
Moderator
Brian Masinick
Greetings Damon! I am a long time antiX user and I also happen to have a Dell Inspiron 5558 laptop, which I am using right now.
Here’s a report on it:
inxi -Fxz System: Kernel: 5.11.0-21.2-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM 2.9.6 Distro: antiX-21-runit_x64-base Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) 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: 30.1 Wh (100.0%) condition: 30.1/41.4 Wh (72.6%) volts: 16.5 min: 14.8 model: Samsung SDI DELL 07G07587587 status: Full CPU: Info: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell rev: 4 cache: L2: 4 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 2878 MHz min/max: 500/2401 MHz boost: enabled Core speeds (MHz): 1: 2878 2: 2400 3: 2462 4: 2944 Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus-ID: 08:00.0 Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 2-5:3 Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.3.5 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 Device-3: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel v: kernel bus-ID: 08:00.1 Sound Server-1: ALSA v: k5.11.0-21.2-liquorix-amd64 running: yes 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: kernel port: e000 bus-ID: 07:00.0 IF: eth0 state: down mac: <filter> Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 2-6:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: warning rfk-block: hardware: no software: yes address: <filter> Drives: Local Storage: total: 447.13 GiB used: 18.82 GiB (4.2%) ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB Partition: ID-1: / size: 78.19 GiB used: 18.82 GiB (24.1%) fs: ext4 dev: /dev/sda6 ID-2: /boot/efi size: 98.4 MiB used: 1.7 MiB (1.7%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 55.0 C mobo: 25.0 C sodimm: SODIMM C Fan Speeds (RPM): cpu: 2200 Info: Processes: 175 Uptime: 2m Memory: 7.69 GiB used: 1.24 GiB (16.1%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1301 Shell: Bash v: 5.1.4 inxi: 3.3.06- This reply was modified 1 year, 1 month ago by Brian Masinick.
--
Brian MasinickMarch 7, 2022 at 5:53 pm #78701Member
Egzoset
Curious if you tried Sparky Linux yet. Since you Like LXDE.
Actually i still don’t know if i like LXDE just yet as i’ve seen it in LIVE mode only…
Apparently i’ve downloaded SparkyLinux v6.0 because of it’s duality supporting both the i686 and x86_64 material, hoping to find ‘bootia32.efi’ in case a crude patch might prove necessary, besides also copying some /i386-efi/ resources as i vaguely reecall. Somewhere it mentioned LxQt, no big deal. FossaPup95 might have worked wonders if it could have completed its “frugal” installation, which inspired my a desire to install Ventoy on the eMMC and simply swap .ISOs around instead of enduring the whole patience-challenging process. My notes say i had to pass 4 menu levels before accessing the display settings with SparkyLinux, by the way…
Right now i wish i could better explain issues that made me move further with even more testing but this i ain’t getting any younger myself. These things can become exhausting when failures pile up and there’s no reward joys to compensate… Zorin felt promissing at 1st, still didn’t stick neither. Etc., etc.
Does some unexpected “HCi0” timeout error matter? Also, more input: how about including GrUB-Customizer as pre-installed!
Mint and Fedora too slow, Bodhi’s ‘ubi-console-setup’ utility crashed. Ubuntu Mate v20.04.3 (LTS Focal) installed fine, well enough to auto-selectect the proper screen anyway, but i removed it a couple days ago once tired of blank/black displays then BlueTooth problems. Another Lubuntu tweak is AntiVirusLiveCD v39.0 of February 20, still on the to-list so far.
Not to mention the “Extra Luxury Edition” in LXDE wasn’t exactly feeling like an invitation – i’m reading notes at random and there’s 4 ~ 5 times more to remind myself and it’s now diner time…
Salix, ZenWalk, Absolute… LibreElec, Debian Live! … Slakware v15.0 itself, etc.
Appologies again, thanks for sharing feedback while expressing enthousiasm and moral support. The guy’s energy (mine…) may just prove somewhat depleeted after having the initial climax from hope. Long ago Windows was the same and DOS before it, in any case each day needs a fair dose of victory to save our sanity.
Good day, have fun!!
March 4, 2022 at 8:25 am #78510In reply to: Pulse audio problems
MemberPap
-on my netbook – pulseaudio looks like magic- if it’s on, no sound at all, kill it and sound playing, just like magic
-on my home computer- against what I was expecting, it ran perfectly in my first try- I started it (pulseaudio -D &), started Heroic, loaded a game- and there- sound and video, as flawless has if it was running the game on a Windows machine! But, after I rebooted, no audio at allI believe the problem is not caused by your game or Wine. The reason I think those are not related is because I had very similar problems on my netbook and on my home computer. And I didn’t try to install Wine or anything gaming-related – I just tried to set up bluetooth audio. At first, everything worked, even bluetooth. After rebooting, no sound, not even by speakers, unless I get rid of pulseaudio. Just be happy pavucontrol actually sees your sound device, because in my case, not even that.
Anyway, from past experience I know pulseaudio doesn’t really support alsa well, because I also had similar problems with volume and sound card. This is what worked for me (in Slackware, but the problem is so similar I guess it will work for you as well): Run alsamixer first, and make sure the sound card is set correctly, then set volume(s) to your liking. After that, make sure
alsactl restore
runs every time you boot the machine. Hopefully this should solve the problem and you will be able to change volume by pavucontrol as well, although volumeicon is what I do (and the changes are remembered next time you reboot).Official, dedicated, determined, fanatic systemd HATER since... its release.
March 3, 2022 at 8:09 am #78390In reply to: Cannot connect Android phone to AntiX…
MemberModdIt
ctcx wrote
Maybe I just forgot to try the script you mention,Please do test before claiming scripts are not working, the Android Device USB connect script works on both antiX21 runit
and sys V full edititions with a lot of different devices and manufacturers involved. All of those I was able to test!.
No users calling for help either.One script was inefective with some devices from Huawei and Honor also Xiaomi, and some but not all the samsung
devices (tested or in use), which popup a connect window intended for windoze, and wants to run an exe.The issues with the phones I have in daily use as well as user devices started to occur after system security updates, before that I used a very simple script
and mounted to a phone directory in homescript. Now/usr/local/bin/android-device-usb-connect.shantiX gui for mounting/unmount android devices,
by PPC and sybok, 21/5/2020.Allow connection on the phone, Close those windoze connect popup windows then run the script which will give access to internal storage.
With regard to tethering and bluetooth sharing I have only limited experience, not just with linux. Some of tested devices connect to keyboard mouse
and other devices easily, a couple including one tablet and some phones to nothing, that includes windoze 7 to 10.The problems are that the protocoll for sharing is implimented by manufacturers of phones tablets etc, bugs may be worked around with windoze drivers
but never for linux. There is also a plethora of constant change to contend with.Users are intended to think they are in control of their data (they are not) so connection to other devices has been made more complicated to near or
impossible for users while allowing a complete phone dump within minutes at an airport or by cops. If you use a cloud backup, see recent whats app or
apple exposure, your data is more or less open source.March 2, 2022 at 11:04 am #78316In reply to: antiX transformation pack – antiX FT 10
Membermadibi
it’s the 2nd day that I’m trying the new beta, and It works with no probs.
The unique little obstacle is when I do the commend “sudo apt install FT10xxx”: I always forget to change the file as executable. Is it possible to provide the file also with this characteristic? I am not an expert, and I thinh that people less expert than me will follow in this trick.
(I remember a couple of weeks ago a guy asking help for the installation of a chess program that he couldnt do, only because of this flag).As far as adv on ft10, I wrote a review on distrowatch where I described what ft10 does
🙂m
PS: I also installed a bluetooth keybord that worked fine since the very 1st try
- This reply was modified 1 year, 2 months ago by madibi.
- This reply was modified 1 year, 2 months ago by madibi.
March 2, 2022 at 10:51 am #78312In reply to: Error while performing sudo apt upgrade [Solved]
Forum Admin
anticapitalista
sudo apt purge connman-bluetooth-firmware-antixthen try again
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 2, 2022 at 10:29 am #78302Topic: Error while performing sudo apt upgrade [Solved]
in forum SoftwareMemberPPC
Today, on my antiX 19.X, 64 bits (installed on my hard drive), I noticed I had about 100 packages that had updates, so I updated my system.
I got this error:
E: Sub-process /usr/bin/dpkg returned an error code (1)When I tried to re-run “sudo apt upgrade”, I got this:
dpkg: erro ao processar o arquivo /var/cache/apt/archives/firmware-realtek_20210818-1~mx19+1_all.deb (--unpack): a tentar sobre-escrever '/lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin', que também está no pacote connman-bluetooth-firmware-antix 0.1.0 dpkg-deb: erro: o subprocesso colar foi morto pelo sinal (Broken pipe) Foram encontrados erros enquanto processava: /var/cache/apt/archives/firmware-realtek_20210818-1~mx19+1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)EDIT (translation of the error message):
This error states that firmware-realtek_20210818-1~mx19+1_all.deb is trying to over write the file /lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin that’s also in the package connman-bluetooth-firmware-antix 0.1.0- This topic was modified 1 year, 2 months ago by PPC.
- This topic was modified 1 year, 2 months ago by PPC.
March 1, 2022 at 9:51 pm #78266In reply to: Broken packages related to bluetooth
MemberPap
I have no idea why bluetooth.conf wasn’t there. I certainly didn’t touch it, ever. The fact is /etc/dbus-1/system.d contained 7 files, but not bluetooth.conf. I added the one you attached and bluetoothd is indeed running after rebooting. However that only returned the system to the previous state, with totally broken bluetooth. blueman-manager won’t start complaining “blueman-applet needs to be running”, and of course blueman-applet won’t start, with a very informative message “Not loading DhcpClient because its conflict has higher priority”. Well thank you blueman-applet, but that doesn’t tell me anything… “its conflict”? Which one is its goddamn “conflict”?
Anyway, I don’t know if it helps, but after that it spawns this:
blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
I mention it only because it says it failed to activate org.blueman.Mechanism, which happens to be another conf file in /etc/dbus-1/system.d, the same directory bluetooth.conf mysteriously disappeared. I am going to assume pulseaudio messed up that directory. One thing is sure, I did nothing affecting the conf files there.As a last resort, before I actually decide I had more than enough, I guess it is worth trying to somehow replace everything in /etc/dbus-1/system.d with the correct ones.
EDITI used antiX live usb to get those files and replaced the ones in /etc/dbus-1/system.d. Unfortunately, this changed nothing. Well, I guess it’s fair to say I had enough. To hell with pulseaudio, it acted pretty much like a virus infecting my system, and getting rid of this piece of crapware left a broken system, at least as far bluetooth is concerned. The only thing left to get bluetooth working again (except audio) is to re-install antiX, when I get time for that. Installing antiX itself doesn’t take much time but installing my own libraries and software does. And the last thing I needed right now is to do that again.
@caprea: You tried to help, and for that, I thank you again.Official, dedicated, determined, fanatic systemd HATER since... its release.
March 1, 2022 at 8:51 pm #78262In reply to: Broken packages related to bluetooth
Moderator
caprea
On antiX21 here the /etc/dbus-1/system.d/bluetooth.conf looks like this. You might compare it to yours.
It’s not possible for me to post this in a normal way because of the hypercautious spamfilter.Attachments:
-
AuthorSearch Results
Search Results for 'bluetooth'
-
Search Results
-
Topic: antix et Bluetooth
Bonjour
je viens d’installer AntiX sur un vieux PC portable,ça traine un peu ,mais ça fonctionne.Seulement, je débute avec AntiX et je ne vois pas comment accéder au paramètres du Bluetooth. Tout ce que j’ai trouvé c’est une commande pour activer en automatique le Bluetooth.Mais je ne sais pas quand et comment voir si un périphérique est connecter ou pas.
Merci de vos réponses.Today, on my antiX 19.X, 64 bits (installed on my hard drive), I noticed I had about 100 packages that had updates, so I updated my system.
I got this error:
E: Sub-process /usr/bin/dpkg returned an error code (1)When I tried to re-run “sudo apt upgrade”, I got this:
dpkg: erro ao processar o arquivo /var/cache/apt/archives/firmware-realtek_20210818-1~mx19+1_all.deb (--unpack): a tentar sobre-escrever '/lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin', que também está no pacote connman-bluetooth-firmware-antix 0.1.0 dpkg-deb: erro: o subprocesso colar foi morto pelo sinal (Broken pipe) Foram encontrados erros enquanto processava: /var/cache/apt/archives/firmware-realtek_20210818-1~mx19+1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)EDIT (translation of the error message):
This error states that firmware-realtek_20210818-1~mx19+1_all.deb is trying to over write the file /lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin that’s also in the package connman-bluetooth-firmware-antix 0.1.0- This topic was modified 1 year, 2 months ago by PPC.
- This topic was modified 1 year, 2 months ago by PPC.