emerge -ajv net-misc/wicd-1.7.2.4-r2 with USE="X amd64 elibc_glibc gtk kernel_linux multilib ncurses nls pm-utils userland_GNU" caused the bluetooth mouse to stop working...it was disconnected. When I tried to reconnect it output: baruch ~ # dmesg | grep -i blue [ 2.759156] usb 1-1.4: Product: Broadcom Bluetooth Device [ 3.571826] Bluetooth: Core ver 2.16 [ 3.571880] Bluetooth: HCI device and connection manager initialized [ 3.571888] Bluetooth: HCI socket layer initialized [ 3.571894] Bluetooth: L2CAP socket layer initialized [ 3.571905] Bluetooth: SCO socket layer initialized baruch ~ # hcitool scan Scanning ... 00:1F:20:1D:1B:4B Bluetooth Laser Travel Mouse baruch ~ # bluez-test-device trusted 00:1F:20:1D:1B:4B 1 baruch ~ # 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. I've had that identical error message in other bug reports for bluez -- Bug 410049 for example Suspected power management may be the cause, so "emerge -C net-misc/wicd" and "emerge -a --depclean" which removed it's deps: sys-power/pm-quirks-20100619 dev-python/urwid-1.0.2 x11-misc/ktsuss-2 sys-power/pm-utils-1.4.1-r2 dev-python/pytz-2012c Changed /etc/portage/package.use to "net-misc/wicd X nls -pm-utils" and emerged wicd, which did not pull sys-power/pm-utils and sys-power/pm-quirks. Then bluez connected the mouse properly. The new flags for wicd on this laptop are: X amd64 elibc_glibc gtk kernel_linux multilib ncurses nls userland_GNU It should be noted that emerging tuxonice-sources the next day pulled sys-power/pm-utils and sys-power/pm-quirks but did not cause the mouse to disconnect.
Bug #410049 comment #26: "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" *** This bug has been marked as a duplicate of bug 410049 ***
(In reply to comment #1) > Bug #410049 comment #26: > > "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" > > *** This bug has been marked as a duplicate of bug 410049 *** First, this is not a duplicate of 410049. Second, I contacted Pacho via email and explained the situation, and he told me to open a new bug summarizing clearly that it breaks with wicd[pm-utils]. Since 410049 never even considered wicd, and wicd is breaking bluez, what do you suggest here?
(In reply to comment #2) > First, this is not a duplicate of 410049. > > Second, I contacted Pacho via email and explained the situation, and he told > me to open a new bug summarizing clearly that it breaks with wicd[pm-utils]. > > Since 410049 never even considered wicd, and wicd is breaking bluez, what do > you suggest here? I don't have bluetooth, so I can't reproduce this. Could you please try to isolate the cause of the issue. Is it the installation of a package (which), or running some program(which), or the combination of both(?). You original report is inconclusive. If I read it correctly, you say that simply emerging wicd made your bluetooth mouse stop? You did not reboot, or start wicd for this? Please try to isolate the problem on a finer level. Also, what do you mean by "wicd is breaking bluez"?
(In reply to comment #3) > (In reply to comment #2) > > First, this is not a duplicate of 410049. > > > > Second, I contacted Pacho via email and explained the situation, and he told > > me to open a new bug summarizing clearly that it breaks with wicd[pm-utils]. > > > > Since 410049 never even considered wicd, and wicd is breaking bluez, what do > > you suggest here? > > I don't have bluetooth, so I can't reproduce this. Could you please try to > isolate the cause of the issue. Is it the installation of a package > (which), or running some program(which), or the combination of both(?). You > original report is inconclusive. If I read it correctly, you say that > simply emerging wicd made your bluetooth mouse stop? You did not reboot, or > start wicd for this? Please try to isolate the problem on a finer level. > > Also, what do you mean by "wicd is breaking bluez"? What I meant was that during the course of installing and setting up wicd, the bluetooth mouse was disconnected and gave the error in the OP when trying to reconnect it. This error has been reported with bluez quite a bit by many people. I just reinstalled wicd (having previously unmerged wicd, it's deps, and pm-utils), changed my system to use wicd rather than starting wlan0 from /etc/conf.d/net, and rebooted. The bt mouse is still working. Based on my make.conf with nothing in package.use for wicd: net-misc/wicd-1.7.2.4-r2 USE="X gtk ncurses pm-utils -ambiance (-ioctl) -libnotify -mac4lin -nls" New set of problems (related to how I was connected to my WPA access point, vs. how the laptop should be configured to use wicd). Which is the preferred method to setup wicd? http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=4&chap=4 or https://wiki.gentoo.org/wiki/Wicd or something else? You can close this bug, since I have no way of knowing how to reproduce it again today and there's no way to know what caused it, or if it was related to wicd. Thanks
(In reply to comment #4) > Which is the preferred method to setup wicd? > > http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=4&chap=4 > or > https://wiki.gentoo.org/wiki/Wicd The first document is not about wicd, it is about what to do if you don't use wicd. In any case, wicd should be pretty self explanatory.
(In reply to comment #5) > (In reply to comment #4) > > > Which is the preferred method to setup wicd? > > > > http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=4&chap=4 > > or > > https://wiki.gentoo.org/wiki/Wicd > > The first document is not about wicd, it is about what to do if you don't > use wicd. In any case, wicd should be pretty self explanatory. I didn't read the handbook page until after pasting. Years ago in Slackware I used wicd, and It Just Worked (TM). Now wicd has my laptop connected to 192.168.100.28 on my wired network, rather than it's assigned address of 192.168.54.13 in /etc/dhcp/dhcpd.conf of the Linux router. Time to rip out wicd. ;)
