There is something wrong with Currents BlueTooth.. mousey wrong
My BT mouse is not connecting with the bluetooth any more. As it is whenever I switch between distros, I have to go though that process of connecting a new BT device, that was never an issue other than being the hassle of having to redo it every time I used a different disto, because it did it with the other one too.
Now, in Slackare Current. It does not even connect, or re-connect. I have to delete it off of the list then as stated, go through the same process of adding a new device. Now that gui that opens when I delete the device it does not go away, the icon for it stays in the gui, when I push the button on the mouse to make it go into find me mode. then hit search, I have to wait a minute then use that same icon for the mouse that should have went off the window for the listings of devices. and keep clicking on it to setup, then when it actually catches it, the other window opens then click that button to set it into setup mode, the lights for the device show up, then disappear, then show up, and when it does catch and say it is connect and paired, with the lights on the main window to indicate a connect, the mouse still does not work. there are times where the lights will just go off, and trying this from the start of the process, again and again, and again, more than 3 times, well, I'd say it has an issue that needs to be looked into and fixed. the about window says, blueman-applet 2.1 Blueman is a GTK+ Bluetooth manager https://github.com/blueman-project/blueman |
I had a similar problem a few weeks ago, and it affected *all* hotplugged devices (e.g. bt mouse, usb mouse, removable drives, etcetera). What I found was that some of my local customization has broken udev event monitoring. Verify that you have the following file:
Code:
$ ls -lh /run/udev/control For those curious, the local customization was a bind mount of /var/run to /run - this on its own is just fine. However, the "clean up" in rc.S that removes /var/run/*/* was removing /run/udev/control, as that also shows up under /var/run/udev/control, on system boot. |
mine
Code:
so what is the remedy for this. certainly not restart x after booting up slack. why all of a sudden is this happening, what changed? Code:
# cat /etc/rc.d/rc.S | grep Clean -A5 |
Stupid question: are you using dunst as your desktop notification daemon?
That one is tricky to set up to work with Blueman. You need to also install dmenu, and you need to press ctrl+shift+period (IIRC) on the notifications. |
whatever slackware comes with is what I am using...
the major complaint is, why all of a sudden after x amount of years of Slackware not having to do any extra tricky crap to get bluetooth to work now all of a sudden I got a do a dance and a skip to get it to work now? put it back the way it was... |
It's not clear what the problem actually is, so neither I nor anyone else can recommend a fix. It appears that you *do* have the /run/udev/control pipe - please confirm that. Also, does restarting X actually make it work? If so, then that's maybe a useful data point, but whether it did or not isn't clear in your response.
This report is the only one I've seen of a problem with new blueman, so absent further information, I'm inclined to say that it's a local issue on your system. |
Also: check if there's anything in dmesg. I had an issue where my controller would just stop responding after about half an hour of JRPG-grinding. Eventually, I checked dmesg, and it showed the port on my USB hub where the Bluetooth dongle was connected to, shutting down. I replaced the hub.
|
Quote:
Also, does restarting X actually make it work? as in using startx to longin and out then back in again? Code:
# ls /run/udev/ Code:
address: F0:65:DD:74:C3:3E Code:
dmesg blurtooth: Code:
$ sudo dmesg | grep Bluetooth Code:
|
Quote:
Ah, I could be wrong writing that, if @BW-userx has overridden the standard LS_OPTIONS environment variable. How about giving the output of... Code:
\ls -F -b -T 0 --color=auto -hl /run/udev/ |
There is at least one patch in blueman's git repo that might affect you - try this (pick the correct arch, of course):
http://slackware.com/~rworkman/blueman-test/ |
Quote:
I am assuming this is the pre-compiled patched app, so I shouldn't bother with getting the source dir and run that slackbuild in there. blueman-2.1-x86_64-1_rlw.txz thanks.. I'm giving this a try. MOD Code:
userx@slack.it.netters:~ as I was in Arch before, when I rebooted into slack, and logged in xfce it gave me a message saying, you might not be able to use bluetooh then I installed that patch and well as stated it did not work. Now running update-all It is showing 'blueman-2.1-x86_64-t.txz in the updates. |
Lucky Me
I have an old iso, so I mounted it, pulled blueman-2.0.8-x86_64-2.txz out of it and replaced it with the other one, reboot, and so far do good. It is working.
I blacklisted blueman as well. |
I noticed that, in addition to reconnect issues, the Info menu item doesn't display the info page for connected devices: no page appears at all. I've installed the latest blueman git code from master: still broken. I'll try Robbie's version later and report back.
|
Consider opening an issue here: https://github.com/blueman-project/blueman/issues
The blueman folks are generally very helpful if you are willing to go through their debugging suggestions. I'll continue to watch the git repo. |
...and let's try the new packages at http://www.slackware.com/~rworkman/blueman-test/ (2_rlw) - I pulled the previous patches from git master, while they should have come from the "2-1-stable" branch. I don't think there were any differences between them, but let's make sure...
|
All times are GMT -5. The time now is 11:15 PM. |