Ubuntu 10.04 Can't open RFCOMM device: Permission denied

[dragonneus]

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

[Scott James Remnant (Canonical) (canonical-scott)]

Please run the following command and attach the output:

UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm4)

[dragonneus (dragonneus)]

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
>

[Scott James Remnant (Canonical) (canonical-scott)]

On Tue, 2010-04-27 at 20:29 +0000, dragonneus wrote:

> 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
>
This shows that you do not *have* an rfcomm4 - try again with 0-3?

Scott
--
Scott James Remnant
<email address hidden>

[dragonneus (dragonneus)]

Does the same thing with rfcomm1, the device isnt created in linux
until its utilized. When its turned on and command ran it will be
crated in /dev, much like serial/usb devices such as the usb to serial
adapter.

Seems like the same issue as for Jaunty. This worked fine in 9.10
(https://bugs.launchpad.net/ubuntu/jaunty/+source/udev/+bug/374782
On Tue, Apr 27, 2010 at 7:00 PM, Scott James Remnant
<email address hidden> wrote:
> On Tue, 2010-04-27 at 20:29 +0000, dragonneus wrote:
>
>> 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
>>
> This shows that you do not *have* an rfcomm4 - try again with 0-3?
>
> 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
>

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2010-04-28 at 01:01 +0000, dragonneus wrote:

> Does the same thing with rfcomm1, the device isnt created in linux
> until its utilized. When its turned on and command ran it will be
> crated in /dev, much like serial/usb devices such as the usb to serial
> adapter.
>
It would be helpful you plugged the rfcomm device in and ran the command
once the /dev node has been created.

Scott
--
Scott James Remnant
<email address hidden>

[dragonneus (dragonneus)]

ok doing that now

On Tue, Apr 27, 2010 at 10:25 PM, Scott James Remnant
<email address hidden> wrote:
> On Wed, 2010-04-28 at 01:01 +0000, dragonneus wrote:
>
>> Does the same thing with rfcomm1, the device isnt created in linux
>> until its utilized. When its turned on and command ran it will be
>> crated in /dev, much like serial/usb devices such as the usb to serial
>> adapter.
>>
> It would be helpful you plugged the rfcomm device in and ran the command
> once the /dev node has been 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
>

[dragonneus (dragonneus)]

if I run
rfcomm connect 4

I get :
dragonneus@AZUREDRAGON:~$ UDEV_LOG=debug udevadm test $(udevadm info
-q path -n rfcomm4)
device node not found
custom logging function 0x2210f008 registered
selinux=0
run_command: calling: test
udevadm_test: version 151
syspath parameter missing

If I run the same command in SUDO:

dragonneus@AZUREDRAGON:~$ UDEV_LOG=debug udevadm test $(udevadm info
-q path -n rfcomm4)
custom logging function 0x2212e008 registered
selinux=0
run_command: calling: test
udevadm_test: version 151
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/lib/udev/rules.d/40-fuse-utils.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-gnupg.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-gpsd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-hplip.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ia64.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-infiniband.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-isdn.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libgphoto2-2.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libpisock9.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libsane.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-pilot-links.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ppc.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-usb-media-players.rules' as rules file
parse_file: reading
'/lib/udev/rules.d/40-xserver-xorg-video-intel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-zaptel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libmtp8.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/55-dm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/56-hpmud_support.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-floppy.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-dm.rules'
as rules file
parse_file: reading
'/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as
rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file
parse_file: reading
'/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
parse_file: reading
'/lib/udev/rules.d/61-option-modem-modeswitch.rules' as rules file
p...

[dragonneus (dragonneus)]

also this is a bluetooth GPS device, it is connected once the rfcomm
connect 4 command is run. it is already setup in the bluetooth
manager, /etc/bluetooth/rfcomm.conf is setup already as:

rfcomm4 {
        bind yes;
        device 00:1C:88:30:11:45 ;
        channel 1;
        comment "Serial Port";
        }

To make the connection I am forced to use SUDO which causes issues
trying to use any program with the GPS.

In Ubuntu 9.10 I didnt need to use sudo with this and programs such as
xgps worked fine.

[Scott James Remnant (Canonical) (canonical-scott)]

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>

[dragonneus (dragonneus)]

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
>

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2010-04-28 at 05:12 +0000, dragonneus wrote:

> 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
>
Thanks.

And lastly, could you run the "groups" command for me and return the
output.

Scott
--
Scott James Remnant
<email address hidden>

[dragonneus (dragonneus)]

Please forgive my ignorance but what groups command?

On Wed, Apr 28, 2010 at 2:13 AM, Scott James Remnant
<email address hidden> wrote:
> On Wed, 2010-04-28 at 05:12 +0000, dragonneus wrote:
>
>> 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
>>
> Thanks.
>
> And lastly, could you run the "groups" command for me and return the
> output.
>
> 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
>

[Scott James Remnant (Canonical) (canonical-scott)]

On Wed, 2010-04-28 at 06:41 +0000, dragonneus wrote:

> Please forgive my ignorance but what groups command?
>
/usr/bin/groups

It's part of the "coreutils" package, which is an "Essential" package in
Ubuntu.

(In summary, you have it installed, or you're not running Ubuntu <g>)

Scott
--
Scott James Remnant
<email address hidden>

[dragonneus (dragonneus)]

dragonneus@AZUREDRAGON:~$ /usr/bin/groups
dragonneus adm dialout cdrom plugdev lpadmin admin sambashare

On Wed, Apr 28, 2010 at 4:12 AM, Scott James Remnant
<email address hidden> wrote:
> On Wed, 2010-04-28 at 06:41 +0000, dragonneus wrote:
>
>> Please forgive my ignorance but what groups command?
>>
> /usr/bin/groups
>
> It's part of the "coreutils" package, which is an "Essential" package in
> Ubuntu.
>
> (In summary, you have it installed, or you're not running Ubuntu <g>)
>
> 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
>

[Scott James Remnant (Canonical) (canonical-scott)]

Thanks, in which case the -EPERM must be coming from inside the kernel - and not related to the device node permissions

[StefanF (stefan)]

I just like to confirm that I have the same problem here.

[Michael Mulqueen (michael.mulqueen)]

I can confirm that I also have this problem. Bluetooth otherwise works fine (well, as far as I can tell, all I really use is OBEX). I'm using a full up-to-date version of 10.04.

michael@Vanadium:~$ hciconfig
hci0: Type: USB
 BD Address: 00:25:56:ED:6F:xx ACL MTU: 1021:8 SCO MTU: 64:1
 UP RUNNING PSCAN
 RX bytes:29827 acl:1056 sco:0 events:1326 errors:0
 TX bytes:1688226 acl:2297 sco:0 commands:86 errors:0

I think it's a Broadcom chip connected via USB (it's inside the netbook, a Thinkpad Ideapad S12). sudo seems to provide some relief to the problem but it's still broken.

I'm trying to connect to a phone (a Symbian-based Nokia running the PyS60 console).

[8200 (8200)]

I can also confirm this bug.

I am using bluetooth for connecting to internet through my mobile (Nokia 5800) and it only works with "sudo rfcomm...", else I get "Can't open RFCOMM device: Permission denied".

[Jan Bakuwel (jan-bakuwel-gmail)]

I can also confirm this problem (Ubuntu 10.04 32bit) using bluetooth to connect to Nokia E61i). It makes no difference if I do this as root (sudo) or not. The output from UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm0) below. Could:

udev_device_update_db: unable to create temporary db file '/dev/.udev/db/tty:rfcomm0.tmp': Permission denied

be a problem? The file exists though:

$ ls -al /dev/.udev/db/tty\:rfcomm0
lrwxrwxrwx 1 root root 18 2010-06-21 17:16 /dev/.udev/db/tty:rfcomm0 -> rfcomm0 char/216:0

I tried removing the link - makes no difference.

$ ls -al /dev/rfcomm0
crw-rw---- 1 root dialout 216, 0 2010-06-21 17:46 /dev/rfcomm0
$ id
uid=2000(UN) gid=2000(UN) groups=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),44(video),46(plugdev),104(fuse),105(lpadmin),112(netdev),119(admin),122(sambashare),2000(UN)

Username substituted for UN.

udev_rules_new: rules use 209676 bytes tokens (17473 * 12 bytes), 33446 bytes buffer
udev_rules_new: temporary index used 55540 bytes (2777 * 20 bytes)
udev_device_new_from_syspath: device 0x21bba248 has devpath '/devices/virtual/tty/rfcomm0'
udev_device_new_from_syspath: device 0x21bba3f0 has devpath '/devices/virtual/tty/rfcomm0'
udev_device_read_db: device 0x21bba3f0 filled with db symlink data '/dev/rfcomm0'
udev_rules_apply_to_event: LINK 'char/216:0' /lib/udev/rules.d/50-udev-default.rules:4
udev_rules_apply_to_event: GROUP 20 /lib/udev/rules.d/50-udev-default.rules:15
udev_rules_apply_to_event: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2
udev_event_execute_rules: no node name set, will use kernel supplied name 'rfcomm0'
udev_device_update_db: unable to create temporary db file '/dev/.udev/db/tty:rfcomm0.tmp': Permission denied
udev_node_add: creating device node '/dev/rfcomm0', devnum=216:0, mode=0660, uid=0, gid=20
udev_node_mknod: preserve file '/dev/rfcomm0', because it has correct dev_t
node_symlink: preserve already existing symlink '/dev/char/216:0' to '../rfcomm0'
udevadm_test: UDEV_LOG=7
udevadm_test: DEVPATH=/devices/virtual/tty/rfcomm0
udevadm_test: MAJOR=216
udevadm_test: MINOR=0
udevadm_test: DEVNAME=/dev/rfcomm0
udevadm_test: ACTION=add
udevadm_test: SUBSYSTEM=tty
udevadm_test: DEVLINKS=/dev/char/216:0
udevadm_test: run: 'socket:@/org/freedesktop/hal/udev_event'

$ pppd nomagic call bluetooth
Failed to open /dev/rfcomm0: Connection refused
$ sudo pppd nomagic call bluetooth
[sudo] password for UN:
Failed to open /dev/rfcomm0: Connection refused
$

Please note that I can't open the device (/dev/rfcomm0) with minicom or the Serial Port Terminal (same error).
It's not a device permissions problem... there is some communication with the Nokia E61i (as shown by hcidump):

$ sudo hcidump -t
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
1277101579.840190 < HCI Command: Create Connection (0x01|0x0005) plen 13
1277101579.847549 > HCI Event: Command Status (0x0f) plen 4
1277101580.315554 > HCI Event: Connect Complete (0x03) plen 11
1277101580.315587 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
1277101580.333546 > HCI Event: Command Status (0x0...

[zzart (zzart999)]

have the same here. ubuntu 10.04 , thinkpad r61, gps navibe

sudo UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm4)
missing option
-q: command not found
custom logging function 0x22318008 registered
selinux=0
run_command: calling: test
udevadm_test: version 151
syspath parameter missing

ls -l /dev/rfcomm*
crw-rw---- 1 root dialout 216, 4 2010-07-09 11:29 /dev/rfcomm4
/usr/bin/groups
mars adm dialout cdrom plugdev lpadmin admin sambashare

i have the output from gps
cat /dev/rfcomm4
$GPGGA,092928,,N,,E,0,00,,,M,,M,,*65
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPGSV,3,1,11,05,,,42,09,,,00,25,,,00,08,,,00*7E
$GPGSV,3,2,11,27,,,00,16,,,00,30,,,00,10,,,39*72
.............

gpsd is still unable to read this ! is this permission problem , or what ?

[dragonneus (dragonneus)]

Gents,

Will this be fixed in this or the next distro? Is there a temp fix so I may use my GPS with my netbook?

Dragonneus

[dragonneus (dragonneus)]

bump**

any temp fix for this?

On Fri, Jul 23, 2010 at 4:27 AM, dragonneus <email address hidden> wrote:
> Gents,
>
> Will this be fixed in this or the next distro? Is there a temp fix so I
> may use my GPS with my netbook?
>
> Dragonneus
>
> --
> 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 “linux” package in Ubuntu: Confirmed
>
> 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/linux/+bug/570692/+subscribe
>

[Adam Bolte (boltronics)]

We just had a new kernel for Lucid released last week (2.6.32-24.39), but it appears no fix was included. Particularly when Ubuntu has been trying so hard to reach the netbook market (which is what I'm experiencing the problem on) and it worked in 9.10, this is a real frustration.

I would be very happy with a workaround, kernel patch, anything to get this sorted. Haven't tried running 10.10 yet to see if that helps, but might give it a shot if I have to.

[Tom Wood (woodts)]

A workaround is to run "rfcomm connect X" as root, where X is the desired channel (4 in your case, 0 for me, for examples). /dev/rfcommX will then be created, to which you can then connect.

[Martin (demlan)]

The work around suggest by Tom does not work for me,

user@name:~$ sudo rfcomm connect 5
Can't find a config entry for rfcomm5

Also the workaround suggest for jaunty (adding a udev rule) where a similar bug existed does not help.

A sudo on the regular rfcomm command solves the problem,

sudo rfcomm -i hci0 connect /dev/rfcomm5 00....
Connected /dev/rfcomm5 to 00... on channel 1

but this means giving root rigths to all programms connecting to rfcomm5 which I definitely do not want to do.

Isn't there any workaround to get a working connection accessible in user space ?

[Martin (demlan)]

Little update:

Tom's suggestion works when the connection is defined in /etc/bluetooth/rfcomm.conf

[dragonneus (dragonneus)]

doesnt work for me

On Mon, Oct 18, 2010 at 6:22 AM, Martin <email address hidden> wrote:
> Little update:
>
> Tom's suggestion works when the connection is defined in
> /etc/bluetooth/rfcomm.conf
>
> --
> 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 “linux” package in Ubuntu: Confirmed
>
> 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/linux/+bug/570692/+subscribe
>

[Erik Westman (systemingenjorer)]

One solution is to change the mod of /usr/bin/rfcomm. I.e $sudo chmod 6755 /usr/bin/rfcomm

This makes the rfcomm device a security risk, but it works as a work-around.

// Erik

[Brian Jepson (bjepson)]

I'm seeing this error in 10.10 (my user is in the dialout group, /dev/rfcommX is being set up correctly as root:dialout). It turns out that the problem is intermittent however.

I connect my device by using Bluetooth Manager (right click, select Connect To: Serial Service). The port gets set up, but I can't access it. I'm testing with:
  echo 1 > /dev/rfcomm0
When it fails, I get:
  bash: /dev/rfcomm0: Device or resource busy

If I toggle the connection (right click, disconnect, then reconnect) a couple of times, I'm able to access the port.

This is happening under VMware Fusion using the Mac's built-in Bluetooth module and the btusb-dkms workaround described at https://help.ubuntu.com/community/MacBookPro6-2/Maverick#Package%20Support%20for%20Intel%20Macs.

[penalvch (penalvch)]

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.

[dragonneus (dragonneus)]

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...

[penalvch (penalvch)]

dragonneus, if you do not have the same model of bluetooth GPS that you used when you originally reported this bug, then please open a new report. Hence, this bug report is being closed due to your last comment regarding you no longer having the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[fprimex (brent-fprimex)]

Hello Customer

We are adding new items weekly.
Status accessories and attributes are very important for successful and popular people. Now you don't have to spend ridiculous money to impress partners with expensive watch. Purchase watches of high quality that look identical to the ones you will find at the jewelry store.

**********************************************************************************************
I ordered a ca-26 watch from you last week it already arrived. Let me say the watch is awesome, I couldn't believe my eyes it looks exactly like the real thing. Let me tell you many thanks and I would buy a lot more watches from you from now on.
Thankee!
                     Marcelo Hogan
**********************************************************************************************

Click here ---> http://penio.ru

[Thomas E. Horner (thomas.horner)]

still occurs in Ubuntu 16.04.4 LTS

[penalvch (penalvch)]

Thomas E. Horner, as this report is closed, it will help immensely if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.