This commit removes what Gentoo is relying on with bluetooth subsystem: http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=2ea98a6a043710ad4958355b62c682b4767f292e So bluetoothd is not started anymore Reproducible: Always
Bug title typo =net-wireless/bluez-4.101
As far as I was able to see in git repo this was delibarately removed as long running processes (as bluetoothd) should not be started by udev. Should it be started by /etc/init.d/bluetooth instead ? Looks like Arch Linux is already doing that: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/rc.bluetooth?h=packages/bluez
Man I'm glad I came across this report! I've been struggling for days trying to get my previously working bluetooth adapter working on my ~amd64 laptop, thinking it was a permission / ownership issue caused by the recent polkit update. Everything I tried to do was failing. Then I read this and realized that the polkit update appeared around the same time as the bluez update did. Damn I wish I could get back the hours I've spent trying to resolve this before reading this thread! Anyhow, I just downgraded to the previous version of bluez and viola! My bluetooth was working again! I hope this gets resolved soon, but in the meantime I've masked 4.101 because I need a functioning bluetooth dongle to interact with my phone.
(In reply to comment #2) > As far as I was able to see in git repo this was delibarately removed as > long running processes (as bluetoothd) should not be started by udev. > Should it be started by /etc/init.d/bluetooth instead ? > Looks like Arch Linux is already doing that: > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/rc. > bluetooth?h=packages/bluez I could be wrong, but I believe at least Gnome (3.x)'s bluetooth system uses the .service file to start the udev daemon. Without the file, it seems that you cannot access bluetooth devices within Gnome. I believe I even tried starting the openrc servce manually, but Gnome doesn't recognize it unless it's started via udev. What I've done is just copied the file from the previous version on top of the bluez-4.101 install and things seem to work fine. So either Gnome needs to update their dependence on the udev service file, or bluez needs to keep that file.
(In reply to comment #4) > (In reply to comment #2) > > As far as I was able to see in git repo this was delibarately removed as > > long running processes (as bluetoothd) should not be started by udev. > > Should it be started by /etc/init.d/bluetooth instead ? > > Looks like Arch Linux is already doing that: > > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/rc. > > bluetooth?h=packages/bluez > > I could be wrong, but I believe at least Gnome (3.x)'s bluetooth system uses > the .service file to start the udev daemon. Without the file, it seems > that you cannot access bluetooth devices within Gnome. I believe I even > tried starting the openrc servce manually, but Gnome doesn't recognize it > unless it's started via udev. > > What I've done is just copied the file from the previous version on top of > the bluez-4.101 install and things seem to work fine. > > So either Gnome needs to update their dependence on the udev service file, > or bluez needs to keep that file. Its not just a Gnome issue. As I run KDE. The devs need to first recognize this issue as they have yet to even marked this thread as "confirmed". Then they need to figure out the approach they want to take. It seems as though the easiest method would be to patch bluez like Arch did. As an aside, what file did you copy from the previous version to make this work? TIA
Problem is actual for me. 'wireless/bluez-4.101' package does not work with my bluetooth. I have HP ProBook 6450b(WD779EA) and use gentoo 3.4.4, gnome desktop environment. All works on wireless/bluez-4.99. Please fix problem.
(In reply to comment #6) > Problem is actual for me. 'wireless/bluez-4.101' package does not work with The package work fine. Until the bug is fixed, just enter "bluetoothd -n" in a terminal. Ctrl-C to stop.
In my case I have replaced the whole start section in /etc/init.d/bluetooth with: start() { ebegin "Starting ${SVCNAME}" start-stop-daemon --start --exec "/usr/sbin/bluetoothd" eend $? } and # rc-update add bluetooth default
(In reply to comment #7) > (In reply to comment #6) > > Problem is actual for me. 'wireless/bluez-4.101' package does not work with > > The package work fine. Until the bug is fixed, just enter "bluetoothd -n" > in a terminal. Ctrl-C to stop. The package isn't working fine if none of the tools, especially the graphical interfaces aren't working with it! Having to open a terminal and evoking the bluetooth daemon manually isn't the solution or a very good work around when you can just mask this version until it's fixed and not have any issues IMHO! There have now been several posts in the forums about this bug and I'm sure more will be forthcoming as users begin upgrading and getting hit with it. Like I said in my previous post, this upgrade came around the same time that the new polkit hit the tree. Many are probably still dealing with that one and haven't realized that this issue is unrelated. However once they do catch on there will be more posts about this here. I'm still interested in hearing which file needs to be copied from 4.99 in order to make 4.101 work as expected. That would be a better workaround IMHO, than manually starting and stopping the daemon in a terminal. Any help would be appreciated TIA
(In reply to comment #9) > I'm still interested in hearing which file needs to be copied from 4.99 in > order to make 4.101 work as expected. That would be a better workaround > IMHO, than manually starting and stopping the daemon in a terminal. > /lib/udev/rules.d/97-bluetooth.rules
This was the reply on linux-bluetooth ml asking why udev rule was removed: "Udev rules are not supposed to spawn daemons. It never was. And now if you do that udev will kill your daemon after a certain timeout. You'd need to a) maintain that rule by yourself and b) patch udev to not do that." What will Gentoo do to start bluetoothd now?
(In reply to comment #10) > (In reply to comment #9) > > > I'm still interested in hearing which file needs to be copied from 4.99 in > > order to make 4.101 work as expected. That would be a better workaround > > IMHO, than manually starting and stopping the daemon in a terminal. > > > > /lib/udev/rules.d/97-bluetooth.rules Albert thanks for the heads-up! I copied /lib/udev/rules.d/97-bluetooth.rules into my home directory prior to updating, then copied it back over after the upgrade and it worked like a charm! My bluetooth is now working as expected so this is a viable workaround. Thanks again!!!!
If you note the comment in the bluez commit, the workaround from comment 8 seems more long term (even if the whole systemd/udev business is likely to get more broken with each release).
+*bluez-4.101-r1 (06 Jul 2012) + + 06 Jul 2012; Pacho Ramos <pacho@gentoo.org> +bluez-4.101-r1.ebuild, + +files/bluetooth-init.d-r2, -bluez-4.101.ebuild: + Recover bluetoothd init.d script to start it now that upstream has decided to + drop udev rule (bug #423513 by Nikolay S. Rybaloff, Marcin Deranek and + others). +
