Bug 125080 - Couldn't connect DCOP signal. Won't receive any status notifications!
Summary: Couldn't connect DCOP signal. Won't receive any status notifications!
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 139770 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-07 00:00 UTC by Iñaki Baz Castillo
Modified: 2008-09-16 17:30 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iñaki Baz Castillo 2006-04-07 00:00:08 UTC
Version:           3.5.2 (using KDE 3.5.2, Debian Package 4:3.5.2-2 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15

Just it, since and upgrade in KDE 3.5.1, all the time after start my computer the first time I press in a file with the right mouse button I get the following message:

  "Couldn't connect DCOP signal. Won't receive any status notifications!"

Now I use KDE 3.5.2 but the bugs still occurs (I use Debian Sid).

Only found a similar case in Google with no response.
Comment 1 George Staikos 2006-04-07 07:35:12 UTC
I can confirm this.
Comment 2 Stephan Binner 2006-04-07 16:34:45 UTC
Work-around: deactivate Kuick plugin or patch kdelibs/interfaces/kimproxy/library/kimproxy.cpp from KMessageBox to kdWarning. 

Does anyone know why it's failing?
Comment 3 David Solbach 2006-04-23 10:02:02 UTC
I can also confirm this, and on my system it's reproducable.

If I rightclick on "media:/hdc1/Torrent/completed/ubuntu-6.06-beta-install-i386.iso", the errror message "Couldn't connect DCOP signal. Won't receive any status notifications!" appears everytime after konqueror was just started. If the Konqueror window is kept open, then the second rightclick doesn't produce the error but the "Actions" item of the popup menu is still emtpy. (I'd exect at least "write iso to cd")

If I do the same using the url "/media/WD80/Torrent/completed/ubuntu-6.06-beta-install-i386.iso", everything works fine. (It's the same file hdc1 = WD80)
Comment 4 David Solbach 2006-04-23 10:16:11 UTC
correction: the above is not really a hint. It happens also on local urls after restarting konqueror, sorry.
Comment 5 Joerg de la Haye 2006-04-25 11:51:07 UTC
I can confirm this, too.
 
(Debian Sid, KDE 3.5.2)
Comment 6 spikethehobbitmage 2006-05-13 04:16:26 UTC
for Debian and Ubuntu, try upgrading Konqueror to version 4:3.5.2-2+b1

Debian pure64 testing/unstable
Comment 7 Robert Gomułka 2006-05-15 20:30:56 UTC
To comment #6 - it doesn't help in my case.
For me this bug is not 100% reproducible - after KDE restart I get the message for about 60-70% of the first clicking. Second and further right clicks are always OK.
Debian SID
Comment 8 appsdev 2006-05-21 19:36:10 UTC
Good Day . . .

3.5.2-0.2.fc5 RedHat

100% reproducible

- open File Manager in Super User Mode
- right click on <Move To>
- message appears

does not appear in ordinary user mode

Hope this helps.

Comment 9 Iñaki Baz Castillo 2006-05-31 23:45:21 UTC
Hey! I've just found the cause of this problem: kdesvn.

In Debian Sid I have this bug since I installed kdesvn package and today in Kubuntu Dapper I have installed kdesvn and inmediatelly the next time I press in a file with the right mouse button I get the following message: 
 
   "Couldn't connect DCOP signal. Won't receive any status notifications!" 

I have installed no more packages, so it needs to be a kdesvn bug (or one of its dependences).

To be sure: does somebody have this bug without kdesvn installed?
Comment 10 Joshua 2006-06-01 00:55:18 UTC
Intersting... I've been dealing with this bug (which can be "fixed" by deleting kuick_plugin.desktop from /usr/kde/share/services - or wherever yours are) but I am also endlessly plagued by a right click issue on kong about some file not having the correct syntax and proceeds to popup 4-5 boxes about svn_this and svn_that. Hmmm.....
Comment 11 Iñaki Baz Castillo 2006-06-01 09:23:44 UTC
I have reported the bug to kdesvn developers and they have asked me the following that should be the explanation of the problem:


Rajko Albrecht said:
---------------------------------------------------------------

Yes, and I think for comment 10 I found the reason for that:

kdesvn tried to get two menuentries into konqueror via two dcop-calls. 
Sometimes that failed, eg., seems that kde/konqueror gives the response for 
call A to call B. So call A got no menue list but call B seems to have wrong 
syntax. This cleared in trunk of kdesvn, eg., there just one call will made. 

The message "Couldn't connect DCOP signal. Won't receive any status 
notifications!" I never get and so I have no idea, but may that it is the 
same reason. Try to remove
 the 

<kde-prefix>/share/apps/konqueror/servicemenus/kdesvn_subversion_toplevel.desktop

and see if this failure happens again. If not, the fix comes with kdesvn 0.9. 
Otherwise I have no idea this moment.

You may post this answer into that bugreport - 'cause I must left in 5 minutes 
for my holiday ;)
---------------------------------------------------------------
Comment 12 Pierre Souchay 2006-08-01 16:06:15 UTC
If I remove the file:
<kde-prefix>/share/apps/konqueror/servicemenus/kdesvn_subversion_toplevel.desktop 
the problem does not occur anymore.
Comment 13 Frank Osterfeld 2006-08-24 11:46:55 UTC
Seems to be fixed in kdesvn 0.9.1 (you probably need to uninstall the _toplevel.desktop file manually if you install from source).
Reopen if it still occurrs.
Comment 14 Bartosz Fabianowski 2006-10-26 00:16:54 UTC
I am still getting this with KDE 3.5.4 and kdesvn 0.9.1 on FreeBSD. The error message is the same as always. There is no kdesvn_subversion_toplevel.desktop file to be found on this system.
Comment 15 step247 2006-11-08 13:42:28 UTC
It's also in KDE 3.5.5 (Gentoo) 

$  konqueror --version
Qt: 3.3.6
KDE: 3.5.5
Konqueror: 3.5.5

This happens for files and URL's too. But only once. 
If Konq is restarted, it's back. 

Couldn't connect DCOP signal.
Won't receive any status notifications!
Comment 16 Tamas R S 2006-11-15 22:15:20 UTC
Kubuntu 6.10 Kde 3.5.5. AMD64  
Same problem, + sometimes after  right click all the memory is gone. one of the process I don't know which one, eat up all the memory until the process killed by the system. Then everything is back to normal.
Comment 17 Tamas R S 2006-11-15 22:24:09 UTC
Removing kdesvn_subversion_toplevel.desktop not, but total removing the all kdesvn packages solved the problem.

THX

TRS
Comment 18 Bram Schoenmakers 2007-01-08 13:21:14 UTC
*** Bug 139770 has been marked as a duplicate of this bug. ***
Comment 19 Mickael Marchand 2007-01-08 14:13:37 UTC
maybe commit 488933 is the one to blame (december 2005),
I had no problem with kded's module when it was pre-loaded

maybe the ondemand stuff is too slow ?
is kded's module loaded in memory when you get the bug ?

try adding :
X-KDE-Kded-autoload=true
in ksvnd.desktop, restart KDE and check if you get the bug

Cheers,
Mik
Comment 20 Richard Steven Hack 2007-04-25 11:31:53 UTC
Confirm bug still exists. Installed kdesvn the other day.

Now when I right click the first time, I get the error message reported by others. Subsequent right clicks are fine.

Have uninstalled kdesvn to see if the error message goes away.

After installing other products yesterday, my Kubuntu KDE System Services module in the System Settings will not load any more either. May or not be related as I installed a number of other packages.

Comment 21 Richard Steven Hack 2007-04-25 11:34:11 UTC
By the way, in Kubuntu KDE, I can't FIND kdesvn_subversion_toplevel.desktop anywhere. Certainly it was not under the .kvsn directory.
Comment 22 Scott Grayban 2007-04-29 09:11:22 UTC
I got the same thing here.

$ kde-config --version
Qt: 3.3.6
KDE: 3.5.4
kde-config: 1.0
Comment 23 Jaime Torres 2008-05-16 20:22:06 UTC
It does not happens in kde 4 (because it does not have DCOP). But the right button works always for me (even at the very first time konqueror is started).
Comment 24 David Faure 2008-09-16 17:30:02 UTC
This message box was in kimproxy, I can't see the relation with kdesvn at all.
In any case, the connection to a DCOP signal is now (in KDE4) a connection to a DBUS signal and the messagebox has been removed; if the connection fails (e.g. due to running konqueror as root), then it just fails ;)

Closing the bug, since it can't happen in KDE 4 anymore.