blueman as default bluetooth client in Gnome

ajmctaggart ajmctaggart at
Mon Aug 10 21:11:41 BST 2009

Thank you all for such helpful input!

I will contact the blueman maintainer via Launchpad, and let he or she know
that some issues would need to be addressed.  Namely:

1)  Dependencies
2)  Buggy on certain setups

Let's say I am able to work with blueman in Launchpad to fix some of these
issues (dependencies issue may have already been fixed).  Is there still a
good chance that gnome-bluetooth would just remain the default because it's
easiest to keep things the same and not mess with Gnome's defaults too much?

I am looking to find the Karmic bug testing done for blueman, so that I may
be able to help the blueman group resolve these in some way; would any of
you be able to point me in the right direction?


On Mon, Aug 10, 2009 at 11:24 AM, Jacob Peddicord <jacob at>wrote:

> On Mon, Aug 10, 2009 at 1:50 PM, Alexander Sack<asac at> wrote:
> > Yes, that's one of the reasons. But thats not it alone. Our testing
> > during karmic sprint showed that its still quite buggy for some use
> > cases and upstream was not as responsive in the past weeks as I would
> > have hoped.
> On a related note, I noticed GNOME had accepted gnome-bluetooth as a
> module[1]. Will we see that change here, or will we still be using
> bluez-gnome? I've tried them both and from a user's point of view,
> they are nearly identical.
> [1]
> --
> Jacob Peddicord
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the ubuntu-devel mailing list