Bug 488920

Strange. I'm not sure what would be causing that... adding Rex here to see if he has any ideas.

No idea really, if it happens only 5-10% of the time, esp only on startup (when a system is loaded/slower than usual), I'd venture there's a race or timeout happening somewhere.

A web search indicates that this issue is not limited to twinkle, so the cause is probably somewhere else, but I don't know enough to guess where.

http://www.google.com/search?hl=en&q="There+was+an+error+setting+up+inter-process+communications+for+KDE.++The+message+returned+by+the+system+was%3A"&btnG=Google+Search&aq=f&oq=

Yeah, I have never seen it here, but it sounds like it does happen to many other folks. 

Some questions: 

1. Is there a dcopserver process running? Is it running as the same uid as your user?

2. Anything in ~/.xsession-errors from the time it fails?

I'm not sure what else to look for here. ;(

Created attachment 334360 [details]
my .xsession-errors.old (.xsession-errors is almost new and contains nothing relevant)

Last time this happened, I neglected to see if there was a dcopserver process running.  There's one running now, so that's the normal state.  I'll check next time.  I do have related content in my .xsession-errors.old (file attached).

Just got the error again, and when I did, the dcopserver process was NOT running.  Logged out and back in, no error this time, and now dcopserver is running.  So the error is associated with failure of this process to start (or keep running?) for some reason.

Rex: Any ideas here?

I am at a loss in what to suggest next. ;(

no ideas really.  something/somewhere is killing dcopserver.  (maybe ip/hostname changes?)

I think I did boot into Vista before booting back into Fedora, which causes my router to assign a different LAN address (192.168.1.45 right now, instead of the usual 192.168.1.47).  Could you explain why this might be the cause?

no, I meant ip/hostname changes during the lifetime of dcopserver running.

[andre@compaq-pc ~]$ which dcopserver
/usr/bin/dcopserver
[andre@compaq-pc ~]$ rpm -qf /usr/bin/dcopserver
kdelibs3-3.5.10-3.fc10.x86_64
[andre@compaq-pc ~]$

Does anyone know where dcopserver is started from when I log into Gnome, and if there is any kind of logging I could set up to try to find out whether it's being started, and if so what's killing it, when I get the dcopserver error?

dcopserver is started on demand when any kde3 app is launched.

In System/Preferences/Personal/Sessions/Startup Programs, I added an entry for twinkle, which starts up automatically when I log in.  If I uncheck this entry, then when I log in, dcopserver doesn't start.  So in my case, twinkle is the only program responsible for dcopserver starting, which explains why for me this error is associated with twinkle.  Other people might have other programs set to start up at login which explains why they might see it with other programs.

Since it's definitely not a twinkle bug, I've changed the Summary and Component.  The correct Component could easily not be kdelibs3, either, but at least it's closer.

Also changed the Version from "rawhide" to "10" since the only reason this was originally assigned to rawhide is that I was running the Koji testing version of twinkle at the time.  All my installed packages are currently F10.  I haven't seen this error on rawhide yet so it's conceivable it doesn't exist there, though since it's rare it's impossible to be sure.

It's not definitely anything yet.

I can't reproduce what you describe, and starting any kde3 application (including twinkle), automatically starts dcopserver, as expected.

Are you saying that launching twinkle, there is *never* any dcopserver process running?

No, I mean that the normal behavior on my machine is that when I log into Gnome, starting twinkle causes dcopserver to run.  In the rare event this doesn't happen (or possibly, dcopserver does start up but then dies), then I see the error and the subsequent strange behavior of twinkle (appearing in a tiny window with nothing but a star).  If I don't start up twinkle automatically at startup, then after I log in, dcopserver isn't running, indicating that twinkle is the only program which I use which is attempting to start dcopserver.  Of course, if I then start twinkle manually, then dcopserver starts (normally).

Once dcopserver is started, it continues to run even if I quit twinkle.  It only dies when I log out of Gnome (which I can verify by logging into a VT).

I've only seen this error on rare occasions, always after logging in immediately after booting.  I suspect it won't happen if you just log out and back in repeatedly.

I just got the error again after booting up and then logging in.  I get the big "DCOP communications error" window.  About 30 seconds after clicking "OK", twinkle appears in a 1/4" window with nothing but a star, but not in the Start Tray - normally it appears only in the Start Tray, but not in its own window.

By right-clicking on this window, I get the normal twinkle menu, and then choose Quit.  After it quits, I restart twinkle.  This time it comes up normally, and dcopserver is running.  I was hoping the failure of dcopserver to start would be reproducible so I could do some diagnostics.  I saw nothing abnormal in the twinkle.log* files.  By looking in /var/log/messages I noticed that I'm manifesting bug #489093, but this happens to me every time at bootup (not login) and probably has nothing to do with this bug.

Is this still an issue?

With F10?

With F11?

With Rawhide?




-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I haven't seen it on F11 yet, but I haven't rebooted that many times since it came out, so it's not conclusive yet (just logging out and back in isn't enough to trigger it).  My father, who is still on F10, reports that it's still a problem there.  I can't test it on Rawhide since mine is hosed to the point that I can't get a login prompt, even on a VT, and have to boot up in rescue mode each day to do updates and hope that eventually it works again.

My father, who did a clean install of F11 a little while ago and is fully updated, said that he saw this today when restarting the machine after "yum install akmod-nvidia" caused it to shutdown for no discernible reason (yum-complete-transaction showed no unfinished transactions, and he was able to run the install command again and finish it, so maybe there was a good reason for the shutdown - it had to install a bunch of compiler-related packages).  On the other hand, I haven't seen the error in almost 2 months on my basically identical F11 machine.  So the issue appears to still exist but is much less likely to manifest.

I just saw this on my F11 machine after logging in for the first time after booting up, under normal conditions.  So it definitely still exists in F11 but at least for me manifests much less often.  That's probably just a timing issue.  I'm changing the Version to 11.

This is happening in rawhide F12. I've got a fully up2date bare-metal Alpha 12 install and when i launch twinkle, i get the dcop error and the taskbar icon floating in its own window. 

What can i provide here to help debug?

Well... i figured it out on my own. At least, i figured out where the problem was and how to fix it. Permissions. I'm not sure though how the problem came to be. Apparently my ~/.kde dir was owned by root, along with a few other related items, such as .DCOPserver_cward.englab.brq.redhat.com__0 and .ICEauthority.

> twinkle 
Session management error: None of the authentication protocols specified are supported
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
DCOPClient::attachInternal. Attach failed Could not open network socket
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/tmp-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/socket-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/socket-cward.englab.brq.redhat.com: Permission denied
kdeinit: Aborting. No write access to '/home/cward/.ICEauthority'.
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPRef::send(): no DCOP client or client not attached error
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
trying to create local folder /home/cward/.kde/cache-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/cache-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/tmp-cward.englab.brq.redhat.com: Permission denied
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/socket-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/socket-cward.englab.brq.redhat.com: Permission denied
kdeinit: Aborting. No write access to '/home/cward/.ICEauthority'.
trying to create local folder /home/cward/.kde/cache-cward.englab.brq.redhat.com: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
I couldn't enable notifications at the dcopserver!
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied
trying to create local folder /home/cward/.kde/share: Permission denied


[cward@cward ~]# sudo chown cward.cward .* -R

[cward@cward ~]# twinkle 
DCOPClient::attachInternal. Attach failed Could not open network socket
kbuildsycoca running...

Twinkle loaded without any warnings or issues. Tray icon is in the tray where it should be too.

I just got this error after booting up and logging into F11.  The .kde directory in my ordinary user directory (~andre), and everything in it, is owned by andre.  There was also an empty ~root/.kde/share/config directory in ~root with a modification time 14 minutes later than my ~root/anaconda-ks.cfg and ~root/install.log* files, which I've deleted.  Could the existence of ~root/.kde have been the problem?

Also please bump the Version to rawhide.

Never mind, I forgot I could do it.

Actually, after seeing the problem, I quit Twinkle, logged out and back in again, which fixes the problem, at least temporarily.  Is it possible that doing that could have changed the ownership of ~andre/.kde from root to andre?  This manifests so rarely for me that it would probably take weeks for me to see the problem again, and I can't check until then.

P.S.  In ~root I see a few other dotfiles also owned by root - ~root/.dbus and ~root/.gnome2_private with the same modification time that ~root/.kde had.  There is also ~root/.gconf, ~root/.gconfd, and ~root/.gnome2 with a modification time over a month later.  (Maybe I logged into X as root.)

After seeing this today, I tried to start dcopserver manually:

[andre@compaq-pc ~]$ dcopserver
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/andre/.DCOPserver_compaq-pc__0
and start dcopserver again.
---------------------------------

[andre@compaq-pc ~]$ ps -A | grep dcopserver
[andre@compaq-pc ~]$ ls -l .DCOPserver_compaq-pc_*
-rw-rw-r--. 1 andre andre 56 2009-09-22 13:30 .DCOPserver_compaq-pc__0
lrwxrwxrwx. 1 andre andre 36 2009-09-22 13:30 .DCOPserver_compaq-pc_:0 -> /home/andre/.DCOPserver_compaq-pc__0
[andre@compaq-pc ~]$

After removing the lock file from yesterday and starting dcopserver, twinkle will only start in an ordinary window, not in the system tray, same as before.  I have to log out and back in to make twinkle work normally again.

Actually, with dcopserver running, I have to kill dcopserver and manually remove both ~/.DCOPserver_compaq-pc_* files, then log out and back in.

Andre, what DE are you using? (gnome, kde, other)?
is twinkle being started as part of session management (or manually)?

Using Gnome with Twinkle started automatically in the system tray.

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Saw this today in F12.

Just noticed this is still assigned to me... perhaps some of the other kdelibs3 maintainers will have an idea here. ;)

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Sorry for the delay, we were using Skype for a while but are now using Twinkle again in F14 and my father just saw this again. Updating Version to 14.

My father saw this in his clean F15 i386 install. Updating Version to 15.

Still present on F16 x86_64.

So have you removed that stale /home/andre/.DCOPserver_compaq-pc__0 lockfile dcopserver was complaining about? If it's still there, it's no wonder dcopserver doesn't start up. Otherwise, I'm not sure what's wrong (permissions? SELinux?). I cannot reproduce this, kdelibs3 apps just work for me.

As before, the error is only sporadic and can be avoided by simply logging out and back in again. I didn't check for the existence of the lockfile.

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.