Hello, Since last week after my upgrade (read a clean install) from Suse 8.0 to 8.2 i'm fighting a very strange problem. I want to start kde on top of my windows XP and use Exceed 7.0.0.0 to do it. My exceed command string is : export DISPLAY=192.74.233.15:0.0 ; startkde I create an exceed client shortcut to automate kde logon and use this shortcut to start kde. The only thing I see is the kde splash screen, and after all the initialization the desktop appears for a few seconds. Hereafter kde disappears. Enabling exceed's debug logging shows the following: export DISPLAY=192.74.233.15:0.0 ; startkde kbuildsycoca running... DCOP Cleaning up dead connections. Server has no DPMS extension >> running as realtime process now (priority 50) mcop warning: user defined signal handler found for SIG_PIPE, overriding KInternet session mode disabled. KInternet should be started from startkde. ERROR: KUniqueApplication: DCOP communication error! I never have the same problem with suse 8.0 (and exceed 7.0.0.0). And strange enough when I start a manual telnet session and run my exceed command string manually everything seems to work fine. (in my telnet session I found also the same 'ERROR: KUniqueApplication: DCOP communication error!' error. Maybe exceed triggers this ? I have used linux software from the Suse 8.2 CD or installed by suse's online update.(because of my problem) Kde 3.1.1 XFree86-4.3.0-15 kdebase3-3.1.1-63 kdebase3-SuSE-8.2-78 Can someone please help me out ? On the internet I've found info about the DCOP error but nothing seems to help me. Fvwm seems to work. I do not found a way to start gnome remotely because startx doesn't run from a remote telnet session. (but that's another story I think) Thanks in advance en greetings, Carl Van Elsacker ICT system engineer