This happened on 3 fresh installs of Gentoo with the same model mouse on 2 different laptops. When the mouse is first discovered and connected, it works. After the screen has blanked (for some longer period of time) the mouse is no longer connected, and will not reconnect. Reproducible: Always Steps to Reproduce: 1. connect mouse 2. wait some period of time after screen blanks 3. move mouse to bring screen back 4. if mouse is not working, try to connect again Actual Results: laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-device trusted 00:1F:20:1D:1B:4B yes laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Expected Results: expect mouse not to disconnect in the first place... Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.13-r4, 3.0.26-tuxonice x86_64) ================================================================= System uname: Linux-3.0.26-tuxonice-x86_64-Intel-R-_Core-TM-_i5-2520M_CPU_@_2.50GHz-with-gentoo-2.0.3 Timestamp of tree: Tue, 27 Mar 2012 15:00:01 +0000 app-shells/bash: 4.2_p20 dev-lang/python: 2.7.2-r3, 3.2.2 dev-util/cmake: 2.8.6-r4 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.0.3 sys-apps/openrc: 0.9.8.4 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.68 sys-devel/automake: 1.11.1 sys-devel/binutils: 2.21.1-r1 sys-devel/gcc: 4.5.3-r2 sys-devel/gcc-config: 1.5-r2 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82-r1 sys-kernel/linux-headers: 3.1 (virtual/os-headers) sys-libs/glibc: 2.13-r4 Repositories: gentoo ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests binpkg-logs distlocks ebuild-locks fixlafiles news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch" FFLAGS="" GENTOO_MIRRORS="http://gentoo.osuosl.org/" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="en_US" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl aes amd64 avx bash-completion berkdb bzip2 cjk cli cracklib crypt cups cxx dbus dri dts fortran gdbm gnutls gpm gtk hdaps ht iconv jpeg jpeg2k mmx modules mp3 mudflap multilib ncurses nls nptl nptlonly nx openmp pclmul pclmulqdq pcre png pni pppd readline sdl session smx sse sse2 sse4.1 sse4.2 ssl ssse3 sysfs tcpd theora truetype unicode unicode3 vaapi vim-syntax vmx x264 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en_US" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="intel" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Retry with bluez-4.99 please
(In reply to comment #1) > Retry with bluez-4.99 please laptop ~ # emerge -ajqv net-wireless/bluez [ebuild U ] net-wireless/bluez-4.99 [4.98-r2] USE="caps cups debug readline test-programs usb -alsa -consolekit -gstreamer -pcmcia" Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 1) net-wireless/bluez-4.99 >>> Installing (1 of 1) net-wireless/bluez-4.99 >>> Jobs: 1 of 1 complete Load avg: 1.37, 0.35, 0.15 laptop ~ # /etc/init.d/dbus restart * Caching service dependencies ... [ ok ] * Stopping D-BUS system messagebus ... [ ok ] * Starting D-BUS system messagebus ... [ ok ] laptop ~ # * Udev coldplug of bluetooth devices ... [ ok ] laptop ~ # /etc/init.d/bluetooth restart * Udev coldplug of bluetooth devices ... [ ok ] laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please reboot and retry (bluetooth service simply does udev coldplugging, doesn't restart the daemon)
(In reply to comment #3) > Please reboot and retry (bluetooth service simply does udev coldplugging, > doesn't restart the daemon) laptop ~ # dmesg | grep blue [ 8.860401] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(In reply to comment #4) > (In reply to comment #3) > > Please reboot and retry (bluetooth service simply does udev coldplugging, > > doesn't restart the daemon) > > laptop ~ # dmesg | grep blue > [ 8.860401] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is > unblocked > laptop ~ # hcitool scan > Scanning ... > 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse > laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B > Creating device failed: org.bluez.Error.AlreadyExists: Already Exists > laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B > Traceback (most recent call last): > File "/usr/bin/bluez-test-input", line 40, in <module> > input.Connect() > File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in > __call__ > return self._proxy_method(*args, **keywords) > File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in > __call__ > **keywords) > File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in > call_blocking > message, timeout) > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not > receive a reply. Possible causes include: the remote application did not > send a reply, the message bus security policy blocked the reply, the reply > timeout expired, or the network connection was broken. And during the above time this was in /var/log/messages: Mar 30 05:42:12 laptop kernel: [ 110.359086] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Mar 30 05:42:14 laptop kernel: [ 111.753537] hci_acldata_packet: hci0 ACL packet for unknown connection handle 16 Mar 30 05:43:14 laptop bluetoothd[2242]: Software caused connection abort (103)
I don't see in that logs bluetoothd got restarted, if you don't want to reboot, run: killall bluetoothd /etc/init.d/bluetooth restart
(In reply to comment #6) > I don't see in that logs bluetoothd got restarted, if you don't want to > reboot, run: > killall bluetoothd > /etc/init.d/bluetooth restart I did reboot. But here: laptop ~ # killall bluetoothd laptop ~ # /etc/init.d/bluetooth restart * Udev coldplug of bluetooth devices ... [ ok ] laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
During the above exercise another terminal tailing messages output: Mar 30 06:56:40 laptop bluetoothd[2242]: Terminating Mar 30 06:56:40 laptop bluetoothd[2242]: Stopping hci0 event socket Mar 30 06:56:40 laptop bluetoothd[2242]: Stopping SDP server Mar 30 06:56:40 laptop bluetoothd[2242]: Exit Mar 30 06:56:58 laptop bluetoothd[2749]: Bluetooth daemon 4.99 Mar 30 06:56:58 laptop bluetoothd[2751]: Starting SDP server Mar 30 06:56:58 laptop bluetoothd[2751]: Unable to start SCO server socket Mar 30 06:56:58 laptop bluetoothd[2751]: Failed to init audio plugin Mar 30 06:56:58 laptop bluetoothd[2751]: Listening for HCI events on hci0 Mar 30 06:56:58 laptop bluetoothd[2751]: HCI dev 0 up Mar 30 06:56:58 laptop bluetoothd[2751]: Unable to load keys to adapter_ops: Function not implemented (38) Mar 30 06:56:58 laptop bluetoothd[2751]: Adapter /org/bluez/2749/hci0 has been enabled Mar 30 06:56:58 laptop bluetoothd[2751]: mce replied with an error: org.freedesktop.DBus.Error.ServiceUnknown, The name com.nokia.mce was not provided by any .service files Mar 30 06:56:58 laptop bluetoothd[2751]: Inquiry Cancel Failed with status 0x12 Mar 30 06:58:11 laptop bluetoothd[2751]: Connection refused (111)
(In reply to comment #8) > During the above exercise another terminal tailing messages output: [...] > Mar 30 06:56:58 laptop bluetoothd[2751]: mce replied with an error: > org.freedesktop.DBus.Error.ServiceUnknown, The name com.nokia.mce was not > provided by any .service files Strange, we are building bluez with "--enable-maemo6" that should provide that one, more surprising is to see it works at boot but later stops working. Try to: 1. Reboot and see it working 2. Wait it for failing. 3. Attach full /var/log/messages from the time it worked to the one it broke Thanks
(In reply to comment #9) > (In reply to comment #8) > > During the above exercise another terminal tailing messages output: > [...] > > Mar 30 06:56:58 laptop bluetoothd[2751]: mce replied with an error: > > org.freedesktop.DBus.Error.ServiceUnknown, The name com.nokia.mce was not > > provided by any .service files > > Strange, we are building bluez with "--enable-maemo6" that should provide > that one, more surprising is to see it works at boot but later stops working. > > Try to: > 1. Reboot and see it working > 2. Wait it for failing. > 3. Attach full /var/log/messages from the time it worked to the one it broke > > Thanks I shutdown the computer and waited for maybe 30 minutes. I booted and now: laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B laptop ~ # And messages: Mar 30 07:23:02 laptop sudo: mingdao : TTY=pts/1 ; PWD=/home/mingdao ; USER=root ; COMMAND=/bin/bash Mar 30 07:23:29 laptop kernel: [ 118.462281] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Mar 30 07:23:30 laptop kernel: [ 118.887198] input: Bluetooth Laser Travel Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:12/input9 Mar 30 07:23:30 laptop kernel: [ 118.887285] generic-bluetooth 0005:046D:B008.0001: input,hidraw0: BLUETOOTH HID v3.18 Mouse [Bluetooth Laser Travel Mouse] on EC:55:F9:FA:55:07 It is connected! But, please, help me to _keep_ it connected after the screen blanks. I am still tailing /var/log/messages in another screen (over ssh). I will not touch the mouse or the laptop until after the screen has been blanked for at least an hour to see what is happening. Tell me what to do. You can reach me in IRC as mingdao if you prefer to speed things up.
(In reply to comment #10) [...] > But, please, help me to _keep_ it connected after the screen blanks. I am > still tailing /var/log/messages in another screen (over ssh). I will not > touch the mouse or the laptop until after the screen has been blanked for at > least an hour to see what is happening. > Fine, then, attach full tailf output after it breaks > Tell me what to do. You can reach me in IRC as mingdao if you prefer to > speed things up. Sadly I will be travelling today and, then, won't be able to help you much faster, but keep posting here in bug report as I will check it frequently ;)
(In reply to comment #11) > (In reply to comment #10) > [...] > > But, please, help me to _keep_ it connected after the screen blanks. I am > > still tailing /var/log/messages in another screen (over ssh). I will not > > touch the mouse or the laptop until after the screen has been blanked for at > > least an hour to see what is happening. > > > > Fine, then, attach full tailf output after it breaks After waiting over an hour I moved the mouse and the screen came back, so hopefully it's going to keep working. If it breaks again, I will file a new bug report if this one is closed ... will mark this resolved. As this is a fresh install, and was to try out Xfce, I'm going to continue emerging packages. > Sadly I will be travelling today and, then, won't be able to help you much > faster, but keep posting here in bug report as I will check it frequently ;) That's no problem. Thanks for your help!
It's not connected again. Last night the laptop was moved and an eSATA device was tested on it. This morning when I came to the office the bt mouse was not connected. To get dmesg on this it was rebooted: dmesg can be seen here: http://paste.pocoo.org/show/578424/ Same bluez pkg: laptop ~ # qlist -Iv net-wireless/bluez net-wireless/bluez-4.99 laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B Creating device failed: org.bluez.Error.AlreadyExists: Already Exists laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Have you tried to run latest kernel-3.3.x?
(In reply to comment #14) > Have you tried to run latest kernel-3.3.x? Have been on tuxonice, but will build sys-kernel/vanilla-sources-3.3.2
laptop ~ # uname -a Linux laptop 3.3.2 #1 SMP PREEMPT Sat Apr 14 13:57:50 CDT 2012 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux laptop ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse laptop ~ # simple-agent hci0 00:1F:20:1D:1B:4B RequestPinCode (/org/bluez/2524/hci0/dev_00_1F_20_1D_1B_4B) Enter PIN Code: 0000 Release Creating device failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. laptop ~ # bluez-test-device trusted 00:1F:20:1D:1B:4B yes laptop ~ # bluez-test-input connect 00:1F:20:1D:1B:4B Traceback (most recent call last): File "/usr/bin/bluez-test-input", line 40, in <module> input.Connect() File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with signature "" on interface "org.bluez.Input" doesn't exist
tail -f /var/log/messages in another vt recorded: Apr 14 14:01:58 laptop dbus[2511]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.14" (uid=0 pid=3013 comm="/usr/bin/python2 /usr/bin/simple-agent hci0 00:1F:") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=2524 comm="/usr/sbin/bluetoothd --udev ") Apr 14 14:01:59 laptop kernel: [ 162.031670] Bluetooth: hci0 ACL packet for unknown connection handle 16
(In reply to comment #17) > tail -f /var/log/messages in another vt recorded: > > Apr 14 14:01:58 laptop dbus[2511]: [system] Rejected send message, 3 matched > rules; type="method_return", sender=":1.14" (uid=0 pid=3013 > comm="/usr/bin/python2 /usr/bin/simple-agent hci0 00:1F:") > interface="(unset)" member="(unset)" error name="(unset)" > requested_reply="0" destination=":1.0" (uid=0 pid=2524 > comm="/usr/sbin/bluetoothd --udev ") > Apr 14 14:01:59 laptop kernel: [ 162.031670] Bluetooth: hci0 ACL packet for > unknown connection handle 16 Was this the only message from while it worked until it started to fail again?
Created attachment 309047 [details] lines 0 - 6225 of earliest /var/log/messages* The earliest file for messages is /var/log/messages-20120401.gz My original bug was on Mar 28 so I cut that file past the first lines of Mar 29. If I read it correctly the bluetooth receiver was first f
Comment on attachment 309047 [details] lines 0 - 6225 of earliest /var/log/messages* The earliest file for messages is /var/log/messages-20120401.gz My original bug was on Mar 28 so I cut that file past the first lines of Mar 29. If I read it correctly the bluetooth receiver was first f The earliest file for messages is /var/log/messages-20120401.gz My original bug was on Mar 28 so I cut that file past the first lines of Mar 29. If I read it correctly the bluetooth receiver was first found by the kernel here: Mar 27 01:40:03 laptop kernel: [ 9.160735] Bluetooth: Core ver 2.16 and the first failure was here: Mar 27 18:40:56 laptop kernel: [ 101.038657] btusb_bulk_complete: hci0 corrupted ACL packet
Mar 28 13:25:13 laptop kernel: [ 4228.313364] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Mar 28 13:25:14 laptop kernel: [ 4229.063854] hci_acldata_packet: hci0 ACL packet for unknown connection handle 16 Mar 28 13:26:14 laptop bluetoothd[2235]: Software caused connection abort (103) This looks wrong, but you will need to directly ask to upstream for this problems :-(. They are more responsive in mailing list: http://www.bluez.org/development/lists/
Also try with bluez-4.101 please
(In reply to comment #22) > Also try with bluez-4.101 please bluez-4.101 does not build as is on Gentoo without patching; and even if it builds bluetoothd does not start because upstream removed the udev.rules file for bluetooth (and you think systemd is not fubaring Linux yet). http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=2ea98a6a043710ad4958355b62c682b4767f292e This issue was not resolved by 4.101 and should not be marked so IMO.
(In reply to comment #23) > (In reply to comment #22) > > Also try with bluez-4.101 please > > bluez-4.101 does not build as is on Gentoo without patching; and even if it > builds bluetoothd does not start because upstream removed the udev.rules > file for bluetooth (and you think systemd is not fubaring Linux yet). > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > h=2ea98a6a043710ad4958355b62c682b4767f292e > It builds for me, but please open a different bug for this issue (it's a completely different problem) > This issue was not resolved by 4.101 and should not be marked so IMO. The bug *must* be reported to upstream and tracked directly there
(In reply to comment #24) > (In reply to comment #23) > > (In reply to comment #22) > > > Also try with bluez-4.101 please > > > > bluez-4.101 does not build as is on Gentoo without patching; and even if it > > builds bluetoothd does not start because upstream removed the udev.rules > > file for bluetooth (and you think systemd is not fubaring Linux yet). > > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > > h=2ea98a6a043710ad4958355b62c682b4767f292e > > > > It builds for me, but please open a different bug for this issue (it's a > completely different problem) There is already bug 423331 for that. > > This issue was not resolved by 4.101 and should not be marked so IMO. > > The bug *must* be reported to upstream and tracked directly there Since reinstalling Gentoo and using 4.99 I have not experienced this problem again, so I did not start over and report to upstream. My point is that there is nothing to indicate 4.101 fixes this or anything else; and 4.101 removes our udev rules for bluez.
(In reply to comment #25) > (In reply to comment #24) > > (In reply to comment #23) > > > (In reply to comment #22) > > > > Also try with bluez-4.101 please > > > > > > bluez-4.101 does not build as is on Gentoo without patching; and even if it > > > builds bluetoothd does not start because upstream removed the udev.rules > > > file for bluetooth (and you think systemd is not fubaring Linux yet). > > > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > > > h=2ea98a6a043710ad4958355b62c682b4767f292e > > > > > > > It builds for me, but please open a different bug for this issue (it's a > > completely different problem) > > There is already bug 423331 for that. Fine, sadly I won't be able to look at it until Saturday due time constraints, for now, bluez compiles with this USE flags merges for me: [ebuild R ] net-wireless/bluez-4.101 USE="alsa consolekit cups gstreamer readline usb -debug -pcmcia -test-programs" 0 kB > > > > This issue was not resolved by 4.101 and should not be marked so IMO. > > > > The bug *must* be reported to upstream and tracked directly there > > Since reinstalling Gentoo and using 4.99 I have not experienced this problem > again, so I did not start over and report to upstream. > > My point is that there is nothing to indicate 4.101 fixes this or anything > else; and 4.101 removes our udev rules for bluez. This problem is clearly an upstream bug, if are still suffering this in 4.101 please report directly to upstream, that bug is not a packaging/downstream bug as far as I see and, then, there is no gain at all keeping it reported only here (and it's better you report it directly instead of me as you have the setup and hardware to test and reply to upstream questions)
(In reply to comment #26) > (In reply to comment #25) > > (In reply to comment #24) > > > (In reply to comment #23) > > > > (In reply to comment #22) > > > > > Also try with bluez-4.101 please > > > > > > > > bluez-4.101 does not build as is on Gentoo without patching; and even if it > > > > builds bluetoothd does not start because upstream removed the udev.rules > > > > file for bluetooth (and you think systemd is not fubaring Linux yet). > > > > http://git.kernel.org/?p=bluetooth/bluez.git;a=commit; > > > > h=2ea98a6a043710ad4958355b62c682b4767f292e > > > > > > > > > > It builds for me, but please open a different bug for this issue (it's a > > > completely different problem) > > > > There is already bug 423331 for that. > > Fine, sadly I won't be able to look at it until Saturday due time > constraints, for now, bluez compiles with this USE flags merges for me: > [ebuild R ] net-wireless/bluez-4.101 USE="alsa consolekit cups > gstreamer readline usb -debug -pcmcia -test-programs" 0 kB > > > > > > > This issue was not resolved by 4.101 and should not be marked so IMO. > > > > > > The bug *must* be reported to upstream and tracked directly there > > > > Since reinstalling Gentoo and using 4.99 I have not experienced this problem > > again, so I did not start over and report to upstream. > > > > My point is that there is nothing to indicate 4.101 fixes this or anything > > else; and 4.101 removes our udev rules for bluez. > > This problem is clearly an upstream bug, if are still suffering this in > 4.101 please report directly to upstream, that bug is not a > packaging/downstream bug as far as I see and, then, there is no gain at all > keeping it reported only here (and it's better you report it directly > instead of me as you have the setup and hardware to test and reply to > upstream questions) Closing again as explained -> report directly to upstream. Regarding missing udev rule, I mailed yesterday to ask upstream how are non-systemd systems supposed to start bluetoothd now (to test you can manually run it as root) as udev rule was dropped intentionally
*** Bug 448748 has been marked as a duplicate of this bug. ***
