Comment 27 for bug 374782

Also try "rfcomm -a" (may need sudo).

Do you have the device in the /etc/bluetooth/rfcomm.conf file? If so could you include it (you can change the addersses if you are concerned). Also, try if it says "bind yes", try "bind no;" (or just use # to comment out all the active lines), reboot, then from a command line as a normal user, type:

rfcomm connect 0 <btaddr>

have another console window open, and if the above says "connected", do the ls -l /dev/rfcomm0 and see if the ownership and/or permissions have problems and/or try printing.

Part of the problem might that you are "binding" the rfcomm device - telling it to listen, and the printer at the other end is also listening. When you do the open on /dev/rfcomm0, it might try to connect or might assume there was a connection. It won't work if both are listening and neither is starting up the connection.

The rfcomm connect command above will initiate the connection to the printer.

(you may also need the -r switch on rfcomm command line for the printer to work)