search

pentoo / pentoo-historical

read-only historical backup of pentoo from googlecode
https://code.google.com/p/pentoo/
2 stars 1 forks source link

start up wifi error #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
http://imageshack.us/gal.php?id=q52kyN3l1d7h2qPT2dqV
http://img29.imageshack.us/img29/6303/errorhv.png
http://img442.imageshack.us/img442/8636/error2r.png

I've had it since the alpha release.
Hope those work :/

-B

Original issue reported on code.google.com by prof.bri...@gmail.com on 6 Jul 2012 at 1:21

GoogleCodeExporter commented 9 years ago 
Here is MORE helpful information: wird.log

2012/07/19 08:23:39 :: ---------------------------
2012/07/19 08:23:39 :: wicd initializing...
2012/07/19 08:23:39 :: ---------------------------
2012/07/19 08:23:39 :: wicd is version 1.7.2.3 761
2012/07/19 08:23:39 :: setting backend to external
2012/07/19 08:23:40 :: trying to load backend external
2012/07/19 08:23:40 :: successfully loaded backend external
2012/07/19 08:23:40 :: trying to load backend external
2012/07/19 08:23:40 :: successfully loaded backend external
2012/07/19 08:23:40 :: Automatically detected wireless interface wlan0
2012/07/19 08:23:40 :: setting wireless interface wlan0
2012/07/19 08:23:40 :: automatically detected wired interface eth0
2012/07/19 08:23:40 :: setting wired interface eth0
2012/07/19 08:23:40 :: setting wpa driver wext
2012/07/19 08:23:41 :: setting use global dns to False
2012/07/19 08:23:41 :: setting global dns
2012/07/19 08:23:41 :: global dns servers are None None None
2012/07/19 08:23:41 :: domain is None
2012/07/19 08:23:41 :: search domain is None
2012/07/19 08:23:42 :: setting automatically reconnect when connection drops 
True
2012/07/19 08:23:43 :: Setting dhcp client to 0
2012/07/19 08:23:43 :: Wireless configuration file found...
2012/07/19 08:23:43 :: Wired configuration file found...
2012/07/19 08:23:43 :: chmoding configuration files 0600...
2012/07/19 08:23:43 :: chowning configuration files root:root...
2012/07/19 08:23:43 :: Using wireless interface...wlan0
2012/07/19 08:23:43 :: Using wired interface...eth0
2012/07/19 08:23:49 :: Autoconnecting...
2012/07/19 08:23:49 :: No wired connection present, attempting to autoconnect 
to wireless network
2012/07/19 08:23:50 :: Unable to autoconnect, you'll have to manually connect
2012/07/19 08:23:54 :: Autoconnecting...
2012/07/19 08:23:54 :: No wired connection present, attempting to autoconnect 
to wireless network
2012/07/19 08:23:55 :: Unable to autoconnect, you'll have to manually connect
2012/07/19 08:23:59 :: Autoconnecting...
2012/07/19 08:23:59 :: No wired connection present, attempting to autoconnect 
to wireless network
2012/07/19 08:24:00 :: Unable to autoconnect, you'll have to manually connect
2012/07/19 08:24:04 :: Autoconnecting...
2012/07/19 08:24:04 :: No wired connection present, attempting to autoconnect 
to wireless network
2012/07/19 08:24:05 :: hidden
2012/07/19 08:24:05 :: Unable to autoconnect, you'll have to manually connect
2012/07/19 08:25:03 :: trying to load backend external
2012/07/19 08:25:03 :: trying to load backend ioctl
2012/07/19 08:25:03 :: WARNING: python-iwscan not found, falling back to using 
iwlist scan.
2012/07/19 08:25:03 :: WARNING: python-wpactrl not found, falling back to using 
wpa_cli.
2012/07/19 08:25:43 :: Connecting to wireless network The-Co.
2012/07/19 08:25:44 :: Putting interface down
2012/07/19 08:25:44 :: Releasing DHCP leases...
2012/07/19 08:25:44 :: Setting false IP...
2012/07/19 08:25:44 :: Stopping wpa_supplicant
2012/07/19 08:25:44 :: Flushing the routing table...
2012/07/19 08:25:44 :: Putting interface up...
2012/07/19 08:25:46 :: Generating psk...
2012/07/19 08:25:47 :: Attempting to authenticate...
2012/07/19 08:25:49 :: Running DHCP with hostname livecd
2012/07/19 08:25:49 :: dhcpcd[9235]: version 5.5.6 starting
2012/07/19 08:25:49 ::
2012/07/19 08:25:49 :: dhcpcd[9235]: all: not configured to accept IPv6 RAs
2012/07/19 08:25:49 ::
2012/07/19 08:25:49 :: dhcpcd[9235]: wlan0: broadcasting for a lease
2012/07/19 08:25:49 ::
2012/07/19 08:25:52 :: dhcpcd[9235]: wlan0: offered 1.3.3.102 from 1.3.3.1
2012/07/19 08:25:52 ::
2012/07/19 08:25:52 :: dhcpcd[9235]: wlan0: acknowledged 1.3.3.102 from 1.3.3.1
2012/07/19 08:25:52 ::
2012/07/19 08:25:52 :: dhcpcd[9235]: wlan0: checking for 1.3.3.102
2012/07/19 08:25:52 ::
2012/07/19 08:25:57 :: dhcpcd[9235]: wlan0: leased 1.3.3.102 for 43200 seconds
2012/07/19 08:25:57 ::
2012/07/19 08:25:57 :: dhcpcd[9235]: forked to background, child pid 9275
2012/07/19 08:25:57 ::
2012/07/19 08:25:57 ::
2012/07/19 08:25:57 :: DHCP connection successful
2012/07/19 08:25:57 :: not verifying
2012/07/19 08:25:58 :: Connecting thread exiting.
2012/07/19 08:25:58 :: Sending connection attempt result success

Original comment by prof.bri...@gmail.com on 19 Jul 2012 at 12:33

GoogleCodeExporter commented 9 years ago 
NOTE:  Running the LIVEUSB I do not get this error.  After a fresh install to 
HDD I get this error.

Original comment by prof.bri...@gmail.com on 19 Jul 2012 at 12:34

GoogleCodeExporter commented 9 years ago 
You need to update your fresh install. For example, this is what you have with 
the fresh system:
[ebuild  N     ] dev-python/pytz-2012c  163 kB
[ebuild  N     ] dev-python/Babel-0.9.6  1,779 kB
[ebuild  N     ] dev-python/notify-python-0.1.1-r2  USE="-examples" 210 kB
[ebuild   R   ~] net-misc/wicd-1.7.2.3  USE="X gtk libnotify* ncurses nls 
pm-utils -ambiance (-ioctl) -mac4lin" 444 kB

Original comment by blshkv on 20 Jul 2012 at 2:15

GoogleCodeExporter commented 9 years ago 
Ok, closing it for now. Please upgrade first and reopen the bug if it's not 
fixed.

Original comment by blshkv on 26 Jul 2012 at 3:57

GoogleCodeExporter commented 9 years ago 
I've also had this, both with beta2 and now with beta3 after installation from 
iso to hd.
My 'fix' was to add wicd to the default runlevel with
rc-update add wicd default

Original comment by Wuod...@gmail.com on 16 Nov 2012 at 6:31

GoogleCodeExporter commented 9 years ago 
Does this affect livecd or hdd install? If it only affects hdd install then we 
should just add a line to the installer to add wicd to the default runlevel.

Original comment by sidhayn on 16 Nov 2012 at 9:37

GoogleCodeExporter commented 9 years ago 
Only after install.  For what it's worth, backtrack forums has a fix for this.  
-B

Original comment by prof.bri...@gmail.com on 16 Nov 2012 at 4:15

GoogleCodeExporter commented 9 years ago 
So do we want to auto enable wifi for the user on install? Or is that bad?

I suppose since it works by default on the livecd we should do that for the 
install as well but I'm not a huge fan of sending packets without asking the 
user.  Thoughts?

Original comment by sidhayn on 16 Nov 2012 at 7:55

GoogleCodeExporter commented 9 years ago 
@prof.brian.j
Mind posting a link to that fix backtrack has for it?

Here it happens only after install to hdd, on 2 different laptops.

If we are fine with starting network right at default level, I could add this 
to the installer.

Original comment by Wuod...@gmail.com on 17 Nov 2012 at 1:20

GoogleCodeExporter commented 9 years ago 
Backtrack thread# 41769
FIX: 
dpkg-reconfigure
update-rc.d wicd defaults

I realise that's for debian, but should be relevant.

Original comment by prof.bri...@gmail.com on 17 Nov 2012 at 3:47

GoogleCodeExporter commented 9 years ago 
Lol.... that isn't relevant at all.

The proper gentoo fix to add wicd to the default runlevel is

rc-update add wicd default

I'm not really thrilled with that though, I would actually rather have wicd not 
auto-start at all...

Original comment by sidhayn on 17 Nov 2012 at 4:25

GoogleCodeExporter commented 9 years ago 
Currently `wicd-gtk --tray` is started with XFCE.

If you want to disable this, use the attached patch to 
/etc/xdg/autostart/wicd-tray.desktop.
That file is generated by emerging net-misc/wicd, so you must patch/overwrite 
the above file during creation of the iso.

Doesn'tue wi mean the mentioned errors really go away :(

---------------------------

For the errors this bug is about:
To me it seems like the wicd-client attempts to autostart wicd, but then fails
to connect to it because it tries to soon.
Just for fun, the other patch for /usr/share/wicd/gtk/wicd-client.py solves
the issue with a sleep 0.5s ... lame but works.

Original comment by Wuod...@gmail.com on 26 Nov 2012 at 8:34

Attachments:

GoogleCodeExporter commented 9 years ago 
How do we stop "wicd-gtk -tray" from starting with xfce?

Original comment by sidhayn on 10 Mar 2013 at 3:26

GoogleCodeExporter commented 9 years ago 
Read above ;)

= How I found out =
Open: App-Menu > Settings > Session and Startup > App. Autostart
Deselect Wicd and click Close

The attached file is created as /root/.config/autostart/wicd-tray.desktop
This is just for root user, for global setting, just add the same to 
/etc/xdg/autostart/wicd-tray.desktop, see patch above.

Original comment by Woudan0@gmail.com on 2 Apr 2013 at 2:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Just committed wicd-1.7.9999_p874.ebuild, all ZC has to do is keyword that in 
our profile - didn't dare to do it straight away.

If we don't want that 9999-ebuild, I could prepare same stuff for Gentoos 
wicd-ebuild.

= wicd-1.7.9999_p874.ebuild =
- builds wicd-1.7 from upstreams repo
- adds a use flag "+gtk-autostart"
- that flag is disabled in pentoo profile
- add a sleep 0.5s when daemon is started

Pushed everything except the "gtk-autostart" thing upstreams.

Original comment by Wuod...@gmail.com on 2 Apr 2013 at 10:38

GoogleCodeExporter commented 9 years ago 
wicd is looking for the "old" name eth0 by default. You might want to fix it 
too.

Original comment by blshkv on 13 Apr 2013 at 1:42

GoogleCodeExporter commented 9 years ago 
This is as good a place as any.  I think the "new" style names are a bit buggy 
with a lot of software and users likely just aren't ready for it.  I was going 
to disable the new style names, what does the rest of the dev team think about 
that?

Original comment by sidhayn on 14 Apr 2013 at 11:18

GoogleCodeExporter commented 9 years ago 
a quick look showed two minor issues with wicd after installation

it tried to backup /etc/resolv.conf and failed because I didn't have one
the stale pid file was still at /var/run/wicd/wicd.pid  /var/run really 
shouldn't have been moved over at all so I'll leave this note here for me to 
retest on a newer iso.

Original comment by sidhayn on 21 May 2013 at 2:44