You are not logged in.

Create New grayed out in $HOME directory

nodakbarnes

Beginner

  • "nodakbarnes" started this thread

Posts: 2

  • Send private message

1

Sunday, October 23rd 2005, 4:25pm

Create New grayed out in $HOME directory

I just installed SuSE 10.0 on my laptop and everything initially worked great. Then I installed Star Office 8. I executed the install as root from my home directory (probably a big mistake). Anyhow, after Star Ofifce installed when I rebooted, KDE would not even start, saying that I did not have write permissions to my home directory (most likely a direct result of installing Star Office as root in that directory). I did a Ctrl-Alt-Backspace and logged into KDE as root. I then changed the permissions of my home directory back to what they should be. Now however, the Create New menu item that should be available when I right-click in Konqueror in my home directory is grayed out. If I open the File Manager in Super User Mode, it is available (obviously since I am root). If I open a terminal in my home directory I can make directories just like I should. Any ideas why Create New is not available in my home directory when logged in as user?

rgheck

Beginner

Posts: 9

  • Send private message

2

Tuesday, October 25th 2005, 8:46am

I'd check and make sure that ALL of the permissions have been reset correctly, including those on hidden files, and that ownership of any files has also not been changed from what it should be. You can start by running
#find ! -user YOURNAME
from your home directory.

nodakbarnes

Beginner

  • "nodakbarnes" started this thread

Posts: 2

  • Send private message

3

Tuesday, October 25th 2005, 5:03pm

Quoted

Originally posted by rgheck
I'd check and make sure that ALL of the permissions have been reset correctly, including those on hidden files, and that ownership of any files has also not been changed from what it should be. You can start by running
#find ! -user YOURNAME
from your home directory.


OK...I ran the command from my home directory and all the files belong to me as they should...any more ideas?
It must be a KDE problem because it is not evident in GNOME.

rgheck

Beginner

Posts: 9

  • Send private message

4

Tuesday, October 25th 2005, 5:44pm

Well, the other thing I'd try, then, is resetting the KDE configuration information, by deleting ~/.kde. That can work wonders. Of course, you probably don't want to lose all of that, so log out of KDE, open up a virtual terminal (Alt+Ctrl+1 or some such thing should do it), log in as yourself, and move that directory somewhere else, e.g.:
#mv ~/.kde ~/oldkde
Then go back to xdm or whatever (Alt+Ctrl+7, probably) and log back into KDE. If that doesn't fix the problem, you can go through the process again and move your old configuration back into place. If it does, you can copy over parts of the configuation (say, your amarok settings, from ~oldkde/share/config/amarokrc) that were unlikely to be causing problems.

The other thing you might do is check to make sure none of the KDE files themselves got corrupted somehow. You can use "rpm -V" to compare checksums on the installed files to those held in the rpm database.