[FreeNX-kNX] kded4 runs away. A bit O.T.for this group now

Julie Ashworth julie.ashworth at berkeley.edu
Tue Oct 18 18:49:22 UTC 2011


I have a similar problem with xfce - specifically, 
'xfce4-xfapplet-plugin' processes remain after a NX session is 
terminated. These plugin processes consume 99% cpu: 

PPID  C CMD
1     0 /usr/libexec/gconfd-2 5
1    99 /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin 
1    99 /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin 
1    99 /usr/libexec/xfce4/panel-plugins/xfce4-xfapplet-plugin 
1     0 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=17
1     0 /usr/libexec/gnome-dictionary-applet --oaf-activate-iid=OAFIID:GNOME_DictionaryApplet_Factory --oaf-ior-fd=27
1     0 /usr/libexec/multiload-applet-2 --oaf-activate-iid=OAFIID:GNOME_MultiLoadApplet_Factory --oaf-ior-fd=21
1     0 /usr/libexec/mini_commander_applet --oaf-activate-iid=OAFIID:GNOME_MiniCommanderApplet_Factory --oaf-ior-fd=24
 
If I terminate the xfce4-xfapplet-plugin processes, then the others
also die. I am tempted to modify the nxnode script to force kill this 
process at logout. 

Btw, I use NX in a multi-user environment with load-balancing.
There are about 60 simultaneous NX sessions open (~1/3 running). 
Only one NX session is allowed per uid.

Does anybody else have a similar problem (and solution)?

Thanks!
Best,
Julie

-- 
Julie Ashworth <julie.ashworth at berkeley.edu>
http://www.neuro.berkeley.edu
PGP Key ID: 0x17F013D2



More information about the FreeNX-kNX mailing list