Skip navigation.
Home
Now Shipping Version 7.0

DCOP Error after Installing Skim


Posts: 24

I'm unsure as to whether this is the correct place to be starting this topic, but I assume it is, since it deals with an issue that arises after I installed skim according to this guide http://www.mepis.org/node/10842 (I've had the issue with other guides, as well, if I remember correctly)

I received a "DCOP communications error" a bit after following the guide and rebooting after using skim for a while. Oddly, it didn't happen the few times I rebooted to test, but only after I had used it for a bit.

"There was an error setting up inter-process communications for KDE. The message returned by the system was:

Could not read network connection list.
/home/sean/.DCOPserver_Shikaku__0

Please check that the "dcopserver" program is running!"

I had searched around, and saw no real fixes. I tried chown'ing the .ICE-unix, and that didn't work. I'm unsure if I should try the many other random-guess fixes (I kind of use this system to do work, so I can't afford to take it down). Skim and everything seems to still work, but I'm unsure...I seem to remember the last time I had this issue my KDE didn't start up correctly at one point, and then it was done.

Any help is greatly appreciated!

Thank you very much.

dukey's picture

Try this...

Pyrrhus Did you do this last bit - from the First post on the thread you mentioned?? I had that error too I think and this fixed it.

Quote "9- Oops! wired dccop error, so as root type

mv /etc/X11/Xsession.d/90im-switch /etc/X11/Xsession.d/98im-switch
Unquote.

-----------------------
Gotta luv Mepis. GREAT work team.
Wish list = perfect Japanese input!! and Flash player!!

Yeah, I did that last part,

Yeah, I did that last part, but it's giving me the trouble.

In that directory I have:
20xorg-common_process-args
75dbus_dbus-launch
30xorg-common_xresources
90xorg-common_ssh-agent
50xorg-common_determine-startup
98im-switch
60gconf2_merge-tree.dpkg-bak
99xorg-common_start

--------------------------
Somebody stole my pants...

dukey's picture

Mine is the same

Late reply - but my xsession.d directory has exactly the same files so....maybe your problem is elsewhere...dunno ??

I've noticed lately that my system is not trouble free. Sometimes it hangs in at the 'globe' bit of the auto-log-in startup. But it never hangs after ctrl-alt-bksp and manual log-in. Dunno what the problem is but it's definitely skim etc related, as it never did this before skim was installed.

generally - J input methods seem finnicky.
Not much help I know....

Yeah, I noticed that just

Yeah, I noticed that just tonight. I normally only relog using KDE when I reboot the computer altogether (since I'm dual booting, running windows for games and compatibility).
I had a slight issue, so I logged out, then back in, and it seemed to freeze on "Loading Desktop". CTRL-ALT-BKSP and then logging in works fine now, though.
It does seem a bit weird, but I guess I'm just happy I have J-input and my system doesn't have any errors (besides not being able to use J-input in Open Office, and the described issues).

Well, ありがとうございます, dukey-さん! It's at least comforting to know that I'm not alone in this problem, and not just left out of the solution-loop. If you ever come across a solution, please be sure to post it somewhere here!

--------------------------
Somebody stole my pants...

dukey's picture

check default language

Pyrrhus... sorry - another month down the track!!

My understanding from your last post is that you still don't have J-input in Open Office?? right?

That surprises me because I did get it to work fine in OO in the end - after fixing some trouble with the default(?) language somehow being set to Afrikaans ?!!.
Might be worth checking that if you didn't already.. Hope it helps.
I have some time off soon - I'll try to go through the skim/J-input install step by step on a fresh system - rebooting endlessly - to see when the problem comes in.

Good luck
------------------------------
Gotta luv Mepis. GREAT work team. Smiling

Correct, I don't have

Correct, I don't have J-Input in OO.

However, I did notice that there are two "Language Support" utilities that were installed. I might have used the wrong one...I used the one out of the two that seemed to be for KDE (/usr/bin/qt-language-selector), rather than the GNOME one. Any ideas?

Oh, and I am defaulted to English (USA)...was worth a check.
--------------------------
Somebody stole my pants...

dukey's picture

Error tracking...

OK... - so I played with reinstalling J-input (http://www.mepis.org/node/10842)with multi reboots to track down the errors.

The short version: On my machine - I got J-input happening in OO - but its 'dodgy' ... some points ...
1. I used the Lang Support module with 'earth' icon, which is apparently the qt version.
2. Be aware - it will default to Afrikaans (the first on the list) - select US English instead in the bottom 'default lang.' section.
3. In the end, OO seems to accept J-input as long as skim is running properly beforehand. If there is no skim icon in the panel - then manually start skim and try OO again.
PS. Dont forget OO needs to be setup to accept J input, & have asian fonts etc.
-------------------

ERRORS during installation: all was OK until SKIM installation. After that - restartX (with ctrl-alt-bksp), DCOP error came in.... "Error = /home/USER/.DCOPServer_CompName_D"
This error is mentioned in the method so I continued to the end with no other errors...

1st Reboot after install was slow... and no 'auto-login' (as before) >> Restart-X >> login OK with J input in most apps but NOT in Open Office.
2nd reboot - same. Restart-X >> no J-input OO. Manually started skim and tried OO again - and J-input was OK!!!
3rd reboot - Auto login was OK, Skim started automatically >> J-input in OO + = OK!!

After more reboots...: Seems that IF my auto login gets through OK, then skim starts properly and all is dandy including J-input for Open Office.
BUT if my auto login fails then I (probably) have to manually start skim after login. 'configuring' skim (R click skim panel icon) to autostart with kde doesn't seem to work 100% either.
Since I finished the procedure - of 6 reboots - half auto login was OK, half not -> manual login and manual skim start required.

So - all in all it's still buggy!!!! BUT J-input for OO is go!!

Phyrrus - if you still don't have Open Office happening - I'd be tempted to try again from the start. Backup your system first in case it breaks!!!!!

I've had a little play with 6.5 - looks great - but havn't tried J-input there yet. Maybe later.
Good luck - E

---------------------------------------------------
Gotta luv Mepis. GREAT work Wazza and the team.
6.5 in bed with Beryl !!!! Looking Fantastic.
Go Mepis Gggggoooooooo

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.