Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? 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. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-24-2003, 09:58 PM
|
#1
|
|
LQ Newbie
Registered: Feb 2003
Posts: 4
Rep:
|
KLauncher could not be reached via DCOP. ????
Redhat 8.0 was working great. I ssh'ed into my machine remotely and that worked. I even started X (startx) and then opened a program and closed it. Then later when i got home, i tried to start a program and got "KLauncher could not be reached via DCOP." What does this mean and how can i solve it and what caused it. ssh'ing in is the only weird thing i did, so is that the problem, and how can I solve it?
Thank you.

|
|
|
|
03-08-2003, 05:26 PM
|
#2
|
|
Member
Registered: Feb 2003
Location: Toronto
Distribution: RH8 / FC1 / Gentoo / Debian / FreeBSD / Centos / Ubuntu
Posts: 182
Rep:
|
"KLauncher could not be reached via DCOP."
I have the exact same problem. Please somebody help. Logging out and logging back in solves the problem, but it's annoying. I hit this almost every day running RH 8.0, KDE.
|
|
|
|
04-08-2003, 04:45 AM
|
#3
|
|
Member
Registered: Jan 2003
Location: Belgium
Distribution: Mandrake 9.2
Posts: 475
Rep:
|
Same problem in MDK. 
|
|
|
|
04-08-2003, 07:19 AM
|
#4
|
|
Member
Registered: Mar 2003
Location: el paso
Distribution: Redhat, Suse, and freebsd
Posts: 90
Rep:
|
good luck
This is what I found when I did a search on google.
Hopefully this will help
http://developer.kde.org/documentati...deqt/dcop.html
Look at this site it might help better to allow you to make changes to your
own dcop...
http://www.volny.cz/bwian/dcop.html
Bye the way this actuall taught me how to edit my own dcop good luck
later.......
Also look at the post on this site under linux networking > Linux roaming profiles, but WITHOUT WINDOWS
Last edited by ckone; 04-08-2003 at 07:47 AM.
|
|
|
|
06-06-2003, 01:01 PM
|
#5
|
|
LQ Newbie
Registered: May 2003
Location: New England
Distribution: Red Hat 9
Posts: 15
Rep:
|
I've got this same problem, and learning how to edit DCOP tells me nothing about how to solve this problem. I finally got remote logging in to work, but now this problem is very irritating, because while logging out and back in doesn't take too much time, it interrupts processes that are running in X that I don't wish to shutdown.
Has anyone figured this out yet?
|
|
|
|
06-07-2003, 10:06 PM
|
#6
|
|
Member
Registered: Feb 2003
Location: Toronto
Distribution: RH8 / FC1 / Gentoo / Debian / FreeBSD / Centos / Ubuntu
Posts: 182
Rep:
|
I still have not solved this problem. However, I have it under control .. sort of. In my case, the problem seems to be related to running TightVNC. The problem usually surfaces if I open more than one KDE session using TightVNC. If I am careful to run just one KDE session then everything is cool.
This is quite annoying, but that's how I how I deal with it. Hopefully there's a better solution out there somewhere.
Apollo
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:22 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|