When I'm trying to open Blueberry there's problem w/ Rfkill

I've been trying to get my PS3 controller working with Manjaro. I've changed bluetooth utility from bluez to blueberry because bluez didn't seem to work. It turned out that when I'm typing "blueberry" in terminal I got:

rfkill: cannot open /dev/rfkill: No such file or directory
rfkill: nie można odczytać /dev/rfkill: Błędny deskryptor pliku
Traceback (most recent call last):
  File "/usr/lib/blueberry/blueberry.py", line 40, in on_activate
    self.create_window()
Rest of it

File "/usr/lib/blueberry/blueberry.py", line 121, in create_window
self.rfkill = rfkillMagic.Interface(self.update_ui_callback, debug)
File "/usr/lib/blueberry/rfkillMagic.py", line 29, in init
self.have_adapter = self.adapter_check()
File "/usr/lib/blueberry/rfkillMagic.py", line 35, in adapter_check
res = subprocess.check_output(RFKILL_CHK).decode('utf-8')
File "/usr/lib/python3.7/subprocess.py", line 395, in check_output
**kwargs).stdout
File "/usr/lib/python3.7/subprocess.py", line 487, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/sbin/rfkill', 'list', 'bluetooth']' returned non-zero exit status 1.`

I've been trying to reinstall all these bluetooth utilities and even upgraded my Kernel from 4.14.149-1 to 5.2.21-1. I don't know what else should I do and how to connect that controller to computer without any cable. Please be patient, I'm kinda newbie :upside_down_face:
Edit: I'm trying to connect it via Microsoft Xbox 360 controller Dongle.

Is rfkill installed?

sudo pacman -Syu rfkill --needed

Also, please post the output of:

rfkill list
inxi -Fxxxz

Never post pics of terminal outputs on technical support threads unless you have absolutely no other connection but your phone. Even then other methods are possible. No pics :smile:

Information on how to properly post hardware specs and logs:

2 Likes

Is rfkill installed?

Yes, also I tried that command that you provided (just to make sure) and I got:

ostrzeżenie: util-linux-2.34-3 jest w najnowszej wersji -- pomijanie
:: Rozpoczynanie pełnej aktualizacji systemu…
 nie ma nic do zrobienia

(in English - Warning: util-lin[...] --skipping [...] there's nothing to do)

rfkill list
rfkill: nie można otworzyć /dev/rfkill: Nie ma takiego pliku ani katalogu
rfkill: nie można odczytać /dev/rfkill: Błędny deskryptor pliku

Again in ENG: "rfkill: can't open /dev/rfkill: No such file or directory" and "Wrong file descriptor".

inxi -Fxxxz here
System:
  Host: fobys-pc Kernel: 5.2.21-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 
  Desktop: Xfce 4.14.1 tk: Gtk 3.24.12 info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: MSI model: H81-P33(MS-7820) v: 1.0 serial: <filter> 
  BIOS: American Megatrends v: 1.6 date: 03/30/2015 
CPU:
  Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP arch: Haswell 
  rev: 3 L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25611 
  Speed: 952 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 892 2: 899 3: 888 4: 883 
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: eVga.com. driver: nvidia v: 430.40 
  bus ID: 01:00.0 chip ID: 10de:1401 
  Display: x11 server: X.Org 1.20.5 driver: nvidia resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 430.40 
  direct render: Yes 
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
  Device-2: NVIDIA GM206 High Definition Audio vendor: eVga.com. driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0fba 
  Device-3: GYROCOM C&C Audiotrak ProDigy CUBE type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-3:4 chip ID: 1852:7921 
  Sound Server: ALSA v: k5.2.21-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8168 v: 8.047.04-NAPI port: d000 bus ID: 04:00.0 
  chip ID: 10ec:8168 
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.14 TiB used: 78.77 GiB (6.8%) 
  ID-1: /dev/sda vendor: Plextor model: PX-128M6S size: 119.24 GiB speed: 6.0 Gb/s 
  serial: <filter> rev: 1.08 scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC45 scheme: MBR 
  ID-3: /dev/sdc model: SSDPR-CX200-120 size: 111.79 GiB speed: 3.0 Gb/s 
  serial: <filter> rev: 12.2 scheme: MBR 
Partition:
  ID-1: / size: 83.17 GiB used: 18.19 GiB (21.9%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 384.36 GiB used: 60.59 GiB (15.8%) fs: ext4 dev: /dev/sdb4 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 62 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0% 
Info:
  Processes: 172 Uptime: 8m Memory: 7.73 GiB used: 1.15 GiB (14.9%) Init: systemd 
  v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 running in: xfce4-terminal 
  inxi: 3.0.36

Thanks for advice. I fixed that

It is possible you don't have the rfkill service & socket enabled.

You can check the status of both with these commands:

systemctl status systemd-rfkill.service 
systemctl status systemd-rfkill.socket

To enable both:

sudo systemctl enable systemd-rfkill.service 
sudo systemctl enable systemd-rfkill.socket

Reboot.

[baklazan@fobys-pc ~]$ systemctl status systemd-rfkill.service
● systemd-rfkill.service - Load/Save RF Kill Switch Status
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.service; static; vendor preset:>
   Active: inactive (dead)
     Docs: man:systemd-rfkill.service(8)

[baklazan@fobys-pc ~]$ systemctl status systemd-rfkill.socket 
● systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.socket; static; vendor preset: >
   Active: inactive (dead)
     Docs: man:systemd-rfkill.socket(8)
   Listen: /dev/rfkill (Special)
[baklazan@fobys-pc ~]$ sudo systemctl enable systemd-rfkill.service
[sudo] hasło użytkownika baklazan: 
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
[baklazan@fobys-pc ~]$ sudo systemctl enable systemd-rfkill.socket
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

Maybe it's dongle's fault? I don't know.

Forum kindly sponsored by