All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Rick Jones <rick@activeservice.co.uk>
Cc: Dan Williams <dcbw@redhat.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>,
	networkmanager-list@gnome.org
Subject: Re: So very close, but so frustrating...
Date: Fri, 02 Oct 2009 09:39:21 +0100	[thread overview]
Message-ID: <1254472761.22191.879.camel@localhost.localdomain> (raw)
In-Reply-To: <CB7A3691FBC7EB0E857B7330@mineee>

On Fri, 2009-10-02 at 01:55 +0100, Rick Jones wrote:
> I've just installed blueman, to replace bluez-gnome, and it does this
> perfectly.
> 
> It's a much better UI-oriented manager for BT devices altogether, it
> shows my phone, I click on "attach serial service", and it exposes the
> BT modem in DBus. NM 0.7 sees it just like a USB modem and it connects
> first time. Magic!
> 
> I'm too hardened to be often impressed first-time with a piece of
> software, but this was spot-on (does audio, obex, etc just as neatly).
> OK, it takes a couple of extra clicks to connect the phone, which I
> guess a built-in NM implementation could do automatically, but that's
> pretty minor.

Except that blueman does this the way that causes Dan to receive bug
reports.


  reply	other threads:[~2009-10-02  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AC3EFD9.1020602@shic.co.uk>
     [not found] ` <7cd7fc040909301718r3e441c53x767084b0b01f4a7c@mail.gmail.com>
     [not found]   ` <1254433173.9657.155.camel@localhost.localdomain>
2009-10-01 23:19     ` So very close, but so frustrating Bastien Nocera
2009-10-02  0:55       ` Rick Jones
2009-10-02  8:39         ` Bastien Nocera [this message]
2009-10-03  1:44       ` Dan Williams
2009-10-03  8:08         ` Dan Williams
2009-10-05 10:55           ` Bastien Nocera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1254472761.22191.879.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=dcbw@redhat.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=networkmanager-list@gnome.org \
    --cc=rick@activeservice.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.