|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Hardware Questions about drivers, peripheral cabling, configuration |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Try 0000. I have a MS BT Mouse 5000 and it only accepts that, with no possibility ot change it.
|
|
|||
|
More information in the comments of this bug report, including different approaches to the problem.
|
|
|||
|
Hi is there anyone can help me on my problem??? Thx
|
|
|||
|
Quote:
Code:
./test-device trusted 00:07:61:D4:B4:DE yes |
|
|||
|
I got this stuff to work, with a Microsoft Bluetooth Notebook Mouse 5000 (using pin 0000 worked, good tip there.) I haven't tested if it works after reboot, but that's not that important. What's important is that we get some official updates to fix this - I think it's a little ridiculous that this stuff was broken somewhere along the way and not fixed for the 11.1 release (I don't know with whom the fault may lie, doesn't matter, it happened.)
When I first tried bluetooth devices I was actually surprised with how well it worked (that was with 10.3) - I'm used to having to fiddle with stuff to get hardware working, but it worked right out of the box! And it worked in 11.0. So needless to say I'm really quite disappointed. So I got a little concerned when the bug report that's linked to here was marked as resolved - are there other bug reports regarding bluetooth stuff? Can we expect official updates to fix all this anytime soon? I'm not sure how to tell if something's being worked on. Also, it's a little unclear what the status of this is - is it only a kde 3 problem? I don't use kde 4 or gnome so I'm not sure if it's broken in those as well. |
|
|||
|
Can I get help with this?
Code:
# ./simple-agent.pl hci0 00:18:A3:00:76:C8
Traceback (most recent call last):
File "./simple-agent.pl", line 80, in <module>
manager = dbus.Interface(bus.get_object("org.bluez", "/"),
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 607, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
|
|
|||
|
Thank you very much for this info. A little clarification, you wrote "dongle", but you really don't do anything with dongle -- but rather with external device, right?
Ok, and now I have problem with dbus, when running it I get error: Error org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with signature "" on interface "org.bluez.Input" doesn't exist Any ideas what is wrong? opensuse11.1 32-bit. |
|
|||
|
Quote:
This is a generic error message. Maybe the device path has changed (check /var/log/messages)... |
|
|||
|
> > Thank you very much for this info. A little clarification, you
> > wrote "dongle", but you really don't do anything with dongle -- > > > but > > rather with external device, right? > Not sure what you're asking -- but I can tell you that I have a > tiny, USB-connected, bluetooth device plugged into the back of my > desktop computer. It provides the wireless connectivity to the > keyboard. I call it a dongle, maybe that isn't the right word. No no :-) The word is 100% correct, I have bt card (dongle) and bt mouse, so when I scan the bt devices I see two of them. And I don't connect to dongle but to mouse directly. > > Error org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" > > with signature "" on interface "org.bluez.Input" doesn't exist > This is a generic error message. Maybe the device path has changed > (check /var/log/messages)... Thank you! It is getting better. Now I get mouse working but I have to after each restart connect to it manually again. The problem is: Code:
dbus-send --system --dest=org.bluez --print-reply /org/bluez/6308/hci0/dev_00_1E_52_FF_68_44 org.bluez.Input.Connect I execute this line (with numbers corrected). Mouse starts working. I execute test-device to make connection permanent, right? Ok. Reboot. Nothing happens. So I check /var/log/messages and it appears that org.bluez is now registered with different number (the part after /org/bluez). So knowing the number I modify dbus-send and mouse starts working again. But the problem of course is, that I have to check /var/log/messages and execute dbus manually each time. How this can be automated, or the number for /org/bluez fixed? |
|
|||
|
matthewcraig:
Thanks for the instruction. I just bought a Ms bluetooth notebook mouse 5000. And found this mouse can not work on my 11.1 kde4 desktop. Follow your tuition, now it works. Same as other person said, the device path may change after reboot. I write a script to find that path, maybe all of you can help refine this. bluetooth_mouse_start.sh Code:
#!/bin/bash MOUSE_ADD=dev_00_12_5A_6C_D3_47 #MS BT Notebook Mouse 5000 BTPATH=`cat /var/log/messages | grep bluez | grep enable | tail -1 |cut -d '[' -f 2| cut -d ']' -f 1` dbus-send --system --dest=org.bluez --print-reply /org/bluez/$BTPATH/hci0/$MOUSE_ADD org.bluez.Input.Connect this script can only be run by root so I use another script put in ~/.kde4/Autostart/ btm.sh Code:
#!/bin/bash kdesu -c bluetooth_mouse_start.sh enter root password, then mouse can move. Hope this can help others |
![]() |
|
| Bookmarks |
| Tags |
| 11.1, apple keyboard bluetooth, bluetooth, kde, solution |
| Thread Tools | |
| Display Modes | |
|
|