Bug#940543: blueman: unable to Search again after Stop Discovery (Status: Busy)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Bug#940543: blueman: unable to Search again after Stop Discovery (Status: Busy)

Phil Morrell
Package: blueman
Version: 2.0.8-1
Severity: normal

Hello,

I think I've managed to narrow this down thanks to btmon. Steps to
reproduce:

1. set `sudo btmon` running in a terminal
2. open Devices... window from the applet
3. ensure nothing in range is in pairing mode
4. click Search and wait 10 seconds

btmon output shows "@ MGMT Command: Start Discovery", then "@ MGMT
Command: Stop Discovery" with "Status: Busy". See attached busy.log.

Observe that the bottom left progress bar does not disappear, even if
Cancel Operation is pressed. The Search, Add and Pair buttons are now
greyed out and disabled.

5. close and re-open the Devices window
6. click Search

btmon output only shows "RAW Open" and Close messages, no "Start
Discovery" command, then "Stop Discovery" with "Status: Rejected".

7. remove and re-insert the USB adapter
8. click Search

btmon output once again shows the "Start Discovery" message.

All of this happened pretty reliably regardless of PC USB adapter vs
laptop built-in etc. However, I did occasionally get lucky with the
expected behaviour of "Stop Discovery" with "Status: Success" causing
the progress bar to disappear. See attached success.log. Similarly, if
any device is found in the search, then the discovery stops correctly.
--
Phil Morrell



-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blueman depends on:
ii  bluez                                         5.50-1
ii  bluez-obexd                                   5.50-1
ii  dbus                                          1.12.16-1
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1
ii  dbus-x11 [dbus-session-bus]                   1.12.16-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-2
ii  gir1.2-appindicator3-0.1                      0.4.92-7
ii  gir1.2-gdkpixbuf-2.0                          2.38.1+dfsg-1
ii  gir1.2-glib-2.0                               1.58.3-2
ii  gir1.2-gtk-3.0                                3.24.5-1
ii  gir1.2-notify-0.7                             0.7.7-4
ii  gir1.2-pango-1.0                              1.42.4-7~deb10u1
ii  gnome-icon-theme                              3.12.0-3
ii  libbluetooth3                                 5.50-1
ii  libc6                                         2.28-10
ii  libglib2.0-0                                  2.58.3-2+deb10u1
ii  libpulse-mainloop-glib0                       12.2-4+deb10u1
ii  libpython3.7                                  3.7.3-2
ii  librsvg2-common                               2.44.10-2.1
ii  notification-daemon                           3.20.0-4
ii  python3                                       3.7.3-1
ii  python3-cairo                                 1.16.2-1+b1
ii  python3-dbus                                  1.2.8-3
ii  python3-gi                                    3.30.4-1
ii  python3-gi-cairo                              3.30.4-1
ii  xfce4-notifyd [notification-daemon]           0.4.3-1

Versions of packages blueman recommends:
ii  policykit-1                  0.105-25
ii  pulseaudio-module-bluetooth  12.2-4+deb10u1

blueman suggests no packages.

-- no debconf information

busy.log (5K) Download Attachment
success.log (5K) Download Attachment
signature.asc (235 bytes) Download Attachment