Bug 709356

Summary: cnetworkmanager D-Bus error, "ServiceName" property
Product: [Fedora] Fedora Reporter: Adam D. <adam820>
Component: cnetworkmanagerAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 15CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-31 15:16:52 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:

Description Adam D. 2011-05-31 13:35:56 UTC
Description of problem:
When trying to use many of the functions in cnetworkmanager, such as -u or -s, or to join a wireless network, it results in a Traceback citing errors in the python scripts. At the bottom it mentions that a property is missing or not exported in in D-Bus.

Version-Release number of selected component (if applicable):

cnetworkmanager-0.21.1-3.fc15.noarch

How reproducible:
Every time. Did it on real hardware and in a VM.

Steps to Reproduce:
1. yum install cnetworkmanager
2. Use NetworkManager to bring up the interfaces if not up already.
2. cnetworkmanager -u (or -s, or many of the other options)
  
Actual results:

[root@localhost ~]# cnetworkmanager -s
Traceback (most recent call last):
 File "/usr/bin/cnetworkmanager", line 242, in <module>
   list_connections(SYSTEM_SERVICE)
 File "/usr/bin/cnetworkmanager", line 225, in list_connections
   acos = map(lambda a: a["Connection"].object_path, acs)
 File "/usr/bin/cnetworkmanager", line 225, in <lambda>
   acos = map(lambda a: a["Connection"].object_path, acs)
 File "/usr/lib/python2.7/site-packages/networkmanager/activeconnection.py", line 44, in __getitem__
   sn = self.__getitem__("ServiceName")
 File "/usr/lib/python2.7/site-packages/networkmanager/activeconnection.py", line 42, in __getitem__
   v = super(ActiveConnection, self).__getitem__(key)
 File "/usr/lib/python2.7/site-packages/dbusclient/__init__.py", line 174, in __getitem__
   value = super(DBusClient, self).__getitem__(key)
 File "/usr/lib/python2.7/site-packages/dbusclient/__init__.py", line 77, in __getitem__
   return pmi.Get(iface, key, byte_arrays=True)
 File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
   **keywords)
 File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
   message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Property "ServiceName" of interface "org.freedesktop.NetworkManager.Connection.Active" isn't exported (or may not exist)

Expected results:

[root@localhost /] cnetworkmanager -s
Active  |  Name           | Type
------+-----------+------------
*          |  System eth0 | 802-3-ethernet

Additional info:

As a result, cannot use cnetworkmanager to connect to wireless from the command line.

Comment 1 Adam D. 2011-05-31 16:30:19 UTC
I forgot to mention that cnetworkmanager-0.21.1-2.fc14.noarch work fine under Fedora 14, so either something changed in this program between 0.21.1-2 and 0.21.1-3, or something changed somewhere else (D-Bus, etc.).

Comment 2 Kevin Fenzi 2011-06-01 14:52:30 UTC
Hi. I've just orphaned this package. Someone with more time/energy may be picking it up soon, or it may drop from the collection. 

In the mean time, does 'nmcli' do what you want?

Comment 3 Adam D. 2011-06-02 12:22:48 UTC
Unless I'm mistaken on how it works, or if they've updated it for Fedora 15, there's no way to create the initial connection to the wireless. It seemed like once you had used the GUI-based NetworkManager applet to create the connection and generate the UUID, you could use nmcli to reinitiate that connection in the future. I'll go ahead and take a look at the man page a little more. I suppose you can close this bug if it's not going to be maintained in this version.

Comment 4 Kevin Fenzi 2011-06-12 16:25:48 UTC
Yeah. You are correct, but you can make/write out a config file and then get nmcli to use it to connect. 

See: 

https://bugzilla.gnome.org/show_bug.cgi?id=645318

(there's a link there to someone's howto to make the connection files).