Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Oct 2001 18:21:25 +0100 (BST)
From:      Dave Peacock <dave@sackheads.org>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   misc/31433: dcopserver program intermitantly fails to start
Message-ID:  <200110221721.f9MHLPc00569@frodo.tempest.org>

next in thread | raw e-mail | index | archive | help


>Number:         31433
>Category:       misc
>Synopsis:       dcopserver program intermitantly fails to start
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 22 10:30:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dave Peacock
>Release:        FreeBSD 4.4-RELEASE i386
>Organization:
>Environment:
System: FreeBSD frodo.tempest.org 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Oct 9 20:55:24 BST 2001 root@frodo.tempest.org:/usr/obj/usr/src/sys/FRODO i386


	Intel PII 266, 64MB RAM, STB Velocity 128 4MB 3D card.
>Description:
	Since upgradting to FreeBSD 4.4-RELEASE (note that I track RELENG_4_4)
	and KDE 2.2.1, I periodically get a window pop up during KDE init that
	says it failed to start interprocess communication, please ensure dcopserver
	is running. 
	AFAICT, dcopserver is only called by KDE and is loaded dynamically, it is not
	something that needs to be loaded at boottime etc. Every 4th or 5th time, KDE 
	_will_ start, but it takes several failiures to get it "right". I think this is
	simply a timing issue of a wait()-like function.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110221721.f9MHLPc00569>