Debian Bug report logs - #552185
[gnome-bluetooth] read/write access to the /dev/rfkill device is required

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: submit@bugs.debian.org

Subject: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Sat, 24 Oct 2009 02:32:42 +0200

Package: gnome-bluetooth
Version: 2.28.3-1
Severity: minor

--- Please enter the report below this line. ---

Dear Andrea et al,

according to /usr/share/doc/gnome-bluetooth/README "read/write access to
the /dev/rfkill device is required and should be provided by the
distribution". Well, I have /dev/rfkill, but as a normal user I have
neither read nor write access to it:

ls -l /dev/rfkill 
crw-r--r-- 1 root root 10, 60 24. Okt 01:54 /dev/rfkill

The ubuntu package provides a udev rule in
61-gnome-bluetooth-rfkill.rules which deals with this issue. However, I
really doubt that gnome-bluetooth is the right package to provide such a
udev rule. Please cross-check with the udev maintainer. Anyway, please
enable rfkill for users in a reasonable way. ;)

Thanks,
Fabian


--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.31-trunk-686

Debian Release: squeeze/sid
  500 testing         ftp2.de.debian.org 
  450 unstable        ftp2.de.debian.org 
  400 experimental    ftp2.de.debian.org 

--- Package information. ---
Depends                     (Version) | Installed
=====================================-+-==============
libatk1.0-0               (>= 1.20.0) | 1.28.0-1
libc6                   (>= 2.3.6-6~) | 2.10.1-1
libcairo2                  (>= 1.2.4) | 1.8.8-2
libdbus-1-3                (>= 1.0.2) | 1.2.16-2
libdbus-glib-1-2            (>= 0.78) | 0.82-2
libfontconfig1             (>= 2.4.0) | 2.6.0-4
libfreetype6               (>= 2.2.1) | 2.3.9-5
libgconf2-4               (>= 2.27.0) | 2.28.0-1
libglib2.0-0              (>= 2.18.0) | 2.22.2-2
libgnome-bluetooth7       (>= 2.28.1) | 2.28.3-1
libgtk2.0-0               (>= 2.16.0) | 2.18.2-1
libnotify1                 (>= 0.4.5) | 0.4.5-1
libnotify1-gtk2.10                    | 
libpango1.0-0             (>= 1.14.0) | 1.26.0-1
libunique-1.0-0            (>= 1.0.0) | 1.1.2-2
zlib1g                   (>= 1:1.1.4) | 1:1.2.3.3.dfsg-15
gconf2                  (>= 2.10.1-2) | 2.28.0-1
bluez                       (>= 4.36) | 4.42-2
obexd-client                          | 0.14-1


Recommends         (Version) | Installed
============================-+-===========
gvfs-backends                | 1.4.1-1


Suggests             (Version) | Installed
==============================-+-===========
nautilus-sendto                | 1.1.5-1

Message #10 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <andrea.veri89@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: asac@ubuntu.com, 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Sat, 24 Oct 2009 12:47:07 +0200

On Sat, 24 Oct 2009 02:32:42 +0200
Fabian Greffrath <fabian@greffrath.com> wrote:


> The ubuntu package provides a udev rule in
> 61-gnome-bluetooth-rfkill.rules which deals with this issue. However,
> I really doubt that gnome-bluetooth is the right package to provide
> such a udev rule. Please cross-check with the udev maintainer.
> Anyway, please enable rfkill for users in a reasonable way. ;)

Hi, I'm in touch with the Ubuntu's maintainer, I'm CCing him here so we
can hear his rationale about having such a udev rule, so maybe we can
adopt it as well if it fits fine with our needs.

Andrea

Message #15 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Apelete Seketeli <apelete@seketeli.org>

To: Debian Bug Tracking System <552185@bugs.debian.org>

Subject: Re: read/write access to the /dev/rfkill device is required

Date: Sat, 24 Oct 2009 13:10:36 +0200

Package: gnome-bluetooth
Version: 2.28.3-1
Severity: important 

Hi,

I've tested the kernel 2.6.31 from experimental which introduce the new
/dev/rfkill device. The lack of read/write access to this device makes the user
unable to switch bluetooth on/off (depending on its initial state). Thus I'm
asking if it would be possible to bump the bug severity and provide a way for
users to enable rfkill as Fabian suggested.

Regards.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-bluetooth depends on:
ii  bluez                  4.56-2            Bluetooth tools and daemons
ii  gconf2                 2.28.0-1          GNOME configuration database syste
ii  libatk1.0-0            1.28.0-1          The ATK accessibility toolkit
ii  libc6                  2.10.1-1          GNU C Library: Shared libraries
ii  libcairo2              1.8.8-2           The Cairo 2D vector graphics libra
ii  libdbus-1-3            1.2.16-2          simple interprocess messaging syst
ii  libdbus-glib-1-2       0.82-2            simple interprocess messaging syst
ii  libfontconfig1         2.6.0-4           generic font configuration library
ii  libfreetype6           2.3.11-1          FreeType 2 font engine, shared lib
ii  libgconf2-4            2.28.0-1          GNOME configuration database syste
ii  libglib2.0-0           2.22.2-2          The GLib library of C routines
ii  libgnome-bluetooth7    2.28.3-1          GNOME Bluetooth tools - support li
ii  libgtk2.0-0            2.18.3-1          The GTK+ graphical user interface 
ii  libnotify1 [libnotify1 0.4.5-1           sends desktop notifications to a n
ii  libpango1.0-0          1.26.0-1          Layout and rendering of internatio
ii  libunique-1.0-0        1.1.2-2           Library for writing single instanc
ii  obexd-client           0.14-1            D-Bus OBEX client
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages gnome-bluetooth recommends:
ii  gvfs-backends                 1.4.1-1    userspace virtual filesystem - bac

Versions of packages gnome-bluetooth suggests:
ii  nautilus-sendto               2.28.0-1   integrates Evolution and Pidgin in

-- no debconf information

Message #20 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <andrea.veri89@gmail.com>

To: Apelete Seketeli <apelete@seketeli.org>

Cc: 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: read/write access to the /dev/rfkill device is required

Date: Sat, 24 Oct 2009 13:31:56 +0200

On Sat, 24 Oct 2009 13:10:36 +0200
Apelete Seketeli <apelete@seketeli.org> wrote:


> I've tested the kernel 2.6.31 from experimental which introduce the
> new /dev/rfkill device. The lack of read/write access to this device
> makes the user unable to switch bluetooth on/off (depending on its
> initial state). Thus I'm asking if it would be possible to bump the
> bug severity and provide a way for users to enable rfkill as Fabian
> suggested.


I had a talk with Alexander (gnome-bluetooth's maintainer for Ubuntu):

<asac> its kind of a temporary solution
<asac> thats why putting it in gnome-bluetooth is right
<asac> in the end it should be wrapped in bluez api
<asac> the rationale for adding it now is that otherwise nothing will
work ;)

So in the end it should be included into bluez API but for now I guess
I'll have to use Ubuntu's workaround. 

What do you guys think?

Message #25 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Apelete Seketeli <apelete@seketeli.org>

To: Andrea Veri <andrea.veri89@gmail.com>

Cc: 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: read/write access to the /dev/rfkill device is required

Date: Sat, 24 Oct 2009 14:12:29 +0200

On Sat, 2009-10-24 at 13:31 +0200, Andrea Veri wrote:
> I had a talk with Alexander (gnome-bluetooth's maintainer for Ubuntu):
> 
> <asac> its kind of a temporary solution
> <asac> thats why putting it in gnome-bluetooth is right
> <asac> in the end it should be wrapped in bluez api
> <asac> the rationale for adding it now is that otherwise nothing will
> work ;)

If nothing will work for the moment I think that set it then...

> So in the end it should be included into bluez API but for now I guess
> I'll have to use Ubuntu's workaround. 
> 
> What do you guys think?

Like I said providing a fix (albeit temporary) seems a better option to
me than no fix at all. Things will be better with the coming 2.6.31
kernel, but being unable to disable bluetooth is really bad for laptop
users.
If Fabian is fine with it too then you should go ahead with the Ubuntu's
workaround.

Cheers.
-- 
Apelete Seketeli <apelete@seketeli.org>

Message #30 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <andrea.veri89@gmail.com>

To: 552185@bugs.debian.org

Subject: applying Ubuntu's patch is not the best way for now

Date: Sat, 24 Oct 2009 16:11:11 +0200

hi,

I had a talk with Filippo about this and he suggested to not include
this patch cause it's not the best way to fix this issue.

We should try to fix this in bluetoothd (bluez) itself.

If you have any idea, please let me know.


Andrea

Message #35 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Alexander Sack <asac@ubuntu.com>

To: Andrea Veri <andrea.veri89@gmail.com>

Cc: Fabian Greffrath <fabian@greffrath.com>, asac@ubuntu.com, 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Mon, 26 Oct 2009 10:49:53 +0100

On Sat, Oct 24, 2009 at 12:47:07PM +0200, Andrea Veri wrote:
> On Sat, 24 Oct 2009 02:32:42 +0200
> Fabian Greffrath <fabian@greffrath.com> wrote:
> 
> 
> > The ubuntu package provides a udev rule in
> > 61-gnome-bluetooth-rfkill.rules which deals with this issue. However,
> > I really doubt that gnome-bluetooth is the right package to provide
> > such a udev rule. Please cross-check with the udev maintainer.
> > Anyway, please enable rfkill for users in a reasonable way. ;)
> 
> Hi, I'm in touch with the Ubuntu's maintainer, I'm CCing him here so we
> can hear his rationale about having such a udev rule, so maybe we can
> adopt it as well if it fits fine with our needs.

the udev rule is a temporary hack, which we added to gnome-bluetooth
to get things going. In the end it should be wrapped by bluez with
policykit and al ... and hence we didnt want to put that in udev or
some other package ...

 - Alexander

Message #40 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Alexander Sack <asac@ubuntu.com>

Cc: Andrea Veri <andrea.veri89@gmail.com>, 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Tue, 27 Oct 2009 09:19:54 +0100

Alexander Sack schrieb:
> the udev rule is a temporary hack, which we added to gnome-bluetooth
> to get things going. In the end it should be wrapped by bluez with
> policykit and al ... and hence we didnt want to put that in udev or
> some other package ...

So the udev rule shouldn't end up in the Debian package anyway.

Has this issue already been brought to the attention of the udev and 
bluez maintainers?

Cheers,
Fabian

Message #45 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <andrea.veri89@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: asac@debian.org, 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Tue, 27 Oct 2009 13:51:21 +0100

Il giorno Tue, 27 Oct 2009 09:19:54 +0100
Fabian Greffrath <fabian@greffrath.com> ha scritto:

> Has this issue already been brought to the attention of the udev and 
> bluez maintainers?

yes, I've mailed bluez upstream already.

you can find my mail at:

http://article.gmane.org/gmane.linux.bluez.kernel/3690

and follow-ups:

http://article.gmane.org/gmane.linux.bluez.kernel/3691
http://article.gmane.org/gmane.linux.bluez.kernel/3692

so again, no one found a better solution yet. 

bluez upstream is implementing a rfkilld for this, but who knows when
it will be ready. That's why Alexander told you this is just a
temporary workaround while we wait upstream to be ready.

Andrea

Message #50 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <andrea.veri89@gmail.com>

Cc: asac@debian.org, 552185@bugs.debian.org

Subject: Re: [Pkg-bluetooth-maintainers] Bug#552185: [gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Tue, 27 Oct 2009 14:11:30 +0100

Andrea Veri schrieb:
> yes, I've mailed bluez upstream already.

Great, thanks for taking care of this issue.

> bluez upstream is implementing a rfkilld for this, but who knows when
> it will be ready. That's why Alexander told you this is just a
> temporary workaround while we wait upstream to be ready.

Alright, fine.

Message #57 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <greffrath@leat.rub.de>

To: 552185@bugs.debian.org, control <control@bugs.debian.org>

Subject: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Mon, 07 Dec 2009 10:10:28 +0100

severity 552185 serious
thanks

Dear all,

since the last dist-upgrade the situation has worsened for me. I am 
not even able to enable bluetooth via gnome-bluetooth anymore. To be 
honest, I am not sure if maybe the bluez upgrade (4.42 -> 4.57) has 
caused this issue, but since bluetooth doesn't work at all, I am 
raising severity.

Something has to be done quickly, I don't consider the current 
bluetooth situation ready for release.

Cheers,
Fabian


-- 
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax:     +49 (0)234 / 32-14227
E-Mail:  greffrath@leat.ruhr-uni-bochum.de

Message #62 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <greffrath@leat.rub.de>

To: 552185@bugs.debian.org

Subject: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 09 Dec 2009 09:53:08 +0100

I have an update on this bug.

Yesterday I tried to manually grant write access to the rfkill device 
and activate Bluetooth via gnome-bluetooth:

$ sudo chmod 0777 /dev/rfkill
$ bluetooth-properties
** Message: adding killswitch idx 0 state 1
** Message: killswitch 0 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 0 type 2 op 2 soft 0 hard 0

Here the bluetooth-properties window pops up and presents me a big 
button that reads "Activate Bluetooth". I click this button and it 
grays out, though bluetooth is still disabled. The following appears 
on the console again:

** Message: killswitch 0 is 1
** Message: killswitches state 1

Looks like it's a regression in bluez and not gnome-bluetooth's fault. 
What do you think?

Fabian

-- 
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax:     +49 (0)234 / 32-14227
E-Mail:  greffrath@leat.ruhr-uni-bochum.de

Message #67 received at 552185@bugs.debian.org (full text, mbox, reply):

From: hungerburg <dub@lazy.shacknet.nu>

To: Debian Bug Tracking System <552185@bugs.debian.org>

Subject: Re: read/write access to the /dev/rfkill device is required

Date: Fri, 11 Dec 2009 14:39:08 +0100

Package: gnome-bluetooth
Version: 2.28.3-2
Severity: normal


Here bluetooth-properties behaves the same as Fabian describes
in the previous message.

Additional information:

- previously paired devices will work fine
- trying to pair a new device will fail "no agent" in syslog
- the gnome/dbus infrastructure does not see the local device

transcript of some console commands:

$
$ bluetooth-agent 1234
  Can't get default adapter
  No such adapter
$
$ bluetooth-agent --adapter hci0 1234
  Can't register agent
  Method "RegisterAgent" with signature "os"
    on interface "org.bluez.Adapter" doesn't exist
$
$ hcitool dev
Devices:
        hci0    00:10:60:XX:YY:ZZ
$
$ /usr/sbin/hciconfig --all hci0
  hci0:   Type: USB
          BD Address: 00:10:60:XX:YY:ZZ ACL MTU: 192:8 SCO MTU: 64:8
          UP RUNNING PSCAN ISCAN 
          RX bytes:935 acl:0 sco:0 events:23 errors:0
          TX bytes:89 acl:0 sco:0 commands:23 errors:0
          Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
          Link policy: 
          Link mode: SLAVE ACCEPT 
          Name: 'James-1711����'
          Class: 0x4a0000
          Service Classes: Networking, Capturing, Telephony
          Device Class: Miscellaneous,
          HCI Ver: 1.1 (0x1) HCI Rev: 0x460 LMP Ver: 1.1 (0x1) LMP Subver: 0x460
          Manufacturer: Cambridge Silicon Radio (10)
$


from the last output I think one can say, that the config in
/etc/bluetooth is ignored when starting bluetoothd, as the
host is not called "James", but "lazy", I also configured a
different Class there.

-- 
peter


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-1-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-bluetooth depends on:
ii  bluez                  4.57-1            Bluetooth tools and daemons
ii  gconf2                 2.28.0-1          GNOME configuration database syste
ii  libatk1.0-0            1.28.0-1          The ATK accessibility toolkit
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libcairo2              1.8.8-2           The Cairo 2D vector graphics libra
ii  libdbus-1-3            1.2.16-2          simple interprocess messaging syst
ii  libdbus-glib-1-2       0.82-2            simple interprocess messaging syst
ii  libfontconfig1         2.6.0-4           generic font configuration library
ii  libfreetype6           2.3.11-1          FreeType 2 font engine, shared lib
ii  libgconf2-4            2.28.0-1          GNOME configuration database syste
ii  libglib2.0-0           2.22.3-1          The GLib library of C routines
ii  libgnome-bluetooth7    2.28.3-2          GNOME Bluetooth tools - support li
ii  libgtk2.0-0            2.18.4-1          The GTK+ graphical user interface 
ii  libnotify1 [libnotify1 0.4.5-1           sends desktop notifications to a n
ii  libpango1.0-0          1.26.1-1          Layout and rendering of internatio
ii  libunique-1.0-0        1.1.6-1           Library for writing single instanc
ii  obexd-client           0.14-1            D-Bus OBEX client
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages gnome-bluetooth recommends:
ii  gvfs-backends                 1.4.1-6    userspace virtual filesystem - bac

Versions of packages gnome-bluetooth suggests:
pn  nautilus-sendto               <none>     (no description available)

-- no debconf information

Message #72 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <andrea.veri89@gmail.com>

To: Fabian Greffrath <greffrath@leat.rub.de>, 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Sat, 19 Dec 2009 00:43:12 +0100

[Message part 1 (text/plain, inline)]

On Wed, 09 Dec 2009, Fabian Greffrath wrote:

> Looks like it's a regression in bluez and not gnome-bluetooth's
> fault. What do you think?

Well, the real problem here is that bluez lacks its own rfkill, so users
are stuck when trying to enable / disable their bluetooth interfaces.

While we could patch gnome-bluetooth to provide this kind of access, I am
still trying to find out what's the best way to workaround this since the Ubuntu
way has been rejected upstream. (I guess you know that giving rfkill access by default
to normal users is not the best to do at the moment)

Looking at the informations you just provide, the issue seems to be in bluez itself,
I think that you should forward the results of your tests directly upstream so we can
start having an idea of what's going on.

Upstream's Mailing Lists details can be found at this page:

http://www.bluez.org/development/lists/

please report back here if you have any update, so let's keep this bug as the main thread for 
this discussion.

Thanks in advance,

Andrea

[signature.asc (application/pgp-signature, inline)]

Message #79 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Witold Baryluk <baryluk@smp.if.uj.edu.pl>

To: Debian Bug Tracking System <552185@bugs.debian.org>

Subject: Re: How about proper group

Date: Tue, 22 Dec 2009 02:51:14 +0100

Package: gnome-bluetooth
Version: 2.28.3-2
Severity: normal

Maybe change /dev/rfkill's group to netdev or plugdev?
AFAIK most users are in plugdev group. Adding them
to netdev is also possible. Eventually this should 
be somehow processes indirectly via i.e. NetworkManager?

After changing it by:
chown :plugdev /dev/rfkill
chmod g+w /dev/rfkill

it (gnome-bluetooth applet, etc.) started working for me
and all functions works (Thinkpad T43 with buildin Broadcom
chip over USB).



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.33-rc1-sredniczarny-00096-gdd59f6c (PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-bluetooth depends on:
ii  bluez                  4.57-1            Bluetooth tools and daemons
ii  gconf2                 2.28.0-1          GNOME configuration database syste
ii  libatk1.0-0            1.28.0-1          The ATK accessibility toolkit
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libcairo2              1.8.8-2           The Cairo 2D vector graphics libra
ii  libdbus-1-3            1.2.16-2          simple interprocess messaging syst
ii  libdbus-glib-1-2       0.82-2            simple interprocess messaging syst
ii  libfontconfig1         2.6.0-4           generic font configuration library
ii  libfreetype6           2.3.11-1          FreeType 2 font engine, shared lib
ii  libgconf2-4            2.28.0-1          GNOME configuration database syste
ii  libglib2.0-0           2.22.3-1          The GLib library of C routines
ii  libgnome-bluetooth7    2.28.3-2          GNOME Bluetooth tools - support li
ii  libgtk2.0-0            2.18.5-1          The GTK+ graphical user interface 
ii  libnotify1 [libnotify1 0.4.5-1           sends desktop notifications to a n
ii  libpango1.0-0          1.26.1-1          Layout and rendering of internatio
ii  libunique-1.0-0        1.1.6-1           Library for writing single instanc
ii  obexd-client           0.14-1            D-Bus OBEX client
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages gnome-bluetooth recommends:
ii  gvfs-backends                 1.4.1-6    userspace virtual filesystem - bac

Versions of packages gnome-bluetooth suggests:
ii  nautilus-sendto               2.28.2-1   integrates Evolution and Pidgin in

-- no debconf information

Message #84 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <andrea.veri89@gmail.com>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 23 Dec 2009 22:21:25 +0100

Am Samstag, den 19.12.2009, 00:43 +0100 schrieb Andrea Veri:
> Looking at the informations you just provide, the issue seems to be in bluez itself,
> I think that you should forward the results of your tests directly upstream so we can
> start having an idea of what's going on.

Update: Today I tried with bluez 4.42-2~bpo50+1 (the version which
worked before) from backports and exact the same happened. So maybe it's
not a regression in bluez, but indeed in gnome-bluetooth. However, from
the changelog I cannot see any significant change between 2.28.3-1 and
2.28.3-2. Or maybe even my Bluetooth-stick is broken... :/

Cheers,
Fabian

Message #89 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <andrea.veri89@gmail.com>

Cc: Fabian Greffrath <greffrath@leat.rub.de>, 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Tue, 05 Jan 2010 17:24:36 +0100

Update: I tried at home with all different combinations of bluez
packages (the current ones from Debian unstable and the ones from the
Debian backports) and gnome-bluetooth (also the current ones from Debian
unstable and the current ones from Ubuntu) - both with /dev/rfkill
permissions manually set to 777 and left untouched - and *nothing*
works.

At work I also tried with an untouched Debian unstable system and it
didn't work. If your bluetooth works for you, then I must strongly
believe that my USB-bluetooth hardware is the culprit. :/

Cheers,
Fabian

Message #94 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <and@debian.org>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 6 Jan 2010 00:20:44 +0100

[Message part 1 (text/plain, inline)]

2010/1/5 Fabian Greffrath <fabian@greffrath.com>

> Update: I tried at home with all different combinations of bluez
> packages (the current ones from Debian unstable and the ones from the
> Debian backports) and gnome-bluetooth (also the current ones from Debian
> unstable and the current ones from Ubuntu) - both with /dev/rfkill
> permissions manually set to 777 and left untouched - and *nothing*
> works.
>


I don't think this issue is bluez-related, since it appeared for the very
first time when we upgraded to gnome-bluetooth's 2.28.x series.

I gave a look at gnome-bluetooth's git logs and I found out some interesting
pieces of code you might want to have a look at:

http://git.gnome.org/browse/gnome-bluetooth/commit/?id=822c0ba3d02183cbac571dcc01f1b234d355c851
and
http://git.gnome.org/browse/gnome-bluetooth/commit/?id=3d2fb9c86dabc35193228948bcb0e6813412f9d5

this means that every g-bluetooth's release *after* the 2.27.9 one will have
this issue, so downgrading to a release which is before that one would fix
this issue.

Did you try the Ubuntu package with bad results as well? they added the udev
rule that should fix this rfkill issue, so it looks to me a bit strange that
nothing works even with it.

[Message part 2 (text/html, inline)]

Message #99 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <and@debian.org>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 06 Jan 2010 09:46:58 +0100

Am Mittwoch, den 06.01.2010, 00:20 +0100 schrieb Andrea Veri:
> this means that every g-bluetooth's release *after* the 2.27.9 one
> will have this issue, so downgrading to a release which is before that
> one would fix this issue.

I would love to try with a 2.27.x Debian package, but couldn't find one
in the usual places. :(

> Did you try the Ubuntu package with bad results as well? they added
> the udev rule that should fix this rfkill issue, so it looks to me a
> bit strange that nothing works even with it.

Yes, I even tried with the gnome-bluetooth_2.28.1-0ubuntu2 packages from
ubuntu and it didn't work (well, at least the system tray icon is back,
but everything else still seems broken, e.g. the spinner in the "Device
Search" window of bluetooth-wizard isn't moving).

BTW, I have the following in dmesg when I plug in my dongle:

  btusb_intr_complete: hci0 urb f6785880 failed to resubmit (19)
  btusb_bulk_complete: hci0 urb f6785a00 failed to resubmit (19)
  btusb_bulk_complete: hci0 urb f6785000 failed to resubmit (19)
  btusb_send_frame: hci0 urb f4327680 submission failed

Does it maybe mean it's broken?

Cheers,
Fabian

Message #104 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: Witold Baryluk <baryluk@smp.if.uj.edu.pl>, 552185@bugs.debian.org

Subject: Re: Bug#552185: How about proper group

Date: Wed, 06 Jan 2010 09:48:22 +0100

block 552185 by 563902
thanks

Le mardi 22 décembre 2009 à 02:51 +0100, Witold Baryluk a écrit :
> Maybe change /dev/rfkill's group to netdev or plugdev?
> AFAIK most users are in plugdev group. Adding them
> to netdev is also possible. Eventually this should 
> be somehow processes indirectly via i.e. NetworkManager?

The clean solution is to let udev call ConsoleKit to set ACLs
for /dev/rfkill.

When this is done, we’ll just need to add dependencies on consolekit and
udev (>= fixed version).

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

Message #111 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <and@debian.org>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 6 Jan 2010 12:41:50 +0100

[Message part 1 (text/plain, inline)]

2010/1/6 Fabian Greffrath <fabian@greffrath.com>

> Am Mittwoch, den 06.01.2010, 00:20 +0100 schrieb Andrea Veri:
> > this means that every g-bluetooth's release *after* the 2.27.9 one
> > will have this issue, so downgrading to a release which is before that
> > one would fix this issue.
>
> I would love to try with a 2.27.x Debian package, but couldn't find one
> in the usual places. :(



gonna try to build a copy for you somewhen :)



> > Did you try the Ubuntu package with bad results as well? they added
> > the udev rule that should fix this rfkill issue, so it looks to me a
> > bit strange that nothing works even with it.
>
> Yes, I even tried with the gnome-bluetooth_2.28.1-0ubuntu2 packages from
> ubuntu and it didn't work (well, at least the system tray icon is back,
> but everything else still seems broken, e.g. the spinner in the "Device
> Search" window of bluetooth-wizard isn't moving).
>
> BTW, I have the following in dmesg when I plug in my dongle:
>
>  btusb_intr_complete: hci0 urb f6785880 failed to resubmit (19)
>  btusb_bulk_complete: hci0 urb f6785a00 failed to resubmit (19)
>  btusb_bulk_complete: hci0 urb f6785000 failed to resubmit (19)
>  btusb_send_frame: hci0 urb f4327680 submission failed
>
> Does it maybe mean it's broken?


looks to me like a kernel issue with the new btusb kernel module, I found
out a bug report in Launchpad as well:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502

I tried it myself and I get the same errors when I plug in my dongle, so
it's definitely not your hardware broken.
It could also be an issue with bluez itself, but bluez is actually
unmaintained in Debian, so I really don't know who could take care of this
issue.

Anyway we gonna try to include the rfkill switch directly into udev,
hopefully this issue will be finally fixed. (or at least the users affected
will reduce)

[Message part 2 (text/html, inline)]

Message #116 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <and@debian.org>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 06 Jan 2010 13:42:19 +0100

Am Mittwoch, den 06.01.2010, 12:41 +0100 schrieb Andrea Veri: 
> gonna try to build a copy for you somewhen :)

This would be highly appreciated! ;)

> looks to me like a kernel issue with the new btusb kernel module, I
> found out a bug report in Launchpad as well:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502

Alright, but the bug report claims this issue has been fixed in Linux
2.6.29~rc3 and I am using 2.6.32-3. It doesn't work with 2.6.30-8 from
testing either, but this kernel is out of question anyway,
because /dev/rfkill has just been added in 2.6.31.

[If I could just find a package for a 2.6.31 kernel. It's high time for
a working Debian package archive like snapshot.d.n once was!]

> I tried it myself and I get the same errors when I plug in my dongle,
> so it's definitely not your hardware broken.
> It could also be an issue with bluez itself, but bluez is actually
> unmaintained in Debian, so I really don't know who could take care of
> this issue.

Maybe it's a regression in Bluez, but I doubt, since downgrading to
4.42-2~bpo50+1 didn't help either.

> Anyway we gonna try to include the rfkill switch directly into udev,
> hopefully this issue will be finally fixed. (or at least the users
> affected will reduce) 

Yes, hopefully. :)

Message #121 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Andrea Veri <and@debian.org>

Cc: 552185@bugs.debian.org

Subject: Re: Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Date: Wed, 06 Jan 2010 15:00:07 +0100

> Alright, but the bug report claims this issue has been fixed in Linux
> 2.6.29~rc3 and I am using 2.6.32-3. It doesn't work with 2.6.30-8 from
> testing either, but this kernel is out of question anyway,
> because /dev/rfkill has just been added in 2.6.31.

Update: I just tried with the linux-image 2.6.31-16.53 package from
Ubuntu and it doesn't work either. :(

Message #126 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: Marco d'Itri <md@Linux.IT>

Cc: 563902@bugs.debian.org, 552185@bugs.debian.org

Subject: Re: Bug#563902: udev: Please set ACL_MANAGE for /dev/rfkill

Date: Thu, 07 Jan 2010 09:21:14 +0100

Le mercredi 06 janvier 2010 à 23:41 +0100, Marco d'Itri a écrit :
> Looks like this is not an acceptable solution.
> Unless there are other users which need an user-accessible /dev/rfkill
> then gnome-bluetooth should deal with this by shipping its own rules
> file (if at all!).

OK, we’ll have to do that until there is some appropriate framework to
access the kill switch then.

Would the following do the trick the correct way?

        ENV{ACL_MANAGE}=="0", GOTO="gnome_bluetooth_end"
        ACTION!="add|change", GOTO="gnome_bluetooth_end"
        KERNEL=="rfkill", ENV{ACL_MANAGE}="1"
        LABEL="gnome_bluetooth_end"

Thanks,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

Message #131 received at 552185-close@bugs.debian.org (full text, mbox, reply):

From: Josselin Mouette <joss@debian.org>

To: 552185-close@bugs.debian.org

Subject: Bug#552185: fixed in gnome-bluetooth 2.28.3-3

Date: Sat, 09 Jan 2010 15:40:29 +0000

Source: gnome-bluetooth
Source-Version: 2.28.3-3

We believe that the bug you reported is fixed in the latest version of
gnome-bluetooth, which is due to be installed in the Debian FTP archive:

gnome-bluetooth_2.28.3-3.diff.gz
  to main/g/gnome-bluetooth/gnome-bluetooth_2.28.3-3.diff.gz
gnome-bluetooth_2.28.3-3.dsc
  to main/g/gnome-bluetooth/gnome-bluetooth_2.28.3-3.dsc
gnome-bluetooth_2.28.3-3_amd64.deb
  to main/g/gnome-bluetooth/gnome-bluetooth_2.28.3-3_amd64.deb
libgnome-bluetooth-dev_2.28.3-3_amd64.deb
  to main/g/gnome-bluetooth/libgnome-bluetooth-dev_2.28.3-3_amd64.deb
libgnome-bluetooth7_2.28.3-3_amd64.deb
  to main/g/gnome-bluetooth/libgnome-bluetooth7_2.28.3-3_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 552185@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <joss@debian.org> (supplier of updated gnome-bluetooth package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 09 Jan 2010 14:13:47 +0100
Source: gnome-bluetooth
Binary: gnome-bluetooth libgnome-bluetooth7 libgnome-bluetooth-dev
Architecture: source amd64
Version: 2.28.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Josselin Mouette <joss@debian.org>
Description: 
 gnome-bluetooth - GNOME Bluetooth tools
 libgnome-bluetooth-dev - GNOME Bluetooth tools - support library development files
 libgnome-bluetooth7 - GNOME Bluetooth tools - support library
Closes: 552185 558377
Changes: 
 gnome-bluetooth (2.28.3-3) unstable; urgency=low
 .
   [ Josselin Mouette ]
   * Recommend obexd-server. Closes: #558377.
 .
   [ Andrea Veri ]
   * debian/control:
     - added a suggests on gnome-user-share, its bluetooth
       support should be working fine now.
 .
   [ Josselin Mouette ]
   * 61-gnome-bluetooth-rfkill.rules: new file. Set ACLs for console
     users on /dev/rfkill. Closes: #552185.
   * Install it in the udev directory.
   * Require udev 146 and consolekit for it to work properly.
   * Pass --disable-icon-update.
Checksums-Sha1: 
 22a68f9944372e6a930a16c7ecbe3e9add313d52 1643 gnome-bluetooth_2.28.3-3.dsc
 fa7f98be8aa1e18510efb76d6364bb7fe2d590bf 5966 gnome-bluetooth_2.28.3-3.diff.gz
 3cecf0c386bc45e010195b0ad847b3cf43d87547 623020 gnome-bluetooth_2.28.3-3_amd64.deb
 7100f6680d126dd915fc4b91c48b97d76cfcde3e 114872 libgnome-bluetooth7_2.28.3-3_amd64.deb
 8e2e5b9a8fe0af7a97ebce4c899946e668fb4023 103638 libgnome-bluetooth-dev_2.28.3-3_amd64.deb
Checksums-Sha256: 
 33a2e5f7a1217582a1ff80c15e01fe412df2169283579376f0704ac714e41b2a 1643 gnome-bluetooth_2.28.3-3.dsc
 d4b0301cea130cfacd642c1887091aa86d98db59f3c41f5c0c46fa319d067108 5966 gnome-bluetooth_2.28.3-3.diff.gz
 8af662959d09486ed67e11ee9dab64105aff171be018912b6eeba891032754dc 623020 gnome-bluetooth_2.28.3-3_amd64.deb
 84ada12d8c9d7a04c1c86fb397a5d039420bfdcda10b11a21bc654a4eb1df0d0 114872 libgnome-bluetooth7_2.28.3-3_amd64.deb
 941575bb54e2fc62ddddff61678a95df222a818be438a4ab8a30de164aeea6ec 103638 libgnome-bluetooth-dev_2.28.3-3_amd64.deb
Files: 
 bc109511db2587a3f4da28a864255cd2 1643 gnome optional gnome-bluetooth_2.28.3-3.dsc
 8ec0f29d1340b292ef30479a292aaa29 5966 gnome optional gnome-bluetooth_2.28.3-3.diff.gz
 3ed6645fb11b423f1a647e38a1d1fa43 623020 gnome optional gnome-bluetooth_2.28.3-3_amd64.deb
 088d5f7e1376d4ff03c1a138c52a36da 114872 libs optional libgnome-bluetooth7_2.28.3-3_amd64.deb
 d7825fb0245f3cecaafe3e16b32b5e85 103638 libdevel extra libgnome-bluetooth-dev_2.28.3-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLSIs3rSla4ddfhTMRApVBAJwLHPsB4jbBDngM253AYu30GixWJQCglO3n
g9/PqiPIDyq2zNpkTZ5iK0w=
=9ig2
-----END PGP SIGNATURE-----

Message #141 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Anton <anton.b1978@gmail.com>

To: 552185@bugs.debian.org

Subject: bluetooth is disabled

Date: Sun, 10 Jan 2010 18:34:05 +0200

after installing gnome-bluetooth 2.28.3-3
the problem still remain and bluetooth is disabled

Message #146 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Apelete Seketeli <apelete@seketeli.org>

To: Debian Bug Tracking System <552185@bugs.debian.org>

Subject: gnome-bluetooth: Problem partially solved

Date: Sun, 10 Jan 2010 21:43:40 +0100

Package: gnome-bluetooth
Version: 2.28.3-3
Severity: normal

Hi,

Just did the update and I can now disable and enable bluetooth through the
applet in the panel :).
Using the Fn+F5 shortcut still doesn't work for the moment.

Cheers.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-bluetooth depends on:
ii  bluez                   4.57-1           Bluetooth tools and daemons
ii  consolekit              0.4.1-2          framework for defining and trackin
ii  gconf2                  2.28.0-1         GNOME configuration database syste
ii  libatk1.0-0             1.28.0-1         The ATK accessibility toolkit
ii  libc6                   2.10.2-5         Embedded GNU C Library: Shared lib
ii  libcairo2               1.8.8-2          The Cairo 2D vector graphics libra
ii  libdbus-1-3             1.2.16-2         simple interprocess messaging syst
ii  libdbus-glib-1-2        0.82-2           simple interprocess messaging syst
ii  libfontconfig1          2.8.0-2          generic font configuration library
ii  libfreetype6            2.3.11-1         FreeType 2 font engine, shared lib
ii  libgconf2-4             2.28.0-1         GNOME configuration database syste
ii  libglib2.0-0            2.22.3-2         The GLib library of C routines
ii  libgnome-bluetooth7     2.28.3-3         GNOME Bluetooth tools - support li
ii  libgtk2.0-0             2.18.5-1         The GTK+ graphical user interface 
ii  libnotify1 [libnotify1- 0.4.5-1          sends desktop notifications to a n
ii  libpango1.0-0           1.26.2-1         Layout and rendering of internatio
ii  libunique-1.0-0         1.1.6-1          Library for writing single instanc
ii  obexd-client            0.14-1           D-Bus OBEX client
ii  udev                    150-2            /dev/ and hotplug management daemo
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages gnome-bluetooth recommends:
ii  gvfs-backends                 1.4.3-1    userspace virtual filesystem - bac
ii  obexd-server                  0.14-1     D-Bus OBEX server

Versions of packages gnome-bluetooth suggests:
pn  gnome-user-share              <none>     (no description available)
ii  nautilus-sendto               2.28.2-1   integrates Evolution and Pidgin in

-- no debconf information

Message #151 received at 552185@bugs.debian.org (full text, mbox, reply):

From: Andrea Veri <and@debian.org>

To: anton.b1978@gmail.com, 552185@bugs.debian.org

Subject: Re: Bug#552185: bluetooth is disabled

Date: Mon, 11 Jan 2010 00:20:54 +0100

[Message part 1 (text/plain, inline)]

On Sun, 10 Jan 2010, Anton wrote:

> after installing gnome-bluetooth 2.28.3-3
> the problem still remain and bluetooth is disabled

you probably didnt reboot your machine right after upgrading the 
package to latest revision.

I did the update today and I am now able to enable / disable my 
bluetooth interface with no problems.

Next step is to send the newer g-bluetooth release (2.29.x series) to 
experimental to test it out a bit.

Andrea

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.