SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
*) hcitool scan
00:25:CF:70:10:77 SLS
*) sdptool browse 00:25:CF:70:10:77
Service Name: OBEX File Transfer
Service RecHandle: 0x100e9
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
*)obexftp -v -b 00:25:CF:70:10:77 -B 9 -p file.txt
If i send the file with obexftp, my phone ask me a pin code...
I try "1234" ,"0000" and other but it's don't work. You have a many idea?
this is the result:
Code:
Connecting...failed: connect
Tried to connect for 3001ms
Interupted/bad reception or the device moved out of range: Operation now in progress
Still trying to connect
Connecting...failed: connect
Tried to connect for 0ms
error on connect(): Device or resource busy
Still trying to connect
Connecting...failed: connect
Tried to connect for 0ms
error on connect(): Device or resource busy
Still trying to connect
did you try any gui-way to connect (blueman-applet)?
usually you have to choose a pin on one device, and then you confirm it on the other one, blueman allows you to "trust" a device, so you'll only have to do this once.
unfortunately, the information for bluetooth, pin and cli that google provides seems outdated, at least it doesn't correspond to slackware's bluetooth-package.
generally, using bluetooth for file transfer is quite a pain, i try to avoid it whenever possible.
Hello friends, thank you for reply.
Didier: when i run "blueman-applet", i recive this error:
Code:
....
....
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: File o directory non esistente
_________
save (/usr/lib/python2.6/site-packages/blueman/plugins/config/File.py:117)
Saving config
Exception AttributeError: "'NoneType' object has no attribute 'Bus'" in <bound method File.__del__ of <File object at 0x84c76bc (blueman+plugins+ConfigPlugin+ConfigPlugin at 0x8302bd0)>> ignored
...bluetoothd command:
Code:
bluetoothd -nd
bluetoothd[13098]: Bluetooth deamon 4.91
bluetoothd[13098]: src/main.c:parse_config() parsing main.conf
bluetoothd[13098]: src/main.c:parse_config() discovto=0
bluetoothd[13098]: src/main.c:parse_config() pairto=0
bluetoothd[13098]: src/main.c:parse_config() pageto=8192
bluetoothd[13098]: src/main.c:parse_config() name=%h-%d
bluetoothd[13098]: src/main.c:parse_config() class=0x000100
bluetoothd[13098]: src/main.c:parse_config() discov_interval=0
bluetoothd[13098]: src/main.c:parse_config() Key file does not have key 'DeviceID'
bluetoothd[13098]: Unable to get on D-Bus
I think that problem of the "blueman-applet" depend by bluetoothd error.
Have you a idea for bluetoothd and blueman-applet works?
Thank you friends
thank you didier, i tryed it and blueman-applet work...but when i scan bluetooth device, i have "Operation not permitted"...if i use "sudo blueman-applet" result is equal.
Hello friends,
why i have the permission problem when i launch the bluetooth scan?
I try blueman-applet with "sudo" but i have same result.
Help me please.
Thank you friends
do you have the right firmware files?
there seems to be an ath3k firmware in -current, see here, but the file is missing in 13.37.
edit:
by the way 1: in my case, the only way to obtain a similarily verbose output of bluetoothd -nd, although without the permission denied-stuff, is having rfkilled it first. could you check rfkill list, maybe it's hard-blocked for some reason.
by the way 2: why don't you use "bluetoothd --udev"?
Hello san, i have tryed with "bluetooth --udev" but doesn't work...The scan option is disabled while if i use "bluetooth -nd" the scan option is enabled but i have "Option not permitted".
In the last day i have modify /etc/dbus-1/system.d/bluetooth.conf...it's correct?
Code:
<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some holes -->
<policy user="arturo">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
</policy>
<policy group="plugdev">
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
<allow send_interface="org.bluez.Adapter"/>
<allow send_destination="org.bluez"
send_interface="org.freedesktop.DBus.Introspectable"/>
</policy>
<!-- allow users of lp group (printing subsystem) to
communicate with bluetoothd -->
<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>
<policy context="default">
<deny send_destination="org.bluez"/>
</policy>
</busconfig>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
