I dont still have that bluetooth gps but ill see if I can find a
similar one and retest it.

On Tue, Jul 24, 2012 at 1:02 PM, Christopher M. Penalver
<email address hidden> wrote:
> dragonneus, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> Can you try with the latest development release of Ubuntu? ISO CD images
> are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do
> not test the kernel in the daily folder, but the one all the way at the
> bottom. Once you've tested the upstream kernel, please remove the
> 'needs-upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description
> and deleting the 'needs-upstream-testing' text. As well, please comment
> on which kernel version specifically you tested.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream', and comment
> as to why specifically you were unable to test it.
>
> Please let us know your results. Thanks in advance.
>
> ** Tags added: lucid needs-upstream-testing regression-release
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/570692
>
> Title:
>   Ubuntu 10.04 Can't open RFCOMM device: Permission denied
>
> Status in “linux” 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 manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570692/+subscriptions