Announcement

Collapse
No announcement yet.

How to start KNetworkManager on the early stage

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How to start KNetworkManager on the early stage

    Every time my Kubuntu starts up a set of net application are loaded (KMail, Kopete, Skype, etc).
    But the problem is that they start before KNetworkManager obtains wi-fi connection. And then KMail show an error message, Kopete stays offline, etc.

    I can manually configure wpa_supplicant and dhclient and start them even before KDE, but as I understand in such a case I wil not be able to use KNetworkManager to see network status, reconfigure connection of needed and so on.

    Can I make KNetworkManager to start at least before all my net applications?

    #2
    Re: How to start KNetworkManager on the early stage

    Hm, I suppose you could write a start up script that starts all internet dependent apps only after you have successfully pinged a site...
    Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

    Comment


      #3
      Re: How to start KNetworkManager on the early stage

      Yes, I can...

      But for instance once started a Skype it then starts automatically and places an icon to tray but I don't know where does it configured for startup.

      Can someone please explain me how does KDE starts applications? As I understand it saves all active applications somewhere and than starts it again after KDE is started?

      Comment


        #4
        Re: How to start KNetworkManager on the early stage

        AFAIK, there are two "normal" ways of determining how kde starts up:

        1. You put a link in the ~/.kde/Autostart folder or, in KDE4, you use System Settings - Autostart

        2. In SystemSettings / Session Manager you instruct KDE to load
        a. the last instance
        b. a saved instance
        c. an empty instance

        My guess is that you have a serious bout of 2b To get rid of it you want 2c, i.e. start KDE without any programs. Instead you want to control your stuff manually by putting your script in ~/.kde/Autostart

        Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

        Comment


          #5
          Re: How to start KNetworkManager on the early stage

          Oh, thanx! I didn't even thinked about session manager's options
          Start with an empty session + manual autostart it seems to be what I need. Thanx!




          Comment

          Users Viewing This Topic

          Collapse

          There are 0 users viewing this topic.

          Working...
          X