Trying to run wicd-curses as a normal userHere is the error when running as a normal user:ERROR:dbus.proxies:Introspect error on :1.12:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.16" (uid=1000 pid=9570 comm="/usr/bin/python2 -O /usr/share/wicd/curses/wicd-cu
dbus is in your daemons array, so you should not need to start it manually. If for some reason you think you should, then use `rc.d restart dbus`. If a service is not running the restart command will simply start it, but if it is already running, restart will stop it, then start it again.You will, however, need a dbus-session (different from the dbus daemon). If you get dbus erro
Hi,
I'm running OS11.1 with Gnome on my laptop with Intel's 3945 wireless card. Like many others I've been having problems with networkmanager not seeing my wifi connection from time to time, even refusing to connect to it manually (and even refusing to connect to the wired network!)
I'm currently using Qubes OS which uses F18. I've run into several issues with netmanager (such as disconnecting frequently when multiple AP share the same SSID) and have found the switch to wicd give me a greater degree of control and more consistent connection.
The problem:
I would like to know how to have the wicd-client NOT start on start-up.
If you are using wicd you should !network in rc.conf and add dbus and wicd in your daemons (dbus first). Unless I don't understand your problem.
BKLive
https://bbs.archlinux.org/profile.php?id=14494
2012-08-06T11:32:40Z
Hello there,
Its been 2 or 3 days now I am hunting for a solution to this problem, My computer is running on Backtrack 5 R2 (GNOME).
When I was using initscripts when laptop goes suspend and then wake wicd used to reconect to the wifi or wired conection that is usefull when moving from one location to another with a diferent network (example from home to university)I am using systemd since 2 o 3 weeks, all the things are working like a charm execpt this one.
Hi all
This works as i just did a successful installation of the latest wicd package. Although networkmanager is much better thatn before, wicd connects quicker and mostly importantly it never has any problem connecting after resuming from hybernation or standby.
Quote:
su -
yum -y install python python-devel wget
After experimenting with wicd I've gone back to network manager. All is well on the networking front however I am having trouble stopping wicd completely.
I've stopped it starting up the daemon
chkconfig --list | grep wicd
returns empty
but when my kde windows starts up the wicd try icon start up.
Email this page
