LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 05-20-2004, 11:25 AM   #1
jasboy
LQ Newbie
 
Registered: May 2004
Posts: 24

Rep: Reputation: 15
Can only login as root


I'm not sure if this is the right place to post this, but I am new.

I'm running Fedora Core 1 with all updates (as of last week), with Linux Terminal Server Project installed and running great. I updated (from Gnome) to KDE 3.2 so I could use there Kiosk Admin Tool for the different users that will be logging in. The problem I am having now is I can only login as root in KDE. I cannot login as root or any other users in Gnome. If I try to login as any other user the screen goes blank and brings me right back to the login screen (i'm using a graphical login). I have deleted the users and created new ones, but it doesn't matter. I checked the ownership of the home directories and they are owned by the individual users. I checked var/log/messages and this is what I get:

May 20 11:09:53 server kdm_greet[3085]: Can't open default user face
May 20 11:11:58 server kde(pam_unix)[3079]: session opened for user randall by (uid=0)
May 20 11:12:00 server kde(pam_unix)[3079]: session closed for user randall
May 20 11:12:03 server kdm_greet[3159]: Can't open default user face
May 20 11:12:46 server kde(pam_unix)[3153]: session opened for user root by (uid=0)
May 20 11:12:50 server xinetd[3277]: warning: can't get client address: Transport endpoint is not connected
May 20 11:12:54 server kernel: Creative EMU10K1 PCI Audio Driver, version 0.20, 20:51:58 Apr 21 2004
May 20 11:12:54 server kernel: emu10k1: EMU10K1 rev 8 model 0x8064 found, IO at 0xd800-0xd81f, IRQ 3
May 20 11:12:54 server kernel: ac97_codec: AC97 Audio codec, id: 0x8384:0x7608 (SigmaTel STAC9708)
May 20 11:12:54 server kernel: emu10k1: SBLive! 5.1 card detected
May 20 11:12:54 server modprobe: modprobe: Can't locate module sound-service-0-0
May 20 11:12:54 server modprobe: modprobe: Can't locate module sound-slot-1
May 20 11:12:54 server modprobe: modprobe: Can't locate module sound-service-1-0
May 20 11:12:54 server modprobe: modprobe: Can't locate module sound-slot-1
May 20 11:12:54 server modprobe: modprobe: Can't locate module sound-service-1-0


Now, as far as sound goes, I don't need it. I might just pull it out.

What else do I need to check for? Or what could be the problem?

Thank you!
 
Old 05-20-2004, 11:57 AM   #2
masinick
Member
 
Registered: Apr 2002
Location: Clinton Township, MI
Distribution: Debian, antiX, Kubuntu, Xubuntu, and many others
Posts: 591
Blog Entries: 15

Rep: Reputation: 69
Device permission issue

It is difficult to determine all of the problems you're having; there may be more than one problem. It does, however, appear to be an issue with device files, possibly more than one of them. Make sure that your user account has write access to any of the files mentioned in the logs. For one thing, any devices relating to the sound card need to have write access by your user name. It seems that you're getting conflicts with other files as well. Start with the device directory, /dev and snoop around. Many files in that directory may well be owned by root and that's sometimes OK. But if you're trying to either read or write on a device in which you have no access, you may run into trouble.

If you have no idea how to proceed, write back.

chown -R <your-user-name>:<your-group-name> /<your-directory>

replacing the bracketed arguments with real user names, group names, and file or directory names, is a way to change file and/or directory ownership.

chmod +r file

is a way to make a file or directory readable.

chmod +w file is a way to make a file or a directory writable. (You can combine arguments, e.g., you can specify +rwx or -rwx to add or subtract read, write, or execute access. This convention changes access to the owner of the file, the group, and others. To change only a user, you'd say

chmod u+r file

and so on.

Does that help?
 
Old 05-20-2004, 12:24 PM   #3
jasboy
LQ Newbie
 
Registered: May 2004
Posts: 24

Original Poster
Rep: Reputation: 15
Well, I will give that a try. What if I change something that is supposed to be root? Will that mess anything up? Besides, I think I'm going to just pull that sound card out since it is not needed at all.

But I don't understand why upgrading to KDE 3.2 effected the login problem!?

Thaks for your reply!
 
  


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
unable to login as user; can login as root. rksanders Debian 24 02-09-2011 08:01 AM
wrong login shell prevent root login cefs99 Linux - Security 4 05-31-2006 08:28 AM
I have re-installed MK 9.2 but cannot login as user, login as root works. bobinglis Mandriva 2 02-22-2004 11:39 AM
can only login as root? user login doesnt work..? anyone? hacking_4_b33r Linux - General 1 02-05-2004 11:40 PM
root login incorrect ,then passwd root,but error sunnycn Linux - Security 6 05-20-2002 10:54 AM


All times are GMT -5. The time now is 07:38 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration