Date: Wed, 15 Aug 2001 21:23:50 -0700 From: Michael Collette <metrol@metrol.net> To: will@FreeBSD.org Cc: ports@FreeBSD.org Subject: KDE2 DCOP problems Message-ID: <3B7B4AD6.E55E0AF7@metrol.net>
next in thread | raw e-mail | index | archive | help
Will, At this point I'm having a heck of a time getting KDE 2.2 to play nice. The compile appears to have gone well, but whenever I try launching a KDE application I'm getting DCOP communication errors. I went in and renamed/deleted the following from my home directory... .DCOP* .MCOP* .kde .kderc .mcoprc .mcop I also went and made sure that I didn't have anything in /tmp related to that user. Stuff like ksocket-user and such. After doing all that, still getting DCOP errors. Seems to be doing the exact same thing when logged in as root. On the suggestion of a user on IRC I went and reinstalled kdebase from a fresh source file I downloaded from ftp.kde.org. A whole bunch of compiling later, same problems. I noticed that KDE 2.2 now does some stuff with FAM. I'm seeing some errors as KDE gets going stating that various apps are unable to read FAM. From what I read in the man page, FAM should be getting started within inetd, though I haven't a clue what the config line in there should look like. I tried running FAM as root manually, then launching KDE as a regular user, but I still see errors relating to FAM not being found. Might DCOP be dumping out because FAM isn't properly running as an inetd service? Well, at this point though I can get to a desktop but KDE is pretty much dead here. Here's what all I'm running... 4.3-STABLE FreeBSD 4.3-STABLE #0: Sat Jul 28 02:34:23 PDT 2001 Later on, -- Off the keyboard, thru the router, over the bridge, nothing but net! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B7B4AD6.E55E0AF7>