Comment 2 for bug 570692

Revision history for this message
dragonneus (dragonneus) wrote : Re: [Bug 570692] Re: Ubuntu 10.04 Can't open RFCOMM device: Permission denied

results of run command. Using Ubuntu 10.04 netbook remix

device node not found
custom logging function 0x21de2008 registered
selinux=0
run_command: calling: test
udevadm_test: version 151
syspath parameter missing

On Tue, Apr 27, 2010 at 1:16 PM, Scott James Remnant
<email address hidden> wrote:
> Please run the following command and attach the output:
>
> UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm4)
>
> ** Changed in: udev (Ubuntu)
>       Status: New => Incomplete
>
> ** Changed in: udev (Ubuntu)
>   Importance: Undecided => Medium
>
> --
> 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
>