rfcomm Permission denied
Hi,
I have a problem using bluetooth serial device i.e. rfcomm works perfectly ok if run as root. For instance: the command: rfcomm connect rfcomm0 00:12:6F:07:5E:B ends up with: Can't open RFCOMM device: Permission denied. The same command run as ROOT runs ok.
This is the debugging which isn't working. Down below it is the same run as root.
Feb 6 09:39:40 x17 udevd[352]: seq 2107 queued, 'add' 'bluetooth'
Feb 6 09:39:40 x17 udevd[352]: passed 180 bytes to monitor 0x7f5b700292d0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2107 running
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b70039f50 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b70043130 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b7003c4d0 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b7003c860 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b7003cce0 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b7003cfd0 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:39:40 x17 udevd-work[3627]: RUN '/usr/sbin/
Feb 6 09:39:40 x17 udevd-work[3627]: passed 225 bytes to monitor 0x7f5b700293d0
Feb 6 09:39:40 x17 udevd-work[3627]: '/usr/sbin/
Feb 6 09:39:40 x17 udevd-work[3627]: '/usr/sbin/
Feb 6 09:39:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2107 processed with 0
Feb 6 09:39:40 x17 udevd[352]: seq 2107 done with 0
Feb 6 09:39:40 x17 bluetoothd[3048]: link_key_request (sba=00:
Feb 6 09:39:40 x17 udevd[352]: seq 2108 queued, 'add' 'tty'
Feb 6 09:39:40 x17 udevd[352]: passed 151 bytes to monitor 0x7f5b700292d0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2108 running
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b70039f50 has devpath '/devices/
Feb 6 09:39:40 x17 udevd-work[3627]: LINK 'char/216:0' /lib/udev/
Feb 6 09:39:40 x17 udevd-work[3627]: GROUP 20 /lib/udev/
Feb 6 09:39:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:39:40 x17 udevd-work[3627]: no node name set, will use kernel supplied name 'rfcomm0'
Feb 6 09:39:40 x17 udevd-work[3627]: created db link (rfcomm0 char/216:0)
Feb 6 09:39:40 x17 udevd-work[3627]: creating device node '/dev/rfcomm0', devnum=216:0, mode=0660, uid=0, gid=20
Feb 6 09:39:40 x17 udevd-work[3627]: preserve file '/dev/rfcomm0', because it has correct dev_t
Feb 6 09:39:40 x17 udevd-work[3627]: chmod(/dev/rfcomm0, 020660)
Feb 6 09:39:40 x17 udevd-work[3627]: chown(/dev/rfcomm0, 0, 20)
Feb 6 09:39:40 x17 udevd-work[3627]: creating symlink '/dev/char/216:0' to '../rfcomm0'
Feb 6 09:39:40 x17 udevd-work[3627]: passed 182 bytes to monitor 0x7f5b7003d170
Feb 6 09:39:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2108 processed with 0
Feb 6 09:39:40 x17 udevd[352]: seq 2108 done with 0
Feb 6 09:39:40 x17 udevd[352]: seq 2109 queued, 'remove' 'tty'
Feb 6 09:39:40 x17 udevd[352]: passed 154 bytes to monitor 0x7f5b700292d0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2109 running
Feb 6 09:39:40 x17 udevd-work[3627]: device 0x7f5b70039f50 filled with db symlink data '/dev/rfcomm0'
Feb 6 09:39:40 x17 udevd-work[3627]: RUN '/lib/udev/
Feb 6 09:39:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:39:40 x17 udevd-work[3627]: no reference left, remove '/dev/char/216:0'
Feb 6 09:39:40 x17 udevd-work[3627]: device node '/dev/rfcomm0' not found
Feb 6 09:39:40 x17 udevd-work[3627]: '/lib/udev/
Feb 6 09:39:40 x17 udevd-work[3627]: '/lib/udev/
Feb 6 09:39:40 x17 udevd-work[3627]: passed 188 bytes to monitor 0x7f5b7003c8e0
Feb 6 09:39:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:39:40 x17 udevd-work[3627]: seq 2109 processed with 0
Feb 6 09:39:40 x17 udevd[352]: seq 2109 done with 0
Feb 6 09:39:43 x17 udevd[352]: seq 2110 queued, 'remove' 'bluetooth'
Feb 6 09:39:43 x17 udevd[352]: passed 183 bytes to monitor 0x7f5b700292d0
Feb 6 09:39:43 x17 udevd-work[3627]: seq 2110 running
Feb 6 09:39:43 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:39:43 x17 udevd-work[3627]: passed 231 bytes to monitor 0x7f5b70043130
Feb 6 09:39:43 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:39:43 x17 udevd-work[3627]: seq 2110 processed with 0
Feb 6 09:39:43 x17 udevd[352]: seq 2110 done with 0
RUN as ROOT.
Feb 6 09:37:40 x17 udevd[352]: seq 2100 queued, 'add' 'bluetooth'
Feb 6 09:37:40 x17 udevd[352]: passed 180 bytes to monitor 0x7f5b700292d0
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2100 running
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b70039fd0 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003a100 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b70042dc0 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003c620 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003c960 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003cc50 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:37:40 x17 udevd-work[3627]: RUN '/usr/sbin/
Feb 6 09:37:40 x17 udevd-work[3627]: passed 225 bytes to monitor 0x7f5b70029330
Feb 6 09:37:40 x17 udevd-work[3627]: '/usr/sbin/
Feb 6 09:37:40 x17 udevd-work[3627]: '/usr/sbin/
Feb 6 09:37:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2100 processed with 0
Feb 6 09:37:40 x17 udevd[352]: seq 2100 done with 0
Feb 6 09:37:40 x17 bluetoothd[3048]: link_key_request (sba=00:
Feb 6 09:37:40 x17 udevd[352]: seq 2101 queued, 'add' 'tty'
Feb 6 09:37:40 x17 udevd[352]: passed 151 bytes to monitor 0x7f5b700292d0
Feb 6 09:37:40 x17 udevd[352]: seq 2102 queued, 'move' 'tty'
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2101 running
Feb 6 09:37:40 x17 udevd-work[3627]: LINK 'char/216:0' /lib/udev/
Feb 6 09:37:40 x17 udevd-work[3627]: GROUP 20 /lib/udev/
Feb 6 09:37:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:37:40 x17 udevd-work[3627]: no node name set, will use kernel supplied name 'rfcomm0'
Feb 6 09:37:40 x17 udevd-work[3627]: created db link (rfcomm0 char/216:0)
Feb 6 09:37:40 x17 udevd-work[3627]: creating device node '/dev/rfcomm0', devnum=216:0, mode=0660, uid=0, gid=20
Feb 6 09:37:40 x17 udevd-work[3627]: preserve file '/dev/rfcomm0', because it has correct dev_t
Feb 6 09:37:40 x17 udevd-work[3627]: chmod(/dev/rfcomm0, 020660)
Feb 6 09:37:40 x17 udevd-work[3627]: chown(/dev/rfcomm0, 0, 20)
Feb 6 09:37:40 x17 udevd-work[3627]: creating symlink '/dev/char/216:0' to '../rfcomm0'
Feb 6 09:37:40 x17 udevd-work[3627]: passed 182 bytes to monitor 0x7f5b70043270
Feb 6 09:37:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2101 processed with 0
Feb 6 09:37:40 x17 udevd[352]: seq 2101 done with 0
Feb 6 09:37:40 x17 udevd[352]: passed 245 bytes to monitor 0x7f5b700292d0
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2102 running
Feb 6 09:37:40 x17 udevd-work[3627]: RUN 'socket:
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b70043130 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003d120 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b70029420 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b70042fc0 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003c8c0 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b7003cc40 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: device 0x7f5b700295d0 has devpath '/devices/
Feb 6 09:37:40 x17 udevd-work[3627]: passed 299 bytes to monitor 0x7f5b70029800
Feb 6 09:37:40 x17 udevd-work[3627]: passed -1 bytes to monitor 0x7f5b7003a2e0
Feb 6 09:37:40 x17 udevd[352]: seq 2102 done with 0
Feb 6 09:37:40 x17 udevd-work[3627]: seq 2102 processed with 0
Config error or kernel error?
Best regard, Erik
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu linux Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Erik.Westman
- Solved:
- Last query:
- Last reply: