KDE startup and wifi initialization under Feisty

Daniel Pittman daniel at rimspace.net
Sat Mar 31 02:16:52 BST 2007

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.

Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707        email: contact at digital-infrastructure.com.au

More information about the kubuntu-users mailing list