systemctl status bluetooth.servicebluetooth.service
- Bluetooth Manager
Loaded: loaded (/lib/systemd/system/bluetooth.service)
Active: active (running) since Thu, 13 Oct 2011 21:06:35 -0400; 43min ago
Main PID: 1027 (bluetoothd)
CGroup: name=systemd:/system/bluetooth.service
â”” 1027 /usr/sbin/bluetoothd -n
But the bluetooth gui says:
No Bluetooth adapters found
I am stumped. Is there a hardware switch to the bluetooth that is turned off?
rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
The bluetooth is not even there.
Gaaaah!!
lspci output
00:00.0 Host bridge: Intel Corporation Sandy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Sandy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09)
00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 4 (rev b4)
00:1c.5 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 6 (rev b4)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Cougar Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation Device 0df4 (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8176 (rev 01)
04:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)
04:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)
04:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 30)
04:00.4 System peripheral: JMicron Technology Corp. xD Host Controller (rev 30)
05:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
Some googling lead to another bloke facing the exact problem
Oct 13 21:57:15 bluetoothd[1027]: Stopping SDP server
Oct 13 21:57:15 bluetoothd[1027]: Exit
Oct 13 21:57:15 bluetoothd[1027]: bluetoothd[1027]: Stopping SDP server
Oct 13 21:57:15 bluetoothd[1027]: bluetoothd[1027]: Exit
Oct 13 21:57:16 bluetoothd[2481]: Bluetooth deamon 4.87
Oct 13 21:57:16 bluetoothd[2481]: bluetoothd[2481]: Bluetooth deamon 4.87
Oct 13 21:57:16 bluetoothd[2481]: Starting SDP server
Oct 13 21:57:16 bluetoothd[2481]: bluetoothd[2481]: Starting SDP server
Oct 13 21:57:16 bluetoothd[2481]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 13 21:57:16 bluetoothd[2481]: bluetoothd[2481]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 13 21:57:16 bluetoothd[2481]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Oct 13 21:57:16 bluetoothd[2481]: bluetoothd[2481]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Oct 13 21:57:16 NetworkManager[934]: bluez error getting default adapter: No such adapter
Some more googling lead to this thread:
Keany says:
before you start BT installation be sure WLAN LED is ON.
Hmm... so the WLAN LED is on, but the Bluetooth LED is not on and there is no function key to turn the bluetooth LED on!
Aarrrgh. Another unsolved mystery.
It shouldn't matter that the 686 and x86_64 version of the libraries are installed. Anything that is compiled only for i686 will require those libraries. For a long time that included at least Skype, citrix client and second life. This would happen on any OS if you were trying to run 32 bit programs on a 64 bit OS.
That being said texmaker works perfectly fine for my system which means it can on yours.
And, some of the earlier dependencies (eg. latex environment) were already installed in the laptop. Maybe that was the reason for the conflict. I have a sneaking suspicion this is not the end of the i686/x86_64 incompatibility drama. My brother seems to have installed whatever version was nearest his mouse. I will clean it up next month with you but right now I have no time.
Okay, I bypassed luck by installed texstudio, a fork of texmaker. In this case, thank goodness, the linux community is torn by forks and strife.
You have the worst luck. I just ran sudo yum install texmaker and it worked. Sounds like you only have the 686 libraries installed and are running the x86_64 version of the app.
sudo yum install texmaker
Installed:
texmaker.x86_64 1:3.1-1.fc15
Dependency Installed:
Xaw3d.x86_64 0:1.5E-20.fc15
kpathsea.x86_64 0:2007-62.fc15
netpbm.x86_64 0:10.47.26-2.fc15
netpbm-progs.x86_64 0:10.47.26-2.fc15
phonon.x86_64 0:4.5.0-2.fc15
phonon-backend-vlc.x86_64 0:0.4.1-2.fc15
poppler-qt.x86_64 0:0.16.7-1.fc15
qt-webkit.x86_64 1:4.7.4-2.fc15
t1lib.x86_64 0:5.1.2-7.fc15
tetex-dvipost.x86_64 0:1.1-12.fc15
tex-preview.noarch 0:11.86-6.fc15
texlive.x86_64 0:2007-62.fc15
texlive-dvips.x86_64 0:2007-62.fc15
texlive-latex.x86_64 0:2007-62.fc15
texlive-texmf.noarch 0:2007-37.fc15
texlive-texmf-dvips.noarch 0:2007-37.fc15
texlive-texmf-fonts.noarch 0:2007-37.fc15
texlive-texmf-latex.noarch 0:2007-37.fc15
texlive-utils.x86_64 0:2007-62.fc15
xdvik.x86_64 0:22.84.14-9.fc15