no I have an ups

As a note to those who use the command line to create users:

When using useradd to create users, use the -m (create home directory) option if you want that user to use the desktop, otherwise you will run into the "Could not start kstartupconfig" error being discussed here.

Another way to fix this problem is to create the home directory manually, chown it as mentioned above, then change the user to point to that home directory:

mkdir /home/foo
chmod user:users /home/foo
usermod -d /home/foo user

To make things easier, the home directory should be the user name, but you can make it anything you want this way.

I have a somewhat similar problem I think. After updating lots of stuff through the auto-update thingie in KDE I come to the command line whenever i start or reboot the computer. Being a complete newbie i tried typing: 'kde' <enter> and got these messages:


and then I'm back on the command line. So I tried these commands:

The first command (export..) worked (at least no error message).

The second command I just don't understand. Is username my username? and users? I tried with my username but got the error message: chown: missing operand after <<users/home/myusername>>

Then I just guessed and tried:

and that gave me no errormessage, but I still get to the command line, not KDE, after rebooting.

And lastly I couldn't find the -XO-lock file in the tmp directory. I looked in /tmp and no such file was there for me to delete as I could see.


Any ideas on how I can get this to work?

anatman:

It sounds like you might not be starting in the proper runlevel. To get the X server, you need to be at runlevel 5. When you start up to the command line, either log in as root or type in "su" if you're already logged in, enter the root password, then type in "runlevel", which will return your current runlevel (1-5)

1 is single user command line mode, with no other terminals available, 3 is multi-user command line mode, and 5 is full graphical mode. The X server and KDE are only available in 5.

If runlevel returns anything other than 5, type in "init 5" as root

After typing in init 5, you should either get the KDE login screen, or some error messages saying why it isn't coming up.

oh btw, chown = change ownership, with username being the username you want to own that file, in this case yours. users is the group your username most likely belongs to.

Thanks ZeromusM. I ran runlevel as root and it said N 5 so I guess that means I'm level 5? This time I got both the export and the chown command working, and my runlevel is 5, but I still can't start kde. So I want to find the .XO-lock file in the /tmp directory, to delete it. Where can I find this file? Anyone know? In the /tmp directory there were files like:

but no .XO file?

Yeah that means you're at runlevel 5. I don't think your problem is what is being talked about here, because when this happens, you will get the graphical login screen, then a popup at login. What you want to do is look for errors in /var/log/Xorg.0.log and dmesg (type "dmesg" to get the output). Also, I assume you typed in "kde" to try to get kde working again - what did the output of that say?

Cut and paste output always helps more than a description of the problem, so the exact wording of any messages you find would be appreciated.

Yes there were some errormessages both in the xorg logfile (no screens found) and kde, and dmesg, but how can I get the output of those files on a floppy so I can copy it on here? I'm using Kubuntu 5.10 live until I get it fixed...

anatman: Please refer to and reply to: Problem starting KDE - xorg no displays found

kstartconfig error
 

Hi Guys

chown -R navi:users /home/navi
this worked for me.

I created the home directory, as it was not created before and then executed this above command.
It worked.

-Navyanth

kstartupconfig error
 

Thanx for the thread. had similar fault, tried everyone suggestions. Realised having /home on FAT32 partition meant problems with write permissions.
So moved /home to a linux file system partition, with symlink to FAT32 partition.
Set FAT32 partition to automount in fstab.
That got rid of one error.

Then logged on as root, created 'users' with their 'home' directories in new /home, on a linux partition.

Moved any data files across to new 'user's' home directories.
got rid of old config files in old FAT32 partition.

Now to get other errors fixed.

Hi, my problem was: I used SMB login and Kerberos. So, the user I logged had the same name @ local as @ the domain, but the domain user could not write into /home/user/.kde
Normal, cause the domain user is considered as another user than the local user, even if it has the same name....

THE SOLUTION: go into user management (I use Suse10.2 so: yast2), configure Expert Options - Authentication and User Data Sources - Samba

As domain Membership click "yes" to "Create Home Directory on Logon"

That's it.

In response to above, about display not set, I would use startx. That seems to always work past this.

Still happening! March 15, 2008, ver 10.3
 

Hi guys. Here it is March 15, 2008, and it bit me too. OpenSUSE 10.3. No /home/dave. The chown fix worked for me too. BUT BUT.....

If somebody from OpenSUSE is looking in, isn't it time this got corrected? It's been going for almost 3 years now.

This is my first time to try OpenSUSE and its installation, anyway, is pretty impressive. The installation went well and offered me more control over partitioning and setup than any others I've experienced. It even let me set screen resolution at my favorite 2048x1536 during the install. But, even though it said it had set up my wireless, it hadn't ^_^. And this "Can't start kstartupconfig" thing.

In faith, Dave
Viva Texas

Linux: Welcome /home.

Could not start kstartupconfig. Check your installation
 

while creating the user account use the command as follows
" useradd -m <username>"
-m indicates it to create the home directory for the specified user.
After creating the account ,you should be able to login into the newly created account