[Solved] Blueman search button disabled

[maspai]

I have a bluetooth dongle and packages mentioned on http://docs.salixos.org/wiki/Bluetooth installed. Bluetooth applet shows on the panel tray (I use Salix Xfce 14.1), but search button in blueman-manager window is disabled. Otherwise is in debian's blueman.
I tried to add "/usr/sbin/service start bluetooth" in /etc/rc.d/rc.local and also run bluetoothd, no avail.

EDIT: If it helps, here is output when I run blueman-manager in terminal:

Code: Select all

$ blueman-manager 
Loading configuration plugins
_________
<module> (/usr/lib/python2.7/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf 
Using file config backend
_________
Load (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:68)
['PulseAudioProfile', 'Services'] 
_________
Load (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:68)
Unable to load plugin module PulseAudioProfile
PulseAudio applet plugin not loaded, nothing to do here 
_________
__load_plugin (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:142)
loading <class 'blueman.plugins.manager.Services.Services'> 
blueman-manager version 1.22 starting
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:110)
org.bluez owner changed to  :1.1 
Using file config backend
_________
SetAdapter (/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py:301)
None 
_________
SetAdapter (/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py:301)
No such adapter 
_________
on_adapter_changed (/usr/lib/python2.7/site-packages/blueman/gui/manager/ManagerToolbar.py:89)
toolbar adapter None 

[gapan]

What happens in you launch blueman-browse from a terminal? Do you get any devices listed?

[maspai]

What happens in you launch blueman-browse from a terminal? Do you get any devices listed?

Code: Select all

$ blueman-browse 
Loading configuration plugins
_________
<module> (/usr/lib/python2.7/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf 
_________
SetAdapter (/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py:301)
None 
_________
SetAdapter (/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py:301)
No such adapter 
Traceback (most recent call last):
  File "/usr/bin/blueman-browse", line 96, in <module>
    Browse()
  File "/usr/bin/blueman-browse", line 54, in __init__
    dev = self.select_device()
  File "/usr/bin/blueman-browse", line 80, in select_device
    d = DeviceSelectorDialog()
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceSelectorDialog.py", line 56, in __init__
    self.selector.List.DiscoverDevices()
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py", line 445, in DiscoverDevices
    self.Adapter.StartDiscovery()
AttributeError: 'NoneType' object has no attribute 'StartDiscovery'

Is this blueman problem? I tried blueman also in another distro with same thing happened. But in a distro with Mate and gnome-bluetooth (as I recall), no problem.

[gapan]

It looks like your bluetooth device is not detected properly. What is the output of

Code: Select all

sudo lsusb

and

Code: Select all

hcitool scan

and also

Code: Select all

sudo hcitool scan

[maspai]

Code: Select all

$ lsusb
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 002: ID 0402:7675 ALi Corp. 
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ hcitool scan
Device is not available: No such device

$ sudo hcitool scan
Password:
Device is not available: No such device

$ sudo dmesg|grep -i bluetooth
[   18.844031] usb 1-2: Product: Bluetooth V2.0 Dongle
[   18.844128] usb 1-2: Manufacturer: Bluetooth v2.0
[   19.539778] Bluetooth: Core ver 2.16
[   19.540362] Bluetooth: HCI device and connection manager initialized
[   19.541344] Bluetooth: HCI socket layer initialized
[   19.541586] Bluetooth: L2CAP socket layer initialized
[   19.541762] Bluetooth: SCO socket layer initialized
[   32.072561] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.072576] Bluetooth: BNEP filters: protocol multicast
[   32.072597] Bluetooth: BNEP socket layer initialized
[   68.395625] Bluetooth: RFCOMM TTY layer initialized
[   68.395657] Bluetooth: RFCOMM socket layer initialized
[   68.395663] Bluetooth: RFCOMM ver 1.11

In Point Linux (Debian-based, with gnome-bluetooth or mate-bluetooth), the device works well. I wonder if this problem is related to kernel instead blueman. Point Linux kernel is from Debian Wheezy, version 3.2x. This problem also happened in Mint Xfce 16 with new kernel and blueman, too.

[maspai]

I'm quite sure this is kernel bug. Almost all sites I found in Google search result related to this says about kernel bug for kernel version 3.10+. How to downgrade (or upgrade to latest) kernel in Salix?

[gapan]

You can just compile a kernel. Apart from the time it takes, it's not that hard. Other than that, Slackware-current has 3.10.30. The packages will most probably work in 14.1, but you'll have to download them and upgrade manually.

What is the output of

Code: Select all

hcitool dev

(that's what I initially wanted to write, but wrote scan instead)

BWT, bluetooth works fine here with the 3.10.17 kernel in 14.1, but the problem could be specific to your model.

[slack631]

BWT, bluetooth works fine here with the 3.10.17 kernel in 14.1, but the problem could be specific to your model.

Hi

It might be easily a problem related to the specific device-driver or so.
I have attached an old Bluetooth Dongle, it works here,blueman-manager has all buttons enabled.
I even paired it with mob-phone. A new directory obexfs appiered,
and it's possible to browse inside, and send files,easily.
I have installed blueman-r708-x86_64-3 package from Slackware and started rc.bluetooth.
Blueman-manager works, no need to run it as root.
Kernel is 3.10.33. I have compiled it with config file from slackware.If it is of some help.

regards

[maspai]

You can just compile a kernel. Apart from the time it takes, it's not that hard. Other than that, Slackware-current has 3.10.30. The packages will most probably work in 14.1, but you'll have to download them and upgrade manually.

What is the output of

Code: Select all

hcitool dev

(that's what I initially wanted to write, but wrote scan instead)

BWT, bluetooth works fine here with the 3.10.17 kernel in 14.1, but the problem could be specific to your model.

Code: Select all

$ hcitool dev
Devices:
$ hciconfig scan
hci0:	Type: BR/EDR  Bus: USB
BD Address: 00:19:86:00:0E:4B  ACL MTU: 1017:8  SCO MTU: 64:0
DOWN 
RX bytes:914 acl:0 sco:0 events:32 errors:0
TX bytes:136 acl:0 sco:0 commands:32 errors:0

As I read, hciconfig scan should show hci0 as UP, and my result is DOWN.

Code: Select all

$ sudo hciconfig hci0 up

returns

Code: Select all

Can't init device hci0: Operation not supported (95)

. This part is said as kernel fail. And these don't happen in kernel 3.2x of my PointLinux (Debian Wheezy).
Anyway, where can I find an easy step-by-step kernel compiling? I have no idea about it . Or can I easily do installpkg to downloaded Slackware Current's 3.10.30 kernel package?

[gapan]

Yes, you can download and upgradepkg the kernel packages from slackware current. Just make sure that you do it for all kernel-* packages that you have installed. And don't forget to run

Code: Select all

sudo lilo

after you have upgraded them.