Re: RFC - Downgrade BlueZ to v4.101 in Fedora 20

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2014-01-23 at 19:53 +0100, David Sommerseth wrote: 
> Hi all,

Hi,

> This might be a viewed as a fire torch, but there is, IMO, a major
> regression in BlueZ 5 which is shipped in Fedora 20.

I agree.  But everyone probably already knows that.

> It doesn't support
> HSP/HFP headset profiles, which enables the microphone on many bluetooth
> headsets.

Indeed -- which is a showstopper for anyone that uses a bluetooth
headset as their primary means of VOX communications.

> Anyhow, not supporting HSP/HSP profiles is at least hitting my work
> ability, and I doubt I'm alone in this situation.

No, you are definitely not alone.  I abandoned F20 because of it.

> Now, if I had known this before I started upgrading to F20, I wouldn't
> have upgraded yet but stayed on F19 a bit longer.

This is a perfect example of why I always (LVM) snapshot my existing
(F19 at the time) OS before I start an upgrade.  Rolling back is really
as simple as updating the /etc/fstab on the snapshot-/ and creating a
grub entry to boot from the snapshot-/.  I've had to roll back to F19 on
both my corporate laptop due to this particular issue and my personal
workstation due to other issues, so I am very grateful for my
cautiousness.

> So, I wonder if it can be considered to enable a "downgrade path" for
> bluez and depending packages, as described in the "Contingency Plan":
> <https://fedoraproject.org/wiki/Changes/Bluez5>

As I understand it's really not quite that simple.  The problem is that
the GNOME that's in F20 depends on Bluez5 and won't work with Bluez4 so
downgrading Bluez to 4 also means downgrading GNOME.  IIRC there was a
third dependency in all of that but I forget what it is.

> As a side note, it also needs to be discussed how such a key feature of
> the bluetooth stack could go unnoticed through QA, and how to avoid this
> from happening again.

Indeed.  I wondered the same myself.

Cheers,
b.



Attachment: signature.asc
Description: This is a digitally signed message part

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux