While trying to figure out why I could not send files to my mobile (or browse its contents), I came across this bug report ($URL). It mentions a kernel regression in the hci code, which is fixed in the following commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=18daf1644e634bae951a6e3d4d19d89170209762 Updating my kernel to gentoo-sources-3.3.1 (where this commit is included) made the problems go away. I had 3.2.1-r2 before. The commit is NOT included in vanilla 3.2.13. Please add it to the gentoo patchset for 3.2.
Could you tell me if you have you applied the patch to 3.2.13 and tried it out?
(In reply to comment #1) > Could you tell me if you have you applied the patch to 3.2.13 and tried it > out? I'll test it during the next days, and keep you informed.
sys-kernel/gentoo-sources-3.2.14: no browsing or file push possible, connections hang (same as in -3.2.1-r2) sys-kernel/gentoo-sources-3.2.14 with the patch manually added: can connect, can browse contents of mobile, can push file to the mobile :)
Whats the state of this bug?
I have the same problem here: I can browse my bluetooth-phone. I can recieve files from the phone. I can not send files to my phone. This seems the error: Aug 14 15:34:19 localhost dbus[1028]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.7" (uid=0 pid=1243 comm="/usr/sbin/bluetoothd --udev ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.36" (uid=1000 pid=1689 comm="/usr/libexec/obex-client ") My config: [ebuild R ] net-wireless/bluez-4.99 USE="alsa consolekit cups readline usb -caps -debug -gstreamer -pcmcia (-selinux) -test-programs" 0 kB [ebuild R ] sys-kernel/gentoo-sources-3.3.8 USE="-build -deblob -symlink" 0 kB [ebuild R ] dev-libs/openobex-1.5 USE="bluetooth usb -debug -irda -syslog" 0 kB [ebuild R ] net-libs/libbluedevil-1.9.2 USE="(-aqua) -debug" 0 kB [ebuild R ] app-mobilephone/obex-data-server-0.4.5 USE="usb -debug -gtk -imagemagick" 0 kB [ebuild R ] net-wireless/bluedevil-1.2.3 USE="(-aqua) -debug" LINGUAS="de -ar -bs -ca -ca@valencia -cs -da -el -en_GB -eo -es -et -eu -fa -fi -fr -ga -hu -it -ja -ko -lt -mai -ms -nb -nds -nl -pa -pl -pt -pt_BR -ro -ru -sk -sl -sr -sr@ijekavian -sr@ijekavianlatin -sr@latin -sv -th -tr -ug -uk -zh_CN -zh_TW" 0 kB
bug here too in Linux version 3.4.9-gentoo: Aug 27 20:47:45 localhost bluetoothd[1697]: Mode session 0x7f3a08514d10 with :1.40 activated Aug 27 20:47:48 localhost dbus[1022]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.32" (uid=0 pid=1696 comm="/usr/sbin/bluetoothd --udev ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.40" (uid=1000 pid=1722 comm="/usr/libexec/obex-client ")
This patch is included in the following kernels: >=3.2.16 http://git.kernel.org/?p=linux/kernel/git/bwh/linux-3.2.y.git;a=commitdiff_plain;h=1c5b4f2f9d7b36fb5d78f959705af57cc0233de9 It also in 3.4, so if this is not solved with 3.4.9, then there is a different issue. Can someone test the latest 3.5 kernel, which is 3.5.3, as of this writing.
Linux version 3.5.3-gentoo -> bug here too Linux version 3.4.9 vanilla -> bug here too: Aug 28 17:17:50 localhost dbus[1062]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.9" (uid=0 pid=1267 comm="/usr/sbin/bluetoothd --udev ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.39" (uid=1000 pid=1708 comm="/usr/libexec/obex-client ")
We've got some technical problems with bugzilla at the moment and this comment got lost: --- Comment #7 from Mike Pagano <mpagano@gentoo.org> --- This patch is included in the following kernels: >=3.2.16 http://git.kernel.org/?p=linux/kernel/git/bwh/linux-3.2.y.git;a=commitdiff_plain;h=1c5b4f2f9d7b36fb5d78f959705af57cc0233de9 It also in 3.4, so if this is not solved with 3.4.9, then there is a different issue. Can someone test the latest 3.5 kernel, which is 3.5.3, as of this writing.
Stephan, I think you have a very similar problem with a different cause. I verified that for my case the patch solved the problem, and it is in now for some time... but if you google for bluetooth/obex push problems you find some more trouble. My suggestion would be we leave *this* bug here as it is and you submit all your info separately into a *new* bug report. Then things will not get mixed up. I'll try to come up with a couple of links, but that may take a bit (I'm on vacation). Feel free to cc me to the new bug report (and mention that I said that in the report, otherwise bugwranglers will complain). @kernel: I'm resolving the bug since 3.3 is stable on most arches now.
