KDE startup and wifi initialization under Feisty

[Larry Hartman]

Messing about on the internet and come across another avenue.....would KDE 
autostart bring it up more quickly?  

BTW, I appreciate this answer as it helps explain things more 
clearly.....didnt have this issue on Dapper and Edgy though.

Larry

On Friday 30 March 2007 09:16:52 pm Daniel Pittman wrote:
> Nigel Ridley <nigel at rmk.co.il> writes:
> > Larry Hartman wrote:
> >> I need to tweak a setting.
> >>
> >> When I log into KDE Korn, KWeather, Kopete, and Akregator all
> >> initialize prior to KNetworkmanager, causing multiple annoying
> >> advisory boxes to appear with messages like "unknown host" etc.
> >> KNetworkmanager does work, I just need to make this application first
> >> in sequence compared to the other internet-based applications.  Can
> >> anyone advise?
> >
> > You have to change the order of the initialization of the scripts.
>
> No: the problem isn't the standard init scripts -- the problem is that
> NetworkManager waits for a GUI client to instruct it to connect before
> attaching to the network.
>
> That application, KNetworkManager, runs concurrent with the other
> applications at session startup -- and consequently the network isn't
> ready when the applications are.
>
> Playing with your init script order isn't going to help anything here,
> sadly, since they are not involved.
>
> Sorry I don't have anything positive to add, too.  I don't know a
> solution to this other than to wait for KDE to bind more closely to a
> "network presence" system of some sort.
>
> Regards,
>         Daniel
> --
> Digital Infrastructure Solutions -- making IT simple, stable and secure
> Phone: 0401 155 707        email: contact at digital-infrastructure.com.au
>                  http://digital-infrastructure.com.au/