public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Homann <fexpop@onlinehome.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian
Date: Fri, 28 Jul 2006 12:46:11 +0200	[thread overview]
Message-ID: <200607281246.11998.fexpop@onlinehome.de> (raw)
In-Reply-To: <1154082789.2298.29.camel@localhost>

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

  reply	other threads:[~2006-07-28 10:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 10:40 [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Felix Homann
2006-07-27 10:43 ` Marcel Holtmann
2006-07-27 10:58   ` Felix Homann
2006-07-27 11:04     ` Marcel Holtmann
2006-07-29 12:26       ` Felix Homann
2006-07-29 12:42         ` Marcel Holtmann
2006-07-27 17:16     ` [Bluez-users] Several problems with bluez-utils 3.2, kbluetoothd Paulo Wollny
2006-07-27 20:08     ` [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Felix Homann
2006-07-28  1:20       ` Marcel Holtmann
2006-07-28  9:00         ` Felix Homann
2006-07-28  9:09           ` Marcel Holtmann
2006-07-28  9:28             ` Felix Homann
2006-07-28  9:38               ` Marcel Holtmann
2006-07-28 10:03                 ` Felix Homann
2006-07-28 10:06                   ` Marcel Holtmann
2006-07-28 10:14                     ` Felix Homann
2006-07-28 10:33                       ` Marcel Holtmann
2006-07-28 10:46                         ` Felix Homann [this message]
2006-07-28 10:51                           ` Marcel Holtmann
2006-07-28 10:40                     ` hugues
2006-07-28 11:07                       ` Felix Homann
2006-07-28 15:00                     ` Felix Homann
2006-07-28 15:07                       ` Marcel Holtmann
2006-07-29 12:11                         ` Felix Homann
2006-07-29 12:33                           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 23:18 Alastair Tse
2006-07-28  1:32 ` Marcel Holtmann
2006-07-28  9:43   ` Alastair Tse
2006-07-29 12:58     ` Marcel Holtmann

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=200607281246.11998.fexpop@onlinehome.de \
    --to=fexpop@onlinehome.de \
    --cc=bluez-users@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox