There is something wrong with Currents BlueTooth.. mousey wrong

BW-userx · 07-02-2019, 09:33 AM

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

rworkman · 07-02-2019, 03:15 PM

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 
srwxr-xr-x 1 root root 0 Jun 30 12:52 /run/udev/control=

One of the things I noticed was that a restart of X would make everything work IF it was already plugged in, and that includes the bluetooth mouse.

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.

BW-userx · 07-02-2019, 03:46 PM

mine

Code:

# ls -lh /run/udev/control
srwxr-xr-x 1 root root 0 Jul  2 04:21 /run/udev/control

no =

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
# Clean up some temporary files:
rm -f /var/run/* /var/run/*/* /var/run/*/*/* /etc/nologin \
  /etc/dhcpc/*.pid /etc/forcefsck /etc/fastboot \
  /var/state/saslauthd/saslauthd.pid \
  /tmp/.Xauth* 1> /dev/null 2> /dev/null
if [ -d /var/lib/pkgtools/setup/tmp ]; then

dugan · 07-02-2019, 04:25 PM

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.

BW-userx · 07-02-2019, 04:39 PM

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...

rworkman · 07-02-2019, 04:43 PM

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.

dugan · 07-02-2019, 05:02 PM

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.

BW-userx · 07-02-2019, 05:12 PM

Quote:

Originally Posted by rworkman

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.

when I get done with this download, I do the rebooting testing thing. this was happening on both of my laptops, the other laptop I did a reinstall of alien bob slackware current iso dated April , 2019, and it works perfectly like it should.

Also, does restarting X actually make it work?

as in using startx to longin and out then back in again?

Code:

# ls /run/udev/
control  data  links  rules.d  tags  watch
root@slack.it.netters:/home/userx
# ls /run/udev/control
/run/udev/control

blueman info of mouse. not dmesg

Code:

address: F0:65:DD:74:C3:3E
UUIDs:
00001000-0000-1000-8000-00805f9b34fb ServiceDiscoveryServerServiceClassID
00001124-0000-1000-8000-00805f9b34fb Human Interface Device Service (HID)
00001200-0000-1000-8000-00805f9b34fb PnP Information

the bluetooth, is the wifi/bluetooth ePCI mini card on motherboard.

Code:

root@slack.it.netters:/home/userx
# dmesg | grep Mouse -A10
[   10.180989] input: PS/2 Generic Mouse as /devices/platform/i8042/serio2/input/input13
[   10.220128] usb 1-5: new full-speed USB device number 5 using xhci_hcd
[   10.265223] mmc0: cannot verify signal voltage switch
[   10.348255] usb 1-5: New USB device found, idVendor=138a, idProduct=003f, bcdDevice= 1.04
[   10.348260] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[   10.348263] usb 1-5: SerialNumber: 00309ac61580
[   10.377403] mmc0: new ultra high speed SDR50 SDXC card at address aaaa
[   10.382258] mmcblk0: mmc0:aaaa SS64G 59.5 GiB
[   10.384835]  mmcblk0: p1
[   10.431175] Console: switching to colour frame buffer device 240x67
[   10.466078] usb 1-7: new high-speed USB device number 6 using xhci_hcd
--
[   79.382031] usb 1-3.3: Product: 2.4G Wireless Mouse
[   79.382034] usb 1-3.3: Manufacturer: MOSART Semi.
[   79.389428] input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/0003:3938:1047.0003/input/input27
[   79.441724] hid-generic 0003:3938:1047.0003: input,hidraw2: USB HID v1.10 Keyboard [MOSART Semi. 2.4G Wireless Mouse] on usb-0000:00:14.0-3.3/input0
[   79.445399] input: MOSART Semi. 2.4G Wireless Mouse Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:3938:1047.0004/input/input28
[   79.445808] input: MOSART Semi. 2.4G Wireless Mouse Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:3938:1047.0004/input/input29
[   79.497633] input: MOSART Semi. 2.4G Wireless Mouse System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:3938:1047.0004/input/input30
[   79.497892] input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.1/0003:3938:1047.0004/input/input32
[   79.498187] hid-generic 0003:3938:1047.0004: input,hiddev97,hidraw3: USB HID v1.10 Mouse [MOSART Semi. 2.4G Wireless Mouse] on usb-0000:00:14.0-3.3/input1
[ 1050.143017] EXT4-fs (mmcblk0p1): recovery complete
[ 1050.143021] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 4323.906387] EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: (null)
root@slack.it.netters:/home/userx
#

the bold is the Wireless Mouse, not my bluetooth.

dmesg blurtooth:

Code:

$ sudo dmesg  | grep Bluetooth
[   10.963777] Bluetooth: Core ver 2.22
[   10.967431] Bluetooth: HCI device and connection manager initialized
[   10.969473] Bluetooth: HCI socket layer initialized
[   10.971186] Bluetooth: L2CAP socket layer initialized
[   10.972937] Bluetooth: SCO socket layer initialized
[   11.008187] Bluetooth: hci0: read Intel version: 370810011002270d00
[   11.011883] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
[   11.251190] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[   11.271302] Bluetooth: hci0: Intel firmware patch completed and activated
[   14.065394] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.065395] Bluetooth: BNEP filters: protocol multicast
[   14.065402] Bluetooth: BNEP socket layer initialized
[   20.922323] Bluetooth: RFCOMM TTY layer initialized
[   20.922332] Bluetooth: RFCOMM socket layer initialized
[   20.922340] Bluetooth: RFCOMM ver 1.11

after trying to connect it , it connected then them little "light bars" went off in a second afterwords.

Code:


[   11.251190] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[   11.271302] Bluetooth: hci0: Intel firmware patch completed and activated
[   12.221822] EXT4-fs (sdb5): re-mounted. Opts: (null)
[   12.471839] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null)
[   12.479106] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   12.489453] fuse init (API version 7.27)
[   14.065394] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.065395] Bluetooth: BNEP filters: protocol multicast
[   14.065402] Bluetooth: BNEP socket layer initialized
[   14.262122] NET: Registered protocol family 10
[   14.267293] Segment Routing with IPv6
[   14.347234] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.556239] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.560871] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   14.639324] vboxdrv: loading out-of-tree module taints kernel.
[   14.648435] vboxdrv: Found 4 processor cores
[   14.664331] vboxdrv: TSC mode is Invariant, tentative frequency 2294687038 Hz
[   14.664332] vboxdrv: Successfully loaded version 6.0.8 (interface 0x00290008)
[   14.667658] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
--
[   20.922323] Bluetooth: RFCOMM TTY layer initialized
[   20.922332] Bluetooth: RFCOMM socket layer initialized
[   20.922340] Bluetooth: RFCOMM ver 1.11
[   21.009529] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   21.057426] 8021q: 802.1Q VLAN Support v1.8
root@slack.it.netters:/home/userx
#

Richard Cranium · 07-02-2019, 05:42 PM

Quote:

Originally Posted by BW-userx

mine

Code:

# ls -lh /run/udev/control
srwxr-xr-x 1 root root 0 Jul  2 04:21 /run/udev/control

no =

Then you do not have a pipe there, you have a regular file.

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/

...? If there is no "=" at the end of control, then you don't have a pipe.

rworkman · 07-02-2019, 11:14 PM

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/

BW-userx · 07-03-2019, 07:02 AM

Quote:

Originally Posted by rworkman

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/

I was just looking into the live series of slack hoping they keep oldies so I could burn them to a USB stick and try to back track this. but nope.

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:~
$ ls /var/log/packages/blue*
/var/log/packages/bluedevil-2.1.1-x86_64-4
/var/log/packages/blueman-2.1-x86_64-1_rlw
/var/log/packages/bluez-5.50-x86_64-2
/var/log/packages/bluez-firmware-1.2-x86_64-2

nope, it did the connect, then dropped it seconds afterwords.

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.

BW-userx · 07-03-2019, 07:47 AM

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.

alex14641 · 07-03-2019, 12:59 PM

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.

rworkman · 07-03-2019, 02:18 PM

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.

rworkman · 07-03-2019, 02:28 PM

...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...