[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 125080] Couldn't connect DCOP signal. Won't receive any status
From:       ibc <ibc2 () euskalnet ! net>
Date:       2006-06-01 7:23:46
Message-ID: 20060601072346.28419.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------You are the assignee for the bug, \
or are watching the assignee.         http://bugs.kde.org/show_bug.cgi?id=125080      \




------- Additional Comments From ibc2 euskalnet net  2006-06-01 09:23 -------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 \
;)---------------------------------------------------------------_______________________________________________Konq-bugs \
mailing listKonq-bugs@mail.kde.orghttps://mail.kde.org/mailman/listinfo/konq-bugs


[prev in list] [next in list] [prev in thread] [next in thread]