First, check the status of the bluetooth service: systemctl status bluetooth.service If the status is not active (running), then enable it: systemctl enable bluetooth.service Then, start the service: systemctl start bluetooth.service Finally, check the status again: systemctl status bluetooth.service If the status is now active (running), then the bluetooth service is enabled.
The Xbacklight no output have properties message can happen if your hardware has poor support or it can’t be detected properly by the xbacklight utility. This might be fixed by using an xbacklight wrapper called acpilight. acpilight can also be used to control the display and keyboard backlight on modern laptops. First, install the acpilight package: sudo pacman -Syu acpilight Add a udev rule to give access to users in the video group, this is needed because users don’t have permissions to alter sys files by default: ...
Arch Linux uses a package manager called pacman, as you may know this is pretty standard on any linux distro, however, I’ve seen that not all the people use the same way to install or upgrade packages. The simpler way you can install a package with pacman is: pacman -S package_name But, this will only install the package on your system and nothing else. You may say but that’s what I want basically, but due to the rolling release nature and since partial upgrades are not supported on Arch Linux this might not be the best approach in the long term and could even break your system. ...
If you just installed i3 on a laptop and for some reason you can’t tap or the scrolling behavior doesn’t like you, you can update how the touchpad behaves using a xorg config file. In my case the scrolling behaviour wasn’t the one I like, so I modified the NaturalScrolling property. ## /etc/X11/xorg.conf.d/30-touchpad.conf Section "InputClass" Identifier "touchpad" Driver "libinput" MatchIsTouchpad "on" Option "Tapping" "on" Option "NaturalScrolling" "true" EndSection You can see all the available options. ...
I started using i3 as my window manager, and at some point started having some issues with env variables on GUI apps. This is because we usually add env variables to the shell config file, in my case the .zshrc file, however, .zshrc will set the env variables only in your shell and not all the apps. So, when setting up a project using git with ssh and a passphrase as authentication (and after doing all the setup for the gnome keyring) I realized that my VSCode wasn’t actually using the keyring and was asking for the ssh passphrase always, however, this wasn’t happening on my shell. ...