You are not logged in.
Recently, I installed ArchLinux (kernel: 4.13.12-1-ARCH) on my XPS 13 laptop. I am using GNOME 3.26.
Everything looks good, except for my Bluetooth device. The network controller in my XPS 13 is
Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
I found some relevant error messages repeated by journalctl:
Nov 26 20:03:02 IgorArch gnome-control-c[1204]: Failed to register object: An object is already exported for the interface org.bluez.Agent1 at /org/bluez/agent/gnome
Nov 26 20:03:02 IgorArch gnome-bluetooth-panel.desktop[1204]: Agent unregistration failed: GDBus.Error:org.bluez.Error.DoesNotExist: Does Not Exist 'g-io-error-quark'
Meanwhile, I don't find any controllers by bluetoothctl.
It is a very strange problem since it worked properly before the last reboot several hours ago. I remember that I did a system update with "pacman -Syu", but I cannot remember which package was actually updated (is there any efficient way to check it?). Meanwhile, I cannot find any problem with the Bluetooth module and service on my laptop:
$ dmesg |grep -in "bluetooth"
732:[ 6.713653] Bluetooth: Core ver 2.22
734:[ 6.713669] Bluetooth: HCI device and connection manager initialized
735:[ 6.713681] Bluetooth: HCI socket layer initialized
736:[ 6.713692] Bluetooth: L2CAP socket layer initialized
737:[ 6.713696] Bluetooth: SCO socket layer initialized
740:[ 6.717540] Bluetooth: HCI UART driver ver 2.3
741:[ 6.717542] Bluetooth: HCI UART protocol H4 registered
742:[ 6.717542] Bluetooth: HCI UART protocol BCSP registered
743:[ 6.717558] Bluetooth: HCI UART protocol LL registered
744:[ 6.717559] Bluetooth: HCI UART protocol ATH3K registered
745:[ 6.717559] Bluetooth: HCI UART protocol Three-wire (H5) registered
746:[ 6.717589] Bluetooth: HCI UART protocol Intel registered
747:[ 6.717600] Bluetooth: HCI UART protocol Broadcom registered
748:[ 6.717601] Bluetooth: HCI UART protocol QCA registered
749:[ 6.717601] Bluetooth: HCI UART protocol AG6XX registered
750:[ 6.717602] Bluetooth: HCI UART protocol Marvell registered
886:[ 10.115652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
887:[ 10.115654] Bluetooth: BNEP filters: protocol multicast
888:[ 10.115657] Bluetooth: BNEP socket layer initialized
$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2017-11-26 20:15:58 CET; 1h 40min ago
Docs: man:bluetoothd(8)
Main PID: 1673 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─1673 /usr/lib/bluetooth/bluetoothd
Any suggestion and help is extremely appreciated!
Offline
I cannot remember which package was actually updated (is there any efficient way to check it?).
There is a time tagged log at /var/log/pacman.log
I have a hunch you are using an old kernel. Either you did not reboot, or your boot manager is picking up an old kernel.
What are the output of uname -a and of pacman -Q linux ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
igor1982 wrote:I cannot remember which package was actually updated (is there any efficient way to check it?).
There is a time tagged log at /var/log/pacman.log
I have a hunch you are using an old kernel. Either you did not reboot, or your boot manager is picking up an old kernel.
What are the output of uname -a and of pacman -Q linux ?
Thanks waller! I will check the time tag from /var/log/pacman.log carefully immediately. Here is a quick reply to your second question:
Linux IgorArch 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux
Offline
Here is a list of updated files. Again, I don't find any clue of my broken Bluetooth I will try to reboot my Arch again, despite I have rebooted it serval times.
[2017-11-26 11:55] [PACMAN] Running 'pacman -Syu'
[2017-11-26 11:55] [PACMAN] synchronizing package lists
[2017-11-26 11:55] [PACMAN] starting full system upgrade
[2017-11-26 11:56] [ALPM] transaction started
[2017-11-26 11:56] [ALPM] upgraded alsa-plugins (1.1.4-1 -> 1.1.5-1)
[2017-11-26 11:56] [ALPM] upgraded cmake (3.9.6-1 -> 3.10.0-2)
[2017-11-26 11:56] [ALPM] upgraded libjpeg-turbo (1.5.2-1 -> 1.5.2-2)
[2017-11-26 11:56] [ALPM] upgraded hwids (20170715-1 -> 20171003-1)
[2017-11-26 11:56] [ALPM] upgraded epiphany (3.26.2-2 -> 3.26.3-1)
[2017-11-26 11:56] [ALPM] installed libyaml (0.1.7-1)
[2017-11-26 11:56] [ALPM] installed gcab (0.7+16+g4bc4be1-1)
[2017-11-26 11:56] [ALPM] upgraded gnupg (2.2.2-1 -> 2.2.3-1)
[2017-11-26 11:56] [ALPM] installed appstream-glib (0.7.4-1)
[2017-11-26 11:56] [ALPM] upgraded mpfr (3.1.5.p2-1 -> 3.1.6.p1-1)
[2017-11-26 11:56] [ALPM] upgraded flatpak (0.10.0-1 -> 0.10.1-1)
[2017-11-26 11:56] [ALPM] upgraded gmime3 (3.0.3-1 -> 3.0.4-1)
[2017-11-26 11:56] [ALPM] upgraded libwbclient (4.7.1-1 -> 4.7.3-1)
[2017-11-26 11:56] [ALPM] upgraded tevent (1:0.9.33-1 -> 1:0.9.34-1)
[2017-11-26 11:56] [ALPM] upgraded ldb (1.2.2-1 -> 1.3.0-1)
[2017-11-26 11:56] [ALPM] upgraded smbclient (4.7.1-1 -> 4.7.3-1)
[2017-11-26 11:56] [ALPM] upgraded rtkit (0.11+6+g417bb7d-1 -> 0.11+8+ge0a51fe-1)
[2017-11-26 11:56] [ALPM] upgraded libplist (2.0.0-1 -> 2.0.0+11+gec9ba8b-1)
[2017-11-26 11:56] [ALPM] upgraded gnome-control-center (3.26.2-1 -> 3.26.2+14+g5ac6a0da6-1)
[2017-11-26 11:56] [ALPM] upgraded gnome-session (3.26.1-1 -> 3.26.1-2)
[2017-11-26 11:56] [ALPM] upgraded jbig2dec (0.13-1 -> 0.14-1)
[2017-11-26 11:57] [ALPM] upgraded libreoffice-fresh (5.4.3-3 -> 5.4.3-4)
[2017-11-26 11:57] [ALPM] upgraded noto-fonts (20171025-1 -> 20171025-2)
[2017-11-26 11:57] [ALPM] upgraded pipewire (0.1.6-1 -> 0.1.6-2)
[2017-11-26 11:57] [ALPM-SCRIPTLET] Created symlink /etc/systemd/user/sockets.target.wants/pipewire.socket → /usr/lib/systemd/user/pipewire.socket.
[2017-11-26 11:57] [ALPM] upgraded python-setuptools (1:37.0.0-1 -> 1:38.1.0-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-base (5.9.2-2 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-xmlpatterns (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-declarative (5.9.2-2 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-location (5.9.2-2 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-multimedia (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-script (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-sensors (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-speech (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-svg (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-tools (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-webchannel (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded qt5-webkit (5.212.0alpha2-8 -> 5.212.0alpha2-10)
[2017-11-26 11:57] [ALPM] upgraded qt5-x11extras (5.9.2-1 -> 5.9.3-1)
[2017-11-26 11:57] [ALPM] upgraded telepathy-idle (0.2.0-1 -> 0.2.0-2)
[2017-11-26 11:57] [ALPM] transaction completed
Offline
Offline
seems that I am using the latest kernel properly:
$ pacman -Q linux
linux 4.13.12-1
Offline
Okay. It appears that the kernel that is running matches the one that is installed and has kernel modules available. You had said you recently installed Arch. A common mistake is to not mount the boot partition on /boot during an upgrade, so the boot loader never gets the the new kernel. This does not seem to be the issue here.
Unfortunately, none of those packages strike me as being a possible culprit.
What are you using as a desktop environment? I see Gnome was updated, and Gnome has a rather totalitarian approach to system management.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Hi ewaller, I am now using GNOME as my desktop environment. The problem is that I cannot find any bluetooth controller with the bluetooth debugging utility bluetoothctl. I am wondering whether it is a problem of Gnome. I am very confused now because I just couldn't find any useful message from the system journals.
Offline
It seems that I found the problem. The Bluetooth device cannot be detected when I restarted the laptop as I did many times yesterday. Interestingly, it can be found properly if I start the laptop completely today.
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0cf3:e300 Qualcomm Atheros Communications
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 413c:2113 Dell Computer Corp.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I remembered that the device in bold above (might be my Bluetooth) didn't show up yesterday when my Bluetooth wasn't working in the "restart" mode.
Offline
hmm my bluetooth stopped working today (worked fine for almost a year), and I can't remember what packages I upgraded yesterday evening.
XPS 13 9360
symptoms:
$ bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
journalctl:
$ journalctl -b |grep Bluetooth
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: Core ver 2.22
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI device and connection manager initialized
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI socket layer initialized
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: L2CAP socket layer initialized
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: SCO socket layer initialized
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART driver ver 2.3
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol H4 registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol BCSP registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol LL registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol ATH3K registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol Intel registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol Broadcom registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol QCA registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol AG6XX registered
Nov 30 13:21:48 xps_9360 kernel: Bluetooth: HCI UART protocol Marvell registered
Nov 30 13:22:08 xps_9360 systemd[1]: Starting Bluetooth service...
Nov 30 13:22:08 xps_9360 bluetoothd[2459]: Bluetooth daemon 5.47
Nov 30 13:22:08 xps_9360 systemd[1]: Started Bluetooth service.
Nov 30 13:22:08 xps_9360 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Nov 30 13:22:08 xps_9360 kernel: Bluetooth: BNEP filters: protocol multicast
Nov 30 13:22:08 xps_9360 kernel: Bluetooth: BNEP socket layer initialized
Nov 30 13:22:08 xps_9360 bluetoothd[2459]: Bluetooth management interface 1.14 initialized
lsusb:
$ lsusb
Bus 004 Device 002: ID 2109:0210 VIA Labs, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:0923 Chicony Electronics Co., Ltd
Bus 003 Device 002: ID 2109:2210 VIA Labs, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:670c Microdia
Bus 001 Device 002: ID 04f3:20d0 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It looks like my bluetooth device isn't recognized anymore ? No idea what I should be doing now..
@igor1982, what do you mean by "start completely" ?
Last edited by Fandekasp (2017-11-30 04:54:11)
Offline
LOL got it... I was indeed restarting the laptop, and stopping / starting it made the "Qualcomm Atheros Communications" device pop up in lsusb, and bluetooth worked back fine. wtf, lost my lunch break over this, Mr Robot will have to wait tomorrow now :'(
Offline
My old laptop had similar symptoms, I think it was an Atheros chip as well. Basically bluetooth would be finicky if you do a sleep/hibernate/restart, but work better when shutting down and startin gup. I just got used to always doing a shut down/start up cycle. My new (current) machine no longer does that, different chipset.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline