[solved] 'service' could not be reached via DCOP.

souperman · 2019-01-06 06:47

Greetings, Q4OS devs!
Just out of the blue, today, I ran into an issue which pops up and says [service] could not be reached via DCOP. Every app I clicked on during that time, popped up the same window, until I logged out and back in again. How can I solve it? Because, it happened once, and I am sure it will happen again.
I am running Q4OS Scorpion, TDE session.
Thank you, for any suggestions on this matter!

Last edited by souperman (2019-01-13 04:23)

Dai_trying · 2019-01-06 10:30

You could try this solution I found in another post with similar issues

Q4OS Team wrote:

You could try to cleanup the TDE cache, just do login to terminal console, ctrl+alt+f1, make sure you are not logged TDE in. Remove all folders 'tdecache-*' in '/var/tmp/' directory and 'tde*' in '/tmp'. Next remove directories 'cache-*' .. 'socket-*' .. 'tmp-*' in '$HOME/.trinity/' and reboot. You should also check and set ownership of all files in your home folder:
$ cd /home
$ sudo chown -R your_username:your_groupname your_home_folder

souperman · 2019-01-07 12:51

I need a little help here as to understand what to do. I've tried the following, with no success (the folders and directories are still there):

find ./var/tmp -name "tdecache-" -type R -exec rm {} \ && find ./tmp -name "tde" -type R -exec rm {} \

I waited long enough, but, I didn't see anything except a '>' at the bottom. What are the proper commands to perform what you suggested? BTW I found the above commands on a Superuser page when I searched "how to remove folders via terminal".

Dai_trying · 2019-01-07 14:08

By putting the \ at the end of that command it means it is looking for some more input which leaves the command "open" to accept it which is why you just have the > displayed in the terminal, try it without that last \ and see if it completes.

souperman · 2019-01-08 03:56

Running the above commands without '\' results in: "Unknown variable for -type: R". What to do next?

Dai_trying · 2019-01-08 08:06

The easiest way to do this would be to follow these commands, for this you should be logged in to the command line only, use ctrl+alt+f1 to get new tty.

cd /tmp
rm -rf tde*
cd /var/tmp
sudo rm -rf tde*
cd ~/.trinity
rm -rf cache*
rm -rf socket*
rm -rf tmp*
cd ~
sudo chown -R your_username:your_groupname your_home_folder

as an example the last line in my case would be this

sudo chown -R dai:dai /home/dai

Then reboot and check that everything is working ok.
HTH

souperman · 2019-01-08 11:06

1. I ran those commands and everything is working ok. As for results, none of the commands returned anything, except one.

cd /tmp
rm -rf tde*

returned:

rm: cannot remove 'tde-root':Operation not permitted
rm: cannot remove 'tdesocket-global/tdm':Permission denied
rm: cannot remove 'tdesocket-root':Operation not permitted

How can I know if those commands did what they were supposed to? What should I be looking at?

2. Is this issue [service] could not be reached via DCOP going to resurface again? Or do I need to do this (run this set of commands) frequently?

Dai_trying · 2019-01-08 11:41

Are you logged in as root?

souperman · 2019-01-08 16:37

No. Should I?

Dai_trying · 2019-01-08 17:04

No I just would only expect those to exist if you were logged in to desktop as root. Just prefix sudo to the rm commands to remove them. ie

sudo rm -rf tde*

souperman · 2019-01-08 18:49

Done! Do I need to repeat this process after a certain interval?

Dai_trying · 2019-01-08 19:02

You shouldn't need to, I have 6 machines running Q4OS and have only needed to run this procedure once and that was quite some time ago, so it would depend if you are doing something that causes this to happen and if you find that is the case please report it here (or in a new thread) as it could be found to be a bug and any reports of the kind could help make the system even more stable than it is already.

souperman · 2019-01-09 04:28

Okay! Thank you for all the help!

Dai_trying · 2019-01-09 09:55

You are welcome

Q4OS Forum

#1 2019-01-06 06:47

[solved] 'service' could not be reached via DCOP.

#2 2019-01-06 10:30

Re: [solved] 'service' could not be reached via DCOP.

#3 2019-01-07 12:51

Re: [solved] 'service' could not be reached via DCOP.

#4 2019-01-07 14:08

Re: [solved] 'service' could not be reached via DCOP.

#5 2019-01-08 03:56

Re: [solved] 'service' could not be reached via DCOP.

#6 2019-01-08 08:06

Re: [solved] 'service' could not be reached via DCOP.

#7 2019-01-08 11:06

Re: [solved] 'service' could not be reached via DCOP.

#8 2019-01-08 11:41

Re: [solved] 'service' could not be reached via DCOP.

#9 2019-01-08 16:37

Re: [solved] 'service' could not be reached via DCOP.

#10 2019-01-08 17:04

Re: [solved] 'service' could not be reached via DCOP.

#11 2019-01-08 18:49

Re: [solved] 'service' could not be reached via DCOP.

#12 2019-01-08 19:02

Re: [solved] 'service' could not be reached via DCOP.

#13 2019-01-09 04:28

Re: [solved] 'service' could not be reached via DCOP.

#14 2019-01-09 09:55

Re: [solved] 'service' could not be reached via DCOP.

Board footer