Maybe it happened to someone in an attempt to send a file via bluetooth, to receive this "friendly" error in response:

Org.openobex The name was not provided any. Service files

This is not an overly serious problem, since, among other things, the same function can be detected from the command line, but it is undeniable comfort can make all via convenient interface .. So quick and painless solution, as root, type:

apt-get install obex-data-server

Obviously also package in question can be easily installed by Synaptic ..

Bookmark to:

These days, in the absence of a wired connection, I'm arranging connect through the phone, using the internal modem via bluetooth. I must say that I thought it was more complicated, but honestly a couple of days I've got lost on it. Anyway, here's how I did not connect .. I state that I use my glorious Nokia N71 (cell phone for many mistreated, but I have always found very well), an offer of flat Wind (Mega 1500 to be precise), and my faithful Debian (but I imagine that for its Ubuntu is the same thing)! Obviously the first step is to properly configure the access point on your phone (it's a simple thing, and the site of your manager is surely the whole procedure step by step for every brand of mobile phone), then we will shape our pc. The point is to bring up the internal modem of the mobile phone (connecting via bluetooth) as a serial modem connected directly to the PC, to do this we need a few commands from the terminal:

hcitool scan

With this command we are going to locate our phone (of course it goes without saying that first it should be enabled Bluetooth and the phone becomes visible!). The output will look like this:

Scanning ... 00:12: D2: 8C: 5E: B2 NOKIA N71

Mark the address that will be returned, will shortly. At this point we give the command:

sdptool search-bdaddr "address found first" DUN | grep Channel

You will be returned to something like "Channel: 1", segnamo even this number. This is the channel used for the Dial-Up. Well, we can do is create a bridge between the Bluetooth and the PC, this command is given as root:

rfcomm bind rfcomm0 "address" "channel"

That's it, typing rfcomm and we should have an output like this:

rfcomm0: 00:12: D2: 8C: 5E: B2 channel 1 clean

This means that everything went well. If there should be written at the end closed, then as root issue the command rfcomm release all and then again rfcomm bind rfcomm0 "address" "channel". Small suggestion to avoid all this every time you connect, edit (with root privileges) the file / etc / bluetooth / rfcomm.conf and make sure that it becomes like this:

# # RFCOMM configuration file. # Rfcomm0 (bind yes; device "mobile address" channel "channel" comment "Name of your phone";)

To have automatically the "bridge" when you turn on your PC. At this point we pass to the connection itself: I use Gnome PPP program is extremely easy to configure. Install it from synaptic, and after starting on the first screen to enter a username and password whatever (not needed in fact), phone number * 99 # or * 99 *** 1 # and then click Configure. On the next screen enter the voice part that you created earlier (if you followed my instructions write / dev/rfcomm0) and as the maximum possible speed, then head on initialization string. The first line (Init 2) Write ATQ0 V1 E0 S0 = 0 & C1 & D2 + FCLASS = 0, while the second line (init 3) will be a string dependent on your operator (in my case, Wind, the string is AT + CGDCONT = 1, "IP", "internet.wind"), you munirvi this information earlier (just a call to customer service). That remains is to close this window and click Connect to surf! One last thing, it is possible that the connection process may stop after a while, and looking at the log you find this error: "Check permissions, or specify a PPPD Path option in wvdial.conf, do not worry, it means that your user is not part of the dip. Open the terminal, Login as root and type:

groupadd-g 30 adduser dip "your user" dip

The next time you login everything will work perfectly!

Bookmark to: