Bug 401983 - With bluetooth integration enabled, system keeps scanning for new bluetooth devices every now and then.
Summary: With bluetooth integration enabled, system keeps scanning for new bluetooth d...
Status: RESOLVED WORKSFORME
Alias: None
Product: Bluedevil
Classification: Plasma
Component: daemon (show other bugs)
Version: 5.14.3
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-10 23:10 UTC by Mike Krutov
Modified: 2019-01-11 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Krutov 2018-12-10 23:10:17 UTC
SUMMARY
BlueDevil seems to be constantly scanning for new bluetooth devices. On my hardware (and I suspect on any combined wifi/bluetooth chips, which are mostly found in laptops) this leads to serious deteoriation in wireless connectivity quality, up to completely loosing a wifi connection for couple minutes after a day of uptime.

I'd suggest to add a separate configuration tickable to prevent this behaviour. 

STEPS TO REPRODUCE
1. Enable BlueDevil "bluetooth integration" feature
2. Open bluetoothctl to monitor for scan("Discovering") requests


OBSERVED RESULT
Software-wise:
Every 2-3 minutes, device goes into "Discovery" mode.

Hardware-wise: 
Wireless speed & packetdrop grows, longer it keeps going worse the connectivity becomes.

EXPECTED RESULT
As this is not a bug per se, while having quite bad outcome AND being a non-obvious thing to detect/debug, I've set it to Wishlist.

Expected result would be to have a configuration item to disable this behaviour while keeping other bluetooth integration features; I'd argue that not scanning continiously should be the default.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Hardware in question:
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Comment 1 David Rosca 2018-12-11 10:43:50 UTC
It only starts device discovery in "Add Device" wizard, nowhere else.
Comment 2 Mike Krutov 2018-12-11 11:00:35 UTC
Quite sure Add device wizard was not running.

I have plasmoid added to my panel, if that matters. 


When I disabled "bluetooth integration" feature it stopped scanning (after restart of my session) without any other changes in system. I'll try to tinker around more and reproduce to see if I'll reproduce this behaviour to confirm add device wizard (what is the name of the wizard process?) is not running.
Comment 3 David Rosca 2018-12-11 11:15:37 UTC
It's "bluedevil-wizard".

One other thing that also starts discovery is KIO "bluetooth:" protocol, so if there is any process that periodically loads this url it will trigger discovery. But in that case, that process should be fixed, not Bluedevil.
Comment 4 Mike Krutov 2018-12-11 11:22:03 UTC
Thanks for answer.

In case I would be able to reproduce this behaviour, how do I find which exact process is calling for KIO bluetooth: ? 

Only things that (should have been) working with BT were:

- pulseaudio, but that should not interact with KIO I think

- bluetooth plasmoid from default plasmoid pack (haven't installed any custom BT plasmoids)

- Through Pulseaudio, Clementine was playing music

All that things are currently running with exact same settings as they were when problem was reproduced, except for "bluetooth integration" setting.
Comment 5 Mike Krutov 2018-12-12 08:28:11 UTC
I have this problem re-appear, unfortunatelly, after system restart. First start of my session @ kde resulted in described behaviour. wizard was not running; running applications were: 
Kate, falkon, Konversation, Firefox, KMail.


Second start of my session resulted in normal behaviour, 

marking as NOTABUG since its not a bug in bluedevil. Need help determining proper component, though.
Comment 6 Bug Janitor Service 2018-12-27 03:44:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2019-01-11 04:33:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!