Debian
blueman package

Unable to save Network settings after enabling PAN

Bug #709171 reported by Dmitry Astapov on 2011-01-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	blueman (Debian)	Fix Released	Unknown	debbugs #611351
	blueman (Fedora)	Won't Fix	Medium	redhat-bugs #633076

Bug Description

Blueman 1.21 does not allow me to enable NAP in Network settings.

Steps to reproduce: applet menu -> Local services -> Network -> check "Enable NAP" and "Enable NAT", select dnsmasq and "PAN support: blueman (dnsmasq)", press "Apply".

As soon as you select "PAN support: blueman (dnsmasq)" radio button, blueman-applet produces the following traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/blueman/plugins/services/Network.py", line 251, in pan_support_toggled
    applet.SetPluginConfig("NMPANSupport", False)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "<string>", line 2, in SetPluginConfig
  File "/usr/lib/python2.6/dist-packages/blueman/plugins/applet/DBusService.py", line 97, in SetPluginConfig
    self.Applet.Plugins.SetConfig(plugin, value)
  File "/usr/bin/blueman-applet", line 257, in SetConfig
    self.__config.props.applet_plugins = plugins
  File "/usr/lib/python2.6/dist-packages/blueman/plugins/ConfigPlugin.py", line 37, in __setattr__
    self.__dict__["Config"]().set(key, value)
  File "/usr/lib/python2.6/dist-packages/blueman/plugins/config/Gconf.py", line 81, in set
    func(BLUEMAN_PATH + self.section + "/" + key, value)
  File "/usr/lib/python2.6/dist-packages/blueman/plugins/config/Gconf.py", line 76, in x
    self.client.set_list(key, gconf.VALUE_STRING, val)
TypeError: value should be a string

If I try to select any other radio button in the window, this traceback will be produces after each selection (modulo first arg of SetPluginConfig).

When I press "Apply", the following message is displayed: "Failed to apply network settings: 'org.freedesktop.DBus.Python.dbus.exceptions.DBusException: Not authorized'". However, dbus-monitor shows no dbus activity after I press "Apply".

I am using Debian/sid (aka unstable).
Version of packages:
blueman1.21-4.1
bluez 4.70-1

hciconfig -a:
hci0: Type: BR/EDR Bus: USB
        BD Address: 00:03:7A:E3:02:1D ACL MTU: 384:8 SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:14194 acl:108 sco:0 events:789 errors:0
        TX bytes:19167 acl:165 sco:0 commands:400 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'dimail-0'
        Class: 0x5a010c
        Service Classes: Networking, Capturing, Object Transfer, Telephony
        Device Class: Computer, Laptop
        HCI Version: 2.0 (0x3) Revision: 0x77b
        LMP Version: 2.0 (0x3) Subversion: 0x77b
        Manufacturer: Cambridge Silicon Radio (10)

Full output of blueman-applet is attached

Related branches

lp:ubuntu/precise/blueman

Revision history for this message

In Red Hat Bugzilla #633076, Andrew (andrew-redhat-bugs) wrote on 2010-09-12:

Description of problem:
I want set Local Services->Network Settings->DUN support->NetworkManager, but the exception is appeared all time.

Version-Release number of selected component (if applicable):
blueman-1.21-4.fc12.i686

How reproducible:
100%

Steps to Reproduce:
1.Services->Network Settings->DUN support->NetworkManager

Actual results:

'/apps/blueman/applet_plugins' ['NMDUNSupport', u'!PPPSupport']
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/blueman/plugins/services/Network.py", line 232, in dun_support_toggled
    applet.SetPluginConfig("PPPSupport", False)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "<string>", line 2, in SetPluginConfig
  File "/usr/lib/python2.6/site-packages/blueman/plugins/applet/DBusService.py", line 97, in SetPluginConfig
    self.Applet.Plugins.SetConfig(plugin, value)
  File "/usr/bin/blueman-applet", line 257, in SetConfig
    self.__config.props.applet_plugins = plugins
  File "/usr/lib/python2.6/site-packages/blueman/plugins/ConfigPlugin.py", line 37, in __setattr__
    self.__dict__["Config"]().set(key, value)
  File "/usr/lib/python2.6/site-packages/blueman/plugins/config/Gconf.py", line 82, in set
  File "/usr/lib/python2.6/site-packages/blueman/plugins/config/Gconf.py", line 77, in x
    func = x
TypeError: value should be a string

Expected results:
An exception should not appear.

Additional info:

Revision history for this message

Dmitry Astapov (dastapov) wrote on 2011-01-28:

Full blueman-applet output Edit (6.1 KiB, text/plain)

Revision history for this message

Dmitry Astapov (dastapov) wrote on 2011-01-28:

Ive tested version 1.22~bzr707-1 - bug is present there as well.

Revision history for this message

Valmantas Palikša (walmis) wrote on 2011-01-28:

Hi, thanks for the report. Fix now committed to bzr.

Changed in blueman:
status:	New → Fix Committed

Bug Watch Updater (bug-watch-updater) on 2011-01-30

Changed in blueman (Debian):
status:	Unknown → New

Revision history for this message

In Red Hat Bugzilla #633076, Bug (bug-redhat-bugs) wrote on 2011-05-31:

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message

In Red Hat Bugzilla #633076, Bug (bug-redhat-bugs) wrote on 2011-06-28:

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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

Bug Watch Updater (bug-watch-updater) on 2012-04-04