Bug 459119

Summary:	nuntius produce endless attempts by bluez to reconnect to bluetooth headset and speaker
Product:	[Applications] kdeconnect	Reporter:	kdeuzver <asdf-kd>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	nicolas.fella
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=417421
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	sender=:1.59 nuntius sender=:1.59 kdeconnect-indicator

Description kdeuzver 2022-09-14 17:36:59 UTC

### SUMMARY

After system upgrade **kdeconnect** brought me the **nuntius** into my autostart.  
I found it produce a spam of endless attempts by bluez to reconnect to my bluetooth headset and speaker.   
Even if bluetooth adapter is disabled and bluetooth headset and speaker are turned off.  
Which leads to endles failure attempts to reconnect bluetooth headset and speaker after i disconnect headset or speaker from my laptop.  
Also it leads to endless desktop notifications of connect/disconnect by Blueman applet.

### Issue anamnes:  
https://github.com/blueman-project/blueman/issues/1854
https://github.com/bluez/bluez/issues/392

**syslog**:
```
...
/var/log/syslog:158695:Sep 13 22:38:58 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158705:Sep 13 22:39:03 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158715:Sep 13 22:39:14 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158716:Sep 13 22:39:19 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158725:Sep 13 22:39:30 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158734:Sep 13 22:39:35 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158743:Sep 13 22:39:46 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158744:Sep 13 22:39:51 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158753:Sep 13 22:40:02 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158762:Sep 13 22:40:07 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158771:Sep 13 22:40:18 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158772:Sep 13 22:40:23 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158781:Sep 13 22:40:34 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158790:Sep 13 22:40:39 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158799:Sep 13 22:40:50 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158808:Sep 13 22:40:55 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
/var/log/syslog:158820:Sep 13 22:41:06 smarttop bluetoothd[1193]: src/device.c:search_cb() F4:4E:FD:03:80:98: error updating services: Host is down (112)
/var/log/syslog:158822:Sep 13 22:41:11 smarttop bluetoothd[1193]: src/device.c:search_cb() 00:00:AB:CE:47:FE: error updating services: Host is down (112)
...
```

**log of `sudo dbus-monitor --system destination=org.bluez,interface=org.bluez.Device1`**:
```
...
method call time=1663162202.133755 sender=:1.59 -> destination=org.bluez serial=63812 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162212.133786 sender=:1.59 -> destination=org.bluez serial=63820 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162222.135780 sender=:1.59 -> destination=org.bluez serial=63828 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162232.133598 sender=:1.59 -> destination=org.bluez serial=63836 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162242.133195 sender=:1.59 -> destination=org.bluez serial=63844 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162252.133746 sender=:1.59 -> destination=org.bluez serial=63852 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162262.133871 sender=:1.59 -> destination=org.bluez serial=63860 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162272.133593 sender=:1.59 -> destination=org.bluez serial=63868 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
method call time=1663162282.133625 sender=:1.59 -> destination=org.bluez serial=63876 path=/org/bluez/hci0/dev_00_00_AB_CE_47_FE; interface=org.bluez.Device1; member=ConnectProfile
   string "00001101-0000-1000-8000-00805f9b34fb"
...
```

**btmon log**:
$ sudo btmon > [btmon.log](https://fars.ee/tCbE.wvwpWU)
$ sudo btmon -w > [btmon.btsnoop.gz](https://github.com/bluez/bluez/files/9561076/btmon.btsnoop.gz)

I found the villain via `d-feet` by search `:1.59`
it is **nuntius**:
https://user-images.githubusercontent.com/2188215/190208051-bed820ca-f892-4f47-b6ee-1a47d8b29af0.png
https://user-images.githubusercontent.com/2188215/190208078-04ec12fd-aa46-47cf-92c9-060f40e5c0d0.png

If i kill the nuntius process, endless notifications spam and reconnection attempts are gone.

### STEPS TO REPRODUCE
1. install kdeconnect and nuntius
2. connect and pair bluetooth headset/speaker
3. disconnect bluetooth headset/speaker

### OBSERVED RESULT
Endless attempts by bluez to reconnect to bluetooth headset and speaker,   
even if bluetooth is disabled and bluetooth headset and speaker are turned off.  
Endless desktop notifications of connect/disconnect by Blueman applet right after headset/speaker disconnection   

### EXPECTED RESULT
No endless attempts by bluez to reconnect to my bluetooth headset and speaker.  
No endless desktop notifications of connect/disconnect by Blueman applet.

### SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Pop_Os! 22.04
(available in About System)
KDE Plasma Version: libkf5plasma 5 5.92.0-0ubuntu1, libkf5plasmaquick5 5 5.92.0-0ubuntu1, plasma-framework 5.92.0-0ubuntu1
KDE Frameworks Version: -
Qt Version: libqt5* 5.15.3 and some 5.15.9 libs

### ADDITIONAL INFORMATION
xfce Version: 4.17
kdeconnect Version: 21.12.3-0ubuntu1
nuntius Version 0.2.0-5build1

Same i guess: https://bugs.kde.org/show_bug.cgi?id=417421

Comment 1 kdeuzver 2022-09-14 17:38:22 UTC

Created attachment 152061 [details]
sender=:1.59 nuntius

Comment 2 kdeuzver 2022-09-14 17:38:50 UTC

Created attachment 152062 [details]
sender=:1.59 kdeconnect-indicator

Comment 3 kdeuzver 2022-09-14 17:40:23 UTC

*** Bug 459118 has been marked as a duplicate of this bug. ***

Comment 4 Nicolas Fella 2022-09-15 11:49:57 UTC

KDE Connect doesn't have anything to do with nuntius, why do you think it does?


It doesn't do anything with bluetooth either. It has a bluetooth backend, but that isn't even built by default

Comment 5 kdeuzver 2022-09-16 16:18:55 UTC

Well... idk, sorry.
I thought it was kdeconnect because it was the only sapp for martphone I had installed before the system upgrade.

Comment 6 kdeuzver 2022-09-16 22:27:17 UTC

(In reply to Nicolas Fella from comment #4)
> KDE Connect doesn't have anything to do with nuntius, why do you think it
> does?
> 
> 
> It doesn't do anything with bluetooth either. It has a bluetooth backend,
> but that isn't even built by default

I thought that kdeconnect was involved because of this:  
    https://bugs.kde.org/attachment.cgi?id=152062
    https://bugs.kde.org/attachment.cgi?id=152061
sender=:1.59 (from log of dbus-monitor) leads to both:  nuntius and kdeconnect-indicator

Comment 7 Albert Vaca Cintora 2023-03-23 17:53:53 UTC

Closing because this isn't really related to kdeconnect.