Bug 158904

Summary: Starting kdetv causes DCOP communication error message if the computer has just started up
Product: [openSUSE] SUSE Linux 10.1 Reporter: Daren Wilz <dwilz>
Component: GNOMEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 6   
Target Milestone: ---   
Hardware: x86-64   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Daren Wilz 2006-03-17 01:58:54 UTC
When bringing the computer up cold, if you login asap and as soon as the desktop application menu is available you click on kdetv you get the following error box

DCOP Communication error (kdetv)
There was an error setting up inter-process communications
with KDE.  The message returned by the system was:
Could not open network socket
Please check that the "dcopserver" program is running.

Clicking "ok" takes you to kdetv which seems to work normally regardless of the error.

If I re-do the test.  But this time I wait a few seconds after the desktop system comes up before selecting kdetv from the menu I do not get the messsage.

I've got a standard Gnome desktop SUSE install on a 2 gHz AMD-64 with 1 gig of RAM.  

A suggestion might be to lock the menu down for a few seconds after the system comes up before allowing the user to make selections from the menu?
Comment 1 Gerd Hoffmann 2006-03-20 10:52:26 UTC
Doesn't look like a kdetv bug to me, I can't find those message strings in kdetv, probably they come from some kde library.

I'd suspect happens simply due to the system still booting up and thus being loaded a bit, then kdelibs (or whoever takes care to start up kdeinit if it isn't running) either runs into some race window or has a timeout set too tight.
Comment 2 Dirk Mueller 2006-03-20 12:26:34 UTC
do you use a setup where your network configuration changes via DNS your local hostname?

Comment 3 Daren Wilz 2006-03-24 18:54:19 UTC
According to the /etc/sysconfig editor the option is set to NO.

New Info: I have my computer at work today where I cannot hook it to a network.  I am not getting the error.  I've tried 3 times, it works everytime without a problem.  When I get home tonight, I'll recheck that the problem occures once again when I hook it back to the network.
Comment 4 Daren Wilz 2006-03-25 00:23:07 UTC
New info,  I'm hooked back up to my home network again.  I was trying to submit a bug report using firefox.  I needed to open up a terminal (konsole). Selecting konsole from the application menu caused Firefox to crash and up comes the same DCOP error message.  Clicking ok on the DCOP message and konsole opened up.  Note that this crash happened after my SUSE test computer was up and running for about 5 minutes.  I'm still running Beta 6 and would like to upgrade it soon to see if these problems go away.
Comment 5 Dirk Mueller 2006-03-25 08:01:03 UTC
ok, do you use network manager? does your hostname (try "watch hostname" in a konsole window) change?

is this a fresh installation or an upgrade? did you ever compile KDE on your own and could it be found still somewhere on your disk? 

is this reproducable? does it happens once per day, per hour, per minute, everytime?

do you have a strace of an occassion when it happend?
Comment 6 Daren Wilz 2006-03-27 00:39:37 UTC
I do have network manager enabled, I saw this tonight when I installed Beta8.  Wasn't sure what it does so I left it enabled (default).  However, I do not have dns changing my hostname. I unchecked that option.  BTW: the DCOP error happened tonight opening up kdetv with Beta 8 installed but it only happened once.  Before with Beta 6 it seemed I could make it happen every time. 

Beta 6 was a fresh install on brand new hardware.  I installed Beta 8 tonight by telling it to reformat everything except my /home partition.  Both installs were vanilla installs with Gnome selected as the desktop.  I didn't compile kde at any time.  I did compile MPlayer and I installed a game in my home directory called Neverwinter Nights.  That is all that is non-standard except for installing the nvidia binary driver.

It was reproducable in Beta 6 everytime.  Here is how I made it happen.  Boot the computer, login a standard user, watch the desktop, as soon as the menu was functional I would click on Multimedia then select kdetv. Bam, I got the error.  

Tonight I tried it 3 times, finally on the 4th time I got the DCOP error message.  The funny thing is, on the 4th try I actually screwed up the fand missed clicking on kdetv, the menu snapped back closed.  I had to reclick on the menu, again, etc and it happened when I finally got the kdetv menu application clicked.

I'll have to check into watch hostname and strace and let you know if I find anything.
Comment 7 Daren Wilz 2006-03-27 00:43:25 UTC
Oops, scratch that part about compiling MPlayer.  I tried to compile MPlayer. I failed though because it wouldn't compile with the version of gcc that you included with SuSE 10.1
Comment 8 Dirk Mueller 2006-05-04 14:09:29 UTC
I should have fixed this for RC1.