** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
Title:
Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
denied.
Status in bluez package
Have the same problem on opensuse. #17 fixes it for me, thank you for
the info.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
Title:
Ubuntu 12.04, i386, cannot use rfcomm as
I have this same problem on Xubunut 16.04.
I cannot access rfcomm* except as root, despite the permissions:
$ ls -al /dev/rfcomm0
crw-rw 1 root dialout 216, 0 Feb 18 13:58 /dev/rfcomm0
and my membership to dialout:
$ id bob
uid=1000(bob) gid=1000(bob)
Writing a udev rule to ignore device by ModemManager worked for me:
/etc/udev/rules.d/55-bluetooth-drone-NoModem.rules
KERNEL=="rfcomm*", ATTR{address}=="xx:d3:xx:00:xx:xx",
ENV{ID_MM_DEVICE_IGNORE}="1"
And reloading rules:
sudo udevadm control --reload-rules
So I connect to device as root
Problem still persists, can't access any /dev/rfcomm device (nor laptop
built-in, nor usb bluetooth adapter) as a regular user.
Tested on:
uname -a
Linux jakub-Inspiron-3537 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
the problem may be in the ModemManager:
$ sudo lsof /dev/rfcomm0
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ModemMana 10865 root9u CHR 216,0 0t0 132879 /dev/rfcomm0
after
$ sudo service ModemManager stop
i was able to connect to the device as regular user.
--
You
Same problem in Xubuntu 15.04. Can't access /dev/rfcomm0 as regular
user. I stopped service ModemManager, then lsof /dev/rfcomm0 returned
nothing and the problem persist. I only can do cat /dev/rfcomm0 as
root.
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags added: vivid
** Changed in: bluez (Ubuntu)
Importance: Undecided = Medium
** Tags removed: vivid
** Tags added: jaunty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
3.19.0-15-generic x86_64 x86_64 x86_64 problem persists
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
Title:
Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
This bug exists in Ubuntu 15.04 allthough I can only run Kernel
3.16.0-31-generic #43-Ubuntu SMP x86_64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
Title:
Ubuntu 12.04,
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
Burkhard Arenfeld, given rfcomm is provided by bluez, and this would
appear not to be a kernel bug, sending to them for review.
** Package changed: linux (Ubuntu) = bluez (Ubuntu)
** Changed in: bluez (Ubuntu)
Importance: Low = Undecided
** Changed in: bluez (Ubuntu)
Status:
Hello Christopher
I've done some tests to find the first time this bug occur. I started the PC
with different Ubuntu live CDs (every CD was a i386, desktop image). The last
working distribution was 8.10 (Intrepid). The first time this bug appears was
in the next version 9.04 (Jaunty). I've
Burkhard Arenfeld, thank you for testing Trusty.
Should I set the kernel-bug-exists-upstream flag now?
No, as this is strictly reserved for actually testing the latest
upstream mainline kernel only. Testing Trusty is testing the downstream
Ubuntu kernel, not mainline.
However, the next step is
Hello again,
I have done some tests with the latest development release of Ubuntu
(trusty-desktop-i386.iso, downloaded on 13.01.2014).
The bug is still there.
Here the steps I've done to check it:
- Boot ubuntu from CD (live cd, image from 13.01.2014)
- Start the bluetooth applet
- Open a
Hello Christopher,
I updated my mainboard bios to the latest version as you advised me to do, but
nothing changed.
Here the output of the command:
sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
4105
07/01/2013
(At first I reset the suid bit of /usr/bin/rfcomm I made earlier
Burkhard Arenfeld, thank you for updating your BIOS. Could you please
confirm this issue exists with the latest development release of Ubuntu?
ISO images are available from http://cdimage.ubuntu.com/daily-
live/current/ . If the issue remains, please just make a comment to
this.
Please note,
** Tags added: bios-outdated-4105
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1014992
Title:
Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
denied.
Status in
Burkhard Arenfeld, as per http://www.asus.com/Motherboards/P8Z68V_LX/#support
an update is available for your BIOS (4105). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it
doesn't, could you please both specify what happened, and just
19 matches
Mail list logo