- This topic has 14 replies, 4 voices, and was last updated Feb 10-9:19 pm by rokytnji.
- AuthorPosts
- November 17, 2022 at 9:28 pm #93426Forum Admin
rokytnji
Bought me a Dell Chromebook with Kali Linux that I played with for awhile.
Decided enough was enough and made up a 64 bit antiX full iso usb.
Hit the escape key when turning this on to pick usb bootup.
Good news. Booted up just fine. Installed just fine. Most hardware worked out of the box
Bad news. No sound. No 2 finger tap. Takes 3 fingers for the 2 finger action.
Tap was easy to fix.
https://www.antixforum.com/forums/topic/acer-c710-chromebook/
Glad I posted earlier.Sound fix required pulse audio install for my fumbling about in alsa on my lonesome
Took me 2 days to find this page
http://blog.nanax.fr/post/2018-05-01-chromebook-linux/Now youtube and xmms play noise. Before
speaker-test
button in hardware crashed in antiXcc . Running it terminal would throw errors but no sound.
Now it works in terminalharry@antix1:~ $ inxi -Fxz System: Kernel: 5.10.153-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 3.2.0 Distro: antiX-22_x64-full Grup Yorum 18 October 2022 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: GOOGLE product: Candy v: 1.0 serial: <superuser required> Mobo: GOOGLE model: Candy v: 1.0 serial: <superuser required> UEFI: coreboot v: MrChromebox-4.18.1 date: 10/27/2022 Battery: ID-1: BAT0 charge: 42.2 Wh (100.0%) condition: 42.2/44.5 Wh (94.9%) volts: 12.9 min: 11.4 model: Samsung DELL XK status: full CPU: Info: dual core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont rev: 8 cache: L1: 112 KiB L2: 1024 KiB Speed (MHz): avg: 2292 high: 2459 min/max: 500/2582 cores: 1: 2459 2: 2125 bogomips: 8666 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-3:4 Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: i965 gpu: i915 resolution: 1366x768~60Hz API: OpenGL v: 4.2 Mesa 20.3.5 renderer: Mesa DRI Intel HD Graphics (BYT) direct render: Yes Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Sound API: ALSA v: k5.10.153-antix.1-amd64-smp running: yes Sound Server-1: PulseAudio v: 14.2 running: no Network: Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 01:00.0 IF: wlan0 state: up mac: <filter> Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:6 Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: running rfk-block: hardware: no software: yes address: <filter> Drives: Local Storage: total: 44.65 GiB used: 20.7 GiB (46.4%) ID-1: /dev/mmcblk1 vendor: Hynix model: HAG2e size: 14.68 GiB ID-2: /dev/sda type: USB vendor: PNY model: USB 2.0 FD size: 29.97 GiB Partition: ID-1: / size: 13.36 GiB used: 7.09 GiB (53.1%) fs: ext4 dev: /dev/mmcblk1p2 ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat dev: /dev/mmcblk1p1 Swap: ID-1: swap-1 type: partition size: 768 MiB used: 0 KiB (0.0%) dev: /dev/mmcblk1p3 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 140 Uptime: 22m Memory: 3.75 GiB used: 1.17 GiB (31.3%) Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1625 Shell: Bash v: 5.1.4 inxi: 3.3.23
harry@antix1:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtmax98090 [chtmax98090], device 0: 3 [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: chtmax98090 [chtmax98090], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0
Using that nanax.fr thread. I errored out a bit following the restart commands. Reboot seemed to fix it though cuz I had sound after that.
Hopefully some one > like me > can use this thread. 😀 Tickled pink I got this working. I did not want to go back to Kali where sound and tap worked.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsNovember 17, 2022 at 9:39 pm #93432Forum Adminrokytnji
::Had to install gitless to make my sound edit work
harry@antix1:~ $ apt-cache policy git git: Installed: 1:2.30.2-1 Candidate: 1:2.30.2-1 Version table: 1:2.34.1-1~bpo11+1 100 100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages *** 1:2.30.2-1 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status harry@antix1:~ $ apt-cache policy gitless gitless: Installed: 0.8.8-4 Candidate: 0.8.8-4 Version table: *** 0.8.8-4 500 500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages 500 http://ftp.us.debian.org/debian bullseye/main i386 Packages 100 /var/lib/dpkg/status harry@antix1:~
Details. Forgot. Edit: when needing a like a F1 key at slim login.
On the l/h side of keyboard is a magnify glass looking icon. That is your search key.
Press it and hold it while going through the top row keys with symbols on this chromebook.- This reply was modified 1 year ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsNovember 19, 2022 at 4:51 pm #93545Moderatorchristophe
::Thanks for this roky!
I’ve got that same model chromebook. I successfully re-did the bios & installed antiX, but the sound won’t work, and the the touch pad is a bit wonky, too.
My workarounds are to use usb devices to fix it.
Problem is (as you know) – there are only 2 usb ports!
So now it looks like I can finally fix these issues the right way!
Much obliged!- This reply was modified 1 year ago by christophe.
confirmed antiX frugaler, since 2019
November 20, 2022 at 12:11 am #93563Forum Adminrokytnji
::Yeah. Missed the fast bootup when my Acer C710 broke. These chromebooks are as cheap as raspberry pi bpards.
That sound chip I posted is a PITA for a lot of Linux users. Now just waiting for some parts to come in for my NUC intel box.
It should become my fastest desktop yet. Also the price of a raspberry pi board.Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsNovember 29, 2022 at 12:04 am #94367Forum Adminrokytnji
::Got tired of shutting down this chromebook when hitting the back space button while not looking.
Power button sits like a key on key board. Easy to hit by accident.
My dirty fix for now
harry@antix1:~ $ cd /etc/acpi/ harry@antix1:/etc/acpi $ ls always-mute.sh lid.sh sleep_suspend.sh asus-keyboard-backlight.sh mutebtn.sh sonybright.sh asus-wireless.sh powerbtn-acpi-support.sh tosh-wireless.sh ejectbtn.sh powerbtn-acpi-support.sh.bk undock.sh events power.sh voldownbtn.sh ibm-wireless.sh sleep_suspendbtn.sh volupbtn.sh harry@antix1:/etc/acpi
Made a backup of powerbtn-acpi-support.sh.bk to keep my original.
Then opened geany with sudo an deleted everything original butharry@antix1:/etc/acpi $ cat powerbtn-acpi-support.sh #!/bin/sh # This script initiates a shutdown when the power putton has been # pressed. Loosely based on the sample that ships with the acpid package. # If the acpid sample is present as a real config file (as it was in earlier # versions of acpid), we skip this script. (Purging and reinstalling acpid # resolves this situation, or simply deleting /etc/acpi/events/powerbtn.) harry@antix1:/etc/acpi
Logged out and back in. Hit power button. Now nothing happens.Chromebook still turns on with power button.
Logout button on menu or command line shutdown work as power button shutdown now. Have not tested Ctrl_alt backspace yet to see if logout works still.Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsNovember 29, 2022 at 12:45 am #94368Moderatorchristophe
::I have to laugh because that power button caught me a couple times, too!
confirmed antiX frugaler, since 2019
February 1, 2023 at 1:00 pm #98665Forum Adminrokytnji
::Still trouble shooting internal bluetooth. Tried a debian bullseye liqourix 6.1-8.1 kernel. Booted OK but lost my sound fix.
linux-image-6.1-8.1-liquorix-amd64 6.1-17.1~bullseye amd64 Linux 6.1 for 64-bit PCs
The 2 working kernels on here where everything like sound fix are working
$ dpkg --list | grep linux-image ii linux-image-5.10.142-antix.2-amd64-smp 5.10.142-antix.2-amd64-smp-1 amd64 Linux kernel, version 5.10.142-antix.2-amd64-smp ii linux-image-5.10.153-antix.1-amd64-smp 5.10.153-antix.1-amd64-smp-1 amd64 Linux kernel, version 5.10.153-antix.1-amd64-smp
Still living without bluetooth.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsFebruary 1, 2023 at 1:06 pm #98666Forum Adminrokytnji
::Meh. I’ll throw this in here also
harry@antix1:~ $ sudo /etc/init.d/bluetooth status - [sudo] password for harry: bluetooth is running. harry@antix1:~ $ inxi -E Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: running rfk-block: hardware: no software: yes address: 90:2E:1C:F7:5C:14 root@antix1:/home/harry# dmesg | grep -iC 3 "bluetooth" [ 6.141502] max98090 i2c-193C9890:00: MAX98090 REVID=0x43 [ 6.143195] max98090 i2c-193C9890:00: use default 2.8v micbias [ 6.147589] input: chtmax98090 Headset Jack as /devices/pci0000:00/80860F28:00/cht-bsw-max98090/sound/card1/input9 [ 6.182504] Bluetooth: Core ver 2.22 [ 6.182509] Bluetooth: Starting self testing [ 6.194237] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 6.212310] Bluetooth: ECDH test passed in 29096 usecs [ 6.212978] iwlwifi 0000:01:00.0: base HW address: 90:2e:1c:f7:5c:10 [ 6.233197] Bluetooth: SMP test passed in 3191 usecs [ 6.233217] Bluetooth: Finished self testing [ 6.233263] NET: Registered protocol family 31 [ 6.233264] Bluetooth: HCI device and connection manager initialized [ 6.233272] Bluetooth: HCI socket layer initialized [ 6.233276] Bluetooth: L2CAP socket layer initialized [ 6.233284] Bluetooth: SCO socket layer initialized [ 6.305489] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (064e:c236) [ 6.326190] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input10 [ 6.326389] usbcore: registered new interface driver uvcvideo [ 6.326392] USB Video Class driver (1.1.1) [ 6.342254] usbcore: registered new interface driver btusb [ 6.359713] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [ 6.362341] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [ 6.416017] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 6.551132] Bluetooth: hci0: unexpected event for opcode 0xfc2f [ 6.570285] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [ 7.417160] Adding 786428k swap on /dev/mmcblk1p3. Priority:-2 extents:1 across:786428k SSDscFS [ 7.437984] EXT4-fs (mmcblk1p2): re-mounted. Opts: discard [ 7.750139] device-mapper: uevent: version 1.0.3 -- [ 8.452482] FS-Cache: Loaded [ 8.500676] FS-Cache: Netfs 'nfs' registered for caching [ 8.540150] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 9.441135] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 9.441140] Bluetooth: BNEP filters: protocol multicast [ 9.441147] Bluetooth: BNEP socket layer initialized [ 9.459939] NET: Registered protocol family 38 [ 9.881949] ACPI: \: failed to evaluate _DSM (0x1001) [ 9.881955] ACPI: \: failed to evaluate _DSM (0x1001) # bluetoothctl show Controller 90:2E:1C:F7:5C:14 (public) Name: BlueZ 5.55 Alias: BlueZ 5.55 Class: 0x0002010c Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: no UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: NAP (00001116-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0537 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: appearance SupportedIncludes: local-name # rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked harry@antix1:~ $ apt-show-versions bluetooth blueman bluez blueman:amd64/bullseye 2.1.4-1.0antix2 uptodate blueman:i386 not installed bluetooth:all/bullseye 5.55-3.1.0antix3 uptodate bluez:amd64/bullseye 5.55-3.1.0antix3 uptodate bluez:i386 not installed harry@antix1:~ $ blueman-applet --loglevel debug blueman-applet version 2.1.4 starting blueman-applet 17.05.12 INFO PluginManager:86 load_plugin: ['KillSwitch', 'DBusService', 'StatusIcon', 'Networking', 'NMPANSupport', 'GameControllerWakelock', 'Menu', 'AppIndicator', 'AuthAgent', 'TransferService', 'DiscvManager', 'RecentConns', 'SerialManager', 'StandardItems', 'DhcpClient', 'NMDUNSupport', 'PowerManager', 'ExitItem', 'NetUsage', 'ShowConnected', 'PPPSupport'] blueman-applet 17.05.12 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.Menu.Menu'> blueman-applet 17.05.13 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.StatusIcon.StatusIcon'> blueman-applet 17.05.13 DEBUG Base:74 do_g_properties_changed: /org/bluez/hci0 {'Address': '90:2E:1C:F7:5C:14', 'AddressType': 'public', 'Name': 'BlueZ 5.55', 'Alias': 'BlueZ 5.55', 'Class': 268, 'Powered': True, 'Discoverable': False, 'DiscoverableTimeout': 180, 'Pairable': False, 'PairableTimeout': 0, 'Discovering': False, 'UUIDs': ['00001801-0000-1000-8000-00805f9b34fb', '00001800-0000-1000-8000-00805f9b34fb', '00001200-0000-1000-8000-00805f9b34fb', '0000110c-0000-1000-8000-00805f9b34fb', '0000110e-0000-1000-8000-00805f9b34fb', '0000180a-0000-1000-8000-00805f9b34fb'], 'Modalias': 'usb:v1D6Bp0246d0537', 'Roles': ['central', 'peripheral']} blueman-applet 17.05.13 INFO Functions:115 launch : Gtk eventtime is 0, not using LaunchContext blueman-applet 17.05.13 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.PowerManager.PowerManager'> blueman-applet 17.05.13 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.KillSwitch.KillSwitch'> blueman-applet 17.05.13 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.DBusService.DBusService'> blueman-applet 17.05.13 INFO PluginManager:157 __load_plugin: loading <class 'blueman.plugins.applet.Networking.Networking'> blueman-applet 17.05.13 INFO Networking:31 load_nap_settings: Loading NAP settings blueman-tray version 2.1.4 starting blueman-applet 17.05.27 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 17.05.27 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 blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <blueman.plugins.applet.Networking.Networking object at 0x7f9700109ee0> blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <blueman.plugins.applet.DBusService.DBusService object at 0x7f9700109ca0> blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <blueman.plugins.applet.KillSwitch.KillSwitch object at 0x7f9700109a00> blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <blueman.plugins.applet.PowerManager.PowerManager object at 0x7f9700109af0> blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <StatusIcon.StatusIcon object at 0x7f970010f540 (blueman+plugins+applet+StatusIcon+StatusIcon at 0x2b39720)> blueman-applet 17.05.27 DEBUG BasePlugin:43 _on_plugin_delete: Deleting plugin instance <blueman.plugins.applet.Menu.Menu object at 0x7f97013c2ee0> harry@antix1:~ $ 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-io-error-quark: Error calling StartServiceByName for org.blueman.Applet: Timeout was reached (24) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/blueman-tray", line 40, in <module> BluemanTray() File "/usr/lib/python3/dist-packages/blueman/main/Tray.py", line 16, in __init__ applet = AppletService() 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 49, in __init__ super().__init__(name='org.blueman.Applet', interface_name='org.blueman.Applet', 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.Applet: Timeout was reached
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsFebruary 1, 2023 at 5:24 pm #98680ModeratorBrian Masinick
::I checked antiX and it sees my Bluetooth device, but when I try to connect, I get a failed to connect message.
Booted PCLinuxOS, and when I first tried it I didn’t have anything, so I checked to see if I had blueman installed, and I did not, so I installed it and PCLinuxOS then immediately connected.
I’ll try siduction, another Debian-based distro and see if it has resolved the issues or if it also struggles with Bluetooth.--
Brian MasinickFebruary 1, 2023 at 6:31 pm #98683ModeratorBrian Masinick
::I also got EndeavourOS to run Bluetooth. With antiX I can get sound working with apulse and I can then plug in my headphones and they work, but no success with Bluetooth. So far, PCLinuxOS and EndeavourOS DO work with Bluetooth and headphones.
--
Brian MasinickFebruary 1, 2023 at 7:48 pm #98686ModeratorBrian Masinick
::Right now on siduction I have a different issue. When I attempt to use any wev based site that has audio or video the specific site just spins.
I’ve tried at least four different web browsers and multiple media sites. To ensure that it wasn’t something else I used several other sites and they work fine.
This issue will probably disappear within a few days just as mysteriously as it appeared. If not I’ll investigate further at that time.
--
Brian MasinickFebruary 1, 2023 at 8:05 pm #98690ModeratorBrian Masinick
::Add openSUSE Tumbleweed to the list of distributions that have no issues with media or Bluetooth.
--
Brian MasinickFebruary 2, 2023 at 2:28 am #98696Memberolsztyn
::With antiX I can get sound working with apulse and I can then plug in my headphones and they work, but no success with Bluetooth.
I believe you need pulseaudio in antiX for bluetooth to work with audio devices. Pavucontrol (mixer) will route audio.
There might be a (complicated) way to make Alsa to work with some routing but I have not seen any.Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersFebruary 2, 2023 at 3:10 am #98698ModeratorBrian Masinick
::Given that I have plenty of distributions to use, instead of beating them up until they’re all perfect, instead I use each of them at what they do best. Also now that I’m retired most of the distributions are just fine. At the very least they all are fine for reading webmail and forums, which is 3/4 (at least) of how I typically use them.
As I commented though a few minor things are going on both siduction and antiX are two of my favorites and there’s a lot they each do well and that’s also true of Endeavour OS, PCLinuxOS, and openSUSE on the HP-14 and also Legacy OS, MX Linux and Mandriva on the Dell Inspiron 5558.
--
Brian MasinickFebruary 10, 2023 at 9:19 pm #99364Forum Adminrokytnji
::ID-1: /dev/mmcblk1 vendor: Hynix model: HAG2e size: 14.68 GiB
MAJOR influence on my distro choice. I like That the antiX full iso update/grade took up a lot less space than the original Kali install.
Funny thing was. Sound worked OK in Kali. I did not have it long enough to test bluetooth though.
MY mind was already made up.Internal bluetooth is still a problem. If I can look in the bios and turn it off. Hope it is not a wifi/bluetooth combo card with 2 chips.
NOT really stressing on this feature though. Cuz everything else is working.Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problems - AuthorPosts
- You must be logged in to reply to this topic.