It started happening during an error in starting KMAIL, it did succeded but afterwards it didn't succed with anything. If you are sure that it is not already running, remove /home/burna/.DCOPserver_jupiter__0 and start dcopserver again." and "kio (kioslave): SlaveBase: failed to connect to /home/burna/.kde/socket-jupiter/klauncherQq0ZAa.slave-socket kio (kioslave): SlaveBase: failed to connect In my machin this prob occures often. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. check over here
LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie "KLauncher could not be reached via DCOP" - Error in KDE User Name Remember Me? lippy Linux - Software 5 06-07-2003 11:06 PM Help Klauncher said "Error loading 'kio_file' Avatar2U Linux - Newbie 3 01-06-2002 10:09 PM All times are GMT -5. thanks nuwan Reply With Quote Quick Navigation Red Hat / Fedora Linux Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Linux Forums Linux Forums Site In the Application tab, I had to hit the "Advanced" button and set the "Register D-Bus" combo to "none".
I forgot to mention that MY problems appeared after updating to 3.1.2 (from the FreeBSD ports in my case). Is there any way to overcome this prob without rebboting the system? The problem seems only be related to the use of KDE apps, apparently konqueror. and how can i make my navigator work properly again ??
Once this error message has appeared once, it seems to happen more and more frequently, while it is still possible to work in some windows, for a while at least. Advertisement HarryTruman Thread Starter Joined: Oct 1, 2004 Messages: 31 I have seen many topics like this asking what to do, but none have a definite answer. Advertisements do not imply our endorsement of that product or service. There were other reports that suggested that it might be related to something that gnome-terminal did.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. nothing! Join over 733,556 other people just like you! Are you new to LinuxQuestions.org?
In this case I was trying to start a terminal program in the K Desktop Environment (KDE 2) on a Silicon Graphics machine. The real test of an error message, though, is whether it gives you any clue how to repair the situation. Duplicate of bug #205517 Remove Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. If I run kdeinit will it kill those downloads -- being done via DownThemAll in FF.
A few minutes after I start KDE I get the "KLauncher could not be reached via DCOP" message again. http://www.cyberhobo.net/2003/07/14/klauncher-could-not-be-reached-via-dcop/ Stay logged in Sign up now! nobody cares about yer stupid database. If you are sure that it is not already running, remove /root/.DCOPserver_MyHost__1 and start dcopserver again. ---------------------- DCOPClient::attachInternal.
Comment 1 Stephan Kulow 2003-03-10 20:56:35 UTC do you have some more info from your .xsession-errors? check my blog Password Forgot Password? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. Thread Status: Not open for further replies.
Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. Here what .xerrors gives me: The important information is: "It looks like dcopserver is already running. Thanks guys! http://jessriegel.com/klauncher-could/klauncher-could-not-reached.html Comment 8 Rick Gaudette 2003-06-16 02:09:38 UTC Hi Guys, Out of the blue this problem has just started happing again.
Comment 4 Rick Gaudette 2003-04-21 20:40:56 UTC I don't typically use gnome-terminal but I just ran it, cd'd and ls'd around a little bit and then lanched some programs from the Yes, my password is: Forgot your password? Register a domain and help support LQ Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search
Find More Posts by itz2000 Thread Tools Show Printable Version Email this Page Search this Thread Advanced Search Posting Rules You may not post new threads You may not post There is also a KDE bug for it: http://bugs.kde.org/show_bug.cgi?id=157407 Bj√∂rn Streicher (bstreicher) on 2008-03-30 Changed in meta-kde4: status: New → Confirmed Eduardo Besembel (besembel) wrote on 2008-05-13: #3 instant√°nea1.jpeg Edit (48.6 Join our site today to ask your question. No, create an account now.
Style Default Style Contact Us Help Home Top RSS Terms and Rules Copyright © TechGuy, Inc. All rights reserved. Kimmo Comment 12 Gerrit 2005-05-21 12:23:19 UTC I have also this problem with KDE 3.3.2 selfcompiled from source on slackware 10.0. http://jessriegel.com/klauncher-could/klauncher-could-not-be-reached-via-d-bus.html These errors occured using Red Hat's 3.0.5 RPMs and the 3.1.0 RPMS available from the Red Hat KDE sourceforge project (in both cases on a fully updated RH 8.0 installation).
Do I have to do something to enable it. Whiteskin, Oct 11, 2004 #2 HarryTruman Thread Starter Joined: Oct 1, 2004 Messages: 31 Yeah, updating looks like my only option. Everything worked fine. If I start a new konqueror from the command line of a konsole I get an Error dialog with "Could not start process Can't tak to klauncher".