Bug 1338717

Summary: [abrt] blueman: connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
Product: [Fedora] Fedora Reporter: Saurav <saurav1.net>
Component: bluemanAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: acooks, afinkelsrc, a_idm, arielnmz, bjrosen, bl, bugiardolr, bugzilla, chanueting, colotunbabay2010, consult, craigkjohnson, crancran, deeppurplefedora, dev, diamantis.karagkiaouris.dev, enelar, error23.d, fedora, glozmantal, jayabharat, jhcolleye, kjeldo, kolyshkin, lko.anshumanshukla, mh7596, miesi, mjd+redhat, pahan, pcfe, r415312, rtalur, stanley.king, vivek.hyperspace
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d9f78b9be6a87ab14287f3eb6c99f0e8ecfc834c
Whiteboard: abrt_hash:430dfff358f5c1a4ac394619799f6b5cd4ebdff7;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:37:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Saurav 2016-05-23 10:29:20 UTC
Description of problem:
On Fedora 24 (only XFCE), with blueman-2.0.4-2.fc24 Bluetooth cannot be enabled without (su or sudo) hciconfig hci0 up piscan. I enabled it like that but then when I tried to make the Bluetooth adapter discoverable, this crash occurred. After forcefully enabling Bluetooth with hciconfig as root, Blueman can see remote devices but with this crash, understandably the latter cannot see Blueman. blueman-2.0.4-1.fc24 does not have either of these problems (Bluetooth is enabled normally and discoverability works), so this seems to be a regression. Hardware: Lenovo G50-80 with Intel Wireless AC 3160 (Wi-Fi+Bluetooth combo).

Version-Release number of selected component:
blueman-2.0.4-2.fc24

Additional info:
reporter:       libreport-2.7.0
cmdline:        python3 /usr/bin/blueman-applet
executable:     /usr/bin/blueman-applet
kernel:         4.5.4-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reproducible:   Not sure how to reproduce the problem
runlevel:       unknown
type:           Python3
uid:            1000

Truncated backtrace:
connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist


Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/blueman/plugins/applet/DiscvManager.py", line 81, in on_set_discoverable
    self.adapter.set("Discoverable", True)
  File "/usr/lib/python3.5/site-packages/blueman/bluez/errors.py", line 148, in warp
    raise parse_dbus_error(exception)
  File "/usr/lib/python3.5/site-packages/blueman/bluez/errors.py", line 146, in warp
    return func(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blueman/bluez/PropertiesBlueZInterface.py", line 27, in set
    return self.__properties_interface.Set(self.get_interface_name(), name, value)
  File "/usr/lib64/python3.5/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib64/python3.5/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist


Local variables in innermost frame:
timeout: -1.0
byte_arrays: False
bus_name: 'org.bluez'
self: <dbus._dbus.SystemBus (system) at 0x7fdda7a90a40>
args: ('org.bluez.Adapter1', 'Discoverable', True)
get_args_opts: {'byte_arrays': False}
dbus_interface: 'org.freedesktop.DBus.Properties'
object_path: dbus.ObjectPath('/org/bluez/hci0')
signature: None
method: 'Set'
message: <dbus.lowlevel.MethodCallMessage path: /org/bluez/hci0, iface: org.freedesktop.DBus.Properties, member: Set dest: org.bluez>
kwargs: {}

Comment 1 Saurav 2016-05-23 10:29:27 UTC
Created attachment 1160514 [details]
File: backtrace

Comment 2 Saurav 2016-05-23 10:29:29 UTC
Created attachment 1160515 [details]
File: environ

Comment 3 Fedora Admin XMLRPC Client 2016-06-21 16:27:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2016-06-21 20:07:53 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Raghavendra Talur 2016-06-24 11:22:32 UTC
I confirm the bug. I had the same issue with 2.0.4-2 version. When I downgrade it to 2.0.4-1 it works fine.

Comment 6 Kirill Kolyshkin 2016-06-24 22:04:54 UTC
Thanks! I also found that downgradeing to blueman-2.0.4-1 fixes the issue. I took it from koji at http://koji.fedoraproject.org/koji/buildinfo?buildID=750696

Comment 7 Joshua Rosen 2016-06-26 14:39:59 UTC
*** Bug 1350222 has been marked as a duplicate of this bug. ***

Comment 8 glozmantal 2016-06-27 07:47:57 UTC
*** Bug 1350336 has been marked as a duplicate of this bug. ***

Comment 9 mohammad 2016-07-03 12:00:54 UTC
*** Bug 1352290 has been marked as a duplicate of this bug. ***

Comment 10 Anshuman Shukla 2016-07-04 02:59:54 UTC
Similar problem has been detected:

Bluetooth fails to turn on fedra 23 (recently) and on fedora 24 (upgraded to a few days ago).

reporter:       libreport-2.7.1
cmdline:        python3 /usr/bin/blueman-adapters
event_log:      2016-07-04-08:26:25> ('report_uReport' completed successfully)
executable:     /usr/bin/blueman-adapters
kernel:         4.6.3-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Comment 11 Alex Gluck 2016-07-04 07:50:48 UTC
Similar problem has been detected:

After upgrade from fedora 23 to fedora 24. If i try delete or another action on mouse 2 i get this error.

reporter:       libreport-2.7.1
cmdline:        python3 /usr/bin/blueman-manager
executable:     /usr/bin/blueman-manager
kernel:         4.6.3-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Comment 12 Gerhard 2016-07-11 11:04:50 UTC
Similar problem has been detected:

Tried to make my bluetooth device visible.

reporter:       libreport-2.7.1
cmdline:        python3 /usr/bin/blueman-adapters
executable:     /usr/bin/blueman-adapters
kernel:         4.5.7-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Comment 13 Alex Gluck 2016-07-11 17:39:00 UTC
I found what i have kernel module asus_nb_wmi, he add 2 device:
asus-wireless
asus-bluetooth

And while module loaded bluetooth not work properly. But if i "rmmod asus_nb_wmi" light indicator "flight mode" and feature "flight mode" doesn't work.

Comment 14 Joshua Rosen 2016-07-15 16:25:49 UTC
Latest update seems to have fixed my problems, Bluetooth is working again.

Comment 15 mohammad 2016-07-18 16:40:33 UTC
*** Bug 1357625 has been marked as a duplicate of this bug. ***

Comment 16 Anshuman Shukla 2016-07-18 17:18:27 UTC
Similar problem has been detected:

Trying to change bluetooth settings like making discoverable

reporter:       libreport-2.7.1
cmdline:        python3 /usr/bin/blueman-manager
executable:     /usr/bin/blueman-manager
kernel:         4.6.3-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Comment 17 Pavel Alexeev 2016-07-22 08:25:30 UTC
Similar problem has been detected:

Set bluetooth visible

reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/blueman-applet
executable:     /usr/bin/blueman-applet
kernel:         4.6.4-301.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
runlevel:       N 5
type:           Python3
uid:            1000

Comment 18 Jean-Henri 2016-08-03 15:12:55 UTC
*** Bug 1363798 has been marked as a duplicate of this bug. ***

Comment 19 Gerhard 2016-08-04 07:36:19 UTC
Similar problem has been detected:

Just wanted to switch bluetooth visibility to on.

reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/blueman-adapters
event_log:      2016-08-04-09:35:12> (»report_uReport« erfolgreich abgeschlossen)
executable:     /usr/bin/blueman-adapters
kernel:         4.6.5-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
runlevel:       N 5
type:           Python3
uid:            1000

Comment 20 Stan King 2016-08-07 17:50:49 UTC
Similar problem has been detected:

1. Searched for bluetooth devices.
2. Saw the mouse I wanted to add.
3. Used right-mouse click to "trust" the device.
4. This error occured.

reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/blueman-manager
event_log:      2016-08-07-13:47:51> ('report_uReport' completed successfully)
executable:     /usr/bin/blueman-manager
kernel:         4.6.4-301.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
runlevel:       N 5
type:           Python3
uid:            1000

Comment 21 Chris Cranford 2016-08-19 15:44:15 UTC
*** Bug 1368511 has been marked as a duplicate of this bug. ***

Comment 22 Benjamin Ariel Nava Martinez 2016-08-25 01:33:31 UTC
Similar problem has been detected:

Whenever I try to do something bluetooth-related (make device discoverable, pair device, trust it, etc.)

reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/blueman-applet
executable:     /usr/bin/blueman-applet
kernel:         4.6.7-300.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
runlevel:       N 5
type:           Python3
uid:            1000

Comment 23 Alex Finkel 2017-03-06 17:27:37 UTC
Similar problem has been detected:

Attempting to change from Always Visible to Always Hidden in Adapter settings.

reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/blueman-adapters
executable:     /usr/bin/blueman-adapters
kernel:         4.9.13-100.fc24.x86_64
package:        blueman-2.0.4-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Set" with signature "ssb" on interface "org.freedesktop.DBus.Properties" doesn't exist
runlevel:       N 5
type:           Python3
uid:            1000

Comment 24 Fedora End Of Life 2017-07-25 20:52:01 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 25 Fedora End Of Life 2017-08-08 14:37:15 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.