[Bug 273873] New: Bluedevil 1.04-3.1 and blueman do not function on KDE 4.6.0 and HP tm2t-2200
Andy Lavarre
alavarre at gmail.com
Sun May 22 17:21:21 BST 2011
https://bugs.kde.org/show_bug.cgi?id=273873
Summary: Bluedevil 1.04-3.1 and blueman do not function on KDE
4.6.0 and HP tm2t-2200
Product: kde
Version: 4.6
Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: unassigned-bugs at kde.org
ReportedBy: alavarre at gmail.com
Version: 4.6 (using KDE 4.6.0)
OS: Linux
I recently got a new machine and am trying to get bluedevil working, but have
not yet succeeded. Below are all the details.
** The bottom line is that the software installs, the menus function, the
system recognizes the BT adapter, but the machine cannot find other devices,
and other devices cannot find this computer.**
+ The machine is HP TouchSmart tm2t-2200
+ The OS is openSUSE 11.4
+ The OS-installed version of BlueDevil was 1.02 (which didn't work) but I have
now added repositories and used YaST to install version 1.04-3.1.
+ This same Bluedevil version works just fine on my old machine with the same
operating system, so it must be the difference in hardware?
+ YaST reports the hardware as
Vendor: usb 0x148f "Ralink Technology, Corp."
> Mmm this is weird, try:
> -hcitool scan (paste the output)
It returns NOTHING - NADA:
hp-tm2:~ # hcitool scan
Scanning ...
hp-tm2:~ #
> -be sure that your adapter is not "hidden"
Not "hidden" according to bluedevil > configure adapters (says Powered, Always
visible)
> -Try other bluetooth software (blueman)
Same response from blueman-manager. So perhaps it is a driver issue?
===================== Details =====================
YaST reports:
38: USB 00.0: 11500 Bluetooth Device
[Created at usb.122]
Unique ID: JPTW.tGttqvOhWG9
Parent ID: FKGF.0j9+vWlqL56
SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0
SysFS BusID: 2-1.3:1.0
Hardware Class: bluetooth
Model: "Ralink Bluetooth Device"
Hotplug: USB
Vendor: usb 0x148f "Ralink Technology, Corp."
Device: usb 0x1000
Revision: "52.76"
Driver: "btusb"
Driver Modules: "btusb"
Speed: 12 Mbps
Module Alias: "usb:v148Fp1000d5276dcE0dsc01dp01icE0isc01ip01"
Driver Info #0:
Driver Status: btusb is active
Driver Activation Cmd: "modprobe btusb"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #36 (Hub)
Bluedevil discovers it at MAC CC:52:AF:50:0D:FE
We have it activated with modprobe btusb
But configuring it fails with bluedevil.
Installing the operating system on the new machine resulted in bluedevil
1.02-3.8.1 being installed. This version does not work.
The older machine has bluedevil 1.04-3.1 installed. That version DOES work on
that machine.
I uninstalled bluedevil and searched around for repositories for the newer
version. I was not able to install 1.04 because of dependency issues, but after
rebooting and runnning yast2 sw_single I now found 1.04-3.1 available so I
installed it. I also compared all the other bluedevil and bluez files between
the two machines. I have the same files on both. But bluedevil does not work on
the new machine although it does work on the old machine.
After all of this and a fresh reboot dmesg reports:
[ 62.418592] Bluetooth: L2CAP ver 2.15
[ 62.418596] Bluetooth: L2CAP socket layer initialized
[ 62.437051] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 62.437054] Bluetooth: BNEP filters: protocol multicast
[ 62.542333] Bluetooth: SCO (Voice Link) ver 0.6
[ 62.542336] Bluetooth: SCO socket layer initialized
[ 63.295452] Bluetooth: RFCOMM TTY layer initialized
[ 63.295458] Bluetooth: RFCOMM socket layer initialized
[ 63.295460] Bluetooth: RFCOMM ver 1.11
Reproducible: Always
Steps to Reproduce:
1. Reboot
2. Right-Click on BT icon in taskbar
3. Select configure adapter or Add device:
Actual Results:
nothing happens, no devices discovered
Expected Results:
should find any number of devices: phone, car, headset
Should find other devices, should be discoverable by other devices
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list