Comment 10 for bug 570692

rfcomm connect 4
 Can't open RFCOMM device: Permission denied

ran requested command and recieve:

crw-rw---- 1 root dialout 216, 4 2010-04-28 01:11 /dev/rfcomm4

------------------------------------------------------------------------------------------------------------------------

On Wed, Apr 28, 2010 at 12:23 AM, Scott James Remnant
<email address hidden> wrote:
> On Wed, 2010-04-28 at 04:12 +0000, dragonneus wrote:
>
>> udev_rules_apply_to_event: GROUP 20 /lib/udev/rules.d/50-udev-default.rules:15
>>
> This is "dialout"
>
> Could you run "ls -l /dev/rfcomm*" for me and attach the output?  (with
> the device plugged in and node created)
>
> Scott
> --
> Scott James Remnant
> <email address hidden>
>
> --
> Ubuntu 10.04 Can't open RFCOMM device: Permission denied
> https://bugs.launchpad.net/bugs/570692
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “udev” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: udev
>
> Cannot open /dev/rfcomm4 new install Ubuntu 10.04. This worked fine in Ubuntu 9.10.
>
> I expected to see:
> Connected /dev/rfcomm4 to 00:1C:88:30:11:45 on channel 1
> Press CTRL-C for hangup
>
> Instead I have recieved:
>  Can't open RFCOMM device: Permission denied
>
> Same issue happened in Jaunty (https://bugs.launchpad.net/ubuntu/jaunty/+source/udev/+bug/374782) read there that "rfcomm were not in the dialout group" Tried to add rule in /etc/udev/rules.d/.
>
>  KERNEL=="rfcomm*", GROUP="dialout" added in rules  worked one time then recieved same error message (Can't open RFCOMM device: Permission denied)
>
> can this please be fixed in the Kernel, it affects many serial devices. In this case for me a bluetooth GPS.
>
> Thank you for your consideration and time,
>
> Dragonneus
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/570692/+subscribe
>