- This topic has 7 replies, 6 voices, and was last updated Apr 28-7:03 am by ThoughtFool.
-
Posts
-
mindan
I installed antix 26 x64 full.
First bug.
During installation i see button “Service Settings (Advanced)”, but when i click it – i see blank window with no services.Second bug.
After installation i open “icewm manager”, and click “show/hide conky”, and it works – conky hides. But after reboot conky is running.
It will be good, if i click this button and file
/home/user/.desktop-session/desktop-session.conf
will change value
LOAD_CONKY=”false”
anticapitalista
Welcome – both ‘bugs’ are actually ‘features’.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
sybok
As @anticapitalista pointed out, the conky show/hide is a change applied to the current session only.
This has been discussed on the forum elsewhere already.ThoughtFool
I encountered a different bug in antiX26 or a new feature, maybe?
I use a PlayStation controller as a mouse, because it doesn’t put as much strain on my wrist compared to a mouse.
When I try to pair the controller via Bluetooth, it tells me to enter a PIN.
I open Blueman, connect the controller via cable, activate its Bluetooth, mark as trusted, unplug the cable and then I need to enter the PIN.I searched the web for solutions and entered some standard PINs as suggested, like “0000”, “1234” or simply entering Space, but to no avail.
In antiX23 I simply marked the device as trusted and paired it with no problems at all. No PIN needed.
Any suggestions?
Robin
and then I need to enter the PIN.
I have seen the very same issue with earphones on 32 bit antiX 26. Still under investigation, no solution found. Stubbornly and stupidly asks for a non-existent PIN, and the default workarounds (entering e.g. 0000) fail. Seems the trixie bluetooth stack is broken, at least partly. Maybe it requires latest kernels? What are your system specs and kernel version? (Since there is literally no other/newer kernel available in 32 bit than 5.10 I can’t check out whether this is fixed in recent kernel versions.)
Windows is like a submarine. Open a window and serious problems will start.
anti-apXos
Tried this?
On antix26, restarting the bluetooth service will not involve systemctl, of course, but will depend on which init you’re using. It would be ‘sudo sv restart bluetooth’ on runit, for example. Or I suppose you could probably just be a barbarian with ‘sudo pkill bluetoothd’ and let the service manager restart it automatically.
"--"
Tried this?
No. Had simply still no time to continue investigating. Many thanks @anti-apXos for pointing me to this, I’ll check out asap and report back. But from my understanding this explains already completely and precisely the weird behaviour, it actually felt like a regression.
From there (since link may fail once manjaro reorganises its forum structure) :
– Create the file /etc/bluetooth/input.conf with the following content:
[General] ClassicBondedOnly=false– Restart bluetooth service.
Reference: https://github.com/bluez/bluez/issues/673
It would be ‘sudo sv restart bluetooth’ on runit, for example.
Or, for people not familiar with console operations, just use the service management from antiX Control Centre, which will bring up the respective service manager for the currently booted init system. In all the modern ones exist buttons for restarting the service with a single click, while in legacy sysvinit it is a pain to understand what to do, while possible (sorry, have forgotten how). All service managers also allow to permanently add the service to system startup, and to add it first time, so it can be operated e.g. by sv commands on console in runit then (alternatively you’d need to create the respective symlinks manually.)
Windows is like a submarine. Open a window and serious problems will start.
Sorry for the late reply.
After following your instructions, Bluetooth is working perfectly now.
Thanks @anti-apXos and @Robin for the quick help!
- You must be logged in to reply to this topic.