Mailinglist Archive: opensuse (1420 mails)

< Previous Next >
Re: [opensuse] I don't know how to make bluetooth work in 13.1 XFCE
  • From: C <smaug42@xxxxxxxxxxxx>
  • Date: Sat, 11 Jan 2014 13:13:07 +0100
  • Message-id: <CAOVv=gNvtW=oRcPLGhhk3WAAYHB1N1UVthgMdhhFhj8bytvk0g@mail.gmail.com>
On Sat, Jan 11, 2014 at 12:57 PM, Carlos E. R. <carlos.e.r@xxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2014-01-11 04:24, Carlos E. R. wrote:

One rumour I heard was that the gnome people had modified things so
that others, like the xfce people, would not be able to use them.
Maybe that is why bluetooth no longer works on xfce.

:-?


It seems there is truth in that. The XFCE functionality in XFCE has
been removed.

The bugzilla I started says:

+++·····················
- --- Comment #1 from Guido Berhörster <> 2014-01-11 09:38:51 UTC ---

There is nothing in Xfce that handles Bluetooth devices (and there
never has been). Older releases (until 12.1 IIRC) included
gnome-bluetooth in the Xfce pattern but that was removed since it grew
a dependency on gnome-control-center which in turn drags in almost all
of GNOME.
·····················++-


Dmam it. :-/


There was also some rather.. impolite words exchanged about this
between the Gnome developers responsible for the change and the rest
of the community that wanted to re-use the Gnome components. The
distilled form is... the Gnome guys were accused of trying to create
lock-in/lock-out, and the Gnome guys said "yah, and?"

It's unfortunate... messy and... hard to fix.

My current workaround on the one device (x86 tablet) I have that needs
working Bluetooth is to install Gnome and the DE I really want to use.
Log into Gnome, pair the Bluetooth, log out, log into my preferred DE
(KDE4 is so much more friendly on touch-tablet devices) and the
pairing sticks until I reboot, or the tablet goes into
standby/hibernation.

C.
--
openSUSE 13.1 x86_64, KDE 4.11
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups