Date: 12 Aug 2001 21:23:00 -0500 From: James McNaughton <jtm63@enteract.com> To: Bob Collins <bob@pineypl.com> Cc: David Leimbach <leimbacd@bellsouth.net>, questions@freebsd.org Subject: Re: DCOPserver and kde 2 Message-ID: <86bslkpukb.fsf@localhost.21stcentury.net> In-Reply-To: <20010729213919.A3008@kludge.pineypl> References: <20010729161359.A1531@kludge.pineypl> <01072915431001.23557@mutt.home.net> <20010729213919.A3008@kludge.pineypl>
next in thread | previous in thread | raw e-mail | index | archive | help
Bob Collins <bob@pineypl.com> writes: > > I did not. ;) I use a better OS! I aggree! > > > Try checking the existence of the following: > > /tmp > > drwxrwxrwt 2 root wheel 1024 Jul 29 09:06 .ICE-unix > > drwx------ 3 dave wheel 512 Jul 29 12:28 kde-dave > > drwx------ 2 dave wheel 1536 Jul 29 15:31 ksocket-dave > > drwx------ 2 dave wheel 512 Jul 29 09:06 mcop-dave > > > > The dave files are for the users named dave :). > > Note the sticky bit on the .ICE-unix directory... this is pretty important :). > > The directory is used to store DCOP socket connections from users. > > > I found I had the directories, however the sticky bit was NOT set. > Once set, I was very eager to try it out, and it fired right up. My > KDE is working again. Thank you very much. > > -Bob > Just to add my experience with KDE 2.x I have never had these problems. My /tmp is setup as a memory file system so power outages make it all go away. This leads me to the conclusion that you could just blow away everything and get KDE back up. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bslkpukb.fsf>