LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices



Reply
 
Search this Thread
Old 01-14-2007, 02:14 PM   #1
dazpaul2222
LQ Newbie
 
Registered: Jan 2007
Posts: 4

Rep: Reputation: 0
Check yor dcop server is running error messae


Yesterday, my friend installed linux on my other computer. However, a mistake has been made and when i try to log in as both a user and root i gt an error message saying:

There was an error setting up intr-process communications for KDE. The message returned by the system was could no read network connections list /root/.dcoperver_Carters Cool Dude2_0

Please check that the dcopserver program is running


What should i do to sort outthe problem, i do ot know anything about linux.
Thanks
 
Old 01-14-2007, 02:20 PM   #2
dazpaul2222
LQ Newbie
 
Registered: Jan 2007
Posts: 4

Original Poster
Rep: Reputation: 0
i spoke to my frien breifly about the problem and he thinks it maybe because on setup, when was asked for a domain name, i did not delete what was originlly in the box
 
Old 01-14-2007, 04:38 PM   #3
jonnycando
Member
 
Registered: Nov 2006
Location: Virginia
Distribution: OpenSuSE 10.2
Posts: 121

Rep: Reputation: 15
Quote:
Originally Posted by dazpaul2222
i spoke to my frien breifly about the problem and he thinks it maybe because on setup, when was asked for a domain name, i did not delete what was originlly in the box
What was already there may or may not make a difference. However if you think it is a setup problem, you can reinstall your Linux. (Since it is already freshly installed, and you might not yet have many of personal files there.) I occasionally had my system (SLED 10.1) loose track of dcopserver, and then certain programs needing it wouldn't load. If I tried to reload it of course, I would get a message saying it was already loaded. If I killed the one that was running first then I could rerun it, but rebooting was the only sure thing. I recently installed OpenSuse 10.2 and have had no such trouble. I think whether you reinstall or not, you should see that you update KDE to at least version 3.5.5
 
Old 01-14-2007, 04:43 PM   #4
dazpaul2222
LQ Newbie
 
Registered: Jan 2007
Posts: 4

Original Poster
Rep: Reputation: 0
you should see that you update KDE to at least version 3.5.5[/QUOTE]

thank u very much. But how do i update it. I am not able to log in under any user including root
 
Old 01-14-2007, 10:50 PM   #5
jonnycando
Member
 
Registered: Nov 2006
Location: Virginia
Distribution: OpenSuSE 10.2
Posts: 121

Rep: Reputation: 15
Quote:
Originally Posted by dazpaul2222
you should see that you update KDE to at least version 3.5.5
thank u very much. But how do i update it. I am not able to log in under any user including root[/QUOTE]


Well, then, you would update KDE after you reinstall Linux. That is, if you find that the version that is installed is lower than 3.5.5.

Last edited by jonnycando; 01-14-2007 at 10:55 PM.
 
Old 01-15-2007, 06:19 AM   #6
dazpaul2222
LQ Newbie
 
Registered: Jan 2007
Posts: 4

Original Poster
Rep: Reputation: 0
Thankyou but how do i sort out the initial problem because at the moment i am not able to log in?
 
Old 01-16-2007, 06:26 PM   #7
jonnycando
Member
 
Registered: Nov 2006
Location: Virginia
Distribution: OpenSuSE 10.2
Posts: 121

Rep: Reputation: 15
Quote:
Originally Posted by dazpaul2222
Thankyou but how do i sort out the initial problem because at the moment i am not able to log in?
From this website.... But you don't need to log in to do a clean reinstall. Try these tips only if you want to preserve and try to repair your present system. The root username is of course "root" and then the password is whatever you selected and hopefully can remember or find this way.

http://aplawrence.com/Linux/lostlinuxpassword.html
If you've lost your root password, you might be able to recover it this way. However, some systems are protected with boot loader passwords that won't let you do that without THAT password. If the boot loader is password protected, you need to boot from other media - for newer systems, the install CD probably has the recovery tools for that ("linux rescue" for example).

But let's try it the easy way first. The first thing to try is to boot to single user mode. This MIGHT not work for you, because your system might be configured to still ask for a root password to get to single user mode. If that's the case, we'll use another trick that replaces init with /bin/bash.

First, try single user. If you don't see either a LILO or GRUB boot screen, try hitting CTRL-X to get one. If it's LILO, just type "linux single" and that should do it (assuming that "linux" is the lilo label). If GRUB, hit 'e", then select the "kernel" line, hit "e" again, and add " single" (or just " 1") to the end of the line. Press ENTER, and then "b" to boot. (More modern grub uses "a" to append to the boot line)
You should get a fairly normal looking boot sequence except that it terminates a little early at a bash prompt. If you get a "Give root password for system maintenance", this isn't going to work, so see the "init" version below.

If you do get the prompt, the / filesystem may not be mounted rw (although "mount" may say it is). Do


mount -o remount,rw /

If that doesn't work (it might not), just type "mount" to find out where "/" is mounted. Let's say it is on /dev/sda2. You'd then type:

mount -o remount,rw /dev/sda2

If you can do this, just type "passwd" once you are in and change it to whatever you like. Or just edit /etc/shadow to remove the password field: move to just beyond the first ":" and remove everything up to the next ":". With vi, that would be "/:" to move to the first ":", space bar once, then "d/:" and ENTER. You'll get a warning about changing a read-only file; that's normal. Before you do this, /etc/shadow might look like:

root:$1$8NFmV6tr$rT.INHxDBWn1VvU5gjGzi/:12209:0:99999:7:-1:-1:1074970543
bin:*:12187:0:99999:7:::
daemon:*:12187:0:99999:7:::
adm:*:12187:0:99999:7:::

and after, the first few lines should be:

root::12209:0:99999:7:-1:-1:1074970543
bin:*:12187:0:99999:7:::
daemon:*:12187:0:99999:7:::
adm:*:12187:0:99999:7:::

You'll need to force the write: with vi, ":wq!". (If that still doesn't work, you needed to do the -o remount,rw, see above).

Another trick is to add "init=/bin/bash" (LILO "linux init=/bin/bash" or add it to the Grub "kernel" line). This will dump you to a bash prompt much earlier than single user mode, and a lot less has been initialized, mounted, etc. You'll definitely need the "-o remount,rw" here. Also note that other filesystems aren't mounted at all, so you may need to mount them manually if you need them. Look in /etc/fstab for the device names.

Keep this in mind if you have a Linux machine in a publically accessible place : without more protection, it's not usually hard to recover a lost root password, which means it's just as easy for someone to CHANGE it, or access root without your knowlege.

Another way to do this is to remove the password from /etc/shadow. Just in case you screw up, I'd copy it somewhere safe first. You want to end up with the root line looking something like this:

# original line
root:$1$EYBTVZHP$QtjkCG768giXzPvW4HqB5/:12832:0:99999:7:::
# after editing
root::12832:0:99999:7:::

If you are having trouble with editing (you really do have to learn vi one of these days), you could just (after making a copy, of course) just

echo "root::12832:0:::::" > /mnt/etc/shadow
or, if you were in single user mode
echo "root::12832:0:::::" > /etc/shadow

and then fix things up when rebooted.

If using something like "linux rescue" or other boot media, if the recovery disk doesn't automatically mount your disk, you need to do it manually. This shouldn't be difficult unless you have an unusual disk controller. For example, a Compaq raid controller will probably be /dev/ida/c0d0. Find the partitions by using fdisk /dev/ida/c0d0 (just "p" and quit) and then mount what you need.

If all else fails, consider that you can pull this drive (or install another drive in this machine) and mount it from another running Linux. Then recover the root password as explained above.

See also
http://aplawrence.com/Bofcusm/861.html
http://aplawrence.com/Bofcusm/872.html
http://aplawrence.com/Bofcusm/873.html
-FeedBurner RSS Feed- -Digg This- -Add to del.icio.us-
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Menudrake - Error could not attach to DCOP Server apjonesy Mandriva 0 08-16-2004 02:15 PM
it gives fetal error messae thatyour media and hardware problem harisrahim Linux - General 3 06-16-2004 04:32 AM
couldn't attach to dcop server error in kde 3.1 acidkick Linux - Software 0 06-09-2004 06:57 PM
dcop server not running versaulis Linux - Software 1 11-22-2003 10:23 PM
dcop server error with vncviwer kjsubbu Linux - Software 0 09-19-2003 01:59 AM


All times are GMT -5. The time now is 08:17 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration