Urgent advise needed. Only guest profile accesible, my own profile not. (OT)

[Alan Dacey (grokit)]

This reply should be used as an example of the absolutely best and correct way of answering an ongoing question on a help channel.  

Excellent work Little Girl. [bows to your superior help skills]

--
Alan 


On Monday, September 30, 2013 7:13:16 PM Little Girl wrote:
> Hey there,
> 
> Bas Roufs wrote:
> 
> > Hello Everybody, this evening, I have consulted the advises in
> > thread and at 'Ask Ubuntu'. This is the page I have consulted from
> > 'Ask Ubuntu':
> > http://askubuntu.com/questions/175739/how-do-i-remount-a-filesystem-as-read-write
> > By doing so, I DID manage to remount the file system and to rename
> > the .kde directory in /home/bas. Then, I have rebooted the system.
> > Afterwords, I tried to login again into /home/bas in the 'normal'
> > way. However, I still have exactly the same problem. After logging
> > in, I come back at the same point where I got stuck yesterday. At a
> > certain moment, the cursor is unmovable and the system is totally
> > stuck.
> 
> What is that moment? What is happening right before that? Is there a
> system notification or is there a program you are launching that
> causes it, or does it just happen if you wait a certain amount of
> time after booting the computer? If it just happens after a certain
> amount of time, does it always happen in the same amount of time?
> 
> > So, I am still stuck. What to do next?
> 
> You've now gotten advice from several people/sources, so it's
> possible a step was overlooked or done differently than intended.
> Please don't be offended at the repeat of the instructions, but I'm
> pasting step by step instructions the way I would write them for
> myself if I had to do what you're doing. That way you can go through
> them and double-check whether you missed any or did something
> differently. Also, this gives anyone else who is reading along a
> chance to look them over and correct any that are wrong:
> 
> ====================
> 
> 1) Press and hold the Shift key during boot-up right after your BIOS message is displayed to get the GRUB menu to open.
> 
> 2) Use the arrow keys to select your kernel’s recovery mode.
> 
> The Recovery Menu will open.
> 
> 3) Use your arrow keys to highlight the line that says:
> 
> root	drop to root shell prompt
> 
> 4) Press the Enter key to get to a root shell prompt.
> 
> 5) Type this command to initialize your home directory:
> 
> cd
> 
> 6) Press the Enter key.
> 
> 7) Type this command to go to your home directory, replacing username with your user name:
> 
> 8) cd /home/username
> 
> 9) Press the Enter key.
> 
> 10) Type this command to give yourself read/write access:
> 
> mount -o remount,rw /
> 
> 11) Press the Enter key.
> 
> 12) Type this command to rename the hidden .kde directory to .kde.old:
> 
> mv ~/.kde ~/.kde.old
> 
> 13) Press the Enter key.
> 
> 14) Type this command to leave recovery mode:
> 
>     exit
> 
> 15) Press the Enter key.
> 
> 16) Choose resume from the Recovery Menu.
> 
> 17) Press the Enter key while the OK button is highlighted.
> 
> 18) Log in to your operating system normally.
> 
> ====================
> 
> If you decide to try going through the steps again and you see any
> odd behavior or get any messages from the system when following any
> of the steps, please make a note of them or copy and paste them in
> here.
> 
> ====================
> 
> Last, but not least, if you have time before the system freezes, you
> can open the KSystemLog application (in the System menu) and look
> through your logs to see if there are any clues to what's causing
> this.
> 
> You mentioned that you can log in as a guest user without any
> problems. I'm not sure if you can access the same logs from a guest
> account. Maybe someone who knows could jump in and let us know how
> that's done. (:
> 
>