kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #178749
[Bug 416056] Re: Automatic rfcomm binding at startup doesn't work
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
--
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/416056
Title:
Automatic rfcomm binding at startup doesn't work
Status in bluez package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Won't Fix
Bug description:
Description: Ubuntu Karmic (development branch)
Release: 9.10
The bluetooth modem of my Nokia phone doesn't work in Ubuntu Karmic.
The error message reads:
"Cannot open /dev/rfcomm0: No such file or directory"
ProblemType: Bug
Architecture: i386
Date: Wed Aug 19 19:49:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.27.3-0ubuntu2
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SourcePackage: yelp
Uname: Linux 2.6.31-6-generic i686
Following /etc/bluetooth/rfcomm.conf file is supposed to make the device bind automatically at startup.
rfcomm0 {
bind yes;
device XX:XX:XX:XX:XX:XX;
channel RFCOMM_CHANNEL_NUM;
comment "Description";
}
This is not the case in Ubuntu Karmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/416056/+subscriptions