Affects all versions of gsb that don't use gnome-bluetooth package,
which would be gsb-current and 2.30. In order for network-manager and
blueman to work together in peaceful harmony the slackware stock
blueman package needs to be rebuilt to enable polkit and, at least in
my case, disable hal support. Pat disables polkit explicitly on his
blueman build, it's trivial to switch the flag to enable at the top of
the slackbuild script and rebuild. I have not had any side effects
with this setup personally, but ymmv.
darkwurm <atyrelyo...@gmail.com> wrote: > Affects all versions of gsb that don't use gnome-bluetooth package, > which would be gsb-current and 2.30. In order for network-manager and > blueman to work together in peaceful harmony the slackware stock > blueman package needs to be rebuilt to enable polkit and, at least in > my case, disable hal support. Pat disables polkit explicitly on his > blueman build, it's trivial to switch the flag to enable at the top of > the slackbuild script and rebuild. I have not had any side effects > with this setup personally, but ymmv.
While we're on the subject, the problem with gnome-bluetooth is that it needs obexd, but the server portion of obexd claims the same dbus interface as obex-data-server, which is required by blueman (and I think kde's bluetooth utils). Obviously that's a problem. I guess you could package only the obexd client, which would iirc let gnome-bluetooth work, but longer-term, it would be nice if blueman were ported to use obexd too.
Robby Workman <r...@rlworkman.net> wrote: > On Mon, 31 Jan 2011 11:07:45 -0800 (PST) > darkwurm <atyrelyo...@gmail.com> wrote:
> > Affects all versions of gsb that don't use gnome-bluetooth package, > > which would be gsb-current and 2.30. In order for network-manager > > and blueman to work together in peaceful harmony the slackware stock > > blueman package needs to be rebuilt to enable polkit and, at least > > in my case, disable hal support. Pat disables polkit explicitly on > > his blueman build, it's trivial to switch the flag to enable at the > > top of the slackbuild script and rebuild. I have not had any side > > effects with this setup personally, but ymmv.
> While we're on the subject, the problem with gnome-bluetooth is > that it needs obexd, but the server portion of obexd claims the > same dbus interface as obex-data-server, which is required by > blueman (and I think kde's bluetooth utils). Obviously that's > a problem. I guess you could package only the obexd client, > which would iirc let gnome-bluetooth work, but longer-term, it > would be nice if blueman were ported to use obexd too.
I run gnome-bluetooth with obexd-client only, keeping the stock slackware obex-data-server for the server side and for blueman, and it works fine.
gnome-bluetooth only uses obexd for the send-to functionality provided by obexd-client. obexd-client and obex-data-server provide different dbus interfaces so I have encountered no problem with this approach.
Chris Vine <ch...@cvine.freeserve.co.uk> wrote: > On Mon, 31 Jan 2011 18:24:59 -0600 > Robby Workman <r...@rlworkman.net> wrote: > > On Mon, 31 Jan 2011 11:07:45 -0800 (PST) > > darkwurm <atyrelyo...@gmail.com> wrote:
> > > Affects all versions of gsb that don't use gnome-bluetooth > > > package, which would be gsb-current and 2.30. In order for > > > network-manager and blueman to work together in peaceful harmony > > > the slackware stock blueman package needs to be rebuilt to enable > > > polkit and, at least in my case, disable hal support. Pat > > > disables polkit explicitly on his blueman build, it's trivial to > > > switch the flag to enable at the top of the slackbuild script and > > > rebuild. I have not had any side effects with this setup > > > personally, but ymmv.
> > While we're on the subject, the problem with gnome-bluetooth is > > that it needs obexd, but the server portion of obexd claims the > > same dbus interface as obex-data-server, which is required by > > blueman (and I think kde's bluetooth utils). Obviously that's > > a problem. I guess you could package only the obexd client, > > which would iirc let gnome-bluetooth work, but longer-term, it > > would be nice if blueman were ported to use obexd too.
> I run gnome-bluetooth with obexd-client only, keeping the stock > slackware obex-data-server for the server side and for blueman, and it > works fine.
> gnome-bluetooth only uses obexd for the send-to functionality provided > by obexd-client. obexd-client and obex-data-server provide different > dbus interfaces so I have encountered no problem with this approach.
> > gnome-bluetooth only uses obexd for the send-to functionality > > provided by obexd-client. obexd-client and obex-data-server > > provide different dbus interfaces so I have encountered no problem > > with this approach.
Chris Vine <ch...@cvine.freeserve.co.uk> wrote: > On Wed, 2 Feb 2011 20:43:49 -0600 > Robby Workman <r...@rlworkman.net> wrote: > [snip] > > > gnome-bluetooth only uses obexd for the send-to functionality > > > provided by obexd-client. obexd-client and obex-data-server > > > provide different dbus interfaces so I have encountered no problem > > > with this approach.
