This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Restoring System/ KIO Slave

Tags: None
(comma "," separated)
jmontmo
Registered Member
Posts
11
Karma
0
OS

Re: Restoring System/ KIO Slave

Thu Jul 09, 2009 4:05 pm
bcooksley wrote:The mount error message is likely related to the new user not being in the needed groups. Usually they need to be in a group such as "hotplug". You can check which groups your user is a member of with the "groups" command.

Try removing ~/.dcop* and ~/.DCOP* from your old user.


Adding the new user to the "plugdev" group took care of the new user's access to the storage media.

Guess by now you're thinking I'm 3 cans short of a six pack, but haven't a clue as to how to remove

~/.dcop* and ~/.DCOP* from the old user. Know how to remove a file or directory using the "rm" command in the CLI, Is this done in a similar manner

J
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Restoring System/ KIO Slave

Fri Jul 10, 2009 1:16 am
Yes it is, the "*" is just a wildcard to select all files beginning with that name.

Code: Select all
rm -r ~/.DCOP* & rm -r ~/.dcop*


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
jmontmo
Registered Member
Posts
11
Karma
0
OS

Re: Restoring System/ KIO Slave

Fri Jul 10, 2009 1:23 pm
bcooksley wrote:Yes it is, the "*" is just a wildcard to select all files beginning with that name.

Code: Select all
rm -r ~/.DCOP* & rm -r ~/.dcop*


It removed DCOP, but couldn't find dcop to remove.

Now if I try to launch a program from the Panel, it gives me the message :

"Klauncher could not be reached via DCOP"

J
jmontmo
Registered Member
Posts
11
Karma
0
OS

Re: Restoring System/ KIO Slave

Fri Jul 10, 2009 1:27 pm
In fact I can't do anything, switch windows, open a file, start the KMenu, zip, nada, nothing is working

J
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Restoring System/ KIO Slave

Fri Jul 10, 2009 2:21 pm
That command should have been done outside of a KDE session, since it will cause communication issues for an existing one. Logging out and back in should fix the problem.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar