← Back to team overview

kernel-packages team mailing list archive

[Bug 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.


This bug affects me on Ubuntu Gnome 14.04 x64.

uname -a:
Linux tp-w530 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

On a Thinkpad W530.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission

Status in “bluez” package in Ubuntu:

Bug description:
  After updating from 8.04 to 12.04 I cannot use rfcomm without sudo.

  I've already added the user  to group 'dialout' .

  Temporary I tried to change udev.rules (KERNEL=="rfcomm[0-9]*", GROUP="dialout", MODE="666")  but this doesn't
  solve the problem so I removed it again.

  Here the commands I used :

  burki@orion:/$ hcitool scan
  Scanning ...
   00:12:6F:08:98:FF	GEO LE-71 00001

  burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF
  Can't open RFCOMM device: Permission denied

  burki@orion:/$ ls -l /dev/rfcomm1
  ls: cannot access /dev/rfcomm1: No such file or directory

  burki@orion:/$ groups
  burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse scanner lpadmin netdev sambashare

  burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF
  Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1
  Press CTRL-C for hangup

  In another terminal while connection is running ...

  burki@orion:/$ ls -l /dev/rfcomm1
  crw-rw---- 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1

  burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1)
  (I've stolen this command from another bug report #570692.  Output is very long. Please see attachment)

  WORKAROUND: sudo chmod u+s /usr/bin/rfcomm

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
   /dev/snd/controlC0:  burki      1730 F.... pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe500000 irq 56'
     Mixer name	: 'Intel CougarPoint HDMI'
     Components	: 'HDA:10ec0887,10438444,00100302 HDA:80862805,80862805,00100000'
     Controls      : 49
     Simple ctrls  : 21
  Date: Tue Jun 19 09:15:54 2012
  HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
   lo        no wireless extensions.

   eth0      no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7
   linux-restricted-modules-3.2.0-25-generic-pae N/A
   linux-backports-modules-3.2.0-25-generic-pae  N/A
   linux-firmware                                1.79
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to: