KLauncher could not be reached via DCOP
Help!
I've just upgraded to kde 3.0.4 woody from kde 2, using the debian woody
packages from the kde site.
I find that whenever I try to start an application (e.g. from kicker) I just
get "KLauncher could not be reached via DCOP".
There's no kluncher process running.
If I run kluncher by hand, with strace, then it exits cleanly:
mprotect(0x405ae000, 5361664, PROT_READ|PROT_EXEC) = 0
munmap(0x40014000, 69898) = 0
getrlimit(0x3, 0xbffff6fc) = 0
setrlimit(RLIMIT_STACK, {rlim_cur=2044*1024, rlim_max=RLIM_INFINITY}) = 0
getpid() = 7474
uname({sys="Linux", node="ethel.diamand.org", ...}) = 0
rt_sigaction(SIGRTMIN, {0x40c1b480, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x40c1b508, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_2, {0x40c1b608, [], 0x4000000}, NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [RTMIN], NULL, 8) = 0
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff504, 30, (nil), 0}) = 0
brk(0) = 0x8049818
brk(0x804a818) = 0x804a818
brk(0x804b000) = 0x804b000
_exit(0) = ?
There's another problem around which is that kdm refuses to run following an
upgrade of Xfree86 to 4.2.0 (from the xf86 site itself) but I think this is
unrelated.
Does anyone have any ideas? I'm getting so desperate I even tried switching to
gnome!
Thanks,
Luke Diamand
Reply to: