Version: (using KDE 4.3.0) Installed from: Ubuntu Packages The networkmanager applet finally seems to mature. Great work :-) What currently seems to be a problem is the fact that it is not priotised in session management. I have Konqueror restoring first, which means that Konqui does not find a network. This behaviour should be changed.
Funny, I thought I already discussed this quite recently. What you request, starting network apps in serial after a network is up, can't be done because after knetworkmanager starts, a network associate and authentication could take up to 45s which would make login unacceptably slow or even wait for some longer timeout before giving up waiting for knetworkmanager. The correct solution is to make network apps able to respond to networking status changes at any time so they show an 'offline mode' view of what they do until networking comes up. The infrastructure for this is there in kdelibs, it just needs implementing in the apps. I hope that makes sense.
This makes sense. I filed a bug report against Konqui https://bugs.kde.org/show_bug.cgi?id=205007 Firefox also has the problem, but I fear filling a bug report there is useful. They do not really support the Linux plattform well. Would there be a way securing that non-KDE-apps which need a network are only restored when network is there? In this case I am only aware of Firefox, so this may be not so big a problem as if the whole process is slowed down.
> Would there be a way securing that non-KDE-apps which need a network are only > restored when network is there? NetworkManager is a common desktop-independent standard way. KDE just provides convenience wrappers around its status functions.