Very slow bootup and dns lost at every boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Hi
i have a panasonic cf73 with edgy eft, some speed tweaks, prelink, readahead, preload.
until i used only wifi to connect to internet everything worked
i had to use ethernet to connect, from then , every bootup takes good 5 mins, every time even the terminal won't load before 4-5 mins, even if i go to tty1 and try to call for example sudo mc, hangs there until 5 mins have passed.
This is very annoying, moreover the laptop loses dns at every bootup, so i have to wait 5 mins, then open networks, put the dns, and then i am able to use it..
sometime is VERY swift in loading, but usually after i delete .metacity and .nautilus, and only for that boot, then hangs slow again..
i tried to disable prelink, readahead, and other things, i tried to put fixed DNS as written in a post on ubuntuforums with no luck.
Once the pc starts is very stable, but i can't stand those 5-6 minutes bootup time, looking at the gnome splashscreen, or at an empty desktop with no icons..
I forgot to add i also have compiz, starting it or not, has no effect, and is the last program to load usually.
i am available to any test.
The slow login/desktop bug appears to have been around for a while. The bug is reported in edgy & feisty and they are mostly unconfirmed and mostly of undecided importance. Although I'm very happy with feisty, I am finding this bug a bit bothersome so I thought I'd do some research through the bug archives.
I think this bug has been reported numerous times. The bug list that follows, I think are reports of effectively the same bug.
Bug #78263 - claims workaround (feisty)
Bug #78493 (edgy)
Bug #79466 (edgy)
Bug #79661 (edgy)
Bug #80827 - claims workaround (edgy)
Bug #92997 - claims workaround (feisty)
Bug #94048 (feisty)
Bug #110616 (feisty?)
Bug #110775 (feisty)
Bug #110187 - reports slow desktop as a side effect of other network config issues. (feisty)
---------------
Bug #95264 - Maybe related (not clear) (feisty)
Bug #93447 - Maybe related (not clear) (edgy)
---------------
It seems most discussions are blaming this bug on one or more of:
Network-manager
avahi
hosts file
resolve file
static IP addresses
no network connection.
I can't vouch for the claimed workarounds - but I intend on investigating them further.
The person who solves this one will likely 'kill a number of bugs with one stone'.
I hope I'm not being too forward by presenting such a list but I am rather keen to see this bug solved. I hope this list helps to unify further discussion & prompts some further thought on the matter.
(note: I have posted it to all above bug reports so that all are in the loop)