Wicd manager starts up, and closes after 5 seconds...

[jacobtc]

Hi...

I'm having some really confusing problems, starting the wicd network manager, when I have done everything there in the "How to start networking" topic, it just errors out with some python problem or something, so I tried sudo rm /etc/wicd/manager-settings.conf, and I tried to start it again, but it just pops up and closes again... I'm running Backtrack 4 in Vmware, and I got my connection type set to Bridged, is that a problem? Also in my interfaces file I only got my wlan0 in there, I've deleted all the other interfaces, is that the problem? I'm really getting pretty confused, because it has worked perfectly fine before, but I reinstalled Backtrack 4 in vmware, and now it doesn't work anymore What is wrong?


Regards
Jacob

[brtw2003]

hi,

have a look in your wicd log file:
less /var/log/wicd/wicd.log

BTW: you don't need to delete anything in /etc/wicd/* !

If you really would like to play seriously with BT4, you should get familiar with ubuntu networking basics
and don't rely on fancy GUIs!

https://help.ubuntu.com/8.10/internet/C/basics.html

/brtw2003

[jacobtc]

hi,

have a look in your wicd log file:
less /var/log/wicd/wicd.log

BTW: you don't need to delete anything in /etc/wicd/* !

If you really would like to play seriously with BT4, you should get familiar with ubuntu networking basics
and don't rely on fancy GUIs!

https://help.ubuntu.com/8.10/internet/C/basics.html

/brtw2003

I know, but wicd is just much easier to use... Also I don't use GUI for WEP cracking and such, I just think that actually connecting to the network should be rather easy, but it just errors on me I thinks it kindda ironic that the only thing holding me back is my damn connection manager -.- But I will post my log in 2 sec...

Here is my error when starting /etc/init.d/networking start and the log from wicd.log

2010/02/19 20:24:26 :: ---------------------------
2010/02/19 20:24:26 :: wicd initializing...
2010/02/19 20:24:26 :: ---------------------------
2010/02/19 20:24:26 :: Automatically detected wireless interface wlan0
2010/02/19 20:24:26 :: found wireless_interface in configuration wlan0
2010/02/19 20:24:26 :: setting wireless interface wlan0
2010/02/19 20:24:26 :: automatically detected wired interface eth0
2010/02/19 20:24:26 :: found wired_interface in configuration eth0
2010/02/19 20:24:26 :: setting wired interface eth0
2010/02/19 20:24:26 :: found wpa_driver in configuration wext
2010/02/19 20:24:26 :: setting wpa driver wext
2010/02/19 20:24:26 :: found always_show_wired_interface in configuration False
2010/02/19 20:24:26 :: found use_global_dns in configuration False
2010/02/19 20:24:26 :: setting use global dns to False
2010/02/19 20:24:26 :: setting use global dns to boolean False
2010/02/19 20:24:26 :: found global_dns_1 in configuration None
2010/02/19 20:24:26 :: found global_dns_2 in configuration None
2010/02/19 20:24:26 :: found global_dns_3 in configuration None
2010/02/19 20:24:26 :: setting global dns
2010/02/19 20:24:26 :: global dns servers are None None None
2010/02/19 20:24:26 :: found auto_reconnect in configuration True
2010/02/19 20:24:26 :: setting automatically reconnect when connection drops
2010/02/19 20:24:26 :: found debug_mode in configuration False
2010/02/19 20:24:26 :: found wired_connect_mode in configuration 1
2010/02/19 20:24:26 :: found signal_display_type in configuration 0
2010/02/19 20:24:26 :: found dhcp_client in configuration 0
2010/02/19 20:24:26 :: Setting dhcp client to 0
2010/02/19 20:24:26 :: found link_detect_tool in configuration 0
2010/02/19 20:24:26 :: found flush_tool in configuration 0
2010/02/19 20:24:26 :: Wireless configuration file found...
2010/02/19 20:24:26 :: Wired configuration file found...
2010/02/19 20:24:26 :: chmoding configuration files 0600...
2010/02/19 20:24:26 :: chowning configuration files root:root...
2010/02/19 20:24:26 :: Using wired interface...eth0
2010/02/19 20:24:26 :: Using wireless interface...wlan0
2010/02/19 20:24:26 :: autoconnecting... wlan0
2010/02/19 20:24:33 :: Traceback (most recent call last):
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 1652, in <module>
2010/02/19 20:24:33 :: main(sys.argv)
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 1623, in main
2010/02/19 20:24:33 :: obj = ConnectionWizard(d_bus_name, auto_connect=auto_connect)
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 188, in __init__
2010/02/19 20:24:33 :: self.AutoConnect(True)
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 379, in AutoConnect
2010/02/19 20:24:33 :: self._wired_autoconnect()
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 392, in _wired_autoconnect
2010/02/19 20:24:33 :: network = self.GetDefaultWiredNetwork()
2010/02/19 20:24:33 :: File "/usr/lib/wicd/wicd-daemon.py", line 1069, in GetDefaultWiredNetwork
2010/02/19 20:24:33 :: config.read(self.wired_conf)
2010/02/19 20:24:33 :: File "/usr/lib/python2.5/ConfigParser.py", line 267, in read
2010/02/19 20:24:33 :: self._read(fp, filename)
2010/02/19 20:24:33 :: File "/usr/lib/python2.5/ConfigParser.py", line 462, in _read
2010/02/19 20:24:33 :: raise MissingSectionHeaderError(fpname, lineno, line)
2010/02/19 20:24:33 :: ConfigParser.MissingSectionHeaderError: File contains no section headers.
2010/02/19 20:24:33 :: file: /etc/wicd/wired-settings.conf, line: 1
2010/02/19 20:24:33 :: '8\x00\x1a\xef\x08\x14j\xff\xff\xff\xff\xff\xff\xf 0[K\xa7U\x00\x17\xb8\x07\xae\x18j\x00Ix\xb58\xb3\r2\ x01L\x0c\xe7P\x82\x83\xa2C}Q\xa1\x19\xf0\xb7*K\xff-Dw\xf1\xefL\xd1KGZ}K@\x86\x05\x00D\x00\x00\x00D\x0 0\x00\x00\x08A:\x01\x00\x18\xf3k:8\x00\x1a\xef\x08 \x14j\xff\xff\xff\xff\xff\xff\x00\\K\xa7U\x00\x17\ xb8\x07\xae\x18j\x00Ix\xb58\xb3\r2\x01L\x0c\xe7P\x 82\x83\xa2C}Q\xa1\x19\xf0\xb7*K\xff-Dw\xf1\xefL\xd1KGZ}K@\x86\x05\x00D\x00\x00\x00D\x0 0\x00\x00\x08A\x02\x01\x00\x18\xf3k:8\x00\x1a\xef\ x08\x14j\xff\xff\xff\xff\xff\xff\x10\\K\xa7U\x00\x 17'

[xX_Spiidey_Xx]

...so I tried sudo rm /etc/wicd/manager-settings.conf, and I tried to start it again, but it just pops up and closes again...

you don't need to sudo if you're root - if you're using bt4, presumably, you're root, unless you added a new privileged user. just a quickie fyi

I'm running Backtrack 4 in Vmware, and I got my connection type set to Bridged, is that a problem? Also in my interfaces file I only got my wlan0 in there, I've deleted all the other interfaces, is that the problem? I'm really getting pretty confused, because it has worked perfectly fine before, but I reinstalled Backtrack 4 in vmware, and now it doesn't work anymore What is wrong?

running your virtual machine with bridged only shares your host ip with the virtual machine. having deleted the other ifaces in your /etc/network/interfaces file except wlan0, should be the root cause of your networking not working (get it? networking/notworking?). *thinking, thinking, thinking... uhhh... right!* and as far as your wlan0 goes - unless you have a usb wireless device connected to your host and passed through to your vm, it ain't gon' work.

so... what you now need to do is add all your interfaces back, or at least eth0, in order to get your bridging working again. also, going the nat route might be better than bridged. some routers and firewalls don't like that. oh, and also make sure you're running wicd before starting wicd-client

i'd go with what brtw2003 has mentioned, and get familiar with networking. it'll not only help you understand the basics, but if you're serious about using bt4, you'll be able to understand networking concepts and use backtrack a lot better.

[jacobtc]

you don't need to sudo if you're root - if you're using bt4, presumably, you're root, unless you added a new privileged user. just a quickie fyi



running your virtual machine with bridged only shares your host ip with the virtual machine. having deleted the other ifaces in your /etc/network/interfaces file except wlan0, should be the root cause of your networking not working (get it? networking/notworking?). *thinking, thinking, thinking... uhhh... right!* and as far as your wlan0 goes - unless you have a usb wireless device connected to your host and passed through to your vm, it ain't gon' work.

so... what you now need to do is add all your interfaces back, or at least eth0, in order to get your bridging working again. also, going the nat route might be better than bridged. some routers and firewalls don't like that. oh, and also make sure you're running wicd before starting wicd-client

i'd go with what brtw2003 has mentioned, and get familiar with networking. it'll not only help you understand the basics, but if you're serious about using bt4, you'll be able to understand networking concepts and use backtrack a lot better.

Oh, well I think I also tried NAT and had the same problem though But I'll try later! Thanks!

Okay new update...

Added eth0 to the interfaces file, and started networking and it responded with that in the picture.
I then proceeded to start wicd, by first doing /etc/init.d/wicd start, and then I openede wicd by going to Internet and then Wicd Network Manager, it opened for about 10 sec, and closed again.
The wicd log gave me this:

/02/19 23:02:48 :: ---------------------------
2010/02/19 23:02:48 :: wicd initializing...
2010/02/19 23:02:48 :: ---------------------------
2010/02/19 23:02:48 :: Automatically detected wireless interface wlan0
2010/02/19 23:02:48 :: found wireless_interface in configuration wlan0
2010/02/19 23:02:48 :: setting wireless interface wlan0
2010/02/19 23:02:48 :: automatically detected wired interface eth0
2010/02/19 23:02:48 :: found wired_interface in configuration eth0
2010/02/19 23:02:48 :: setting wired interface eth0
2010/02/19 23:02:48 :: found wpa_driver in configuration wext
2010/02/19 23:02:48 :: setting wpa driver wext
2010/02/19 23:02:48 :: found always_show_wired_interface in configuration False
2010/02/19 23:02:48 :: found use_global_dns in configuration False
2010/02/19 23:02:48 :: setting use global dns to False
2010/02/19 23:02:48 :: setting use global dns to boolean False
2010/02/19 23:02:48 :: found global_dns_1 in configuration None
2010/02/19 23:02:48 :: found global_dns_2 in configuration None
2010/02/19 23:02:48 :: found global_dns_3 in configuration None
2010/02/19 23:02:48 :: setting global dns
2010/02/19 23:02:48 :: global dns servers are None None None
2010/02/19 23:02:48 :: found auto_reconnect in configuration True
2010/02/19 23:02:48 :: setting automatically reconnect when connection drops
2010/02/19 23:02:48 :: found debug_mode in configuration False
2010/02/19 23:02:48 :: found wired_connect_mode in configuration 1
2010/02/19 23:02:48 :: found signal_display_type in configuration 0
2010/02/19 23:02:48 :: found dhcp_client in configuration 0
2010/02/19 23:02:48 :: Setting dhcp client to 0
2010/02/19 23:02:48 :: found link_detect_tool in configuration 0
2010/02/19 23:02:48 :: found flush_tool in configuration 0
2010/02/19 23:02:48 :: Wireless configuration file found...
2010/02/19 23:02:48 :: Wired configuration file found...
2010/02/19 23:02:48 :: chmoding configuration files 0600...
2010/02/19 23:02:48 :: chowning configuration files root:root...
2010/02/19 23:02:48 :: Using wired interface...eth0
2010/02/19 23:02:48 :: Using wireless interface...wlan0
2010/02/19 23:02:48 :: autoconnecting... wlan0
2010/02/19 23:03:04 :: Traceback (most recent call last):
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 1652, in <module>
2010/02/19 23:03:04 :: main(sys.argv)
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 1623, in main
2010/02/19 23:03:04 :: obj = ConnectionWizard(d_bus_name, auto_connect=auto_connect)
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 188, in __init__
2010/02/19 23:03:04 :: self.AutoConnect(True)
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 379, in AutoConnect
2010/02/19 23:03:04 :: self._wired_autoconnect()
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 392, in _wired_autoconnect
2010/02/19 23:03:04 :: network = self.GetDefaultWiredNetwork()
2010/02/19 23:03:04 :: File "/usr/lib/wicd/wicd-daemon.py", line 1069, in GetDefaultWiredNetwork
2010/02/19 23:03:04 :: config.read(self.wired_conf)
2010/02/19 23:03:04 :: File "/usr/lib/python2.5/ConfigParser.py", line 267, in read
2010/02/19 23:03:04 :: self._read(fp, filename)
2010/02/19 23:03:04 :: File "/usr/lib/python2.5/ConfigParser.py", line 462, in _read
2010/02/19 23:03:04 :: raise MissingSectionHeaderError(fpname, lineno, line)
2010/02/19 23:03:04 :: ConfigParser.MissingSectionHeaderError: File contains no section headers.
2010/02/19 23:03:04 :: file: /etc/wicd/wired-settings.conf, line: 1
2010/02/19 23:03:04 :: '8\x00\x1a\xef\x08\x14j\xff\xff\xff\xff\xff\xff\xf 0[K\xa7U\x00\x17\xb8\x07\xae\x18j\x00Ix\xb58\xb3\r2\ x01L\x0c\xe7P\x82\x83\xa2C}Q\xa1\x19\xf0\xb7*K\xff-Dw\xf1\xefL\xd1KGZ}K@\x86\x05\x00D\x00\x00\x00D\x0 0\x00\x00\x08A:\x01\x00\x18\xf3k:8\x00\x1a\xef\x08 \x14j\xff\xff\xff\xff\xff\xff\x00\\K\xa7U\x00\x17\ xb8\x07\xae\x18j\x00Ix\xb58\xb3\r2\x01L\x0c\xe7P\x 82\x83\xa2C}Q\xa1\x19\xf0\xb7*K\xff-Dw\xf1\xefL\xd1KGZ}K@\x86\x05\x00D\x00\x00\x00D\x0 0\x00\x00\x08A\x02\x01\x00\x18\xf3k:8\x00\x1a\xef\ x08\x14j\xff\xff\xff\xff\xff\xff\x10\\K\xa7U\x00\x 17'

"

So what is wrong?

[brtw2003]

seems you messed up your /etc/wicd/wired-settings.conf
just reinstall wicd (using apt) to switch back to the orig. files !

/brtw2003

[jacobtc]

seems you messed up your /etc/wicd/wired-settings.conf
just reinstall wicd (using apt) to switch back to the orig. files !

/brtw2003

I just did apt-get install wicd, but now, it won't even open anymore?

[Valkyrie]

I just did apt-get install wicd, but now, it won't even open anymore?

Just out of interest. How much ram have you dedicated to the BT4 virtual machine? I dedicated only 512mb as my dell 6100 only has 1 gig ram..I had major problems with konsole, wicd hanging etc.. on vmware. If u do have 512mb dedicated I rekon its too little for BT4 final, 512mb worked ok for me on beta though.

[w1sh3s]

The SS that you posted says that you have started the service but you need to start the GUI. So click into the internet in the BT symbol and click Wicd.

[jacobtc]

Just out of interest. How much ram have you dedicated to the BT4 virtual machine? I dedicated only 512mb as my dell 6100 only has 1 gig ram..I had major problems with konsole, wicd hanging etc.. on vmware. If u do have 512mb dedicated I rekon its too little for BT4 final, 512mb worked ok for me on beta though.

got 1gig dedicated, so that should be enough...

The SS that you posted says that you have started the service but you need to start the GUI. So click into the internet in the BT symbol and click Wicd.

I already opened it, but it just closes after 10 sec...

No one?....