This may apply to my multiseat setup, but I am not sure. After upgrading to the latest wicd in testing, it no longer automatically connects to any interface (wired and wireless). Pressing disconnect all I am able to connect to the wireless network, but still not the wired. After restarting the wicd daemon, I am able to connect to both networks and automatic connection works as well. Ceni however works fine. I am wondering if anyone else has had a similar problem?
Dave
topic title: wicd and wired network
3 posts
• Page 1 of 1
-
Posts: 1,062
- Joined: 20 Jan 2010
-
Posts: 54
- Joined: 30 May 2010
#2
What you describe is why I 'just use ceni' 95% of the time. If one of them works, that's what matters to me.
Best wishes!
Best wishes!
-
Posts: 1,062
- Joined: 20 Jan 2010
#3
I agree with this, wicd has worked 95 % of the time for me though ceni is still always there as a backup. In the 5% that wicd crashes it crashes hard __{{emoticon}}__ . After fiddling around, removing testing, installing stable, removing stable installing unstable, changing config file after config file, then changing them back, changing routers, changing nic cards, running live cd and rebuilding to the current state, I finally found the problem. In my slight brain wave I decided to check the dependency tree __{{emoticon}}__ , (probably should have done this sooner __{{emoticon}}__ ) Even though this is fresh out of the debian repository, there is a package that is required yet missing as a dependency in the .deb __{{emoticon}}__ . It is: dhcp3-client.
Simply installed it and all was back to normal __{{emoticon}}__
SaminBare wrote: If one of them works, that's what matters to me.
I agree with this, wicd has worked 95 % of the time for me though ceni is still always there as a backup. In the 5% that wicd crashes it crashes hard __{{emoticon}}__ . After fiddling around, removing testing, installing stable, removing stable installing unstable, changing config file after config file, then changing them back, changing routers, changing nic cards, running live cd and rebuilding to the current state, I finally found the problem. In my slight brain wave I decided to check the dependency tree __{{emoticon}}__ , (probably should have done this sooner __{{emoticon}}__ ) Even though this is fresh out of the debian repository, there is a package that is required yet missing as a dependency in the .deb __{{emoticon}}__ . It is: dhcp3-client.
Simply installed it and all was back to normal __{{emoticon}}__