On Thu, 2014-01-23 at 14:17 -0600, Dan Williams wrote: > On Thu, 2014-01-23 at 20:04 +0100, David Sommerseth wrote: > > On 23/01/14 19:58, Frank Murphy wrote: > > > On Thu, 23 Jan 2014 19:53:19 +0100 > > > David Sommerseth <davids@xxxxxxxxxx> wrote: > > > > > >> > > >> Hi all, > > >> > > >> 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. It doesn't > > >> support HSP/HFP headset profiles, which enables the microphone on > > >> many bluetooth headsets. It's already tracked in this BZ: > > >> > > >> > > > > > > is just downgrading bluez any help? > > > yum downgrade bluez* --releasever=19 > > > > Nope, several packages depends on the bluez-5.13-1 package. > > > > --------------------------- > > --> Finished Dependency Resolution > > Error: Package: pulseaudio-module-bluetooth-4.0-9.gitf81e3.fc20.x86_64 > > (@updates/20) > > Requires: bluez >= 5.0 > > Removing: bluez-5.13-1.fc20.x86_64 (@updates/20) > > bluez = 5.13-1.fc20 > > Downgraded By: bluez-4.101-9.fc19.x86_64 (updates) > > bluez = 4.101-9.fc19 > > Available: bluez-4.101-6.fc19.x86_64 (fedora) > > bluez = 4.101-6.fc19 > > Error: Package: 1:gnome-bluetooth-3.10.0-1.fc20.x86_64 (@anaconda/20) > > Requires: bluez >= 5.0 > > Removing: bluez-5.13-1.fc20.x86_64 (@updates/20) > > bluez = 5.13-1.fc20 > > Downgraded By: bluez-4.101-9.fc19.x86_64 (updates) > > bluez = 4.101-9.fc19 > > Available: bluez-4.101-6.fc19.x86_64 (fedora) > > bluez = 4.101-6.fc19 > > You could try using --skip-broken to work around the problem > > You could try running: rpm -Va --nofiles --nodigest > > ---------------------------- > > > > Might even be a worse conflict for other users, depending on installed > > packages. I believe there's no way around re-compiling NetworkManager, > > pulseaudio and other GNOME and KDE packages depending on bluez. > > NM only uses bluez via the D-Bus interface, so if you force install > bluez4, NM will still work and should even handle the change at runtime. > And then you'll get DUN back too :) Clarification: I actually don't mean runtime. NM must be restarted to notice the change from bluez4 <-> bluez5, but it does not need to be recompiled. Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
