On Wednesday 30 October 2013 11:02:35 Ludwig Nussel wrote:
I will be tracking his progress by updates on the bluez5 branch of bluedevil and see if we have basic functionality or not. If we indeed have a working Bluedevil for Bluez5 by the beginning of October, then I guess this would go nice along the release of Gnome 3.10. With some optimism, I believe we could aim for Bluez5 support in 13.1 for both KDE and Gnome, however in case that Bluedevil is not ready, we should be able to have Bluez4 for KDE alongside Bluez5 for Gnome.
There are still people reporting bluetooth problems with KDE. What is the current state there?
Ludwig, At this moment there is no release of Bluedevil that supports Bluez5. We have some git-snapshots in KUSC for Bluedevil to support Bluez5, but we haven't seen any commits for the last two weeks anymore. The upstream author didn't released any preview, alpha or beta version for it yet and indicated also that he will not accept any bugreports on it. Before RC1, I spoke with Jos to indicate that KDE at this moment has a non- working Bluetooth setup due to Bluez5 and that we hopefully can fix that before the 13.1 Release. As far as I know he send that information out, but it doesn't make people actually read that information nor stopping them from registering bugs. In the past we had to take the decision to pull GNome back and patch it to make use of Bluez4 or to go forward with Bluez5 in the hope that KDE would catch up in time. It was impossible to have Bluez4 co-installable with Bluez5 and we saw more and more packages moving to Bluez5 support. Looking upstream than the main driver for supporting newer versions, seems to be the versions that Fedora is supporting. Not surprisingly as that there is quite a big number of Fedora people working on upstream KDE. The same will happen with the UPower 1.,0 change. API's have changed and Gnome 3.12 will require this new version, however KDE doesn't support UPower 1.0 (yet). So again we are looking at Fedora which indicated that they will make that change most likely sometime around April 2014.
PS: do we actually still have anyone who is taking care of monitoring the default KDE bug assignee alias (kde-maintainers@suse.de)?
That alias is something that the SuSE KDE team had set-up in the past and nobody from the current team is assigned to that alias. What we have done is that some of us have registered themselves to Hermes to receive emails whenever something happens for that email alias. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org