Bug 13627

Summary:	change kde config produces dcopserver error msg
Product:	[Retired] Red Hat Linux	Reporter:	Gene Czarcinski <gczarcinski>
Component:	kdelibs	Assignee:	Bernhard Rosenkraenzer <bero>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-07-15 16:27:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gene Czarcinski 2000-07-09 17:28:21 UTC

I built a beta3 system with gnome and kde installed.  I booted up runlevel
5 (since switchdesk-kde does nothing), and logged on as a normal user with
kde selected.  Everything looked fine.  I then logged off and back on --
everything still OK.  I then used the KDE Control Center to change some
configurations -- desktop color, enabling color buttons for kpanel, and
selecting a them such as the HighColor Default.  Evenything looked OK with
the new configuration.  I then logged off and back on -- at kde startup, I
got an error message in a panel:

DCOP Communication Error ()

There was some error setting up inter-process communications for KDE.  The
message returned by the system was:

Could not read network connection list

Please check that the "dcopserver" program is running! [it was].

Comment 1 Gene Czarcinski 2000-07-09 20:22:13 UTC

More info ...

This problem does NOT depend on changing anything.  However, it may be some kind
of timing problem (race condition).

When I run under vmware (looking like a slow up), kde sort of works -- OK the
first time but then I start getting dcopserver error messages when I re-login.

On real hardware, it is a bit different --

I built a fresh beta3 system with gnome & kde.  I then booted up (runlevel 5)
and select kde and logged in as a normal user, it works.  I then logoff which
changing anything or even saving the session.  When I log back in, I get a great
gray screen with the kde-intro panel displayed.  I ctl-alt-backspace to get out
and try again -- same thing.

I then reboot and login.  This time I get kde to "sort of" start .. the window
manager comes up but I get the dcopserver error msg.

I can play with this some more if you need more info.  I am hoping that you can
duplicate the problem.

Gene

Comment 2 Gene Czarcinski 2000-07-09 20:36:40 UTC

The following is from the kde mailing lists --

List:     kde-devel
Subject:  Re: DCOPServer?
From:     David Faure <david>
Date:     2000-07-03 18:27:54
[Download message RAW]

On Mon, Jul 03, 2000 at 06:26:11PM +0200, Wim Stubbe wrote:
> > > Session management error: networkIdsList argument is NULL
> > 
> > That's a well known warning, not harmfull at all
> > (and hopefully fixed in the next Qt !)
> > Look somewhere else for why it doesn't start...
> > 
> > > I think that KDE refuses to start due to that problem, but
> > > I'm not sure about that. (It starts till kwin registers
> > > and hangs then).
> > > 
> > > It worked a few days ago. Do you have an idea?
> > 
> > Nothing else in the debug output ?
> 
> 
> I now have the same problem, didn't find anything yet, but I'm rebuilding
> everything now.
> and indeed, nothing in the debug output. :-(

Yes there is.
kdeinit: error in loading shared libraries: Instance: cannot open shared object
file: \
No such file or directory 

That was because of the "Instance kdeinit has not data" warning that screwed
up LD_PRELOAD=`kdeinit --libkmapnotify`. Hehe.
Fixed.

-- 
David FAURE, david, faure

I guess I have to wait for beta4 to get a fix.

Gene

Comment 3 Michael Redinger 2000-07-15 16:26:05 UTC

Same here - however, it always happens. I did a complete install. The machine
I'm running this on is a Dell OptiPlex GX1 (P 450 and 64 MB RAM, ATI Rage Pro
card).

When doing a telinit 5 I found the following messages:

kio (Ksycoca): No databse, opening a dummy one.
Instance kdeinit has no about data
Aborting. $HOME not set!

(don't know if this is relevant ...).

I checked and did not find any dcopserver process. Starting it manually does not
change anything, same message still.

Comment 4 Michael Redinger 2000-07-15 16:27:04 UTC

Oops, forgot this one:

When starting dcopserver manually I do get the following message:

Session management error: networkIdsList argument is NULL

Comment 5 Bernhard Rosenkraenzer 2000-07-17 11:29:38 UTC

This is fixed in the current version.

Comment 6 David Balažic 2000-07-20 17:22:03 UTC

I installed X11 and KDE ( as the only package groups ) from beta3.

On next(first) boot the kdm login screen appeared with a dialog in
front saying :
---------
There was some error setting up inter-process
communications for KDE. The message returned
by the system was:

 Could not read network connection list.

Please check that the "dcopserver" program is running !

                  [ OK ]
---------

Comment 7 Bernhard Rosenkraenzer 2000-07-20 17:33:10 UTC

Like I've already said, the version in beta3 was buggy. It's fixed in the
current version.