Description of problem: Trying to start wicd instead of NetworkMaanger. Version-Release number of selected component: wicd-gtk-1.7.2.4-13.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray dso_list: dbus-python-1.2.0-1.fc20.x86_64 executable: /usr/share/wicd/gtk/wicd-client.py kernel: 3.16.3-200.fc20.x86_64 runlevel: N 5 type: Python uid: 3000 Truncated backtrace: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.44" (uid=3000 pid=1373 comm="/usr/bin/python -O /usr/share/wicd/gtk/wicd-client") interface="org.wicd.daemon" member="SetGUIOpen" error name="(unset)" requested_reply="0" destination=":1.49" (uid=0 pid=1628 comm="/usr/bin/python -O /usr/share/wicd/daemon/wicd-dae") Traceback (most recent call last): File "/usr/share/wicd/gtk/wicd-client.py", line 537, in on_activate self.toggle_wicd_gui() File "/usr/share/wicd/gtk/wicd-client.py", line 824, in toggle_wicd_gui self.gui_win = gui.appGui(tray=self) File "/usr/share/wicd/gtk/gui.py", line 239, in __init__ daemon.SetGUIOpen(True) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.44" (uid=3000 pid=1373 comm="/usr/bin/python -O /usr/share/wicd/gtk/wicd-client") interface="org.wicd.daemon" member="SetGUIOpen" error name="(unset)" requested_reply="0" destination=":1.49" (uid=0 pid=1628 comm="/usr/bin/python -O /usr/share/wicd/daemon/wicd-dae") Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x2357ad0> args: (True,) object_path: '/org/wicd/daemon' signature: None bus_name: dbus.UTF8String(':1.49') get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: -1.0 kwargs: {} dbus_interface: 'org.wicd.daemon' message: <dbus.lowlevel.MethodCallMessage path: /org/wicd/daemon, iface: org.wicd.daemon, member: SetGUIOpen dest: :1.49> method: 'SetGUIOpen'
Created attachment 942932 [details] File: backtrace
Created attachment 942933 [details] File: environ
Silly question, but is the wicd service enabled and running? The client needs that running to connect to.
wicd is not running because I'm using NetworkManager. Unfortunately, service wicd stop doesn't shut down the widget as I think a user would expect. I haven't been able to figure out how not to start the widget. I wish it were possible to switch between Network Manager and wicd with just one click. It would be nice to share the configuration information between the two, but that may not be practical. My reason for wanting to switch is to be able to provide a WPA2 access point under Xfce. Under Gnome, when I last looked, it was possible to set a WEP access point, but not a WPA2. If it were possible to provide a WPA2 acces point under Xfce, I would consider the overall problem solved.
(In reply to Peter H. Jones from comment #4) > wicd is not running because I'm using NetworkManager. Unfortunately, service > wicd stop doesn't shut down the widget as I think a user would expect. I > haven't been able to figure out how not to start the widget. Yes, wicd is quite terrible. It would be nice if the client exited if the daemon is shut down, but it doesn't. I would call that a separate bug. > I wish it were possible to switch between Network Manager and wicd with just > one click. It would be nice to share the configuration information between > the two, but that may not be practical. > > My reason for wanting to switch is to be able to provide a WPA2 access point > under Xfce. Under Gnome, when I last looked, it was possible to set a WEP > access point, but not a WPA2. If it were possible to provide a WPA2 acces > point under Xfce, I would consider the overall problem solved. You are way too optimistic here. :) There will likely never be information sharing between wicd and NetworkManager. I just don't see it ever happening. wicd is barely more than a wrapper around the CLI tools and an alternative for people who do not want to run NetworkManager or cannot easily run NetworkManager because of their window manager or desktop environment set up. I am trying not to diverge too much from upstream and submit things there that fix problems, but it is getting harder and harder to keep wicd usable on Fedora. So back to the actual issue reported here. With wicd.service not running, the client gives this D-Bus barf, which I would expect. Does the client start up if wicd.service is running?
I tried the following: systemctl disable NetworkManager systemctl enable wicd Reboot After I logged in, a box appeared on the screen with the following text: "Unable to contact the Wicd daemon due to an access denied error from DBus. Please check that your user is in the users group." I don't think I have a "users" group, and I don't want to install one just to run wicd.
I think you need the ".service" on the ends of the service names with systemctl: systemctl disable NetworkManager.service systemctl enable wicd.service Does that help?
I've been using .service as suggested. See bug 1172088.
I'm going to build wicd-1.7.3, which was recently released. Maintaining the 1.7.2.4 release is getting to be annoying, so I want to bring F-20 up to the latest and try to get that working. I'll build it in to the testing repo.
wicd-1.7.3-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/wicd-1.7.3-1.fc20
Package wicd-1.7.3-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wicd-1.7.3-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7748/wicd-1.7.3-1.fc20 then log in and leave karma (feedback).
wicd-1.7.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.