Make sure that $ HOME , $ DISPLAY and the various $ KDEDIR(S) are set correctly when doing so!Are you running stock M11? Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search etc. Not a member yet? check over here
Thanks guys! Use top -c or ps aux to see the actual program name: % ps
aux waba 23184 Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest cyberhobo says: Thu, 09 Oct 2003 at 12:37 pm Any real hobo that reads my Error Collection posts is OK by me, offended or no.
This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. Nothing launches. I see it either one the desktop or vnc (one works and one doesn't, but it can be either).
It seems to be a hit and miss which would appear or not. i did something. itz2000 View Public Profile View LQ Blog View Review Entries View HCL Entries Visit itz2000's homepage! Any other thoughts?
Controlled by $ DCOPAUTHORITY /tmp/.ICE-unix/dcop
pid - number e.g. Sometime I find a solution. foto slut says: Tue, 15 Jul 2003 at 12:14 pm enuff of this stupid shit. User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License.
HOME /.ICEauthority Authorization information controlled by $ ICEAUTHORITY kcminit kcminit executes initialization services during
Initialization services are specified in the .desktop files of applications or services via the X-KDE-Init line: [Desktop Entry] Encoding=UTF-8 Exec=kcmshell energy Icon=energy_star Type=Application X-KDE-Library=energy X-KDE-Init=energy Initialization services are typically used for It operates in close connection with the kdeinit master process to start new processes. Some related files: $
HOME /.DCOPserver_$ HOSTNAME _$ DISPLAY e.g. .DCOPserver_linux__0. Get new posts in your inbox scrounge it up Search for: most recent July 25 - Climbing results, final thoughts July 24 - Stanley cafe, hot springs, Mores mountain July 23
Athlon II X4 635, sAM3 * HDA ATI SB VT1708S Analog * 2x4Gb DDR3 1600 Kingston * 22" Samsung SyncMaster P2250 * HP DeskJet F2280 Top smilliken Forum Guide Posts: 2074 http://jessriegel.com/klauncher-could/klauncher-could-not-reached-via-dcop.html In my machin this prob occures often. A6Quattro Fedora 6 07-20-2005 01:49 PM nslookup gives "connection timed out; no server could be reached" hello321_1999 Linux - Networking 3 11-26-2004 12:23 PM "Could not start process - Can't talk Are you new to LinuxQuestions.org?
kde and process communication problems Kevin Galligan galligan "at" objice.com Wed Jun 5 21:47:01 2002 Previous message: kde and process communication problems Next message: Broadcasting with Vnc? S 21:41 0:00 kdeinit: kded waba 23203 0.8 3.4 31516 17892 ? Results 1 to 1 of 1 Thread: KLauncher could not be reached via DCOP Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to
You are currently viewing LQ as a guest. From vnc everything works fine, but when I log into > the normal desktop I get all sorts of interprocess communication errors, > even when I try to open simple text Anyway... KDE applications communicate with klauncher over DCOP in order to start new applications or services.Best known from the error message: KLauncher could not be reached via DCOP which either indicates a
You may have to register before you can post: click the register link above to proceed. Now everything is all screwed up! but I'm not sure what I've done good that it didn't fit in the other times it happened... have a peek at these guys Or, if I continue to dig, I get more information than I can digest, and again wave the white flag.
indicates the master kdeinit process. If you are sure that it is not already running, remove /root/.DCOPserver_MyHost__1 and start dcopserver again. ---------------------- DCOPClient::attachInternal. klauncher can be restarted by restarting kdeinit from a console window. S 21:41 0:00 kdeinit: Running...
No wicd, hp gui, kmix, etc You do not have the required permissions to view the files attached to this post. MX-16_x64 Metamorphosis 12 Dec 2016 ext4 Xfce 4.12.2 * AMD Asus M4A785TD-V EVO AM3 * ASUS GeForce GT640-1GD5-L * AMD Proc. Nothing launches. Attach failed Could not open network socket " Telpochyaotl says: Tue, 20 Dec 2005 at 11:08 am Cool… kdeinit works, but why does this happen?
Make sure that $ HOME , $ DISPLAY and the various $ KDEDIR(S) are set correctly when doing so! I'm a noob. Just starting out and have a question?