Ubuntu
bluez package

rfcomm permission denied in Ubuntu Jaunty

Asked by quixote_arg

Since I upgraded to Ubuntu Jaunty, I cannot connect to my phone with rfcomm as a regular user anymore

I had a file in /etc/bluetooth/rfcomm.conf with the settings

with a regular user I connected with

$ rfcomm connect 0

now it throws "permission denied" (same user, same config, only upgraded to Jaunty)

any workaround? I want that link to be accesible for the same user so running

$ sudo rfcomm connect 0

is possible but I prefer to avoid that

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu bluez Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
everythingsround (pclawler) said : 		#1

I'm getting:
Can't connect RFCOMM socket: Device or resource busy

release seems to do nothing...reboot and all.

sudo rm /dev/rfomm* - no go

and even editing /etc/bluetooth/rfcomm.conf
got me to the point in which I used up my rfcomm3 and rfcomm4
I don't want to keep going and fill these up with no way to release. Any suggestions?

Revision history for this message
quixote_arg (tulsidas) said : 		#2

what kind of information is needed?

Revision history for this message
lxop (lxop) said : 		#3

I have the same problem. I've noticed that the /dev/rfcomm0 file now has group root instead of group dialout. This means I can't access the port from my normal account, but I can't say whether that is also why I can't run rfcomm as a normal user too.

Revision history for this message
quixote_arg (tulsidas) said : 		#4

Any ideas or patch to apply?

Revision history for this message
quixote_arg (tulsidas) said : 		#5

sudo chown <user>.<user> /dev/rfcomm0

does the trick, but it's kind of an annoyance since it has to be done each time

Revision history for this message
Launchpad Janitor (janitor) said : 		#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.