Announcement

Collapse
No announcement yet.

Not to 'autostart'

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Not to 'autostart'

    I have installed Superkaramba and a couple of widgets on it. However, it seems that my system is not able to take the load and gets slow when it runs. This I know because when I quit it completely, the system perks up a bit.
    My query is that how do I stop SuperKaramba from starting automatically after login. I do not want to uninstall it. Searched the forums for "autostart" and found an app named "kcontrol_autostart" which in its description said "a kcontrol center module to manage applications at startup" So I installed it. However, when I go to this particular module in the Kcontrolcenter, it doesn't show up any application in the list (and hence the inability to remove the particular application from the list)

    Any ideas, either through this "autostart" module or any other method?
    Triple booting Kubuntu Intrepid with XP and Ubuntu Hardy <br />Intel Pentium DualCore 2 Ghz, 1 GB RAM Intel 945GM MoBo
    Tags: None
    • Top
    • Bottom
    #2
    Re: Not to 'autostart'

    Check ~/.kde/Autostart. Things in there get run when you log in.
    For external use only.
    • Top
    • Bottom

    Comment

      #3
      Re: Not to 'autostart'

      My query is that how do I stop SuperKaramba from starting automatically after login.
      Do you leave SuperKaramba running when you log out ?

      K > System Settings >| Advanced - tab |> Session Manager

      There is On Login:

      Restore previous session
      Will save all applications running on exit and restore them when they next start up.

      Restore manually saved session
      Allows the session to be saved at any time via "Save Session" in the K-Menu. This means the currently started application will reappear when they next start up.

      Start with an empty session
      Do not save anything. Will come up with an empty desktop on next start.


      If you use Restore previous session it would be a good idea to use Runaway Process Catcher (Detect and end broken processes which consume too much CPU time).

      Right click panel > Add Applet to Panel > Runaway Process Catcher
      Before you edit, BACKUP !

      Why there are dead links ?
      1. Thread: Please explain how to access old kubuntu forum posts
      2. Thread: Lost Information
      • Top
      • Bottom

      Comment

        #4
        Re: Not to 'autostart'

        Originally posted by Rog131
        Do you leave SuperKaramba running when you log out ?
        Earlier I used to leave it running. Since last couple of times, I quit it before logging out/shutting. Still it starts automatically after next login.

        Originally posted by Rog131
        K > System Settings >| Advanced - tab |> Session Manager

        There is On Login:

        Restore previous session
        Will save all applications running on exit and restore them when they next start up.

        Restore manually saved session
        Allows the session to be saved at any time via "Save Session" in the K-Menu. This means the currently started application will reappear when they next start up.

        Start with an empty session
        Do not save anything. Will come up with an empty desktop on next start.


        If you use Restore previous session it would be a good idea to use Runaway Process Catcher (Detect and end broken processes which consume too much CPU time).

        Right click panel > Add Applet to Panel > Runaway Process Catcher
        I do use "Restore previous session".
        I added the "Runaway Process Catcher" applet to the panel, and it keeps showing something similar to this:
        A program call 'Kwin' is slowing down the others on your machine. It may have a bug that is causing this or it may just be busy.
        Would you like to stop the program?
        Similar message appeared for Firefox too. Should I stop "kwin"? I don't know what does that program do? Is it safe to stop it? Is there anything else I can do to perk up the machine?

        Originally posted by SheeEttin
        Check ~/.kde/Autostart. Things in there get run when you log in.
        The directory '~/.kde/Autostart' contains only one file named '.directory' (gave the command 'ls -a')
        what does it mean?

        And still the original question remains, i.e., how do I stop a particular program from autostarting after login?

        Triple booting Kubuntu Intrepid with XP and Ubuntu Hardy <br />Intel Pentium DualCore 2 Ghz, 1 GB RAM Intel 945GM MoBo
        • Top
        • Bottom

        Comment

          #5
          Re: Not to 'autostart'

          Should I stop "kwin"? I don't know what does that program do? Is it safe to stop it?
          KWin is a window manager for the X Window System.

          KWin
          http://en.wikipedia.org/wiki/KWin

          And it is part of Kde. So don't stop it. But there is something wrong. KWin shouldn't use resources that much. Are you using Beryl/Compiz ?

          Have you tried K>System>KDE System Guard (ksysguard) ?. Is your CPU load high ?


          And still the original question remains, i.e., how do I stop a particular program from autostarting after login?
          - If it isn't in autostart folder - it shouldn't run
          Is /home/user/.kde/Autostart/ your autostart folder ? You can move it.

          - If it isn't running when you log out (Restore previous session) - it shouldn't run.
          Before you log out - check ksysguard, what processes do you have on. Or use Start
          with an empty session


          Before you edit, BACKUP !

          Why there are dead links ?
          1. Thread: Please explain how to access old kubuntu forum posts
          2. Thread: Lost Information
          • Top
          • Bottom

          Comment

            #6
            Re: Not to 'autostart'

            Originally posted by Rog131
            Are you using Beryl/Compiz ?
            No, I am not using Beryl/Compiz. However, I have customised window decorations a bit.


            Originally posted by Rog131
            Have you tried K>System>KDE System Guard (ksysguard) ?. Is your CPU load high ?
            CPU load ranges between 50-60 percent, but frequent spikes to more than 95 percent when I move windows between different desktops or open a new application and stuff like that.

            Originally posted by Rog131
            - If it isn't in autostart folder - it shouldn't run
            Is /home/user/.kde/Autostart/ your autostart folder ? You can move it.
            I checked the "About Me" section of System Settings. It shows the autostart path as "/home/myself/.kde/Autostart/"

            Originally posted by Rog131
            - If it isn't running when you log out (Restore previous session) - it shouldn't run.
            As mentioned earlier, Superkaramba starts after login even if it wasn't running before the previous logout (also Kopete and Amarok). My autostart path is the same as mentioned above and it contains nothing but a file named ".directory". (Hope I had given the correct command, i.e., "ls -a", to list the files). Do you need any other info?

            PS: I would also like to share that "top" command shows 1 'zombie' task/process. Would that be a problem?
            Triple booting Kubuntu Intrepid with XP and Ubuntu Hardy <br />Intel Pentium DualCore 2 Ghz, 1 GB RAM Intel 945GM MoBo
            • Top
            • Bottom

            Comment

              #7
              Re: Not to 'autostart'

              I think I figured this out. 8)
              The applications used to start automatically after login (even when they were stopped before previous logout/shutdown) because I used to shutdown/restart the system from a terminal (sudo shutdown -h/r now) for some reason. Tonight when I restarted by first logging out of KDE and then restarting from KDM screen, amarok and superkaramba did not start automatically, since I had stopped it earlier.

              Now that the solution is found, can some one explain the difference between shutting down from a terminal and from KDM (Direct shutdown from KDE does not work as in case of many others). I thought both the ways the system would be brought down in identical manner.
              Triple booting Kubuntu Intrepid with XP and Ubuntu Hardy <br />Intel Pentium DualCore 2 Ghz, 1 GB RAM Intel 945GM MoBo
              • Top
              • Bottom

              Comment

                #8
                Re: Not to 'autostart'

                Nope. If you use shutdown from a terminal, KDE doesn't do its shutdown magic, it just gets told to shut down by the system and complies. Doesn't do any session saving.

                I'm pretty familiar with this because KDE & I had problems with shutting down properly earlier. Now I can use the KDE shutdown options, but it gives the same behavior of a console shutdown.
                Incidentally, I have an instance of Kate that seems to have lodged itself in my saved session... I can't seem to get rid of it.
                For external use only.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X