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? Thanks, Anthony <div class="gmail_quote">On Mon, Aug 10, 2009 at 11:24 AM, Jacob Peddicord <<a href="mailto:jacob@peddicord.net">jacob@peddicord.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Mon, Aug 10, 2009 at 1:50 PM, Alexander Sack<<a href="mailto:asac@ubuntu.com">asac@ubuntu.com</a>> 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. </div>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] <a href="http://live.gnome.org/TwoPointTwentyseven/Desktop" target="_blank">http://live.gnome.org/TwoPointTwentyseven/Desktop</a> -- Jacob Peddicord <a href="http://jacob.peddicord.net/" target="_blank">http://jacob.peddicord.net/</a> </blockquote></div>