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
wrote:
> dragonneus, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this
essage (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,
bump**
any temp fix for this?
On Fri, Jul 23, 2010 at 4:27 AM, dragonneus <570...@bugs.launchpad.net> 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
>
> --
> Ubun
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 member of U
dragonn...@azuredragon:~$ /usr/bin/groups
dragonneus adm dialout cdrom plugdev lpadmin admin sambashare
On Wed, Apr 28, 2010 at 4:12 AM, Scott James Remnant
wrote:
> On Wed, 2010-04-28 at 06:41 +0000, dragonneus wrote:
>
>> Please forgive my ignorance but what groups command?
&
Please forgive my ignorance but what groups command?
On Wed, Apr 28, 2010 at 2:13 AM, Scott James Remnant
wrote:
> On Wed, 2010-04-28 at 05:12 +0000, dragonneus wrote:
>
>> rfcomm connect 4
>> Can't open RFCOMM device: Permission denied
>>
>> ran requeste
, Apr 28, 2010 at 12:23 AM, Scott James Remnant
wrote:
> On Wed, 2010-04-28 at 04:12 +, 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 /de
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 Por
udev_event_execute_rules: no node name set, will use kernel supplied
name 'rfcomm4'
udev_device_update_db: unable to create temporary db file
'/dev/.udev/db/tty:rfcomm4.tmp': Permission denied
udev_node_add: creating device node '/dev/rfcomm4', devnum=216:4,
mode=0660, u
ok doing that now
On Tue, Apr 27, 2010 at 10:25 PM, Scott James Remnant
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
://bugs.launchpad.net/ubuntu/jaunty/+source/udev/+bug/374782
On Tue, Apr 27, 2010 at 7:00 PM, Scott James Remnant
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
>> cust
;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 considera
d 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
** Affects: udev (Ubuntu)
Im
13 matches
Mail list logo
