For starters. I use wicd as a replacement for network manager due to my need to have multiples of VLAN's configured on my hard-wired connection. This is not possible through Yast or NetworkManager, and so, I have switched to traditional methods.
My wireless works with Network Manager, as well works with manual configuration / connection from https://en.opensuse.org/SDB:Tracking...wpa_supplicant
So, I switched to traditional ifup method from within Yast --> Network Devices --> Network Settings --> Global Options --> "Traditional Method With ifup"
I installed the wicd suplicant from: http://software.opensuse.org/package/wicd
and have tried 2 of the 3 versions under 13.1 the current one installed is:
Wicd Version:
What is expected:
* Starting the machine should show an indication within the notification area of some type of a wireless symbol or connection.
* The application should start automatically and automatically connect to remembered wireless networks
What happens:
* On startup I am prompted for a password for the application "wicd"
* the application fails to start the daemon and therefor errors out and will not start
-- further troubleshooting
tailing the logs while starting:
I also read that further troubleshooting could be done through: wicd-curses
From this point I am over my head, so in an attempt to resolve I went to my best friend google... okay my only friend google.
he provided me with links like
https://bbs.archlinux.org/viewtopic.php?id=144706
The helpfulness of the above post is limited as it is for arch linux...
someone references installing xorg in order to fix this... I don't buy it.
here is what I have installed
project page --> https://launchpad.net/wicd/+download
possibly related to --> http://askubuntu.com/questions/43860...f-13-10-server
** but this being a different distro I'm not sure
https://bugs.launchpad.net/ubuntu/+s...d/+bug/1132529
please hep me.....
My wireless works with Network Manager, as well works with manual configuration / connection from https://en.opensuse.org/SDB:Tracking...wpa_supplicant
So, I switched to traditional ifup method from within Yast --> Network Devices --> Network Settings --> Global Options --> "Traditional Method With ifup"
I installed the wicd suplicant from: http://software.opensuse.org/package/wicd
and have tried 2 of the 3 versions under 13.1 the current one installed is:
Wicd Version:
Code:
linux-gunq:/home/************ # rpm -qi wicd
Name : wicd
Version : 1.7.2.4
Release : 30.1
Architecture: noarch
Install Date: Thu May 1 20:59:45 2014
Group : Productivity/Networking/System
Size : 16950
License : GPL-2.0
Signature : RSA/SHA1, Tue Apr 1 13:37:41 2014, Key ID caf5c7e1a9ba0727
Source RPM : wicd-1.7.2.4-30.1.src.rpm
Build Date : Tue Apr 1 13:37:22 2014
Build Host : build11
Relocations : (not relocatable)
Vendor : obs://build.opensuse.org/home:KT315
URL : http://wicd.sourceforge.net/
Summary : A wireless and wired network manager
Description :
A complete network connection manager
Wicd supports wired and wireless networks, and capable of
creating and tracking profiles for both. It has a
template-based wireless encryption system, which allows the user
to easily add encryption methods used. It ships with some common
encryption types, such as WPA and WEP. Wicd will automatically
connect at startup to any preferred network within range.
This is a metapackage, it allows installation of all the components of
Wicd, including one of the clients, which must be manually chosen.
Distribution: home:KT315 / openSUSE_13.1
linux-gunq:/home/********* #* Starting the machine should show an indication within the notification area of some type of a wireless symbol or connection.
* The application should start automatically and automatically connect to remembered wireless networks
What happens:
* On startup I am prompted for a password for the application "wicd"
* the application fails to start the daemon and therefor errors out and will not start
-- further troubleshooting
tailing the logs while starting:
Code:
2014-05-01T10:30:57.545240-03:00 linux-gunq dbus[803]: [system] Activating via systemd: service name='org.wicd.daemon' unit='dbus-org.wicd.daemon.service'
2014-05-01T10:30:57.545572-03:00 linux-gunq systemd[1]: Starting Wicd a wireless and wired network manager for Linux...
2014-05-01T10:30:57.610416-03:00 linux-gunq wicd[17247]: It seems like the daemon is already running.
2014-05-01T10:30:57.610740-03:00 linux-gunq wicd[17247]: If it is not, please remove /var/run/wicd/wicd.pid and try again.
2014-05-01T10:30:57.616187-03:00 linux-gunq systemd[1]: wicd.service: main process exited, code=exited, status=1/FAILURE
2014-05-01T10:30:57.616490-03:00 linux-gunq systemd[1]: Failed to start Wicd a wireless and wired network manager for Linux.
2014-05-01T10:30:57.616673-03:00 linux-gunq systemd[1]: Unit wicd.service entered failed state.
..............
2014-05-01T10:31:22.544600-03:00 linux-gunq dbus[803]: [system] Failed to activate service 'org.wicd.daemon': timed outCode:
linux-gunq:~ # wicd-curses
Can't connect to the daemon, trying to start it automatically...
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 1043, in <module>
setup_dbus()
File "/usr/share/wicd/curses/wicd-curses.py", line 1031, in setup_dbus
dbus_ifaces = dbusmanager.get_dbus_ifaces()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 36, in get_dbus_ifaces
return DBUS_MANAGER.get_dbus_ifaces()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 62, in get_dbus_ifaces
if not self._dbus_ifaces: connect_to_dbus()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 48, in connect_to_dbus
return DBUS_MANAGER.connect_to_dbus()
File "/usr/lib/python2.7/site-packages/wicd/dbusmanager.py", line 79, in connect_to_dbus
proxy_obj = self._bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 278, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
linux-gunq:~ #he provided me with links like
https://bbs.archlinux.org/viewtopic.php?id=144706
The helpfulness of the above post is limited as it is for arch linux...
someone references installing xorg in order to fix this... I don't buy it.
here is what I have installed
Code:
linux-gunq:~ # rpm -qa | grep wicd
wicd-lang-1.7.2.4-30.1.noarch
wicd-1.7.2.4-30.1.noarch
wicd-gtk-1.7.2.4-30.1.noarch
wicd-daemon-1.7.2.4-30.1.noarch
wicd-cli-1.7.2.4-30.1.noarch
wicd-curses-1.7.2.4-30.1.noarch
python-wicd-1.7.2.4-30.1.noarch
linux-gunq:~ #possibly related to --> http://askubuntu.com/questions/43860...f-13-10-server
** but this being a different distro I'm not sure
https://bugs.launchpad.net/ubuntu/+s...d/+bug/1132529
please hep me.....