Debian Bug report logs - #779613
"no such file or directory" trying to connect through the blueman-applet

Display info messages

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

From: Antoine Beaupré <anarcat@koumbit.org>

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

Subject: "no such file or directory" trying to connect through the blueman-applet

Date: Mon, 02 Mar 2015 22:21:51 -0500

Package: blueman
Version: 1.99~alpha1-1
Severity: grave

Since I upgraded this laptop to jessie, I cannot use Blueman to connect
to the internet by tethering to my phone.

I think this is an upstream bug described here:

https://github.com/blueman-project/blueman/issues/161

In the GUI, I see "No such file or directory" in the status bar.

I am able to workaround the problem by using commandline tools to
connect to the phone, so I don't believe the phone or the BlueZ stack is
the problem. The workaround is to use rfcomm directly, in my case:

rfcomm -r -A -E -M connect rfcomm0 <bluetoothaddr>

where <bluetoothaddr> is a MAC-like address I see from the bluetoothctl
list output, once I figure out how to enable bluetooth (ironically,
through blueman-applet).

I insist on pointing out this is a regression from Wheezy and should
really be fixed before jessie is released, hence the "grave" severity
above. Bluetooth has little purpose on this laptop but this
functionality, and I suspect this is the case with a lot of people.

I am available for debugging this further as necessary, but I would
seriously consider downgrading back to the stable version (1.23) while
upstream works on 2.0, which seems to be more in an alpha state.
According to this bug report, this is a known problem:

https://github.com/blueman-project/blueman/issues/13

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages blueman depends on:
ii  bluez                                5.23-2+b1
ii  dbus                                 1.8.16-1
ii  dunst [notification-daemon]          1.1.0-1
ii  gir1.2-appindicator3-0.1             0.4.92-3.1
ii  gir1.2-gconf-2.0                     3.2.6-3
ii  gir1.2-gdkpixbuf-2.0                 2.31.1-2+b1
ii  gir1.2-glib-2.0                      1.42.0-2.2
ii  gir1.2-gtk-3.0                       3.14.5-1
ii  gir1.2-notify-0.7                    0.7.6-2
ii  gir1.2-pango-1.0                     1.36.8-3
ii  gnome-icon-theme                     3.12.0-1
ii  libatk1.0-0                          2.14.0-1
ii  libbluetooth3                        5.23-2+b1
ii  libc6                                2.19-15
ii  libcairo-gobject2                    1.14.0-2.1
ii  libcairo2                            1.14.0-2.1
ii  libgdk-pixbuf2.0-0                   2.31.1-2+b1
ii  libglib2.0-0                         2.42.1-1
ii  libgtk-3-0                           3.14.5-1
ii  libpango-1.0-0                       1.36.8-3
ii  libpangocairo-1.0-0                  1.36.8-3
ii  libpulse-mainloop-glib0              5.0-13
ii  libpython2.7                         2.7.8-11
ii  librsvg2-common                      2.40.5-1
ii  libstartup-notification0             0.12-4
ii  notification-daemon                  0.7.6-2
ii  obex-data-server                     0.4.5-1+b4
ii  python                               2.7.8-3
ii  python-dbus                          1.2.0-2+b3
ii  python-gi                            3.14.0-1
ii  python-gi-cairo                      3.14.0-1
ii  xfce4-notifyd [notification-daemon]  0.2.4-3

Versions of packages blueman recommends:
ii  policykit-1  0.105-8

blueman suggests no packages.

-- no debconf information

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

From: Christopher Schramm <debian@cschramm.eu>

To: Antoine Beaupré <anarcat@koumbit.org>, 779613@bugs.debian.org

Subject: Re: Bug#779613: "no such file or directory" trying to connect through the blueman-applet

Date: Tue, 03 Mar 2015 07:57:24 +0100

Hi Antoine,

unfortunately BlueZ 5's generic connect method is a misconception in my
eyes as in your case it will not connect the NAP service. In the current
upstream master you will not get a generic connect item in the menu
anymore, but see which services are provided and could be connected with
it. In case of Android phones there typically exists some audio service
that should be connectible, but fails with that error message. It may
just be that the device needs to be in a specific state (e.g. have a
media app running) to make the connection work.

Anyway, connecting to a NAP should work. You just have to select the
service from the device menu and not use the generic connect item for that.

> I insist on pointing out this is a regression from Wheezy and should
> really be fixed before jessie is released, hence the "grave" severity
> above.

That's not correct as...

> I would
> seriously consider downgrading back to the stable version (1.23) while
> upstream works on 2.0, which seems to be more in an alpha state.

This wouldn't bring us anywhere as 1.23 does not support BlueZ 5 at all.

Regards

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

From: Antoine Beaupré <anarcat@koumbit.org>

To: Christopher Schramm <debian@cschramm.eu>, 779613@bugs.debian.org

Subject: Re: Bug#779613: "no such file or directory" trying to connect through the blueman-applet

Date: Tue, 03 Mar 2015 10:20:03 -0500

On 2015-03-03 01:57:24, Christopher Schramm wrote:
> Hi Antoine,
>
> unfortunately BlueZ 5's generic connect method is a misconception in my
> eyes as in your case it will not connect the NAP service. In the current
> upstream master you will not get a generic connect item in the menu
> anymore, but see which services are provided and could be connected with
> it. In case of Android phones there typically exists some audio service
> that should be connectible, but fails with that error message. It may
> just be that the device needs to be in a specific state (e.g. have a
> media app running) to make the connection work.
>
> Anyway, connecting to a NAP should work. You just have to select the
> service from the device menu and not use the generic connect item for that.

There's no service from the menu, in fact, the "Serial server" menu item
is gone.

There's only a "connect" option which simply fails.

And this is not an android phone, this is a LG flip phone.

>> I insist on pointing out this is a regression from Wheezy and should
>> really be fixed before jessie is released, hence the "grave" severity
>> above.
>
> That's not correct as...
>
>> I would
>> seriously consider downgrading back to the stable version (1.23) while
>> upstream works on 2.0, which seems to be more in an alpha state.
>
> This wouldn't bring us anywhere as 1.23 does not support BlueZ 5 at all.

Understood. Upstream seems to be saying they fixed this peculiar
problem in git (although the milestone item says the contrary), maybe a
git snapshot should be tried in experimental?

A.

-- 
Be who you are and say what you feel
Because those who mind don't matter
And those who matter don't mind.
                         - Dr. Seuss

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

From: Christopher Schramm <debian@cschramm.eu>

To: Antoine Beaupré <anarcat@koumbit.org>, 779613@bugs.debian.org

Subject: Re: Bug#779613: "no such file or directory" trying to connect through the blueman-applet

Date: Wed, 04 Mar 2015 08:20:45 +0100

>> Anyway, connecting to a NAP should work. You just have to select the
>> service from the device menu and not use the generic connect item for that.
> 
> There's no service from the menu, in fact, the "Serial server" menu item
> is gone.

So you are talking about a serial service, not a NAP service. Support
for serial services with BlueZ 5 is not available in the alpha1
snapshot, but recently made it into current upstream master. I'm
actually planning to do an alpha2 snapshot release and package it for
unstable or experimental at the end of the week.

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

From: Antoine Beaupré <anarcat@koumbit.org>

To: Christopher Schramm <debian@cschramm.eu>, 779613@bugs.debian.org

Subject: Re: Bug#779613: "no such file or directory" trying to connect through the blueman-applet

Date: Wed, 04 Mar 2015 06:46:05 -0500

On 2015-03-04 02:20:45, Christopher Schramm wrote:
>>> Anyway, connecting to a NAP should work. You just have to select the
>>> service from the device menu and not use the generic connect item for that.
>> 
>> There's no service from the menu, in fact, the "Serial server" menu item
>> is gone.
>
> So you are talking about a serial service, not a NAP service.

Frankly, I have no idea. I am just seeing this failing to work now,
whereas it was working before.

> Support for serial services with BlueZ 5 is not available in the
> alpha1 snapshot, but recently made it into current upstream
> master. I'm actually planning to do an alpha2 snapshot release and
> package it for unstable or experimental at the end of the week.

Okay that's great, I'll try to test that when it's available!

It seems a little ... daring to ship Jessie with alpha releases
however...

A.
-- 
Hard times are coming when we will be wanting the voices of writers
who can see alternatives to how we live now and can see through our
fear-stricken society and its obsessive technologies to other ways of
being, and even imagine some real grounds for hope. We will need
writers who can remember freedom. Poets, visionaries—the realists of a
larger reality.         - Ursula Le Guin

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

From: Christopher Schramm <debian@cschramm.eu>

To: Antoine Beaupré <anarcat@koumbit.org>, 779613@bugs.debian.org

Subject: Re: Bug#779613: "no such file or directory" trying to connect through the blueman-applet

Date: Wed, 04 Mar 2015 12:48:32 +0100

> It seems a little ... daring to ship Jessie with alpha releases
> however...

Sure, but as blueman is not that important to block the migration to
BlueZ 5, the only alternative is to not ship blueman at all.

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

From: Christopher Schramm <debian@cschramm.eu>

To: 779613-close@bugs.debian.org

Subject: Bug#779613: fixed in blueman 1.99~alpha2-1

Date: Fri, 10 Apr 2015 18:03:37 +0000

Source: blueman
Source-Version: 1.99~alpha2-1

We believe that the bug you reported is fixed in the latest version of
blueman, which is due to be installed in the Debian FTP archive.

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 779613@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Schramm <debian@cschramm.eu> (supplier of updated blueman 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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 06 Mar 2015 10:12:00 +0200
Source: blueman
Binary: blueman
Architecture: source amd64
Version: 1.99~alpha2-1
Distribution: unstable
Urgency: low
Maintainer: Christopher Schramm <debian@cschramm.eu>
Changed-By: Christopher Schramm <debian@cschramm.eu>
Description:
 blueman    - Graphical bluetooth manager
Closes: 549274 652005 761284 761286 762526 762527 764635 779613
Changes:
 blueman (1.99~alpha2-1) unstable; urgency=low
 .
   * New upstream release (Closes: #779613, #764635, #762526, #762527, #549274,
                           #652005, #761284, #761286)
Checksums-Sha1:
 eb4f8a818a234eedaebfaef56789b43395d3c691 1941 blueman_1.99~alpha2-1.dsc
 bde5f2370d14bf887b93f68e1131af172485503f 1947536 blueman_1.99~alpha2.orig.tar.xz
 d00d852bd6081f70415dda66477f91e424e02350 4416 blueman_1.99~alpha2-1.debian.tar.xz
 35f80bd1f0628dec4dd4d23ef1d19b6c8da22aed 1715282 blueman_1.99~alpha2-1_amd64.deb
Checksums-Sha256:
 6d8374315b6a206c172c5f3bfe3ba89d2b8577baa80b480cb697343c15eafc6c 1941 blueman_1.99~alpha2-1.dsc
 2a95aef542809de91b5328fa1d71269dd3682b0a41bae7b4b423c36b97b9a91b 1947536 blueman_1.99~alpha2.orig.tar.xz
 37b0f2420742ed0d4d26dcfb8eb9dce82dec6b162b20a0898d0abe0721de3325 4416 blueman_1.99~alpha2-1.debian.tar.xz
 2fed8f916dbf7453ed77f64711a5ecf1b5788e466a026bd7cbbab24c605e94df 1715282 blueman_1.99~alpha2-1_amd64.deb
Files:
 18149c5574f7f86f43a611c264ff6615 1941 x11 optional blueman_1.99~alpha2-1.dsc
 ca3fd306dc9d0f3c31914351995f6d62 1947536 x11 optional blueman_1.99~alpha2.orig.tar.xz
 47c05bc37b727346265c2bc0c23cb2a2 4416 x11 optional blueman_1.99~alpha2-1.debian.tar.xz
 d0ac064c51ebb3a62817491694609a65 1715282 x11 optional blueman_1.99~alpha2-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVKBEBAAoJEDIkf7tArR+mvgsP/0sVvFzxTUs+LMecMN/0MAhQ
S03fiVhfP4cAEjTPqtIHiaAdHp+AfCaSs+6gw6z/toc8W6u5ka4KZqG+H6uOk7SA
lJaAxh78NfHha8UbYhaFX13c/jIz56ve8fXBVsMVcftSyODaSd+NBQemin5rNs2A
7vyoyoeBgK09hxB80wkP8MUd53chJ2Vl1Vc30QeKxnuDObBrUHvlkSBC1uQJMdPX
Jr9TGdcK//3y9kuV6btnn20Hu2grZmG6u6AN7eT87BGEX+8SNfuOdTLhbP8JARpW
FE2U5hPD3jL56f9ZAMfDR1qaMHNW2r/CQ8a5n8EO0e2hY6P8aJOemDfBi1pK0lUk
X2K+5XHzk0oAXRsKaOZ6j9s1j5cDel3ZT26aVuEwKZ4210rg4YBrpijXsQK5xj8g
0yeINBwng1oNfFAu6PkOJICI0JyMcKZrSu4SN5y+vnvKB51idWtRbV53C+duj3wh
/UR4p8X4I8hL8FO8s2cV/jmUUbviFSraQEHBtdscdtqWpG/He9UNJaByKoh60Xs2
13mFl7V5hpPqUCgBFZP042vqmo6lb8NrCLD1jDVZPIedZ7v6t4MX2pf3VSbPzHhY
JE6Jn27JRRMAg42qv5pnncbDNJopq9QeYzdcZMoGvWy1lwNweW7z7ZYS7xkvQtrK
c6sXR5WRlP2GpiGodS28
=2k1p
-----END PGP SIGNATURE-----

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

From: Antoine Beaupré <anarcat@debian.org>

To: 779613@bugs.debian.org

Subject: Re: Bug#779613 closed by Christopher Schramm <debian@cschramm.eu> (Bug#779613: fixed in blueman 1.99~alpha2-1)

Date: Thu, 23 Apr 2015 10:31:39 -0400

See now it's too bad that this wasn't marked as an RC bug because now
Jessie doesn't ship with this fix.

Isn't there a way the new alpha can be bumped into jessie now?

a.
-- 
Computer science is no more about computers
than astronomy is about telescopes
                        - E. Dijkstra

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

From: Christopher Schramm <debian@cschramm.eu>

To: Antoine Beaupré <anarcat@debian.org>, 779613@bugs.debian.org

Subject: Re: Bug#779613: closed by Christopher Schramm <debian@cschramm.eu> (Bug#779613: fixed in blueman 1.99~alpha2-1)

Date: Sun, 26 Apr 2015 18:30:30 +0200

> See now it's too bad that this wasn't marked as an RC bug because now
> Jessie doesn't ship with this fix.

I'm not sure what's your point here. If this would have been marked as
an RC bug, Jessie would not even ship blueman.

> Isn't there a way the new alpha can be bumped into jessie now?

Newer versions will be made available through jessie-backports, but I'm
not aware of any other way than that.

Send a report that this bug log contains spam.