Jump to content
xisto Community
abhiram

Gnome Running In The Background In Kde Something is not right....

Recommended Posts

Hi, recently, a few days ago, I logged into GNOME for a spell and then logged out and didn't go back to it again. I started using KDE but it's been slowing down a bit these days. I gave the command 'ps -e' and it shows GNOME and Nautilus running in the background. Here's a sample output:

PID TTY          TIME CMD    1 ?        00:00:04 init
    2 ?        00:00:00 keventd
    3 ?        00:00:00 ksoftirqd_CPU0
    4 ?        00:00:00 kswapd
    5 ?        00:00:00 bdflush
    6 ?        00:00:00 kupdated
  10 ?        00:00:00 mdrecoveryd
  11 ?        00:00:00 kjournald
  61 ?        00:00:01 syslogd
  64 ?        00:00:00 klogd
  93 ?        00:00:00 udevd
  279 ?        00:00:00 khubd
2809 ?        00:00:00 rpc.portmap
2815 ?        00:00:00 inetd
2819 ?        00:00:00 sshd
2823 ?        00:00:00 named
2834 ?        00:00:00 crond
2836 ?        00:00:00 atd
2839 ?        00:00:00 sendmail
2842 ?        00:00:00 sendmail
2886 ?        00:00:00 httpd
2890 ?        00:00:00 smbd
2891 ?        00:00:00 nmbd
2894 ?        00:00:00 httpd
2895 ?        00:00:00 httpd
2896 ?        00:00:00 httpd
2897 ?        00:00:00 httpd
2898 ?        00:00:00 gpm
2901 tty6    00:00:00 agetty
2902 ?        00:00:00 kdm
2903 ?        00:00:00 httpd
2910 ?        00:00:08 X
2917 ?        00:00:00 kdm
3032 ?        00:00:00 startkde
3164 ?        00:00:00 kdeinit
3172 ?        00:00:00 kdeinit
3182 ?        00:00:00 kdeinit
3192 ?        00:00:00 kdeinit
3288 ?        00:00:00 kdeinit
3326 ?        00:00:04 artsd
3331 ?        00:00:00 kdeinit
3332 ?        00:00:00 kwrapper
3335 ?        00:00:00 kdeinit
3338 ?        00:00:00 kdeinit
3368 ?        00:00:01 kdeinit
3392 ?        00:00:00 kdeinit
3417 ?        00:00:00 kdeinit
3421 ?        00:00:00 nautilus
3477 ?        00:00:00 gaim
3482 ?        00:00:00 gconfd-2
3497 ?        00:00:00 kdeinit
3519 ?        00:00:04 amarokapp
3587 ?        00:00:00 kdeinit
3810 ?        00:00:00 bonobo-activati
3818 ?        00:00:00 nautilus
3819 ?        00:00:00 nautilus
3821 ?        00:00:00 gnome-vfs-daemo
3831 ?        00:00:00 gnome-vfs-daemo
3832 ?        00:00:00 gnome-vfs-daemo
3867 ?        00:00:00 amarokapp
3869 ?        00:00:00 nautilus
3870 ?        00:00:00 nautilus
3874 ?        00:00:00 mapping-daemon
3915 ?        00:00:00 amarokapp
3947 ?        00:00:01 amarokapp
3948 ?        00:00:04 amarokapp
3950 ?        00:00:00 amarokapp
3989 ?        00:00:00 kdeinit
3991 ?        00:00:00 kdeinit
3992 ?        00:00:00 kdeinit
3994 ?        00:00:00 kdeinit
4085 ?        00:00:00 kdeinit
4095 ?        00:00:00 kdeinit
5694 ?        00:00:00 firefox
5712 ?        00:00:00 run-mozilla.sh
5717 ?        00:00:08 firefox-bin
5745 ?        00:00:00 firefox-bin
5746 ?        00:00:00 firefox-bin
5759 ?        00:00:00 firefox-bin
5982 ?        00:00:00 kdeinit
5995 pts/1    00:00:00 bash
6099 ?        00:00:00 amarokapp
10616 pts/1    00:00:00 ps
10617 ?        00:00:00 nmbd


Why is it constantly starting Nautilus when I reboot? It starts back even if kill it.

Also, why are there so many kdeinits? Ever since I logged into GNOME, my screensaver also stopped working... in both KDE and FLUXBOX.

Any ideas?
Thanks.

Share this post


Link to post
Share on other sites

try starting "ps -f" instead of "ps -e", in order to see also the parent process ID. Then you will be able to see which process started your kdeinit, and you will be able to debug more indepth.RegardsYordan

Share this post


Link to post
Share on other sites

Thanks for the tip Yordan, that's pretty useful.

I've played around with it for a while and now it no longer starts Nautilus... but the 'ps -fe' is showing some pretty weird things:

abhiram  3171    1  0 21:12 ?        00:00:00 kdeinit Running...abhiram  3179    1  0 21:12 ?        00:00:00 kdeinit: dcopserver --nosid
abhiram  3192  3171  0 21:12 ?        00:00:00 kdeinit: klauncher
abhiram  3202    1  0 21:12 ?        00:00:00 kdeinit: kded
abhiram  3299  3202  0 21:12 ?        00:00:00 kdeinit: kded
abhiram  3346    1  0 21:12 ?        00:00:00 kdeinit: kaccess
abhiram  3351    1  0 21:12 ?        00:00:00 kdeinit: ksmserver
abhiram  3356  3171  0 21:12 ?        00:00:00 kdeinit: kwin -session 10aed6dad7000111203124600000003140000_1
abhiram  3384    1  1 21:12 ?        00:00:01 kdeinit: kdesktop
abhiram  3406    1  0 21:12 ?        00:00:00 kdeinit: kicker
abhiram  3429    1  0 21:12 ?        00:00:00 kdeinit: kmix -session 10aed6dad7000112784068600000033500012_1
abhiram  3481    1  0 21:12 ?        00:00:00 kdeinit: knotify
abhiram  3498  3171  0 21:12 ?        00:00:00 kdeinit: kio_file file /tmp/ksocket-abhiram/klauncher2flH6b.sl


Are these kdeinits ok? kmix, klauncher, knotify and kdesktop I can understand... but what about the others?

Also, any idea why the screensaver won't start?

Share this post


Link to post
Share on other sites

lso, why are there so many kdeinits?

KDE_INIT is like a library linker for KDE. kde will load kdeinit for each kde program you start.

if you are interesting in speeding up program loading time, and removing the need for kdeinit thenmaybe you should have a look at pre-link.

Prelink is a tool which calculaltes linking tables, and caches them.
when KDE is pre-linked, KDE_INIT is nolonger needed, and will not run.
Also program loading speeds will be improved, especially ones that use a lot of libraries.

have a look at prelink how-to's
prelink rquires that libraries are compiled with the compiler argument -fPIC.
some distro's do this, some dont, try and find a tutorial specific to you distro, you may need to re-compile some packages.

Share this post


Link to post
Share on other sites

I've looked around for prelink, but from what I've heard, it's more useful for older machines. With new systems, there really isn't much of a speed boost ... atleast, not on Slackware. Anyways, KDE isn't too slow on my system. I just wanted to know if KDEINIT was a bug or not. Thanks for clearing that up B).I'm just waiting to get some free time on my hand so I can try out gentoo.

Share this post


Link to post
Share on other sites

Are they present if you reboot your system ?


Yup, they're there always... whether I reboot or not.
I'm using Kernel 2.4 by the way. Maybe that has something to do with it. I don't recall having so many in Mandrake (not 'driva' when I used it a year ago B)) which was running kernel 2.6. Come to think of it I never noticed it until recently when my screensaver stopped working.

Share this post


Link to post
Share on other sites

Well... i've been trying to install Kernel 2.6 for some time now, but keep running into some problems. Slackware gives you 2.4 by default and you have to upgrade to 2.6 on your own. But as far as it goes, 2.4 is working fine, so I really don't have a problem with it. A little slow, but faster than windows B).

Share this post


Link to post
Share on other sites

from what i remember about slackware, in version 10.X the 2.6 series kernel was in a testing folder in the packages directory of the install disks.i think its just a mattr of installing it, then editing grub or lilo.I think Slackware 10.X is 2.6 ready.I liked slackware, but didnt like the absence of an optimised kernel etc.the slaware kernel is i486 otimised i think, or atleast it was in 10.0.u used to re-compile it with Athlon optimisation.Not that the performace boost is noticable or anything, i just like re-compiling things.. lol, such a nerd B)

Share this post


Link to post
Share on other sites

Yea, some people did install 2.6 directly during installation without any problems. But when I was installing slackware, I wanted the most stable system and so B).... I installed only kernel 2.4.

Share this post


Link to post
Share on other sites

Nah ... I tried, but nothing worked. Anyways, I finally formatted my 8 month old slackware and got gentoo on it now. I think there are some issues with gnome and slackware anyway. That's why Paul Volkerding (the guy who maintains slackware) finally removed gnome from slack 10.2 after 3 years of thinking back and forth. No problems of that sort with gentoo right now... thanks anyway ;).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.