LinuxQuestions.org - Mandrake 10.1 cannot load KDE from graphical LILO screen

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Mandrake 10.1 cannot load KDE from graphical LILO screen (https://www.linuxquestions.org/questions/linux-newbie-8/mandrake-10-1-cannot-load-kde-from-graphical-lilo-screen-410287/)

Mandrake 10.1 cannot load KDE from graphical LILO screen

I installed Mandrake 10.1 successfully on an external USB hardrive to work with my Dell Inspiron 1000 notebook, except for this problem--for some reason, whenever I try to log in as my user (instead of root), KDE 3.2 returns an error saying that it "could not read network connection list //.DCOPserver_localhost_0" and it tells me to check to see that dcopserver is running. KDE then returns another error saying that it has "no write access to $HOME directory (/)" before quickly displaying and grinding to a halt on its startup screen ("setting up interprocess communication"). How do I fix this?

Thank you

These are both likely caused by the same problem, that of permissions in your own home directory. Try this command as root:

Code:

chown <your_username> ~<your_username> -R && chmod u+w ~<your_username> -R

This will firstly make sure you own all the files and directories in your home, and secondly give you write access to them all. Note that there's no space between the '~' and the username, so it'd be something like "~bob" (this is a shortcut for "bob's home directory").

Also, there can be problems with certain KDE temporary files in certain situations, so logged in as your user:

Code:

$ cd ~

rm .ICEauthority*

$ rm .DCOPServer*

You may need to reboot after removing these files (or restart a specific service, though I don't know which one specifically and rebooting restarts them all :D)

Also, to be nitpicky, you can't load KDE from LILO. LILO is the LInux LOader, and starts the kernel running. What you're probably thinking of is the graphical Display Manager, e.g. xdm/kdm/gdm.

Didn't work :(

Here's my /etc/fstab file...

/dev/sda1 / ext3 noatime 0 0
none /home supermount dev=/dev/sda8,fs=ext2:vfat,--unmask=0,iochartset=iso8859-1,sync,codepage=850 0 0
/dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
/dev/hda2 /mnt/windows ntfs umask=0,nls=iso8859-1,ro 0 0
none /proc proc defaults 0 0
/dev/sda6 /usr ext3 noatime 0 0
/dev/sda7 /var ext3 noatime 0 0

I guess somehow the parition on which /home is kept wasn't properly formatted, even though it said that it was during installation *cringe*

Also bash tells me that "u+v" isn't a valid mode string

wait, never mind, it worked with "u+ -v"

Excellent, glad you got it sorted. I must admit, I've had the "invalid mode string" error a few times with modes of that kind, but my man page categorically says it's how to format it, so... :rolleyes: Thanks for finding a version that works without having to resort to the '755' style!