From: Felix Homann <fexpop@onlinehome.de>
To: bluez-users@lists.sourceforge.net
Date: Fri, 28 Jul 2006 12:46:11 +0200
References: <200607271240.49400.fexpop@onlinehome.de>
	<200607281214.55877.fexpop@onlinehome.de>
	<1154082789.2298.29.camel@localhost>
In-Reply-To: <1154082789.2298.29.camel@localhost>
MIME-Version: 1.0
Message-Id: <200607281246.11998.fexpop@onlinehome.de>
Subject: Re: [Bluez-users] Several problems with bluez-utils 3.1,
	kbluetoothd and a Belkin dongle in Debian
Reply-To: BlueZ users <bluez-users@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-users-bounces@lists.sourceforge.net
Errors-To: bluez-users-bounces@lists.sourceforge.net

Hi Marcel,

On Friday 28 July 2006 12:33, Marcel Holtmann wrote:
> > I think I'll go back to bluez-utils
> > 2.25-1 then until I can control the visibility somehow.
>
> you can use dbus-send, but that is a little bit more complicated.
>

Thanks :-)

but with 2.25 I know (partially) what I'm doing and where. My system does just 
what I want it to. Right now, I can't see any advantage from my user's point 
of view in using the new version due to the lack of documentation and 
control. Even if I can manage to get it done via dbus-send somehow , it's 
simpler just to downgrade the package.


Kind regards,

Felix

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users